From 03c59a711dc45034854b28d742b8d7223417e24b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:53:50 -0800
Subject: [PATCH 001/236] ado-whidbey-long

---
 xml/System.Data/DataRowExtensions.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Data/DataRowExtensions.xml b/xml/System.Data/DataRowExtensions.xml
index 160843f516e..e917279b36f 100644
--- a/xml/System.Data/DataRowExtensions.xml
+++ b/xml/System.Data/DataRowExtensions.xml
@@ -455,7 +455,7 @@
 ## Remarks  
  If `value` is **null**, the <xref:System.Data.DataRowExtensions.SetField%2A> method converts the **null** value to <xref:System.DBNull.Value> in the underlying <xref:System.Data.DataColumn>.  
   
- The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the [!INCLUDE[ado_whidbey_long](~/includes/ado-whidbey-long-md.md)] behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
+ The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the ADO.NET 2.0 behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
   
  Exceptions can be passed up through the <xref:System.Data.DataRowExtensions.SetField%2A> method from the underlying <xref:System.Data.DataRow> object.  
   
@@ -514,7 +514,7 @@
 ## Remarks  
  If `value` is **null**, the <xref:System.Data.DataRowExtensions.SetField%2A> method converts the **null** value to <xref:System.DBNull.Value> in the underlying <xref:System.Data.DataColumn>.  
   
- The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the [!INCLUDE[ado_whidbey_long](~/includes/ado-whidbey-long-md.md)] behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
+ The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the ADO.NET 2.0 behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
   
  Exceptions can be passed up through the <xref:System.Data.DataRowExtensions.SetField%2A> method from the underlying <xref:System.Data.DataRow> object.  
   
@@ -572,7 +572,7 @@
 ## Remarks  
  If `value` is **null**, the <xref:System.Data.DataRowExtensions.SetField%2A> method converts the **null** value to <xref:System.DBNull.Value> in the underlying <xref:System.Data.DataColumn>.  
   
- The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the [!INCLUDE[ado_whidbey_long](~/includes/ado-whidbey-long-md.md)] behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
+ The <xref:System.Data.DataRowExtensions.SetField%2A> method does not perform any type conversions. This does not mean, however, that a type conversion will not occur. The <xref:System.Data.DataRowExtensions.SetField%2A> method exposes the ADO.NET 2.0 behavior of the <xref:System.Data.DataRow> class. A type conversion could be performed by the <xref:System.Data.DataRow> object and the converted value would then be saved to the row.  
   
  Exceptions can be passed up through the <xref:System.Data.DataRowExtensions.SetField%2A> method from the underlying <xref:System.Data.DataRow> object.  
   

From b25d08a90229b80cc4362adf3315fb7cac9f3f0a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:55:18 -0800
Subject: [PATCH 002/236] adonet-edm

---
 xml/System.Data.Common.CommandTrees/DbConstantExpression.xml    | 2 +-
 .../IEntityWithRelationships.xml                                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Data.Common.CommandTrees/DbConstantExpression.xml b/xml/System.Data.Common.CommandTrees/DbConstantExpression.xml
index 03dd46158a4..1f834f92011 100644
--- a/xml/System.Data.Common.CommandTrees/DbConstantExpression.xml
+++ b/xml/System.Data.Common.CommandTrees/DbConstantExpression.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Constant expressions are only supported for the following [!INCLUDE[adonet_edm](~/includes/adonet-edm-md.md)] types: `Edm.String`, `Edm.Boolean`, `Edm.Byte`, `Edm.Float`, `Edm.Double`, `Edm.Decimal`, `Edm.DateTime`, `Edm.Guid`, `Edm.Binary`. For more information, see [Conceptual Model Types (CSDL)](/previous-versions/dotnet/netframework-4.0/bb399548(v=vs.100)).  
+ Constant expressions are only supported for the following Entity Data Model types: `Edm.String`, `Edm.Boolean`, `Edm.Byte`, `Edm.Float`, `Edm.Double`, `Edm.Decimal`, `Edm.DateTime`, `Edm.Guid`, `Edm.Binary`. For more information, see [Conceptual Model Types (CSDL)](/previous-versions/dotnet/netframework-4.0/bb399548(v=vs.100)).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Objects.DataClasses/IEntityWithRelationships.xml b/xml/System.Data.Objects.DataClasses/IEntityWithRelationships.xml
index dbd42dc6074..6b9280b6ddd 100644
--- a/xml/System.Data.Objects.DataClasses/IEntityWithRelationships.xml
+++ b/xml/System.Data.Objects.DataClasses/IEntityWithRelationships.xml
@@ -17,7 +17,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Data.Objects.DataClasses.IEntityWithRelationships> defines the features that must be implemented by an entity type that has relationships to other types. Relationships are defined as associations in the [!INCLUDE[adonet_edm](~/includes/adonet-edm-md.md)].  
+ <xref:System.Data.Objects.DataClasses.IEntityWithRelationships> defines the features that must be implemented by an entity type that has relationships to other types. Relationships are defined as associations in the Entity Data Model.  
   
  <xref:System.Data.Objects.DataClasses.EntityObject> is the base class for all entity types generated by the Entity Data Model tools. The <xref:System.Data.Objects.DataClasses.EntityObject> class implements <xref:System.Data.Objects.DataClasses.IEntityWithRelationships>.  
   

From dff7b873c97f5d7ec15583afd720858b53be083a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:56:28 -0800
Subject: [PATCH 003/236] adonet-ef

---
 xml/System.Data.Metadata.Edm/DataSpace.xml         |  2 +-
 xml/System.Data.Objects/MergeOption.xml            |  2 +-
 xml/System.Data/EntityKey.xml                      |  4 ++--
 xml/System.Web.UI.WebControls/EntityDataSource.xml | 10 +++++-----
 xml/ns-System.Data.EntityClient.xml                |  2 +-
 5 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/xml/System.Data.Metadata.Edm/DataSpace.xml b/xml/System.Data.Metadata.Edm/DataSpace.xml
index c0654f5587f..bb043bb88b5 100644
--- a/xml/System.Data.Metadata.Edm/DataSpace.xml
+++ b/xml/System.Data.Metadata.Edm/DataSpace.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the models in the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)], see [Metadata Workspace Overview](https://docs.microsoft.com/previous-versions/bb399600(v=vs.90)).  
+ For more information about the models in the Entity Framework, see [Metadata Workspace Overview](https://docs.microsoft.com/previous-versions/bb399600(v=vs.90)).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Objects/MergeOption.xml b/xml/System.Data.Objects/MergeOption.xml
index 3b0d2becf0f..7216a98f2a6 100644
--- a/xml/System.Data.Objects/MergeOption.xml
+++ b/xml/System.Data.Objects/MergeOption.xml
@@ -78,7 +78,7 @@
       </ReturnValue>
       <MemberValue>3</MemberValue>
       <Docs>
-        <summary>Objects are maintained in a <see cref="F:System.Data.EntityState.Detached" /> state and are not tracked in the <see cref="T:System.Data.Objects.ObjectStateManager" />. However, [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)]-generated entities and POCO entities with proxies maintain a reference to the object context to facilitate loading of related objects.</summary>
+        <summary>Objects are maintained in a <see cref="F:System.Data.EntityState.Detached" /> state and are not tracked in the <see cref="T:System.Data.Objects.ObjectStateManager" />. However, Entity Framework-generated entities and POCO entities with proxies maintain a reference to the object context to facilitate loading of related objects.</summary>
       </Docs>
     </Member>
     <Member MemberName="OverwriteChanges">
diff --git a/xml/System.Data/EntityKey.xml b/xml/System.Data/EntityKey.xml
index 0718aa6d87b..ff65b5c885a 100644
--- a/xml/System.Data/EntityKey.xml
+++ b/xml/System.Data/EntityKey.xml
@@ -482,7 +482,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- When a new entity is created, the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)] defines temporary key and sets the <xref:System.Data.EntityKey.IsTemporary%2A> property to `true`. When you call the <xref:System.Data.Objects.ObjectContext.SaveChanges%2A> method, the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)] assigns a permanent key and sets the <xref:System.Data.EntityKey.IsTemporary%2A> property to `false`.
+ When a new entity is created, the Entity Framework defines temporary key and sets the <xref:System.Data.EntityKey.IsTemporary%2A> property to `true`. When you call the <xref:System.Data.Objects.ObjectContext.SaveChanges%2A> method, the Entity Framework assigns a permanent key and sets the <xref:System.Data.EntityKey.IsTemporary%2A> property to `false`.
 
 > [!NOTE]
 >  Temporary keys are constructed automatically by the framework; they cannot be constructed directly by a user.
@@ -495,7 +495,7 @@
 
  In addition, temporary keys have no <xref:System.Data.Metadata.Edm.EntitySet> or key values, but permanent keys do.
 
- When the <xref:System.Data.Objects.ObjectStateEntry.AcceptChanges%2A> method is called on an entity's <xref:System.Data.Objects.ObjectStateEntry> and the entity transitions from the <xref:System.Data.EntityState.Added> state to <xref:System.Data.EntityState.Unchanged> state, the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)] automatically computes a new permanent key for the entity and synchronizes all temporary key references.
+ When the <xref:System.Data.Objects.ObjectStateEntry.AcceptChanges%2A> method is called on an entity's <xref:System.Data.Objects.ObjectStateEntry> and the entity transitions from the <xref:System.Data.EntityState.Added> state to <xref:System.Data.EntityState.Unchanged> state, the Entity Framework automatically computes a new permanent key for the entity and synchronizes all temporary key references.
 
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls/EntityDataSource.xml b/xml/System.Web.UI.WebControls/EntityDataSource.xml
index 1107774a25e..cb1a5a8372e 100644
--- a/xml/System.Web.UI.WebControls/EntityDataSource.xml
+++ b/xml/System.Web.UI.WebControls/EntityDataSource.xml
@@ -1485,7 +1485,7 @@ protected void EntityDataSource2_ContextDisposing(object sender,
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.UI.WebControls.EntityDataSource.Include%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control specifies a comma-separated list of query paths that define the objects that are returned together with the specifically queried object. Each comma-separated value in the string is passed, without modification, as a separate call to the <xref:System.Data.Objects.ObjectQuery%601.Include%2A> method of an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)]. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The <xref:System.Web.UI.WebControls.EntityDataSource.Include%2A> property is the argument applied to the <xref:System.Data.Objects.ObjectQuery%601> before it is executed.
+ The <xref:System.Web.UI.WebControls.EntityDataSource.Include%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control specifies a comma-separated list of query paths that define the objects that are returned together with the specifically queried object. Each comma-separated value in the string is passed, without modification, as a separate call to the <xref:System.Data.Objects.ObjectQuery%601.Include%2A> method of an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the Entity Framework. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The <xref:System.Web.UI.WebControls.EntityDataSource.Include%2A> property is the argument applied to the <xref:System.Data.Objects.ObjectQuery%601> before it is executed.
 
  The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.Include%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.Include%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use query paths to automatically load related objects, see [How to: Use Query Paths to Shape Results](https://msdn.microsoft.com/library/100bf7f5-00ba-4c17-8e27-7a8a14831093).
 
@@ -1754,7 +1754,7 @@ ObjectQuery<Contact> customers =
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.UI.WebControls.EntityDataSource.OrderBy%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control is a string that represents an [ORDER BY](/dotnet/framework/data/adonet/ef/language-reference/order-by-entity-sql) expression of an Entity SQL query. This string is passed, without modification, to an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)]. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.OrderBy%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.OrderBy%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [ORDER BY](/dotnet/framework/data/adonet/ef/language-reference/order-by-entity-sql) clause to order query results, see [How to: Sort Data](https://msdn.microsoft.com/library/c05f2506-cb9d-4ebc-822b-300042ad53e7).
+ The <xref:System.Web.UI.WebControls.EntityDataSource.OrderBy%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control is a string that represents an [ORDER BY](/dotnet/framework/data/adonet/ef/language-reference/order-by-entity-sql) expression of an Entity SQL query. This string is passed, without modification, to an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the Entity Framework. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.OrderBy%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.OrderBy%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [ORDER BY](/dotnet/framework/data/adonet/ef/language-reference/order-by-entity-sql) clause to order query results, see [How to: Sort Data](https://msdn.microsoft.com/library/c05f2506-cb9d-4ebc-822b-300042ad53e7).
 
 
 
@@ -1947,7 +1947,7 @@ ObjectQuery<SalesOrderHeader> onlineOrders =
 ## Remarks
  The <xref:System.Web.UI.WebControls.EntityDataSource.Select%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control contains a string that represents the [SELECT](/dotnet/framework/data/adonet/ef/language-reference/select-entity-sql) statement of an Entity SQL query. This enables you to project a specified set of properties from the objects returned by the query.
 
- This string is passed, without modification, to the <xref:System.Data.Objects.ObjectQuery%601> that is executed by the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)]. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.Select%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.Select%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [SELECT](/dotnet/framework/data/adonet/ef/language-reference/select-entity-sql) clause to define a projection for a query, see [How to: Execute a Query that Returns Anonymous Type Objects](https://msdn.microsoft.com/library/3b264025-e911-4d73-90ce-992d2b9d189d).
+ This string is passed, without modification, to the <xref:System.Data.Objects.ObjectQuery%601> that is executed by the Entity Framework. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.Select%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.Select%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [SELECT](/dotnet/framework/data/adonet/ef/language-reference/select-entity-sql) clause to define a projection for a query, see [How to: Execute a Query that Returns Anonymous Type Objects](https://msdn.microsoft.com/library/3b264025-e911-4d73-90ce-992d2b9d189d).
 
  Updates are not supported for projected data. This means that when you use the <xref:System.Web.UI.WebControls.EntityDataSource.Select%2A> property to specify a projection, the bound data binding does not support updates.
 
@@ -2155,7 +2155,7 @@ ObjectQuery<Product> products = context.Product
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- To track changes when update and delete operations are enabled, the <xref:System.Web.UI.WebControls.EntityDataSource> control must store information about original values of loaded objects in the <xref:System.Web.UI.PageStatePersister.ControlState%2A>. Storing this required information in the view state will increase the page size. You can disable storing original values in the view state by setting the <xref:System.Web.UI.WebControls.EntityDataSource.StoreOriginalValuesInViewState%2A> property to `false`. If you do this, the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)] cannot track concurrency in updated objects. For more information, see [Updating Data (EntityDataSource)](https://msdn.microsoft.com/library/ca153eec-6817-4c1d-b262-efd6d35b0246).
+ To track changes when update and delete operations are enabled, the <xref:System.Web.UI.WebControls.EntityDataSource> control must store information about original values of loaded objects in the <xref:System.Web.UI.PageStatePersister.ControlState%2A>. Storing this required information in the view state will increase the page size. You can disable storing original values in the view state by setting the <xref:System.Web.UI.WebControls.EntityDataSource.StoreOriginalValuesInViewState%2A> property to `false`. If you do this, the Entity Framework cannot track concurrency in updated objects. For more information, see [Updating Data (EntityDataSource)](https://msdn.microsoft.com/library/ca153eec-6817-4c1d-b262-efd6d35b0246).
 
  ]]></format>
         </remarks>
@@ -2410,7 +2410,7 @@ ObjectQuery<Product> products = context.Product
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.UI.WebControls.EntityDataSource.Where%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control is a string that represents a [WHERE](/dotnet/framework/data/adonet/ef/language-reference/where-entity-sql) clause that is the predicate of an Entity SQL query. This string is passed, without modification, to an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)]. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.Where%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.Where%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [WHERE](/dotnet/framework/data/adonet/ef/language-reference/where-entity-sql) clause to filter a query, see [How to: Filter Data](https://msdn.microsoft.com/library/776f8556-3350-4572-804a-b1513515c1b2).
+ The <xref:System.Web.UI.WebControls.EntityDataSource.Where%2A> property of the <xref:System.Web.UI.WebControls.EntityDataSource> control is a string that represents a [WHERE](/dotnet/framework/data/adonet/ef/language-reference/where-entity-sql) clause that is the predicate of an Entity SQL query. This string is passed, without modification, to an <xref:System.Data.Objects.ObjectQuery%601> that is executed by the Entity Framework. This query is the source of the data regulated by the <xref:System.Web.UI.WebControls.EntityDataSource> control. The string supplied to the <xref:System.Web.UI.WebControls.EntityDataSource.Where%2A> property uses the same format as the string that is passed to the <xref:System.Data.Objects.ObjectQuery%601.Where%2A> method of <xref:System.Data.Objects.ObjectQuery%601>. For examples of how to use the [WHERE](/dotnet/framework/data/adonet/ef/language-reference/where-entity-sql) clause to filter a query, see [How to: Filter Data](https://msdn.microsoft.com/library/776f8556-3350-4572-804a-b1513515c1b2).
 
  To filter query results by equating an entity type property to an expression, see information about the <xref:System.Web.UI.WebControls.EntityDataSource.AutoGenerateWhereClause%2A> property.
 
diff --git a/xml/ns-System.Data.EntityClient.xml b/xml/ns-System.Data.EntityClient.xml
index 993f799e3d8..555e908aa71 100644
--- a/xml/ns-System.Data.EntityClient.xml
+++ b/xml/ns-System.Data.EntityClient.xml
@@ -8,7 +8,7 @@
  The `EntityClient` provider uses storage-specific [!INCLUDE[vstecado](~/includes/vstecado-md.md)] Data Provider classes and mapping metadata for interacting with entity data models. `EntityClient` translates operations performed on conceptual entities into operations performed on physical data sources. It translates result sets returned from physical data sources into conceptual entities.
 
 > [!NOTE]
->  For more information about how to use this namespace in [!INCLUDE[adonet_ef](~/includes/adonet-ef-md.md)] applications, see [ADO.NET Entity Framework](/dotnet/framework/data/adonet/ef/).
+>  For more information about how to use this namespace in Entity Framework applications, see [ADO.NET Entity Framework](/dotnet/framework/data/adonet/ef/).
 
  ]]></format>
     </remarks>

From 374763d9300eba2f69057415e0aa125dfa75ca5a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:57:02 -0800
Subject: [PATCH 004/236] ajax-current-short

---
 xml/System.Web.ClientServices/ConnectivityStatus.xml | 2 +-
 xml/ns-System.Web.ClientServices.Providers.xml       | 2 +-
 xml/ns-System.Web.ClientServices.xml                 | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Web.ClientServices/ConnectivityStatus.xml b/xml/System.Web.ClientServices/ConnectivityStatus.xml
index 3067dcc2c9a..2dedec8b587 100644
--- a/xml/System.Web.ClientServices/ConnectivityStatus.xml
+++ b/xml/System.Web.ClientServices/ConnectivityStatus.xml
@@ -60,7 +60,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you set the <xref:System.Web.ClientServices.ConnectivityStatus.IsOffline%2A> property, the <xref:System.Web.ClientServices.ConnectivityStatus> class caches the value to the local file system. The client service providers in the <xref:System.Web.ClientServices.Providers> namespace check this value to determine whether to use the offline data cache instead of attempting to access the associated [!INCLUDE[ajax_current_short](~/includes/ajax-current-short-md.md)] authentication, roles, and profile services.  
+ When you set the <xref:System.Web.ClientServices.ConnectivityStatus.IsOffline%2A> property, the <xref:System.Web.ClientServices.ConnectivityStatus> class caches the value to the local file system. The client service providers in the <xref:System.Web.ClientServices.Providers> namespace check this value to determine whether to use the offline data cache instead of attempting to access the associated Microsoft Ajax authentication, roles, and profile services.  
   
    
   
diff --git a/xml/ns-System.Web.ClientServices.Providers.xml b/xml/ns-System.Web.ClientServices.Providers.xml
index 6d60fd53432..e2e453e5dc7 100644
--- a/xml/ns-System.Web.ClientServices.Providers.xml
+++ b/xml/ns-System.Web.ClientServices.Providers.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The classes in the <xref:System.Web.ClientServices.Providers> namespace include client application service providers that enable Windows-based applications to use the [!INCLUDE[ajax_current_short](~/includes/ajax-current-short-md.md)] authentication, roles, and profile services. You can enable these services and specify client service providers in your application configuration file, and then access the services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
+ The classes in the <xref:System.Web.ClientServices.Providers> namespace include client application service providers that enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profile services. You can enable these services and specify client service providers in your application configuration file, and then access the services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
 
  To access the login service, you can use either Windows or Forms authentication by specifying the <xref:System.Web.ClientServices.Providers.ClientWindowsAuthenticationMembershipProvider> or <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> in your application configuration. Windows authentication uses the identity supplied when a user logs in to the operating system. Forms authentication requires that you to retrieve login information from the user and pass it to the service. You can do this by specifying an <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider> implementation with your <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> configuration. The <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider.GetCredentials%2A?displayProperty=nameWithType> method returns a <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationCredentials> object that contains user login information. You can populate this object, for example, by displaying a login dialog box in the <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider.GetCredentials%2A> method.
 
diff --git a/xml/ns-System.Web.ClientServices.xml b/xml/ns-System.Web.ClientServices.xml
index 1c19c832ef7..56f38703b7c 100644
--- a/xml/ns-System.Web.ClientServices.xml
+++ b/xml/ns-System.Web.ClientServices.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The classes in the <xref:System.Web.ClientServices> namespace support the client application service providers in the <xref:System.Web.ClientServices.Providers> namespace. These service providers enable Windows-based applications to use the [!INCLUDE[ajax_current_short](~/includes/ajax-current-short-md.md)] authentication, roles, and profiles services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
+ The classes in the <xref:System.Web.ClientServices> namespace support the client application service providers in the <xref:System.Web.ClientServices.Providers> namespace. These service providers enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profiles services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
 
  The <xref:System.Web.ClientServices.ClientFormsIdentity> and <xref:System.Web.ClientServices.ClientRolePrincipal> classes provide properties and methods related to a user's identity, role, and authentication state.
 

From f9955a63025bcf755b4ba5bfe68c2a50d0380ab4 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:57:32 -0800
Subject: [PATCH 005/236] compact

---
 xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml | 4 ++--
 xml/Microsoft.Build.Tasks/Vbc.xml                    | 4 ++--
 xml/System.Globalization/CultureInfo.xml             | 2 +-
 xml/System/NotSupportedException.xml                 | 6 +++---
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml b/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
index a673b1d0cdb..87f7ffa07be 100644
--- a/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
+++ b/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
@@ -1565,8 +1565,8 @@
       </Parameters>
       <Docs>
         <param name="targetCompactFramework">
-          <see langword="true" /> to target the [!INCLUDE[Compact](~/includes/compact-md.md)]; otherwise, <see langword="false" />.</param>
-        <summary>Specifies a value indicating whether to target the [!INCLUDE[Compact](~/includes/compact-md.md)].</summary>
+          <see langword="true" /> to target the .NET Compact Framework; otherwise, <see langword="false" />.</param>
+        <summary>Specifies a value indicating whether to target the .NET Compact Framework.</summary>
         <returns>
           <see langword="true" /> if the method was successful; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/Microsoft.Build.Tasks/Vbc.xml b/xml/Microsoft.Build.Tasks/Vbc.xml
index 5162851eefa..c51d940f0d4 100644
--- a/xml/Microsoft.Build.Tasks/Vbc.xml
+++ b/xml/Microsoft.Build.Tasks/Vbc.xml
@@ -951,9 +951,9 @@ This property can have a value of **x86**, **x64**, **Itanium**, or **anycpu**.
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a Boolean value that specifies whether to target the [!INCLUDE[Compact](~/includes/compact-md.md)].</summary>
+        <summary>Gets or sets a Boolean value that specifies whether to target the .NET Compact Framework.</summary>
         <value>
-          <see langword="true" /> if the <c>Vbc</c> task should target the [!INCLUDE[Compact](~/includes/compact-md.md)]; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the <c>Vbc</c> task should target the .NET Compact Framework; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index caf3c8465e4..968bfbfd5d3 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -1354,7 +1354,7 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
 -   By calling the Windows `GetUserDefaultUILanguage` function.  
   
 > [!NOTE]
->  In the [!INCLUDE[Compact](~/includes/compact-md.md)], the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property is read-only. The current UI culture is determined by the system's regional settings and cannot be changed programmatically.  
+>  In the .NET Compact Framework, the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property is read-only. The current UI culture is determined by the system's regional settings and cannot be changed programmatically.  
   
  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], to change the user interface culture used by a thread, set the <xref:System.Threading.Thread.CurrentUICulture%2A?displayProperty=nameWithType> property to the new culture. If you explicitly change a thread's UI culture in this way, that change persists if the thread crosses application domain boundaries.  
   
diff --git a/xml/System/NotSupportedException.xml b/xml/System/NotSupportedException.xml
index 266a42a2118..2d7d351350f 100644
--- a/xml/System/NotSupportedException.xml
+++ b/xml/System/NotSupportedException.xml
@@ -122,17 +122,17 @@
  This exception is thrown in scenarios in which it is generally sometimes possible for the object to perform the requested operation, and the object state determines whether the operation can be performed.  
   
 ## .NET Compact Framework notes  
- When working with the [!INCLUDE[Compact](~/includes/compact-md.md)] and using P/Invoke on a native function, this exception may be thrown if:  
+ When working with the .NET Compact Framework and using P/Invoke on a native function, this exception may be thrown if:  
   
 -   The declaration in managed code is incorrect.  
   
--   The [!INCLUDE[Compact](~/includes/compact-md.md)] does not support what you are trying to do.  
+-   The .NET Compact Framework does not support what you are trying to do.  
   
 -   The DLL names are mangled on export.  
   
  If a <xref:System.NotSupportedException.%23ctor%2A> exception is thrown, check:  
   
--   For any violations of the [!INCLUDE[Compact](~/includes/compact-md.md)] P/Invoke restrictions.  
+-   For any violations of the .NET Compact Framework P/Invoke restrictions.  
   
 -   For any arguments that require pre-allocated memory. If these exist, you should pass a reference to an existing variable.  
   

From 316cfcddb613635329498b93784007cd1a7c071f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:58:16 -0800
Subject: [PATCH 006/236] cpp-iter-arg

---
 .../ConstContainerBidirectionalIterator`1.xml                   | 2 +-
 .../ConstContainerRandomAccessIterator`1.xml                    | 2 +-
 .../ConstReverseBidirectionalIterator`1.xml                     | 2 +-
 .../ConstReverseRandomAccessIterator`1.xml                      | 2 +-
 .../ContainerBidirectionalIterator`1.xml                        | 2 +-
 .../ContainerRandomAccessIterator`1.xml                         | 2 +-
 xml/Microsoft.VisualC.StlClr.Generic/IBaseIterator`1.xml        | 2 +-
 .../IBidirectionalContainer`1.xml                               | 2 +-
 .../IBidirectionalIterator`1.xml                                | 2 +-
 xml/Microsoft.VisualC.StlClr.Generic/IForwardIterator`1.xml     | 2 +-
 xml/Microsoft.VisualC.StlClr.Generic/IInputIterator`1.xml       | 2 +-
 xml/Microsoft.VisualC.StlClr.Generic/INode`1.xml                | 2 +-
 xml/Microsoft.VisualC.StlClr.Generic/IOutputIterator`1.xml      | 2 +-
 .../IRandomAccessContainer`1.xml                                | 2 +-
 .../IRandomAccessIterator`1.xml                                 | 2 +-
 .../ReverseBidirectionalIterator`1.xml                          | 2 +-
 .../ReverseRandomAccessIterator`1.xml                           | 2 +-
 xml/Microsoft.VisualC.StlClr/DequeEnumeratorBase`1.xml          | 2 +-
 xml/Microsoft.VisualC.StlClr/DequeEnumerator`1.xml              | 2 +-
 19 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerBidirectionalIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerBidirectionalIterator`1.xml
index 4fc026c7786..81d523e126e 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerBidirectionalIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerBidirectionalIterator`1.xml
@@ -37,7 +37,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines an iterator that can access elements in a container in the forward direction by using the increment operator and in the backward direction by using the decrement operator. The element that the iterator points to cannot be modified. Bidirectional iterators can be used anywhere that a constant input or constant output iterator is required.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerRandomAccessIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerRandomAccessIterator`1.xml
index e9e9f5f6aa3..69ca4e30a3a 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerRandomAccessIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ConstContainerRandomAccessIterator`1.xml
@@ -40,7 +40,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Provides an iterator that supports the following operations: moving forward one position by calling <c>operator++</c>, moving backward one position by calling <c>operator--</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic. The element pointed to by the iterator cannot be modified.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseBidirectionalIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseBidirectionalIterator`1.xml
index f55fad52c36..5f57b3d0db1 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseBidirectionalIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseBidirectionalIterator`1.xml
@@ -37,7 +37,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines an iterator that accesses elements in a container in the reverse direction. Elements can be accessed in the forward direction by using the decrement operator and in the backward direction by using the increment operator. The element that the iterator points to cannot be modified. Constant reverse bidirectional iterators can be used anywhere that a constant reverse input or constant reverse output iterator is required.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseRandomAccessIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseRandomAccessIterator`1.xml
index ab6d2c5decc..d0bffcecd0b 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseRandomAccessIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ConstReverseRandomAccessIterator`1.xml
@@ -40,7 +40,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Provides an iterator that supports the following operations: moving forward one position by calling <c>operator--</c>, moving backward one position by calling <c>operator++</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic. The element accessed by the iterator cannot be modified.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ContainerBidirectionalIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ContainerBidirectionalIterator`1.xml
index e62f69bfd14..f5366f8c694 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ContainerBidirectionalIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ContainerBidirectionalIterator`1.xml
@@ -37,7 +37,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines an iterator that can access elements in a container in the forward direction by using the increment operator and in the backward direction by using the decrement operator. The element that the iterator points to can be both written to and read from any number of times. Bidirectional iterators can be used anywhere that an input or output iterator is required.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ContainerRandomAccessIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ContainerRandomAccessIterator`1.xml
index 4e1a95f26ac..35b5135c982 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ContainerRandomAccessIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ContainerRandomAccessIterator`1.xml
@@ -40,7 +40,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Provides an iterator that supports the following operations: moving forward one position by calling <c>operator++</c>, moving backward one position by calling <c>operator--</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IBaseIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IBaseIterator`1.xml
index e56a5a82de6..79ae9551117 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IBaseIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IBaseIterator`1.xml
@@ -19,7 +19,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines the base interface for all STL/CLR iterators.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalContainer`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalContainer`1.xml
index ed8a8ffd971..1bee7a72ceb 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalContainer`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalContainer`1.xml
@@ -15,7 +15,7 @@
   </TypeParameters>
   <Interfaces />
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for a container that supports both forward and backward iteration. Containers that implement bidirectional iteration support the following operations: moving forward one position by calling <c>operator++</c>, and moving backward one position by calling <c>operator--</c>.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalIterator`1.xml
index 52cc23750ab..c3c0faf4b02 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IBidirectionalIterator`1.xml
@@ -31,7 +31,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for an iterator that can access elements in a container in the forward direction by using the increment operator and in the backward direction by using the decrement operator. The element that the iterator points to can be both written to and read from any number of times. Bidirectional iterators can be used anywhere an input or output iterator is required.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IForwardIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IForwardIterator`1.xml
index c4b6deffd44..51692ebfaed 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IForwardIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IForwardIterator`1.xml
@@ -28,7 +28,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for an iterator that can access elements in a container only in the forward direction by using the increment operator. The element that the iterator points to can be both written to and read from any number of times. Forward iterators can be used anywhere an input or output iterator is required.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IInputIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IInputIterator`1.xml
index f79d98a94b7..61c56acae11 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IInputIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IInputIterator`1.xml
@@ -22,7 +22,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for an iterator that is used to read a sequence from a container only in the forward direction. The element that the iterator points to can be read only one time, and it cannot be modified.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/INode`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/INode`1.xml
index 3ba9e62c1c3..e70e9c1fb29 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/INode`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/INode`1.xml
@@ -15,7 +15,7 @@
   </TypeParameters>
   <Interfaces />
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for the node data structure. Containers that support bidirectional iteration contain nodes. A node consists of a value for the element at that position in the container and pointers to the next and previous elements in the container.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IOutputIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IOutputIterator`1.xml
index 495c67a8eb4..10e60a2869c 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IOutputIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IOutputIterator`1.xml
@@ -22,7 +22,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for an iterator that is used to write a sequence to a container only in the forward direction. The element that the iterator points to can be written to only one time.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessContainer`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessContainer`1.xml
index 40e39e3271b..0ebb765c5cf 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessContainer`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessContainer`1.xml
@@ -15,7 +15,7 @@
   </TypeParameters>
   <Interfaces />
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Interface for a container that supports random access iteration. Containers that implement random access iteration support the following operations: moving forward one position by calling <c>operator++</c>, moving backward one position by calling <c>operator--</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessIterator`1.xml
index 8d76c9b377f..a205382a28d 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/IRandomAccessIterator`1.xml
@@ -34,7 +34,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines the interface for a random access iterator. Random access iterators support the following operations: moving forward one position by calling <c>operator++</c>, moving backward one position by calling <c>operator--</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ReverseBidirectionalIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ReverseBidirectionalIterator`1.xml
index 7a5208b4643..87350b3e9c8 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ReverseBidirectionalIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ReverseBidirectionalIterator`1.xml
@@ -37,7 +37,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Defines an iterator that accesses elements in a container in the reverse direction. Elements can be accessed in the forward direction by using the decrement operator and in the backward direction by using the increment operator. The element that the iterator points to can be both written to and read from any number of times. Reverse bidirectional iterators can be used anywhere that a reverse input or reverse output iterator is required.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr.Generic/ReverseRandomAccessIterator`1.xml b/xml/Microsoft.VisualC.StlClr.Generic/ReverseRandomAccessIterator`1.xml
index 5511dabaa02..3d3adb6f29d 100644
--- a/xml/Microsoft.VisualC.StlClr.Generic/ReverseRandomAccessIterator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr.Generic/ReverseRandomAccessIterator`1.xml
@@ -40,7 +40,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Provides an iterator that supports the following operations: moving forward one position by calling <c>operator--</c>, moving backward one position by calling <c>operator++</c>, accessing an element by using <c>operator[]</c>, and accessing an element by using pointer arithmetic.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.VisualC.StlClr/DequeEnumeratorBase`1.xml b/xml/Microsoft.VisualC.StlClr/DequeEnumeratorBase`1.xml
index c9016deda05..d528413f528 100644
--- a/xml/Microsoft.VisualC.StlClr/DequeEnumeratorBase`1.xml
+++ b/xml/Microsoft.VisualC.StlClr/DequeEnumeratorBase`1.xml
@@ -28,7 +28,7 @@
     </Attribute>
   </Attributes>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Supports simple iteration over any STL/CLR object that implements the <see cref="T:Microsoft.VisualC.StlClr.IDeque`1" /> interface.</summary>
     <remarks>To be added.</remarks>
   </Docs>
diff --git a/xml/Microsoft.VisualC.StlClr/DequeEnumerator`1.xml b/xml/Microsoft.VisualC.StlClr/DequeEnumerator`1.xml
index c13aeb4dd8c..dafaa0f9f47 100644
--- a/xml/Microsoft.VisualC.StlClr/DequeEnumerator`1.xml
+++ b/xml/Microsoft.VisualC.StlClr/DequeEnumerator`1.xml
@@ -31,7 +31,7 @@
     </Interface>
   </Interfaces>
   <Docs>
-    <typeparam name="TValue">[!INCLUDE[cpp_iter_arg](~/includes/cpp-iter-arg-md.md)]</typeparam>
+    <typeparam name="TValue">The type of an element in the controlled sequence.</typeparam>
     <summary>Supports simple iteration over any STL/CLR object that implements the <see cref="T:Microsoft.VisualC.StlClr.IDeque`1" /> interface.</summary>
     <remarks>
       <format type="text/markdown"><![CDATA[  

From c8a0095da74b1e6e9670a958d47b478db2b8d597 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:58:57 -0800
Subject: [PATCH 007/236] csprcslong

---
 xml/System.Windows.Forms/Application.xml |  2 +-
 xml/System/Type.xml                      | 20 ++++++++++----------
 2 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index 8bda6c433f0..4306223861e 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1524,7 +1524,7 @@
 > [!IMPORTANT]
 >  To set the default value for `UseCompatibleTextRendering` in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] or later, see <xref:Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.UseCompatibleTextRendering%2A?displayProperty=nameWithType>.  
   
- In [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)] or later, a call to <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> is automatically generated in the Program.cs file. To change the text rendering default, modify the generated code.  
+ In Visual C# 2005 or later, a call to <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> is automatically generated in the Program.cs file. To change the text rendering default, modify the generated code.  
   
 ```csharp  
 static class Program  
diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 705eb34c204..7517cce44b4 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -5245,7 +5245,7 @@ The <xref:System.Type.GetMembers%2A> method does not return members in a particu
  The following example finds specific overloads of `MethodA`, specifying a variety of argument types.  
   
 > [!NOTE]
->  The [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)] example requires the `/unsafe` compiler option.  
+>  The Visual C# 2005 example requires the `/unsafe` compiler option.  
   
  [!code-cpp[Type_GetMethod4#1](~/samples/snippets/cpp/VS_Snippets_CLR/Type_GetMethod4/CPP/type_getmethod4.cpp#1)]
  [!code-csharp[Type_GetMethod4#1](~/samples/snippets/csharp/VS_Snippets_CLR/Type_GetMethod4/CS/type_getmethod4.cs#1)]
@@ -5616,7 +5616,7 @@ One of the elements in the <paramref name="types" /> array is <see langword="nul
  The following example finds specific overloads of `MethodA`, specifying binding constraints and a variety of argument types.  
   
 > [!NOTE]
->  The [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)] example requires the `/unsafe` compiler option.  
+>  The Visual C# 2005 example requires the `/unsafe` compiler option.  
   
  [!code-cpp[Type_GetMethod5#1](~/samples/snippets/cpp/VS_Snippets_CLR/Type_GetMethod5/CPP/type_getmethod5.cpp#1)]
  [!code-csharp[Type_GetMethod5#1](~/samples/snippets/csharp/VS_Snippets_CLR/Type_GetMethod5/CS/type_getmethod5.cs#1)]
@@ -5856,7 +5856,7 @@ One of the elements in the <paramref name="types" /> array is <see langword="nul
  The following example finds specific overloads of `MethodA`, specifying binding constraints, calling conventions, and a variety of argument types.  
   
 > [!NOTE]
->  The [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)] example requires the `/unsafe` compiler option.  
+>  The Visual C# 2005 example requires the `/unsafe` compiler option.  
   
  [!code-cpp[Type_GetMethod3#1](~/samples/snippets/cpp/VS_Snippets_CLR/Type_GetMethod3/CPP/type_getmethod3.cpp#1)]
  [!code-csharp[Type_GetMethod3#1](~/samples/snippets/csharp/VS_Snippets_CLR/Type_GetMethod3/CS/type_getmethod3.cs#1)]
@@ -7059,7 +7059,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, by using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, use the <xref:System.Type.GetProperty%28System.String%2CSystem.Reflection.BindingFlags%29> method overload and add the <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> flag to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7181,7 +7181,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, include <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7274,7 +7274,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7370,7 +7370,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7475,7 +7475,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7575,7 +7575,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7736,7 +7736,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], [!INCLUDE[csprcslong](~/includes/csprcslong-md.md)], and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   

From 4fa3997b9177d23871100a59e77260b8c6f539a1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 10:59:41 -0800
Subject: [PATCH 008/236] desktop-appname

---
 xml/System.IO.Compression/BrotliStream.xml    | 10 ++++----
 xml/System.IO.Compression/DeflateStream.xml   | 12 +++++-----
 xml/System.IO.Compression/GZipStream.xml      | 12 +++++-----
 xml/System.IO.Pipes/PipeStream.xml            |  8 +++----
 xml/System.IO/BufferedStream.xml              |  8 +++----
 xml/System.IO/FileStream.xml                  | 14 +++++------
 xml/System.IO/Stream.xml                      | 24 +++++++++----------
 .../CryptoStream.xml                          |  2 +-
 8 files changed, 45 insertions(+), 45 deletions(-)

diff --git a/xml/System.IO.Compression/BrotliStream.xml b/xml/System.IO.Compression/BrotliStream.xml
index ba4cee3f59d..3dfa2e5ba36 100644
--- a/xml/System.IO.Compression/BrotliStream.xml
+++ b/xml/System.IO.Compression/BrotliStream.xml
@@ -412,7 +412,7 @@
 
 ## Remarks
 
-The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
 
 This method disposes the Brotli stream by writing any changes to the backing store and closing the stream to release resources.   
 
@@ -731,7 +731,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -780,7 +780,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -963,7 +963,7 @@ If the write operation is successful, the position within the Brotli stream adva
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1012,7 +1012,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Compression/DeflateStream.xml b/xml/System.IO.Compression/DeflateStream.xml
index c2fb19ec02c..c817a0cf780 100644
--- a/xml/System.IO.Compression/DeflateStream.xml
+++ b/xml/System.IO.Compression/DeflateStream.xml
@@ -760,7 +760,7 @@ Copying begins at the current position in the current Deflate stream and does no
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -859,7 +859,7 @@ Copying begins at the current position in the current Deflate stream.
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the Deflate stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1318,7 +1318,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1372,7 +1372,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1640,7 +1640,7 @@ If the write operation is successful, the position within the Deflate stream adv
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1694,7 +1694,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Compression/GZipStream.xml b/xml/System.IO.Compression/GZipStream.xml
index 5052506f3dd..dd8e7087b49 100644
--- a/xml/System.IO.Compression/GZipStream.xml
+++ b/xml/System.IO.Compression/GZipStream.xml
@@ -744,7 +744,7 @@ Copying begins at the current position in the current GZip stream, and does not
 
 ## Remarks
 
-The <xref:System.IO.Compression.GZipStream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Compression.GZipStream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -843,7 +843,7 @@ Copying begins at the current position in the current GZip stream.
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the GZip stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1304,7 +1304,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1358,7 +1358,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1632,7 +1632,7 @@ If the write operation is successful, the position within the GZip stream advanc
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1686,7 +1686,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Pipes/PipeStream.xml b/xml/System.IO.Pipes/PipeStream.xml
index b02ff843e17..43f2c78d0af 100644
--- a/xml/System.IO.Pipes/PipeStream.xml
+++ b/xml/System.IO.Pipes/PipeStream.xml
@@ -1528,7 +1528,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
 
 Use the <xref:System.IO.Pipes.PipeStream.CanRead%2A> property to determine whether the current instance supports reading.  
 
@@ -1591,7 +1591,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -2190,7 +2190,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -2254,7 +2254,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
   
 ## Remarks  
 
-The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO/BufferedStream.xml b/xml/System.IO/BufferedStream.xml
index 0811fe2abc1..6fa50c76ca6 100644
--- a/xml/System.IO/BufferedStream.xml
+++ b/xml/System.IO/BufferedStream.xml
@@ -778,7 +778,7 @@ bufStream->Close();
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
 
@@ -885,7 +885,7 @@ This method is called by the public <xref:System.ComponentModel.Component.Dispos
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1416,7 +1416,7 @@ Use <xref:System.IO.BinaryReader> for reading primitive data types.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.BufferedStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1891,7 +1891,7 @@ If the write operation is successful, the position within the buffered stream ad
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.BufferedStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO/FileStream.xml b/xml/System.IO/FileStream.xml
index bca388d8b60..1f2683083d1 100644
--- a/xml/System.IO/FileStream.xml
+++ b/xml/System.IO/FileStream.xml
@@ -54,7 +54,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.IO.FileStream> class to read from, write to, open, and close files on a file system, and to manipulate other file-related operating system handles, including pipes, standard input, and standard output. You can use the <xref:System.IO.FileStream.Read%2A>, <xref:System.IO.FileStream.Write%2A>, <xref:System.IO.Stream.CopyTo%2A>, and <xref:System.IO.FileStream.Flush%2A> methods to perform synchronous operations, or the <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A> methods to perform asynchronous operations. Use the asynchronous methods to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. <xref:System.IO.FileStream> buffers input and output for better performance.  
+ Use the <xref:System.IO.FileStream> class to read from, write to, open, and close files on a file system, and to manipulate other file-related operating system handles, including pipes, standard input, and standard output. You can use the <xref:System.IO.FileStream.Read%2A>, <xref:System.IO.FileStream.Write%2A>, <xref:System.IO.Stream.CopyTo%2A>, and <xref:System.IO.FileStream.Flush%2A> methods to perform synchronous operations, or the <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A> methods to perform asynchronous operations. Use the asynchronous methods to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. <xref:System.IO.FileStream> buffers input and output for better performance.  
   
 > [!IMPORTANT]
 >  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
@@ -2059,7 +2059,7 @@ See <xref:System.IO.Stream.Close?displayProperty=nameWithType> for more informat
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -2181,7 +2181,7 @@ For an example of copying between two streams, see the <xref:System.IO.Stream.Co
 
 ## Remarks
 
-The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -3288,7 +3288,7 @@ Use <xref:System.IO.BinaryReader> for reading primitive data types.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -3366,7 +3366,7 @@ The following example shows how to read from a file asynchronously.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -3996,7 +3996,7 @@ If the write operation is successful, the position within the file stream advanc
 
 ## Remarks
 
-The `WriteAsync` method lets you perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method lets you perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -4066,7 +4066,7 @@ If the operation is canceled before it completes, the returned task contains the
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.FileStream.WriteAsync%2A> method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.FileStream.WriteAsync%2A> method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.FileStream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
diff --git a/xml/System.IO/Stream.xml b/xml/System.IO/Stream.xml
index e9591638495..4b2c9a47926 100644
--- a/xml/System.IO/Stream.xml
+++ b/xml/System.IO/Stream.xml
@@ -98,7 +98,7 @@
   
  Disposing a <xref:System.IO.Stream> object flushes any buffered data, and essentially calls the <xref:System.IO.Stream.Flush%2A> method for you. <xref:System.IO.Stream.Dispose%2A> also releases operating system resources such as file handles, network connections, or memory used for any internal buffering. The <xref:System.IO.BufferedStream> class provides the capability of wrapping a buffered stream around another stream in order to improve read and write performance.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  When used in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)]. You can also convert a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)] to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
   
@@ -834,7 +834,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Copying begins at the current position in the current stream.  
   
@@ -907,7 +907,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Copying begins at the current position in the current stream.  
   
@@ -963,7 +963,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
   
@@ -1030,7 +1030,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
   
@@ -1276,7 +1276,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+ The <xref:System.IO.Stream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
  
  This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.   
   
@@ -1987,7 +1987,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2054,7 +2054,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2135,7 +2135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2658,7 +2658,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
@@ -2725,7 +2725,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
@@ -2806,7 +2806,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
diff --git a/xml/System.Security.Cryptography/CryptoStream.xml b/xml/System.Security.Cryptography/CryptoStream.xml
index c269a24acf5..1fba4011299 100644
--- a/xml/System.Security.Cryptography/CryptoStream.xml
+++ b/xml/System.Security.Cryptography/CryptoStream.xml
@@ -579,7 +579,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.CryptoStream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or [!INCLUDE[desktop_appname](~/includes/desktop-appname-md.md)] app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+ The <xref:System.Security.Cryptography.CryptoStream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
  
  This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.   
   

From f536e101106868d159fa356af11384e1ca140f2d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:00:09 -0800
Subject: [PATCH 009/236] dnprdnext

---
 .../CodeDomProvider.xml                       |  12 +-
 .../PerformanceCounterCategory.xml            |   6 +-
 xml/System.Reflection.Emit/DynamicMethod.xml  |   2 +-
 .../HMACSHA384.xml                            |   2 +-
 .../HMACSHA512.xml                            |   2 +-
 xml/System.Windows.Forms/Clipboard.xml        |   2 +-
 xml/System.Windows.Forms/ColumnHeader.xml     |   2 +-
 xml/System.Windows.Forms/Control.xml          |   4 +-
 xml/System.Windows.Forms/DataObject.xml       |   2 +-
 xml/System.Windows.Forms/TabControl.xml       |   6 +-
 xml/System.Windows.Forms/TabPage.xml          |   8 +-
 xml/System.Xml.XPath/XPathItem.xml            |  18 +--
 xml/System.Xml/XmlNodeReader.xml              |  90 +++++++-------
 xml/System.Xml/XmlTextReader.xml              |   4 +-
 xml/System.Xml/XmlValidatingReader.xml        | 112 +++++++++---------
 15 files changed, 136 insertions(+), 136 deletions(-)

diff --git a/xml/System.CodeDom.Compiler/CodeDomProvider.xml b/xml/System.CodeDom.Compiler/CodeDomProvider.xml
index 285b8c48d8f..bdb3c6a6fee 100644
--- a/xml/System.CodeDom.Compiler/CodeDomProvider.xml
+++ b/xml/System.CodeDom.Compiler/CodeDomProvider.xml
@@ -42,7 +42,7 @@
  A <xref:System.CodeDom.Compiler.CodeDomProvider> can be used to create and retrieve instances of code generators and code compilers. Code generators can be used to generate code in a particular language, and code compilers can be used to compile code into assemblies.  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the methods made available in the code generator and code compiler are available directly from the code provider. You do not need to call <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> or <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> to access the methods, and those methods are marked as obsolete. This applies to preexisting as well as new code provider implementations.  
+>  In the .NET Framework 2.0, the methods made available in the code generator and code compiler are available directly from the code provider. You do not need to call <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> or <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> to access the methods, and those methods are marked as obsolete. This applies to preexisting as well as new code provider implementations.  
   
  A <xref:System.CodeDom.Compiler.CodeDomProvider> implementation typically provides code generation and/or code compilation interfaces for generating code and managing compilation for a single programming language. Several languages are supported by <xref:System.CodeDom.Compiler.CodeDomProvider> implementations that ship with the Windows SDK. These languages include C#, Visual Basic, C++, and JScript. Developers or compiler vendors can implement the <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> interfaces and provide a <xref:System.CodeDom.Compiler.CodeDomProvider> that extends CodeDOM support to other programming languages.  
   
@@ -327,7 +327,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is obsolete in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeCompiler> methods that are directly available in the code provider.  
+ This method is obsolete in the .NET Framework 2.0. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeCompiler> methods that are directly available in the code provider.  
   
  ]]></format>
         </remarks>
@@ -436,7 +436,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is obsolete in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeGenerator> methods that are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class.  
+ This method is obsolete in the .NET Framework 2.0. The recommended alternative is to call the <xref:System.CodeDom.Compiler.ICodeGenerator> methods that are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class.  
   
  ]]></format>
         </remarks>
@@ -490,7 +490,7 @@
  This method uses the specified <xref:System.IO.TextWriter> for output. This method supports more optimized code generation that incrementally updates the source code.  
   
 > [!NOTE]
->  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.  
+>  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the .NET Framework 2.0 and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.  
   
  ]]></format>
         </remarks>
@@ -542,7 +542,7 @@
  This method uses the specified file name for output.  
   
 > [!NOTE]
->  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.  
+>  The base class implementation calls the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A> method, which is obsolete in the .NET Framework 2.0 and results in a <xref:System.NotSupportedException> if an <xref:System.CodeDom.Compiler.ICodeGenerator> object is not returned.  
   
  ]]></format>
         </remarks>
@@ -1209,7 +1209,7 @@
  Use the <xref:System.CodeDom.Compiler.CodeDomProvider.GetAllCompilerInfo%2A> method to enumerate the language provider settings on a computer.  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the default language providers supplied by the .NET Framework are not specified in the [&lt;system.codedom&gt; Element](/dotnet/framework/configure-apps/file-schema/compiler/system-codedom-element) compiler configuration section and cannot be removed, so this method returns information about the default providers and any specified in the configuration file.  
+>  In the .NET Framework 2.0, the default language providers supplied by the .NET Framework are not specified in the [&lt;system.codedom&gt; Element](/dotnet/framework/configure-apps/file-schema/compiler/system-codedom-element) compiler configuration section and cannot be removed, so this method returns information about the default providers and any specified in the configuration file.  
   
    
   
diff --git a/xml/System.Diagnostics/PerformanceCounterCategory.xml b/xml/System.Diagnostics/PerformanceCounterCategory.xml
index 62c2266c7b4..2c7f6ae005e 100644
--- a/xml/System.Diagnostics/PerformanceCounterCategory.xml
+++ b/xml/System.Diagnostics/PerformanceCounterCategory.xml
@@ -353,7 +353,7 @@
 ## Remarks  
  The <xref:System.Diagnostics.PerformanceCounterCategory.CategoryType%2A> property indicates whether the <xref:System.Diagnostics.PerformanceCounterCategory> object can have multiple instances. The possible values are <xref:System.Diagnostics.PerformanceCounterCategoryType.MultiInstance>, <xref:System.Diagnostics.PerformanceCounterCategoryType.SingleInstance>, or <xref:System.Diagnostics.PerformanceCounterCategoryType.Unknown>.  
   
- There are two types of performance counter categories: single-instance and multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
+ There are two types of performance counter categories: single-instance and multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the .NET Framework 2.0, the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
   
  ]]></format>
         </remarks>
@@ -735,7 +735,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the  .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
+ The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the  .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the .NET Framework 2.0, the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
   
  Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory.  You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
   
@@ -929,7 +929,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
+ The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the .NET Framework 2.0, the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
   
  Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
   
diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index 23b917fd370..de4e55dfcd5 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -1082,7 +1082,7 @@
  The example code creates an instance of `Example` and then creates two delegates. The first is of type `UseLikeStatic`, which has the same parameters as the dynamic method. The second is of type `UseLikeInstance`, which lacks the first parameter (of type `Example`). This delegate is created using the <xref:System.Reflection.Emit.DynamicMethod.CreateDelegate%28System.Type%2CSystem.Object%29> method overload; the second parameter of that method overload is an instance of `Example`, in this case the instance just created, which is bound to the newly created delegate. Whenever that delegate is invoked, the dynamic method acts on the bound instance of `Example`.  
   
 > [!NOTE]
->  This is an example of the relaxed rules for delegate binding introduced in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], along with new overloads of the <xref:System.Delegate.CreateDelegate%2A?displayProperty=nameWithType> method. For more information, see the <xref:System.Delegate> class.  
+>  This is an example of the relaxed rules for delegate binding introduced in the .NET Framework 2.0, along with new overloads of the <xref:System.Delegate.CreateDelegate%2A?displayProperty=nameWithType> method. For more information, see the <xref:System.Delegate> class.  
   
  The `UseLikeStatic` delegate is invoked, passing in the instance of `Example` that is bound to the `UseLikeInstance` delegate. Then the `UseLikeInstance` delegate is invoked, so that both delegates act on the same instance of `Example`. The changes in the values of the internal field are displayed after each call. Finally, a `UseLikeInstance` delegate is bound to an instance of `DerivedFromExample`, and the delegate calls are repeated.  
   
diff --git a/xml/System.Security.Cryptography/HMACSHA384.xml b/xml/System.Security.Cryptography/HMACSHA384.xml
index ce9de88bb7e..dc565f27d97 100644
--- a/xml/System.Security.Cryptography/HMACSHA384.xml
+++ b/xml/System.Security.Cryptography/HMACSHA384.xml
@@ -453,7 +453,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Provides a workaround for the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] implementation of the <see cref="T:System.Security.Cryptography.HMACSHA384" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation of the algorithm.</summary>
+        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA384" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation of the algorithm.</summary>
         <value>
           <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Security.Cryptography/HMACSHA512.xml b/xml/System.Security.Cryptography/HMACSHA512.xml
index 746557139e8..0009697666f 100644
--- a/xml/System.Security.Cryptography/HMACSHA512.xml
+++ b/xml/System.Security.Cryptography/HMACSHA512.xml
@@ -453,7 +453,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Provides a workaround for the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] implementation of the <see cref="T:System.Security.Cryptography.HMACSHA512" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation.</summary>
+        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA512" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation.</summary>
         <value>
           <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Forms/Clipboard.xml b/xml/System.Windows.Forms/Clipboard.xml
index 6458a7e3243..940840e99c2 100644
--- a/xml/System.Windows.Forms/Clipboard.xml
+++ b/xml/System.Windows.Forms/Clipboard.xml
@@ -35,7 +35,7 @@
   
  Call <xref:System.Windows.Forms.Clipboard.GetDataObject%2A> to retrieve data from the Clipboard. The data is returned as an object that implements the <xref:System.Windows.Forms.IDataObject> interface. Use the methods specified by <xref:System.Windows.Forms.IDataObject> and fields in <xref:System.Windows.Forms.DataFormats> to extract the data from the object. If you do not know the format of the data you retrieved, call the <xref:System.Windows.Forms.IDataObject.GetFormats%2A> method of the <xref:System.Windows.Forms.IDataObject> interface to get a list of all formats that data is stored in. Then call the <xref:System.Windows.Forms.IDataObject.GetData%2A> method of the <xref:System.Windows.Forms.IDataObject> interface, and specify a format that your application can use.  
   
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Windows.Forms.Clipboard> class provides additional methods that make it easier to work with the system Clipboard. Call the <xref:System.Windows.Forms.Clipboard.Clear%2A> method to remove all data from the Clipboard. To add data of a particular format to the Clipboard, replacing the existing data, call the appropriate `Set`*Format* method, such as <xref:System.Windows.Forms.Clipboard.SetText%2A>, or call the <xref:System.Windows.Forms.Clipboard.SetData%2A> method to specify the format. To retrieve data of a particular format from the Clipboard, first call the appropriate `Contains`*Format* method (such as <xref:System.Windows.Forms.Clipboard.ContainsText%2A>) method to determine whether the Clipboard contains data in that format, and then call the appropriate `Get`*Format* method (such as <xref:System.Windows.Forms.Clipboard.GetText%2A>) to retrieve the data if the Clipboard contains it. To specify the format in these operations, call the <xref:System.Windows.Forms.Clipboard.ContainsData%2A> and <xref:System.Windows.Forms.Clipboard.GetData%2A> methods instead.  
+ In .NET Framework 2.0, the <xref:System.Windows.Forms.Clipboard> class provides additional methods that make it easier to work with the system Clipboard. Call the <xref:System.Windows.Forms.Clipboard.Clear%2A> method to remove all data from the Clipboard. To add data of a particular format to the Clipboard, replacing the existing data, call the appropriate `Set`*Format* method, such as <xref:System.Windows.Forms.Clipboard.SetText%2A>, or call the <xref:System.Windows.Forms.Clipboard.SetData%2A> method to specify the format. To retrieve data of a particular format from the Clipboard, first call the appropriate `Contains`*Format* method (such as <xref:System.Windows.Forms.Clipboard.ContainsText%2A>) method to determine whether the Clipboard contains data in that format, and then call the appropriate `Get`*Format* method (such as <xref:System.Windows.Forms.Clipboard.GetText%2A>) to retrieve the data if the Clipboard contains it. To specify the format in these operations, call the <xref:System.Windows.Forms.Clipboard.ContainsData%2A> and <xref:System.Windows.Forms.Clipboard.GetData%2A> methods instead.  
   
 > [!NOTE]
 >  All Windows-based applications share the system Clipboard, so the contents are subject to change when you switch to another application.  
diff --git a/xml/System.Windows.Forms/ColumnHeader.xml b/xml/System.Windows.Forms/ColumnHeader.xml
index 3a80ae45d7f..d9ddd1a10fc 100644
--- a/xml/System.Windows.Forms/ColumnHeader.xml
+++ b/xml/System.Windows.Forms/ColumnHeader.xml
@@ -688,7 +688,7 @@ If you set the <xref:System.Windows.Forms.ColumnHeader.ImageKey%2A> property, th
  You can use this property to provide different text alignment settings for the text displayed in each <xref:System.Windows.Forms.ColumnHeader>.  
   
 > [!NOTE]
->  Due to a limitation in the underlying control, this property has no effect on the first column in the <xref:System.Windows.Forms.ListView> control, which is always aligned to the left. To work around this limitation in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], you can handle the <xref:System.Windows.Forms.ListView.DrawColumnHeader?displayProperty=nameWithType> event and paint the column header yourself.  
+>  Due to a limitation in the underlying control, this property has no effect on the first column in the <xref:System.Windows.Forms.ListView> control, which is always aligned to the left. To work around this limitation in .NET Framework 2.0, you can handle the <xref:System.Windows.Forms.ListView.DrawColumnHeader?displayProperty=nameWithType> event and paint the column header yourself.  
   
    
   
diff --git a/xml/System.Windows.Forms/Control.xml b/xml/System.Windows.Forms/Control.xml
index a6bffb93d73..4333a01b6b5 100644
--- a/xml/System.Windows.Forms/Control.xml
+++ b/xml/System.Windows.Forms/Control.xml
@@ -4688,7 +4688,7 @@ Point clientPoint = targetControl.PointToClient(new Point(de.X, de.Y));
 ```  
   
 > [!NOTE]
->  In versions earlier than [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], if you put a <xref:System.Windows.Forms.UserControl> with <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events on a Windows Form and drag and drop something onto the <xref:System.Windows.Forms.UserControl> at design time, the `DropDrop` and `DropEnter` events are raised. However, when you close and reopen the solution, the <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events are not raised again.  
+>  In versions earlier than .NET Framework 2.0, if you put a <xref:System.Windows.Forms.UserControl> with <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events on a Windows Form and drag and drop something onto the <xref:System.Windows.Forms.UserControl> at design time, the `DropDrop` and `DropEnter` events are raised. However, when you close and reopen the solution, the <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events are not raised again.  
   
  For more information about handling events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
@@ -4737,7 +4737,7 @@ Point clientPoint = targetControl.PointToClient(new Point(de.X, de.Y));
  The <xref:System.Windows.Forms.Control.DragEnter> event is raised when the user first drags the mouse cursor over the control during a drag-and-drop operation.  
   
 > [!NOTE]
->  In versions earlier than [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], if you put a <xref:System.Windows.Forms.UserControl> with <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events on a Windows Form and drag and drop something onto the <xref:System.Windows.Forms.UserControl> at design time, the `DropDrop` and `DropEnter` events are raised. However, when you close and reopen the solution, the <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events are not raised again.  
+>  In versions earlier than .NET Framework 2.0, if you put a <xref:System.Windows.Forms.UserControl> with <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events on a Windows Form and drag and drop something onto the <xref:System.Windows.Forms.UserControl> at design time, the `DropDrop` and `DropEnter` events are raised. However, when you close and reopen the solution, the <xref:System.Windows.Forms.Control.DragEnter> and <xref:System.Windows.Forms.Control.DragDrop> events are not raised again.  
   
  The following describes how and when events related to drag-and-drop operations are raised.  
   
diff --git a/xml/System.Windows.Forms/DataObject.xml b/xml/System.Windows.Forms/DataObject.xml
index 481ab859944..4becb14dba0 100644
--- a/xml/System.Windows.Forms/DataObject.xml
+++ b/xml/System.Windows.Forms/DataObject.xml
@@ -52,7 +52,7 @@
   
  To determine what formats the data is stored in, call <xref:System.Windows.Forms.DataObject.GetFormats%2A>. To determine if a format is available, call <xref:System.Windows.Forms.DataObject.GetDataPresent%2A> with the desired format.  
   
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Windows.Forms.DataObject> class provides additional methods that make it easier to work with data in common formats. To add data of a particular format to the <xref:System.Windows.Forms.DataObject>, use the appropriate `Set`*Format* method, such as <xref:System.Windows.Forms.DataObject.SetText%2A>. To retrieve data of a particular format from the <xref:System.Windows.Forms.DataObject>, first call the appropriate `Contains`*Format* method (such as <xref:System.Windows.Forms.DataObject.ContainsText%2A>) to determine whether the <xref:System.Windows.Forms.DataObject> contains data in that format, then call the appropriate `Get`*Format* method (such as <xref:System.Windows.Forms.DataObject.GetText%2A>) to retrieve the data if the <xref:System.Windows.Forms.DataObject> contains it.  
+ In .NET Framework 2.0, the <xref:System.Windows.Forms.DataObject> class provides additional methods that make it easier to work with data in common formats. To add data of a particular format to the <xref:System.Windows.Forms.DataObject>, use the appropriate `Set`*Format* method, such as <xref:System.Windows.Forms.DataObject.SetText%2A>. To retrieve data of a particular format from the <xref:System.Windows.Forms.DataObject>, first call the appropriate `Contains`*Format* method (such as <xref:System.Windows.Forms.DataObject.ContainsText%2A>) to determine whether the <xref:System.Windows.Forms.DataObject> contains data in that format, then call the appropriate `Get`*Format* method (such as <xref:System.Windows.Forms.DataObject.GetText%2A>) to retrieve the data if the <xref:System.Windows.Forms.DataObject> contains it.  
   
 > [!NOTE]
 >  Special considerations may be necessary when using the metafile format with the Clipboard. Due to a limitation in the current implementation of the <xref:System.Windows.Forms.DataObject> class, the metafile format used by the .NET Framework may not be recognized by applications that use an older metafile format. In this case, you must interoperate with the Win32 Clipboard application programming interfaces (APIs).
diff --git a/xml/System.Windows.Forms/TabControl.xml b/xml/System.Windows.Forms/TabControl.xml
index 47fcf31eb31..eae4599daf4 100644
--- a/xml/System.Windows.Forms/TabControl.xml
+++ b/xml/System.Windows.Forms/TabControl.xml
@@ -60,7 +60,7 @@
   
 -   <xref:System.Windows.Forms.TabControl.SelectedTab%2A>  
   
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], you can also use one of the following methods:  
+ In .NET Framework 2.0, you can also use one of the following methods:  
   
 -   <xref:System.Windows.Forms.TabControl.SelectTab%2A>  
   
@@ -1663,7 +1663,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], this method also raises the <xref:System.Windows.Forms.Control.Enter> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Enter> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
@@ -1852,7 +1852,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], this method also raises the <xref:System.Windows.Forms.Control.Leave> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Leave> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
diff --git a/xml/System.Windows.Forms/TabPage.xml b/xml/System.Windows.Forms/TabPage.xml
index 46507ded9be..68306c21291 100644
--- a/xml/System.Windows.Forms/TabPage.xml
+++ b/xml/System.Windows.Forms/TabPage.xml
@@ -67,14 +67,14 @@
  The tabs in a <xref:System.Windows.Forms.TabControl> are part of the <xref:System.Windows.Forms.TabControl> but not parts of the individual <xref:System.Windows.Forms.TabPage> controls. Members of the <xref:System.Windows.Forms.TabPage> class, such as the <xref:System.Windows.Forms.Control.ForeColor%2A> property, affect only the client rectangle of the tab page, but not the tabs. Additionally, the <xref:System.Windows.Forms.Control.Hide%2A> method of the <xref:System.Windows.Forms.TabPage> will not hide the tab. To hide the tab, you must remove the <xref:System.Windows.Forms.TabPage> control from the <xref:System.Windows.Forms.TabControl.TabPages%2A?displayProperty=nameWithType> collection.  
   
 > [!NOTE]
->  In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+>  In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  For more information about how this control responds to the <xref:System.Windows.Forms.Control.Focus%2A> and <xref:System.Windows.Forms.Control.Select%2A> methods, see the following <xref:System.Windows.Forms.Control> members: <xref:System.Windows.Forms.Control.CanFocus%2A>, <xref:System.Windows.Forms.Control.CanSelect%2A>, <xref:System.Windows.Forms.Control.Focused%2A>, <xref:System.Windows.Forms.Control.ContainsFocus%2A>, <xref:System.Windows.Forms.Control.Focus%2A>, <xref:System.Windows.Forms.Control.Select%2A>.  
   
 > [!NOTE]
 >  Controls contained in a <xref:System.Windows.Forms.TabPage> are not created until the tab page is shown, and any data bindings in these controls are not activated until the tab page is shown.  
   
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the <xref:System.Windows.Forms.TabPage.UseVisualStyleBackColor%2A> property lets you indicate whether the background of the tab page should render using the current visual style. This occurs only when the <xref:System.Windows.Forms.TabPage.UseVisualStyleBackColor%2A> and <xref:System.Windows.Forms.Application.RenderWithVisualStyles%2A?displayProperty=nameWithType> property values are both `true` and the <xref:System.Windows.Forms.TabControl.Appearance%2A> property of the parent <xref:System.Windows.Forms.TabControl> is <xref:System.Windows.Forms.TabAppearance.Normal>. Otherwise, the background is painted normally.  
+ In .NET Framework 2.0, the <xref:System.Windows.Forms.TabPage.UseVisualStyleBackColor%2A> property lets you indicate whether the background of the tab page should render using the current visual style. This occurs only when the <xref:System.Windows.Forms.TabPage.UseVisualStyleBackColor%2A> and <xref:System.Windows.Forms.Application.RenderWithVisualStyles%2A?displayProperty=nameWithType> property values are both `true` and the <xref:System.Windows.Forms.TabControl.Appearance%2A> property of the parent <xref:System.Windows.Forms.TabControl> is <xref:System.Windows.Forms.TabAppearance.Normal>. Otherwise, the background is painted normally.  
   
    
   
@@ -878,7 +878,7 @@ If you set the <xref:System.Windows.Forms.TabPage.ImageKey%2A> property, the <xr
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
@@ -919,7 +919,7 @@ If you set the <xref:System.Windows.Forms.TabPage.ImageKey%2A> property, the <xr
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
diff --git a/xml/System.Xml.XPath/XPathItem.xml b/xml/System.Xml.XPath/XPathItem.xml
index 66bcb08918d..9e96804360b 100644
--- a/xml/System.Xml.XPath/XPathItem.xml
+++ b/xml/System.Xml.XPath/XPathItem.xml
@@ -194,7 +194,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>When overridden in a derived class, gets the current item as a boxed object of the most appropriate [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] type according to its schema type.</summary>
+        <summary>When overridden in a derived class, gets the current item as a boxed object of the most appropriate .NET Framework 2.0 type according to its schema type.</summary>
         <value>The current item as a boxed object of the most appropriate [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -308,7 +308,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueAs%2A> method attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] type specified.  
+ When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueAs%2A> method attempts to convert the value of the item to the .NET Framework 2.0 type specified.  
   
  ]]></format>
         </remarks>
@@ -365,7 +365,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueAs%2A> method attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] type specified.  
+ When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueAs%2A> method attempts to convert the value of the item to the .NET Framework 2.0 type specified.  
   
  The <xref:System.Xml.IXmlNamespaceResolver> object is used to resolve namespace prefixes related to type conversions. For example, when converting an `xs:QName` to an `xs:string`.  
   
@@ -420,7 +420,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Xml.XPath.XPathItem.ValueAsDateTime%2A> property attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] <xref:System.Boolean> type according to the XPath 2.0 rules for casting the item's type.  
+ The <xref:System.Xml.XPath.XPathItem.ValueAsDateTime%2A> property attempts to convert the value of the item to the .NET Framework 2.0 <xref:System.Boolean> type according to the XPath 2.0 rules for casting the item's type.  
   
  For more information about type support in the <xref:System.Xml?displayProperty=nameWithType> namespace, see [Type Support in the System.Xml Classes](/dotnet/standard/data/xml/type-support-in-the-system-xml-classes).  
   
@@ -471,7 +471,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Xml.XPath.XPathItem.ValueAsDateTime%2A> property attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] <xref:System.DateTime> type according to the XPath 2.0 rules for casting the item's type.  
+ The <xref:System.Xml.XPath.XPathItem.ValueAsDateTime%2A> property attempts to convert the value of the item to the .NET Framework 2.0 <xref:System.DateTime> type according to the XPath 2.0 rules for casting the item's type.  
   
  For more information about type support in the <xref:System.Xml?displayProperty=nameWithType> namespace, see [Type Support in the System.Xml Classes](/dotnet/standard/data/xml/type-support-in-the-system-xml-classes).  
   
@@ -522,7 +522,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Xml.XPath.XPathItem.ValueAsDouble%2A> property attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] <xref:System.Double> type according to the XPath 2.0 rules for casting the item's type.  
+ The <xref:System.Xml.XPath.XPathItem.ValueAsDouble%2A> property attempts to convert the value of the item to the .NET Framework 2.0 <xref:System.Double> type according to the XPath 2.0 rules for casting the item's type.  
   
  For more information about type support in the <xref:System.Xml?displayProperty=nameWithType> namespace, see [Type Support in the System.Xml Classes](/dotnet/standard/data/xml/type-support-in-the-system-xml-classes).  
   
@@ -574,7 +574,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Xml.XPath.XPathItem.ValueAsInt%2A> property attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] <xref:System.Int32> type according to the XPath 2.0 rules for casting the item's type.  
+ The <xref:System.Xml.XPath.XPathItem.ValueAsInt%2A> property attempts to convert the value of the item to the .NET Framework 2.0 <xref:System.Int32> type according to the XPath 2.0 rules for casting the item's type.  
   
  For more information about type support in the <xref:System.Xml?displayProperty=nameWithType> namespace, see [Type Support in the System.Xml Classes](/dotnet/standard/data/xml/type-support-in-the-system-xml-classes).  
   
@@ -626,7 +626,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Xml.XPath.XPathItem.ValueAsLong%2A> property attempts to convert the value of the item to the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] <xref:System.Int64> type according to the XPath 2.0 rules for casting the item's type.  
+ The <xref:System.Xml.XPath.XPathItem.ValueAsLong%2A> property attempts to convert the value of the item to the .NET Framework 2.0 <xref:System.Int64> type according to the XPath 2.0 rules for casting the item's type.  
   
  For more information about type support in the <xref:System.Xml?displayProperty=nameWithType> namespace, see [Type Support in the System.Xml Classes](/dotnet/standard/data/xml/type-support-in-the-system-xml-classes).  
   
@@ -672,7 +672,7 @@
         <ReturnType>System.Type</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>When overridden in a derived class, gets the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] type of the item.</summary>
+        <summary>When overridden in a derived class, gets the .NET Framework 2.0 type of the item.</summary>
         <value>The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type of the item. The default value is <see cref="T:System.String" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Xml/XmlNodeReader.xml b/xml/System.Xml/XmlNodeReader.xml
index aace1001e8b..673767715fe 100644
--- a/xml/System.Xml/XmlNodeReader.xml
+++ b/xml/System.Xml/XmlNodeReader.xml
@@ -115,7 +115,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  For more information and examples of the code used to create an `XmlNodeReader`, see <xref:System.Xml.XmlReader> and overloads of the <xref:System.Xml.XmlReader.Create%2A> method.  
   
@@ -162,7 +162,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property is relevant to `Element`, `DocumentType` and `XmlDeclaration` nodes only. (Other node types do not have attributes.)  
   
@@ -218,7 +218,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  A networked XML document is comprised of chunks of data aggregated using various W3C standard inclusion mechanisms and therefore contains nodes that come from different places. DTD entities are an example of this, but this is not limited to DTDs. The base URI tells you where these nodes came from. If there is no base URI for the nodes being returned (for example, they were parsed from an in-memory string), String.Empty is returned.  
   
@@ -280,7 +280,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The binary content read methods include the <xref:System.Xml.XmlNodeReader.ReadContentAsBase64%2A>, <xref:System.Xml.XmlNodeReader.ReadContentAsBinHex%2A>, <xref:System.Xml.XmlNodeReader.ReadElementContentAsBase64%2A>, and <xref:System.Xml.XmlNodeReader.ReadElementContentAsBinHex%2A> methods.  
   
@@ -328,7 +328,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -373,7 +373,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method also releases any resources held while reading. If `Close` has already been called, no action is performed.  
   
@@ -439,7 +439,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -485,7 +485,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -544,7 +544,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method does not move the reader.  
   
@@ -597,7 +597,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method does not move the reader.  
   
@@ -662,7 +662,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The following XML contains an attribute in a specific namespace:  
   
@@ -730,7 +730,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -785,7 +785,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The following table lists node types that have a value to return.  
   
@@ -854,7 +854,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property applies to attribute nodes only. If the reader is not positioned on an attribute node, this property returns `false`.  
   
@@ -902,7 +902,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property enables you to determine the difference between the following:  
   
@@ -959,7 +959,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
 
 > [!NOTE]
-> In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 This property does not move the reader.
 
@@ -1036,7 +1036,7 @@ This property does not move the reader.
 ## Remarks  
 
 > [!NOTE]
-> In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 This property does not move the reader.
 
@@ -1086,7 +1086,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1145,7 +1145,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  In the following XML string, if the reader is positioned on the `href` attribute, the prefix `a` is resolved by calling `reader.LookupNamespace("a")`. The returned string is `urn:456`.  
   
@@ -1213,7 +1213,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1273,7 +1273,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlNodeReader.Name%2A>, <xref:System.Xml.XmlNodeReader.NamespaceURI%2A>, and <xref:System.Xml.XmlNodeReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1328,7 +1328,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlNodeReader.Name%2A>, <xref:System.Xml.XmlNodeReader.NamespaceURI%2A>, and <xref:System.Xml.XmlNodeReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1377,7 +1377,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method to return to an element after navigating through its attributes. This method moves the reader to one of the following node types: `Element`, `DocumentType`, or `XmlDeclaration`.  
   
@@ -1435,7 +1435,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1491,7 +1491,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If the current node is not an attribute node, this method is equivalent to <xref:System.Xml.XmlNodeReader.MoveToFirstAttribute%2A>. If `MoveToNextAttribute` returns `true`, the reader moves to the next attribute; otherwise, the position of the reader does not change.  
   
@@ -1567,7 +1567,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1625,7 +1625,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property is relevant to `Element` and `Attribute` nodes only.  
   
@@ -1681,7 +1681,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  All node and attribute names returned from this class are atomized using the `NameTable`. When the same name is returned multiple times (for example, `Customer`), then the same `String` object is returned for that name. This makes it possible for you to write efficient code that does object comparisons on these strings instead of expensive string comparisons.  
   
@@ -1729,7 +1729,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1787,7 +1787,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1832,7 +1832,7 @@ This property does not move the reader.
 ## Remarks  
 
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 ]]></format>
         </remarks>
@@ -1885,7 +1885,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  When a reader is first created and initialized, there is no information available. You must call `Read` to read the first node.  
   
@@ -1951,7 +1951,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method after calling <xref:System.Xml.XmlNodeReader.MoveToAttribute%2A> to read through the text or entity reference nodes that make up the attribute value. The <xref:System.Xml.XmlNodeReader.Depth%2A> of the attribute value nodes is one plus the depth of the attribute node; it increments and decrements by one when you step into and out of general entity references.  
   
@@ -2014,7 +2014,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method streams the content, decodes the Base64 content, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2085,7 +2085,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method streams the content, decodes the BinHex content, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text.  
   
@@ -2156,7 +2156,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the content, decodes it using Base64 encoding, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2230,7 +2230,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the element content, decodes it using BinHex encoding, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer.  
   
@@ -2303,7 +2303,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -2351,7 +2351,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If positioned on an element, `ReadString` concatenates all text, significant white space, white space, and CData section node types together and returns the concatenated data as the element content. It stops when any markup is encountered. This could occur in a mixed content model, or when an element end tag is read.  
   
@@ -2409,7 +2409,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If the reader is positioned on an `EntityReference` node (`XmlNodeType.EntityReference`), if <xref:System.Xml.XmlNodeReader.Read%2A> is called after calling this method, the entity replacement text is parsed. When the entity replacement text is finished, an `EndEntity` node is returned to close the entity reference scope.  
   
@@ -2469,7 +2469,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The <xref:System.Xml.Schema.IXmlSchemaInfo> interface represents the Post Schema Validation Infoset (PSVI) of the underlying XML node. The PSVI contents of this property are set after the node has been validated.  
   
@@ -2518,7 +2518,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  For example, suppose you have the following XML input:  
   
@@ -2766,7 +2766,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -2824,7 +2824,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property represents the xml:lang scope within which the current node resides. For example, here is an XML fragment with `xml:lang` set to US English in the root element:  
   
@@ -2881,7 +2881,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Xml/XmlTextReader.xml b/xml/System.Xml/XmlTextReader.xml
index b5365d05fd2..a412c40afb1 100644
--- a/xml/System.Xml/XmlTextReader.xml
+++ b/xml/System.Xml/XmlTextReader.xml
@@ -1181,7 +1181,7 @@ XmlTextReader reader = new XmlTextReader(s);
 > [!NOTE]
 >  Starting with the .NET Framework 2.0, we recommend that you create <xref:System.Xml.XmlReader> instances by using the <xref:System.Xml.XmlReader.Create%2A?displayProperty=nameWithType> method to take advantage of new functionality.  
   
- This is a change in the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)] release. In previous versions, the `XmlTextReader` class could not resolve entities and `CanResolveEntity` always returned `false`.  
+ This is a change in the .NET Framework 2.0 release. In previous versions, the `XmlTextReader` class could not resolve entities and `CanResolveEntity` always returned `false`.  
   
  ]]></format>
         </remarks>
@@ -4314,7 +4314,7 @@ if (XmlNodeType.Element == reader.NodeType && "thing" == reader.Name)
 
 ## Remarks  
 
-> In the [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)], the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 ]]></format>
         </remarks>
diff --git a/xml/System.Xml/XmlValidatingReader.xml b/xml/System.Xml/XmlValidatingReader.xml
index aa971b79a1e..6c3234b66cb 100644
--- a/xml/System.Xml/XmlValidatingReader.xml
+++ b/xml/System.Xml/XmlValidatingReader.xml
@@ -66,7 +66,7 @@
  <xref:System.Xml.XmlValidatingReader> throws an <xref:System.Xml.XmlException> on XML parse errors. After an exception is thrown the state of the reader is not predictable. For example, the reported node type may be different than the actual node type of the current node. Use the <xref:System.Xml.XmlValidatingReader.ReadState%2A> property to check whether a reader is in error state.  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
     </remarks>
@@ -125,7 +125,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  All nodes returned from the given `XmlReader` are also returned from this validating reader, so there is no information loss in the process. New nodes not returned from the underlying reader may be added by this reader (for example, default attributes and the children of an entity reference). Any properties set on the given `XmlTextReader` also apply to this validating reader. For example, if the supplied reader had WhitespaceHandling.None set, this validating reader also ignores white space.  
   
@@ -204,7 +204,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This constructor parses the given string as a fragment of XML. If the XML fragment is an element or attribute, you can bypass the root level rules for well-formed XML documents.  
   
@@ -281,7 +281,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This constructor parses the given string as a fragment of XML. If the XML fragment is an element or attribute, you can bypass the root level rules for well-formed XML documents. This constructor can handle strings returned from <xref:System.Xml.XmlReader.ReadInnerXml%2A>.  
   
@@ -354,7 +354,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property is relevant to `Element`, `DocumentType`, and `XmlDeclaration` nodes only. (Other node types do not have attributes.)  
   
@@ -412,7 +412,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  A networked XML document is comprised of chunks of data aggregated by using various World Wide Web Consortium (W3C) standard inclusion mechanisms and therefore contains nodes that come from different places. document type definition (DTD) entities are an example of this, but this is not limited to DTDs. The base URI tells you where these nodes came from. If there is no base URI for the nodes being returned (for example, they were parsed from an in-memory string), String.Empty is returned.  
   
@@ -475,7 +475,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
   
  The binary content read methods include the <xref:System.Xml.XmlValidatingReader.ReadContentAsBase64%2A>, <xref:System.Xml.XmlValidatingReader.ReadContentAsBinHex%2A>, <xref:System.Xml.XmlValidatingReader.ReadElementContentAsBase64%2A>, and <xref:System.Xml.XmlValidatingReader.ReadElementContentAsBinHex%2A> methods.  
   
@@ -524,7 +524,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -570,7 +570,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This method also releases any resources held while reading. If this reader was constructed by using an <xref:System.Xml.XmlTextReader>, this method also calls `Close` on the underlying reader. If this reader was constructed by using a stream, this method also calls `Close` on the underlying stream.  
   
@@ -620,7 +620,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -677,7 +677,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  When any external reference is read (such as expanding an entity in a document type definition (DTD) file or reading a schema file) the encoding property is set to the encoding value of the external reference. If encoding is not specified in the external reference, and there is no byte-order mark, this defaults to UTF-8.  
   
@@ -727,7 +727,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property can be changed and takes effect after the next <xref:System.Xml.XmlValidatingReader.Read%2A> call.  
   
@@ -813,7 +813,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -874,7 +874,7 @@
  This method does not move the reader.  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -926,7 +926,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This method does not move the reader.  
   
@@ -996,7 +996,7 @@
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  The following XML contains an attribute in a specific namespace:  
   
@@ -1068,7 +1068,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -1115,7 +1115,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  The following table lists node types that have a value to return.  
   
@@ -1186,7 +1186,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
  This property applies only to an attribute node.  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1252,7 +1252,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property enables you to determine the difference between the following:  
   
@@ -1428,7 +1428,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property is most commonly used for error reporting, but can be called at any time. The starting value for this property is 1. Combined with <xref:System.Xml.XmlValidatingReader.LinePosition%2A>, a value of 1,1 indicates the start of the document.  
   
@@ -1478,7 +1478,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property is most commonly used for error reporting, but can be called at any time. The starting value for this property is `1`.  
   
@@ -1540,7 +1540,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1599,7 +1599,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
   
  In the following XML string, if the reader is positioned on the `href` attribute, the prefix `a` is resolved by calling `reader.LookupNamespace("a", true)`. The returned string is `urn:456`.  
   
@@ -1668,7 +1668,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1729,7 +1729,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlValidatingReader.Name%2A>, <xref:System.Xml.XmlValidatingReader.NamespaceURI%2A>, and <xref:System.Xml.XmlValidatingReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1794,7 +1794,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlValidatingReader.Name%2A>, <xref:System.Xml.XmlValidatingReader.NamespaceURI%2A>, and <xref:System.Xml.XmlValidatingReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1844,7 +1844,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method to return to an element after navigating through its attributes. This method moves the reader to one of the following node types: `Element`, `DocumentType`, or `XmlDeclaration`.  
   
@@ -1903,7 +1903,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1960,7 +1960,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  If the current node is an element node, this method is equivalent to <xref:System.Xml.XmlValidatingReader.MoveToFirstAttribute%2A>. If `MoveToNextAttribute` returns `true`, the reader moves to the next attribute; otherwise, the position of the reader does not change.  
   
@@ -2037,7 +2037,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -2097,7 +2097,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -2144,7 +2144,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
  This property is relevant to `Element` and `Attribute` nodes only.  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -2199,7 +2199,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  All node and attribute names returned from <xref:System.Xml.XmlValidatingReader> are atomized by using the `NameTable`. When the same name is returned multiple times (for example, `Customer`), the same `String` object will be returned for that name. This makes it possible for you to write efficient code that does object comparisons on these strings instead of expensive string comparisons.  
   
@@ -2248,7 +2248,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property never returns the following `XmlNodeType` types: `Document`, `DocumentFragment`, `Entity`, or `Notation`.  
   
@@ -2309,7 +2309,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -2364,7 +2364,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
  This property applies only to an attribute node.  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -2412,7 +2412,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  When a reader is first created and initialized, there is no information available. You must call `Read` to read the first node.  
   
@@ -2479,7 +2479,7 @@ If the reader is positioned on a `DocumentType` node, this method can be used to
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method after calling <xref:System.Xml.XmlValidatingReader.MoveToAttribute%2A> to read through the text or entity reference nodes that make up the attribute value. The <xref:System.Xml.XmlReader.Depth%2A> of the attribute value nodes is one plus the depth of the attribute node. The `Depth` increments and decrements by one when you step into and out of general entity references.  
   
@@ -2570,7 +2570,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
   
  This method streams the content, decodes the Base64 content, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2642,7 +2642,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page. 
   
  This method streams the content, decodes the BinHex content, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text.  
   
@@ -2715,7 +2715,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the element content, decodes it using Base64 encoding, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2785,7 +2785,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the element content, decodes it using BinHex encoding, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer.  
   
@@ -2848,7 +2848,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property allows the user to access properties specific to the supplied reader. It returns a typed `XmlReader`. The user should query for the type before casting.  
   
@@ -2898,7 +2898,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -2950,7 +2950,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  If positioned on an element, `ReadString` concatenates all text, significant white space, white space, and CDATA section node types together and returns the concatenated data as the element content. The reader stops when any markup is encountered, including comments and processing instructions. This could occur in a mixed content model, or when an element end tag is read.  
   
@@ -3022,7 +3022,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  For example, if the schema type is defined as `xsd:int`, the runtime type `int32` is returned for the object. This can be tested using the <xref:System.Object.GetType%2A> method and cast accordingly. The <xref:System.Xml.XmlValidatingReader.ReadTypedValue%2A> method always returns a type that is derived from the <xref:System.Object> class. It never returns the <xref:System.Object> type.  
   
@@ -3097,7 +3097,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  If the reader is positioned on an `EntityReference` node (`XmlNodeType.EntityReference`), if <xref:System.Xml.XmlValidatingReader.Read%2A> is called after calling this method, the entity replacement text is parsed. After the entity replacement text is finished, an `EndEntity` node is returned to close the entity reference scope.  
   
@@ -3163,7 +3163,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  The `XmlSchemaCollection` holds pre-loaded XML-Data Reduced (XDR) and XML Schema definition language (XSD) schemas. This property gives the reader access to the cache of schemas and allows it to validate without having to re-load schemas every time. The reader does not add anything to the `XmlSchemaCollection`.  
   
@@ -3251,7 +3251,7 @@ reader.MoveToAttribute("name");
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  The user needs to test for the returned type. For example,  
   
@@ -3564,7 +3564,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  These events occur during <xref:System.Xml.XmlValidatingReader.Read%2A> and only if a <xref:System.Xml.XmlValidatingReader.ValidationType%2A> of DTD, XDR, Schema, or Auto is specified.  
   
@@ -3639,7 +3639,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property must be set before the first call to <xref:System.Xml.XmlValidatingReader.Read%2A>. Setting this property to ValidationType.None creates a non-validating reader.  
   
@@ -3741,7 +3741,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -3800,7 +3800,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  This property represents the xml:lang scope within which the current node resides. For example, here is an XML fragment with `xml:lang` set to U.S. English in the root element:  
   
@@ -3858,7 +3858,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  The `XmlResolver` is used to load any DTDs, entities, or schemas needed to complete the validation process.  
   
@@ -3939,7 +3939,7 @@ object obj = vreader.SchemaType;
 ## Remarks  
   
 > [!NOTE]
->  The <xref:System.Xml.XmlValidatingReader> class is obsolete in [!INCLUDE[dnprdnext](~/includes/dnprdnext-md.md)]. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
+>  The <xref:System.Xml.XmlValidatingReader> class is obsolete in .NET Framework 2.0. You can create a validating <xref:System.Xml.XmlReader> instance by using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. For more information, see the Remarks section of the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>

From 6622a10e35ef03039f6e1ee0ceee3fcb9b4e92b9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:00:50 -0800
Subject: [PATCH 010/236] dnprdnlong

---
 .../SecurityUtilities.xml                                 | 2 +-
 xml/System.CodeDom.Compiler/CodeDomProvider.xml           | 6 +++---
 xml/System.CodeDom.Compiler/ICodeCompiler.xml             | 2 +-
 xml/System.CodeDom.Compiler/ICodeGenerator.xml            | 2 +-
 xml/System.Collections/ArrayList.xml                      | 4 ++--
 xml/System.Collections/DictionaryEntry.xml                | 2 +-
 xml/System.Diagnostics/PerformanceCounter.xml             | 2 +-
 xml/System.Diagnostics/PerformanceCounterCategory.xml     | 6 +++---
 xml/System.DirectoryServices/DirectoryEntry.xml           | 2 +-
 xml/System.Drawing/Font.xml                               | 2 +-
 xml/System.Reflection.Emit/DynamicMethod.xml              | 6 +++---
 xml/System.Security.Cryptography/HMACSHA384.xml           | 4 ++--
 xml/System.Security.Cryptography/HMACSHA512.xml           | 4 ++--
 .../ReflectionPermissionFlag.xml                          | 2 +-
 xml/System.Web.Compilation/BuildManager.xml               | 6 +++---
 xml/System.Windows.Forms/AccessibleStates.xml             | 2 +-
 xml/System.Windows.Forms/Application.xml                  | 6 +++---
 xml/System.Windows.Forms/ButtonBase.xml                   | 2 +-
 xml/System.Windows.Forms/CheckedListBox.xml               | 2 +-
 xml/System.Windows.Forms/ContainerControl.xml             | 2 +-
 xml/System.Windows.Forms/GroupBox.xml                     | 2 +-
 xml/System.Windows.Forms/Label.xml                        | 2 +-
 xml/System.Windows.Forms/LinkLabel.xml                    | 2 +-
 xml/System.Windows.Forms/PropertyGrid.xml                 | 2 +-
 xml/System.Windows.Forms/TabControl.xml                   | 8 ++++----
 xml/System.Windows.Forms/TreeView.xml                     | 2 +-
 xml/ns-System.Web.ClientServices.Providers.xml            | 2 +-
 xml/ns-System.Web.ClientServices.xml                      | 2 +-
 28 files changed, 44 insertions(+), 44 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/SecurityUtilities.xml b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/SecurityUtilities.xml
index b0e141d6a72..7af019892d9 100644
--- a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/SecurityUtilities.xml
+++ b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/SecurityUtilities.xml
@@ -254,7 +254,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This overload of the method calls SignTool.exe and therefore requires the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to be installed.  
+ This overload of the method calls SignTool.exe and therefore requires the .NET Framework 2.0 to be installed.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.CodeDom.Compiler/CodeDomProvider.xml b/xml/System.CodeDom.Compiler/CodeDomProvider.xml
index bdb3c6a6fee..be763757d20 100644
--- a/xml/System.CodeDom.Compiler/CodeDomProvider.xml
+++ b/xml/System.CodeDom.Compiler/CodeDomProvider.xml
@@ -67,7 +67,7 @@
  ]]></format>
     </remarks>
     <block subset="none" type="overrides">
-      <para>In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <see cref="T:System.CodeDom.Compiler.CodeDomProvider" />, <see cref="T:System.CodeDom.Compiler.ICodeGenerator" />, <see cref="T:System.CodeDom.Compiler.ICodeParser" />, and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" />. In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator" />, <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateParser" />, and <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler" /> methods are obsolete, and the methods of <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> are directly available in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class. You should override those methods in your code provider implementation and not call the base methods.</para>
+      <para>In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <see cref="T:System.CodeDom.Compiler.CodeDomProvider" />, <see cref="T:System.CodeDom.Compiler.ICodeGenerator" />, <see cref="T:System.CodeDom.Compiler.ICodeParser" />, and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" />. In the .NET Framework 2.0, the <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator" />, <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateParser" />, and <see cref="M:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler" /> methods are obsolete, and the methods of <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> and <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> are directly available in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class. You should override those methods in your code provider implementation and not call the base methods.</para>
     </block>
     <altmember cref="T:System.CodeDom.Compiler.CompilerInfo" />
     <altmember cref="T:Microsoft.CSharp.CSharpCodeProvider" />
@@ -332,7 +332,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], you should implement the <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
+          <para>In the .NET Framework 2.0, you should implement the <see cref="T:System.CodeDom.Compiler.ICodeCompiler" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
         </block>
       </Docs>
     </Member>
@@ -441,7 +441,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], you should implement the <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
+          <para>In the .NET Framework 2.0, you should implement the <see cref="T:System.CodeDom.Compiler.ICodeGenerator" /> members in the <see cref="T:System.CodeDom.Compiler.CodeDomProvider" /> class and throw a <see cref="T:System.NotSupportedException" /> when this method is called.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System.CodeDom.Compiler/ICodeCompiler.xml b/xml/System.CodeDom.Compiler/ICodeCompiler.xml
index 44fd3123442..8603e4d7cc1 100644
--- a/xml/System.CodeDom.Compiler/ICodeCompiler.xml
+++ b/xml/System.CodeDom.Compiler/ICodeCompiler.xml
@@ -28,7 +28,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <xref:System.CodeDom.Compiler.CodeDomProvider>, <xref:System.CodeDom.Compiler.ICodeGenerator>, <xref:System.CodeDom.Compiler.ICodeParser>, and <xref:System.CodeDom.Compiler.ICodeCompiler>. In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.  
+>  In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <xref:System.CodeDom.Compiler.CodeDomProvider>, <xref:System.CodeDom.Compiler.ICodeGenerator>, <xref:System.CodeDom.Compiler.ICodeParser>, and <xref:System.CodeDom.Compiler.ICodeCompiler>. In the .NET Framework 2.0, the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.  
   
  The <xref:System.CodeDom.Compiler.ICodeCompiler> interface can be implemented for a specific compiler to enable developers to programmatically compile assemblies from Code Document Object Model (CodeDOM) compile units, strings containing source code, or source code files.  
   
diff --git a/xml/System.CodeDom.Compiler/ICodeGenerator.xml b/xml/System.CodeDom.Compiler/ICodeGenerator.xml
index 48d5aac1503..ea4f0b5a6f8 100644
--- a/xml/System.CodeDom.Compiler/ICodeGenerator.xml
+++ b/xml/System.CodeDom.Compiler/ICodeGenerator.xml
@@ -28,7 +28,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <xref:System.CodeDom.Compiler.CodeDomProvider>, <xref:System.CodeDom.Compiler.ICodeGenerator>, <xref:System.CodeDom.Compiler.ICodeParser>, and <xref:System.CodeDom.Compiler.ICodeCompiler>. In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.  
+>  In the .NET Framework versions 1.0 and 1.1, code providers consist of implementations of <xref:System.CodeDom.Compiler.CodeDomProvider>, <xref:System.CodeDom.Compiler.ICodeGenerator>, <xref:System.CodeDom.Compiler.ICodeParser>, and <xref:System.CodeDom.Compiler.ICodeCompiler>. In the .NET Framework 2.0, the <xref:System.CodeDom.Compiler.CodeDomProvider.CreateGenerator%2A>, <xref:System.CodeDom.Compiler.CodeDomProvider.CreateParser%2A>, and <xref:System.CodeDom.Compiler.CodeDomProvider.CreateCompiler%2A> methods are obsolete, and the methods of <xref:System.CodeDom.Compiler.ICodeGenerator> and <xref:System.CodeDom.Compiler.ICodeCompiler> are directly available in the <xref:System.CodeDom.Compiler.CodeDomProvider> class. You should override those methods in your code provider implementation and not call the base methods.  
   
  Developers of compilers can implement this interface to allow people to dynamically generate code in a particular language. This can be used for a variety of purposes, such as creating code-generating wizards, creating dynamic assemblies with content that can be debugged, and for templated documents with embedded code, such as ASP.NET.  
   
diff --git a/xml/System.Collections/ArrayList.xml b/xml/System.Collections/ArrayList.xml
index 9249d986ad3..84be8c15323 100644
--- a/xml/System.Collections/ArrayList.xml
+++ b/xml/System.Collections/ArrayList.xml
@@ -374,7 +374,7 @@
  This method is an `O(1)` operation.  
   
 ## Version Compatibility  
- In the .NET Framework version 1.0 and 1.1, calling the <xref:System.Collections.ArrayList.GetEnumerator%28System.Int32%2CSystem.Int32%29> method overload on the <xref:System.Collections.ArrayList> wrapper returned an enumerator that treated the second argument as an upper bound rather than as a count. In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] the second argument is correctly treated as a count.  
+ In the .NET Framework version 1.0 and 1.1, calling the <xref:System.Collections.ArrayList.GetEnumerator%28System.Int32%2CSystem.Int32%29> method overload on the <xref:System.Collections.ArrayList> wrapper returned an enumerator that treated the second argument as an upper bound rather than as a count. In the .NET Framework 2.0 the second argument is correctly treated as a count.  
   
  ]]></format>
         </remarks>
@@ -1724,7 +1724,7 @@
  This method is an `O(1)` operation.  
   
 ## Version Compatibility  
- In the .NET Framework versions 1.0 and 1.1, the enumerator for an <xref:System.Collections.ArrayList> wrapper returned by the <xref:System.Collections.ArrayList.Adapter%2A> method treated the second argument as an upper bound rather than as a count. In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] the second argument is correctly treated as a count.  
+ In the .NET Framework versions 1.0 and 1.1, the enumerator for an <xref:System.Collections.ArrayList> wrapper returned by the <xref:System.Collections.ArrayList.Adapter%2A> method treated the second argument as an upper bound rather than as a count. In the .NET Framework 2.0 the second argument is correctly treated as a count.  
   
    
   
diff --git a/xml/System.Collections/DictionaryEntry.xml b/xml/System.Collections/DictionaryEntry.xml
index fecb41076c3..32ed390f53e 100644
--- a/xml/System.Collections/DictionaryEntry.xml
+++ b/xml/System.Collections/DictionaryEntry.xml
@@ -126,7 +126,7 @@ The <xref:System.Collections.IDictionaryEnumerator.Entry%2A?displayProperty=name
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] `key` can be `null`.  
+ In the .NET Framework 2.0 `key` can be `null`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Diagnostics/PerformanceCounter.xml b/xml/System.Diagnostics/PerformanceCounter.xml
index 83d7623c5c6..ecabe424ebd 100644
--- a/xml/System.Diagnostics/PerformanceCounter.xml
+++ b/xml/System.Diagnostics/PerformanceCounter.xml
@@ -83,7 +83,7 @@
  To obtain performance data for counters that required an initial or previous value for performing the necessary calculation, call the <xref:System.Diagnostics.PerformanceCounter.NextValue%2A> method twice and use the information returned as your application requires.  
   
 > [!NOTE]
->  Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry. For more information about the file mapping size, see [&lt;performanceCounters&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/performancecounters-element).  
+>  Performance counter categories installed with the .NET Framework 2.0 use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry. For more information about the file mapping size, see [&lt;performanceCounters&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/performancecounters-element).  
   
    
   
diff --git a/xml/System.Diagnostics/PerformanceCounterCategory.xml b/xml/System.Diagnostics/PerformanceCounterCategory.xml
index 2c7f6ae005e..5b607f84d17 100644
--- a/xml/System.Diagnostics/PerformanceCounterCategory.xml
+++ b/xml/System.Diagnostics/PerformanceCounterCategory.xml
@@ -49,7 +49,7 @@
 >  It is strongly recommended that new performance counter categories be created during the installation of the application, not during the execution of the application. This allows time for the operating system to refresh its list of registered performance counter categories. If the list has not been refreshed, the attempt to use the category will fail.  
   
 > [!NOTE]
->  Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry. For more information about the file mapping size, see [&lt;performanceCounters&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/performancecounters-element).  
+>  Performance counter categories installed with the .NET Framework 2.0 use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry. For more information about the file mapping size, see [&lt;performanceCounters&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/performancecounters-element).  
   
    
   
@@ -737,7 +737,7 @@
 ## Remarks  
  The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the  .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the .NET Framework 2.0, the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
   
- Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory.  You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
+ Performance counter categories installed with the .NET Framework 2.0 use separate shared memory, with each performance counter category having its own memory.  You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
   
 > [!NOTE]
 >  It is strongly recommended that new performance counter categories be created during the installation of the application, not during the execution of the application. This allows time for the operating system to refresh its list of registered performance counter categories. If the list has not been refreshed, the attempt to use the category will fail.  
@@ -931,7 +931,7 @@
 ## Remarks  
  The `categoryType` parameter specifies whether the performance counter category is single-instance or multi-instance. By default, a category is single-instance when it is created and becomes multi-instance when another instance is added. Categories are created when an application is set up, and instances are added at run time. In the .NET Framework versions 1.0 and 1.1, it is not necessary to know if a performance counter category is multi-instance or single-instance. In the .NET Framework 2.0, the <xref:System.Diagnostics.PerformanceCounterCategoryType> enumeration is used to indicate whether a performance counter can have multiple instances.  
   
- Performance counter categories installed with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
+ Performance counter categories installed with the .NET Framework 2.0 use separate shared memory, with each performance counter category having its own memory. You can specify the size of separate shared memory by creating a DWORD named FileMappingSize in the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\\*\<category name>*\Performance. The FileMappingSize value is set to the shared memory size of the category. The default size is 131072 decimal. If the FileMappingSize value is not present, the `fileMappingSize` attribute value for the `performanceCounters` element specified in the Machine.config file is used, causing additional overhead for configuration file processing. You can realize a performance improvement for application startup by setting the file mapping size in the registry.  
   
 > [!NOTE]
 >  It is strongly recommended that new performance counter categories be created during the installation of the application, not during the execution of the application. This allows time for the operating system to refresh its list of registered performance counter categories. If the list has not been refreshed, the attempt to use the category will fail.  
diff --git a/xml/System.DirectoryServices/DirectoryEntry.xml b/xml/System.DirectoryServices/DirectoryEntry.xml
index 8f7153aff3c..83d1a385557 100644
--- a/xml/System.DirectoryServices/DirectoryEntry.xml
+++ b/xml/System.DirectoryServices/DirectoryEntry.xml
@@ -310,7 +310,7 @@ int main()
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Prior to [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the default value is <xref:System.DirectoryServices.AuthenticationTypes.None>. Beginning with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the default value is <xref:System.DirectoryServices.AuthenticationTypes.Secure>.  
+ Prior to .NET Framework 2.0, the default value is <xref:System.DirectoryServices.AuthenticationTypes.None>. Beginning with .NET Framework 2.0, the default value is <xref:System.DirectoryServices.AuthenticationTypes.Secure>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Drawing/Font.xml b/xml/System.Drawing/Font.xml
index 53bba7cb3df..d8a6ab2ff67 100644
--- a/xml/System.Drawing/Font.xml
+++ b/xml/System.Drawing/Font.xml
@@ -134,7 +134,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For localized applications that are based on the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] and earlier releases, specifying a font for `prototype` when that font has not been installed on the computer that is used to build your application will cause the Microsoft Sans Serif font to be used instead. If your application depends on this behavior and you must recompile your application for the .NET Framework 3.0, you should specify the Microsoft Sans Serif font for `prototype`.  
+ For localized applications that are based on the .NET Framework 2.0 and earlier releases, specifying a font for `prototype` when that font has not been installed on the computer that is used to build your application will cause the Microsoft Sans Serif font to be used instead. If your application depends on this behavior and you must recompile your application for the .NET Framework 3.0, you should specify the Microsoft Sans Serif font for `prototype`.  
   
    
   
diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index de4e55dfcd5..d56ec7421b0 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -78,10 +78,10 @@
   
  Dynamic methods and their parameters do not have to be named, but you can specify names to assist in debugging. Custom attributes are not supported on dynamic methods or their parameters.  
   
- Although dynamic methods are `static` methods (`Shared` methods in Visual Basic), the relaxed rules for delegate binding introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] allow a dynamic method to be bound to an object, so that it acts like an instance method when called using that delegate instance. An example that demonstrates this is provided for the <xref:System.Reflection.Emit.DynamicMethod.CreateDelegate%28System.Type%2CSystem.Object%29> method overload.  
+ Although dynamic methods are `static` methods (`Shared` methods in Visual Basic), the relaxed rules for delegate binding introduced in the .NET Framework 2.0 allow a dynamic method to be bound to an object, so that it acts like an instance method when called using that delegate instance. An example that demonstrates this is provided for the <xref:System.Reflection.Emit.DynamicMethod.CreateDelegate%28System.Type%2CSystem.Object%29> method overload.  
   
 > [!NOTE]
->  In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], dynamic methods do not support symbol information, that is, local variable names and line-number mapping. This limitation might be removed in a future version. You can use <xref:System.Reflection.Emit.AssemblyBuilder> during development to simplify debugging the generated Microsoft intermediate language (MSIL), and then switch to dynamic methods during final deployment, because the <xref:System.Reflection.Emit.ILGenerator> calls are the same in both cases.  
+>  In the .NET Framework 2.0, dynamic methods do not support symbol information, that is, local variable names and line-number mapping. This limitation might be removed in a future version. You can use <xref:System.Reflection.Emit.AssemblyBuilder> during development to simplify debugging the generated Microsoft intermediate language (MSIL), and then switch to dynamic methods during final deployment, because the <xref:System.Reflection.Emit.ILGenerator> calls are the same in both cases.  
   
 ## Verification  
  The following list summarizes the conditions under which dynamic methods can contain unverifiable code. (For example, a dynamic method is unverifiable if its <xref:System.Reflection.Emit.DynamicMethod.InitLocals%2A> property is set to `false`.)  
@@ -439,7 +439,7 @@
  The example code creates an instance of `Example` and then creates two delegates. The first is of type `UseLikeStatic`, which has the same parameters as the dynamic method. The second is of type `UseLikeInstance`, which lacks the first parameter (of type `Example`). This delegate is created using the <xref:System.Reflection.Emit.DynamicMethod.CreateDelegate%28System.Type%2CSystem.Object%29> method overload; the second parameter of that method overload is an instance of `Example`, in this case the instance just created, which is bound to the newly created delegate. Whenever that delegate is invoked, the dynamic method acts on the bound instance of `Example`.  
   
 > [!NOTE]
->  This is an example of the relaxed rules for delegate binding introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], along with new overloads of the <xref:System.Delegate.CreateDelegate%2A?displayProperty=nameWithType> method. For more information, see the <xref:System.Delegate> class.  
+>  This is an example of the relaxed rules for delegate binding introduced in the .NET Framework 2.0, along with new overloads of the <xref:System.Delegate.CreateDelegate%2A?displayProperty=nameWithType> method. For more information, see the <xref:System.Delegate> class.  
   
  The `UseLikeStatic` delegate is invoked, passing in the instance of `Example` that is bound to the `UseLikeInstance` delegate. Then the `UseLikeInstance` delegate is invoked, so that both delegates act on the same instance of `Example`. The changes in the values of the internal field are displayed after each call. Finally, a `UseLikeInstance` delegate is bound to an instance of `DerivedFromExample`, and the delegate calls are repeated.  
   
diff --git a/xml/System.Security.Cryptography/HMACSHA384.xml b/xml/System.Security.Cryptography/HMACSHA384.xml
index dc565f27d97..c415ae566db 100644
--- a/xml/System.Security.Cryptography/HMACSHA384.xml
+++ b/xml/System.Security.Cryptography/HMACSHA384.xml
@@ -455,12 +455,12 @@
       <Docs>
         <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA384" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation of the algorithm.</summary>
         <value>
-          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of the <xref:System.Security.Cryptography.HMACSHA384.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA384> object produces values that match the values produced by the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)]. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
+ The purpose of the <xref:System.Security.Cryptography.HMACSHA384.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA384> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
   
 ```csharp
 public static void Test()
diff --git a/xml/System.Security.Cryptography/HMACSHA512.xml b/xml/System.Security.Cryptography/HMACSHA512.xml
index 0009697666f..84849dbf24b 100644
--- a/xml/System.Security.Cryptography/HMACSHA512.xml
+++ b/xml/System.Security.Cryptography/HMACSHA512.xml
@@ -455,12 +455,12 @@
       <Docs>
         <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA512" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation.</summary>
         <value>
-          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of the <xref:System.Security.Cryptography.HMACSHA512.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA512> object produces values that match the values produced by the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)]. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
+ The purpose of the <xref:System.Security.Cryptography.HMACSHA512.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA512> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
   
 ```csharp
 public static void Test()
diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
index 2be7863e7d4..7bd3ddee7f0 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
@@ -63,7 +63,7 @@
   
  Starting with the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)], the `ReflectionEmit` flag is no longer required to emit code, unless debug symbols are emitted. To use this feature, your application should target the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] or later.  
   
- Starting with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the `TypeInformation` flag is no longer required to reflect on nonpublic types and members; the flag has been marked obsolete.  
+ Starting with the .NET Framework 2.0, the `TypeInformation` flag is no longer required to reflect on nonpublic types and members; the flag has been marked obsolete.  
   
    
   
diff --git a/xml/System.Web.Compilation/BuildManager.xml b/xml/System.Web.Compilation/BuildManager.xml
index e558d6f2c76..a6461c0f399 100644
--- a/xml/System.Web.Compilation/BuildManager.xml
+++ b/xml/System.Web.Compilation/BuildManager.xml
@@ -760,11 +760,11 @@
  If the Web site does have a Web.config file, ASP.NET determines the target framework by examining the Web.config file.  
   
 ## Web Sites that Target the .NET Framework 2.0  
- Web applications that target the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] are compiled as if the target were the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)]. The build process does not differentiate between the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] and the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], this property returns a target framework moniker that indicates the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)].  
+ Web applications that target the .NET Framework 2.0 are compiled as if the target were the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)]. The build process does not differentiate between the .NET Framework 2.0 and the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)].  
   
- This normally will not cause any problems. Visual Studio prevents you from creating references to [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] features in a project that is targeted for the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)]. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], because WCF was introduced with the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and is not compatible with the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)].  
+ This normally will not cause any problems. Visual Studio prevents you from creating references to [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] features in a project that is targeted for the .NET Framework 2.0. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for .NET Framework 2.0, because WCF was introduced with the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and is not compatible with the .NET Framework 2.0.  
   
- If you plan to deploy a Web site in a [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] run-time environment and you use a tool other than Visual Studio to reference features that are compatible only with [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)], the project might build without generating errors or warnings. However, the application might generate errors when the Web site runs on the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)].  
+ If you plan to deploy a Web site in a .NET Framework 2.0 run-time environment and you use a tool other than Visual Studio to reference features that are compatible only with [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)], the project might build without generating errors or warnings. However, the application might generate errors when the Web site runs on the .NET Framework 2.0.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/AccessibleStates.xml b/xml/System.Windows.Forms/AccessibleStates.xml
index cecc60e1288..8ae28beb3b0 100644
--- a/xml/System.Windows.Forms/AccessibleStates.xml
+++ b/xml/System.Windows.Forms/AccessibleStates.xml
@@ -832,7 +832,7 @@
       </ReturnValue>
       <MemberValue>1073741823</MemberValue>
       <Docs>
-        <summary>A valid object. This property is deprecated in [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)].</summary>
+        <summary>A valid object. This property is deprecated in .NET Framework 2.0.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index 4306223861e..c4106dec4cb 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -592,7 +592,7 @@
 -   If one of more of the handlers cancels the event, then <xref:System.Windows.Forms.Application.Exit%2A> returns without further action. Otherwise, a <xref:System.Windows.Forms.Form.FormClosed> event is raised for every open form, then all running message loops and forms are closed.  
   
 > [!NOTE]
->  The <xref:System.Windows.Forms.Application.Exit%2A> method does not raise the <xref:System.Windows.Forms.Form.Closed> and <xref:System.Windows.Forms.Form.Closing> events, which are obsolete as of [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)].  
+>  The <xref:System.Windows.Forms.Application.Exit%2A> method does not raise the <xref:System.Windows.Forms.Form.Closed> and <xref:System.Windows.Forms.Form.Closing> events, which are obsolete as of .NET Framework 2.0.  
   
    
   
@@ -1509,11 +1509,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] graphics library. This change was made in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] because of performance and localization issues with [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
+ Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
  You should never call this method if your Windows Forms code is hosted in another application, such as Internet Explorer. Only call this method in stand-alone Windows Forms applications.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index 73e02f4db20..e23f0338814 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1649,7 +1649,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index 0d960086085..be1a5a3410c 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1701,7 +1701,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/ContainerControl.xml b/xml/System.Windows.Forms/ContainerControl.xml
index 5c892a5d339..fed6c72c60c 100644
--- a/xml/System.Windows.Forms/ContainerControl.xml
+++ b/xml/System.Windows.Forms/ContainerControl.xml
@@ -496,7 +496,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] and later, IME functionality is handled by the framework and native IME support for individual controls is disabled.  
+ In the .NET Framework 2.0 and later, IME functionality is handled by the framework and native IME support for individual controls is disabled.  
   
  A user control that derives from the <xref:System.Windows.Forms.ContainerControl> class can enable native IME support by overriding this property to return `true`. However, the application is then responsible for making sure that there are no conflicts between the native IME and the Windows Forms IME. This scenario is not supported.  
   
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index 46524337aa7..30e392a17f8 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1168,7 +1168,7 @@
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index 6323e287ca9..bf58a1c69ff 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2283,7 +2283,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index 99c722013eb..86f05faae83 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1706,7 +1706,7 @@
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index bdb51cfd03f..6dfa2581137 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3896,7 +3896,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/TabControl.xml b/xml/System.Windows.Forms/TabControl.xml
index eae4599daf4..e788a1e9220 100644
--- a/xml/System.Windows.Forms/TabControl.xml
+++ b/xml/System.Windows.Forms/TabControl.xml
@@ -66,7 +66,7 @@
   
 -   <xref:System.Windows.Forms.TabControl.DeselectTab%2A>  
   
- In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], you can respond when the current tab changes by handling one of the following events:  
+ In .NET Framework 2.0, you can respond when the current tab changes by handling one of the following events:  
   
 -   <xref:System.Windows.Forms.TabControl.Deselecting>  
   
@@ -78,7 +78,7 @@
   
  The tabs in a <xref:System.Windows.Forms.TabControl> are part of the <xref:System.Windows.Forms.TabControl>, but not parts of the individual <xref:System.Windows.Forms.TabPage> controls. Members of the <xref:System.Windows.Forms.TabPage> class, such as the <xref:System.Windows.Forms.Control.ForeColor%2A> property, affect only the client rectangle of the tab page, but not the tabs. Additionally, the <xref:System.Windows.Forms.Control.Hide%2A> method of the <xref:System.Windows.Forms.TabPage> will not hide the tab. To hide the tab, you must remove the <xref:System.Windows.Forms.TabPage> control from the <xref:System.Windows.Forms.TabControl.TabPages%2A?displayProperty=nameWithType> collection.  
   
- In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  The following events are not raised for the <xref:System.Windows.Forms.TabControl> class unless there is at least one <xref:System.Windows.Forms.TabPage> in the <xref:System.Windows.Forms.TabControl.TabPages%2A?displayProperty=nameWithType> collection: <xref:System.Windows.Forms.Control.Click?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.DoubleClick?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.MouseDown?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.MouseUp?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.MouseHover?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.MouseEnter?displayProperty=nameWithType>, <xref:System.Windows.Forms.Control.MouseLeave?displayProperty=nameWithType> and <xref:System.Windows.Forms.Control.MouseMove?displayProperty=nameWithType>. If there is at least one <xref:System.Windows.Forms.TabPage> in the collection, and the user interacts with the tab control's header (where the <xref:System.Windows.Forms.TabPage> names appear), the <xref:System.Windows.Forms.TabControl> raises the appropriate event. However, if the user interaction is within the <xref:System.Windows.Forms.Control.ClientRectangle%2A> of the tab page, the <xref:System.Windows.Forms.TabPage> raises the appropriate event.  
   
@@ -1663,7 +1663,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Enter> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Enter> event of the current <xref:System.Windows.Forms.TabPage>. In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
@@ -1852,7 +1852,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Leave> event of the current <xref:System.Windows.Forms.TabPage>. In [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)], the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
+ In .NET Framework 2.0, this method also raises the <xref:System.Windows.Forms.Control.Leave> event of the current <xref:System.Windows.Forms.TabPage>. In .NET Framework 2.0, the tab is considered part of the tab page for determining when the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> occur. In earlier versions of the .NET Framework, the <xref:System.Windows.Forms.Control.Enter> and <xref:System.Windows.Forms.Control.Leave> events of the <xref:System.Windows.Forms.TabPage> do not occur when focus enters or leaves a tab, but only when focus enters or leaves the client rectangle of the tab page.  
   
  Raising an event invokes the event handler through a delegate. For more information, see [Handling and Raising Events](/dotnet/standard/events/).  
   
diff --git a/xml/System.Windows.Forms/TreeView.xml b/xml/System.Windows.Forms/TreeView.xml
index 25fa094fccd..bb1766f4731 100644
--- a/xml/System.Windows.Forms/TreeView.xml
+++ b/xml/System.Windows.Forms/TreeView.xml
@@ -1947,7 +1947,7 @@ If you set the <xref:System.Windows.Forms.TreeView.ImageKey%2A> property, the <x
  If the <xref:System.Windows.Forms.ImageList> property value is anything other than `null`, all the tree nodes display the first <xref:System.Drawing.Image> stored in the <xref:System.Windows.Forms.ImageList>. You can specify which images from the list are displayed for selected and unselected nodes by setting the <xref:System.Windows.Forms.TreeView.ImageIndex%2A> and <xref:System.Windows.Forms.TreeView.SelectedImageIndex%2A> properties. Individual <xref:System.Windows.Forms.TreeNode> objects can specify which image is displayed by setting their <xref:System.Windows.Forms.TreeNode.ImageIndex%2A> and <xref:System.Windows.Forms.TreeNode.SelectedImageIndex%2A> properties. These individual settings will override the settings in the corresponding <xref:System.Windows.Forms.TreeView> properties.  
   
 > [!NOTE]
->  In the .NET Framework version 1.1, there is an issue that prevents images from appearing on <xref:System.Windows.Forms.TreeView> nodes when your application calls <xref:System.Windows.Forms.Application.EnableVisualStyles%2A?displayProperty=nameWithType>. To work around this issue, call <xref:System.Windows.Forms.Application.DoEvents%2A?displayProperty=nameWithType> in your `Main` method immediately after you call <xref:System.Windows.Forms.Application.EnableVisualStyles%2A>. This issue is fixed in the [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)].  
+>  In the .NET Framework version 1.1, there is an issue that prevents images from appearing on <xref:System.Windows.Forms.TreeView> nodes when your application calls <xref:System.Windows.Forms.Application.EnableVisualStyles%2A?displayProperty=nameWithType>. To work around this issue, call <xref:System.Windows.Forms.Application.DoEvents%2A?displayProperty=nameWithType> in your `Main` method immediately after you call <xref:System.Windows.Forms.Application.EnableVisualStyles%2A>. This issue is fixed in the .NET Framework 2.0.  
   
    
   
diff --git a/xml/ns-System.Web.ClientServices.Providers.xml b/xml/ns-System.Web.ClientServices.Providers.xml
index e2e453e5dc7..bf4b555766c 100644
--- a/xml/ns-System.Web.ClientServices.Providers.xml
+++ b/xml/ns-System.Web.ClientServices.Providers.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The classes in the <xref:System.Web.ClientServices.Providers> namespace include client application service providers that enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profile services. You can enable these services and specify client service providers in your application configuration file, and then access the services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
+ The classes in the <xref:System.Web.ClientServices.Providers> namespace include client application service providers that enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profile services. You can enable these services and specify client service providers in your application configuration file, and then access the services through existing .NET Framework 2.0 membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
 
  To access the login service, you can use either Windows or Forms authentication by specifying the <xref:System.Web.ClientServices.Providers.ClientWindowsAuthenticationMembershipProvider> or <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> in your application configuration. Windows authentication uses the identity supplied when a user logs in to the operating system. Forms authentication requires that you to retrieve login information from the user and pass it to the service. You can do this by specifying an <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider> implementation with your <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> configuration. The <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider.GetCredentials%2A?displayProperty=nameWithType> method returns a <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationCredentials> object that contains user login information. You can populate this object, for example, by displaying a login dialog box in the <xref:System.Web.ClientServices.Providers.IClientFormsAuthenticationCredentialsProvider.GetCredentials%2A> method.
 
diff --git a/xml/ns-System.Web.ClientServices.xml b/xml/ns-System.Web.ClientServices.xml
index 56f38703b7c..ff902713a99 100644
--- a/xml/ns-System.Web.ClientServices.xml
+++ b/xml/ns-System.Web.ClientServices.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The classes in the <xref:System.Web.ClientServices> namespace support the client application service providers in the <xref:System.Web.ClientServices.Providers> namespace. These service providers enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profiles services through existing [!INCLUDE[dnprdnlong](~/includes/dnprdnlong-md.md)] membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
+ The classes in the <xref:System.Web.ClientServices> namespace support the client application service providers in the <xref:System.Web.ClientServices.Providers> namespace. These service providers enable Windows-based applications to use the Microsoft Ajax authentication, roles, and profiles services through existing .NET Framework 2.0 membership, identity, and application settings infrastructures. The client service providers also support occasional connectivity by storing and retrieving user information in a local data cache when the application is offline. For more information, see [Client Application Services](/dotnet/framework/common-client-technologies/client-application-services).
 
  The <xref:System.Web.ClientServices.ClientFormsIdentity> and <xref:System.Web.ClientServices.ClientRolePrincipal> classes provide properties and methods related to a user's identity, role, and authentication state.
 

From 9a9017c4b0dbd223e8ed525afcf21a719df22dc7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:01:33 -0800
Subject: [PATCH 011/236] dnprdnshort

---
 .../ICscHostObject.xml                        |   8 +-
 .../IVbcHostObject.xml                        |   8 +-
 xml/Microsoft.Build.Tasks/Csc.xml             |   2 +-
 .../GenerateApplicationManifest.xml           |   8 +-
 .../GenerateManifestBase.xml                  |   4 +-
 .../GetFrameworkPath.xml                      |  10 +-
 .../GetFrameworkSdkPath.xml                   |   6 +-
 xml/Microsoft.Build.Tasks/MSBuild.xml         |   2 +-
 xml/Microsoft.Build.Tasks/ManagedCompiler.xml |   8 +-
 .../ToolLocationHelper.xml                    |   2 +-
 .../ADODC+BOFActionEnum.xml                   |   2 +-
 .../ADODC+EOFActionEnum.xml                   |   2 +-
 .../ADODC+ErrorDelegate.xml                   |   2 +-
 .../ADODC+FetchCompleteDelegate.xml           |   2 +-
 .../ADODC+FieldChangeCompleteDelegate.xml     |   2 +-
 .../ADODC+OrientationEnum.xml                 |   2 +-
 .../ADODC+RecordsetChangeCompleteDelegate.xml |   2 +-
 .../ADODC+WillChangeFieldDelegate.xml         |   2 +-
 .../ADODC+WillChangeRecordDelegate.xml        |   2 +-
 .../ADODC+WillChangeRecordsetDelegate.xml     |   2 +-
 .../ADODC+WillMoveDelegate.xml                |   2 +-
 .../ADODC.xml                                 |  86 ++++-----
 .../ADODCArray.xml                            | 144 +++++++-------
 .../BaseControlArray.xml                      |  48 ++---
 .../BaseOcxArray.xml                          |  52 ++---
 .../BindingCollectionEnumerator.xml           |   8 +-
 .../ButtonArray.xml                           | 138 +++++++-------
 .../CheckBoxArray.xml                         | 144 +++++++-------
 .../CheckedListBoxArray.xml                   | 146 +++++++-------
 .../ColorDialogArray.xml                      |  24 +--
 .../ComboBoxArray.xml                         | 166 ++++++++--------
 .../DBKINDENUM.xml                            |   2 +-
 .../DirListBox.xml                            |  50 ++---
 .../DirListBoxArray.xml                       | 128 ++++++-------
 .../DriveListBox.xml                          |  44 ++---
 .../DriveListBoxArray.xml                     | 136 ++++++-------
 .../FileListBoxArray.xml                      | 126 ++++++-------
 .../FontDialogArray.xml                       |  26 +--
 .../FormShowConstants.xml                     |   2 +-
 .../GroupBoxArray.xml                         | 118 ++++++------
 .../HScrollBarArray.xml                       | 116 ++++++------
 .../IAccessor.xml                             |  10 +-
 .../IChapteredRowset.xml                      |   6 +-
 .../IConnectionPoint.xml                      |  12 +-
 .../IEnumConnectionPoints.xml                 |  10 +-
 .../IEnumConnections.xml                      |  10 +-
 .../IRowPositionChange.xml                    |   4 +-
 .../IRowsetInfo.xml                           |   8 +-
 .../IRowsetNotify.xml                         |   8 +-
 .../ImageListArray.xml                        |  22 +--
 .../LabelArray.xml                            | 132 ++++++-------
 .../ListBoxArray.xml                          | 154 +++++++--------
 .../ListViewArray.xml                         | 178 +++++++++---------
 .../LoadResConstants.xml                      |   2 +-
 .../MBindingCollection.xml                    |  32 ++--
 .../MaskedTextBoxArray.xml                    | 152 +++++++--------
 .../MenuItemArray.xml                         |  32 ++--
 .../MouseButtonConstants.xml                  |   2 +-
 .../OpenFileDialogArray.xml                   |  26 +--
 .../PanelArray.xml                            | 138 +++++++-------
 .../PictureBoxArray.xml                       | 122 ++++++------
 .../PrintDialogArray.xml                      |  24 +--
 .../ProgressBarArray.xml                      | 114 +++++------
 .../RadioButtonArray.xml                      | 142 +++++++-------
 .../RichTextBoxArray.xml                      | 148 +++++++--------
 .../SRDescriptionAttribute.xml                |   6 +-
 .../SaveFileDialogArray.xml                   |  26 +--
 .../ScaleMode.xml                             |   2 +-
 .../ShiftConstants.xml                        |   2 +-
 .../StatusBarArray.xml                        | 134 ++++++-------
 .../StatusStripArray.xml                      | 150 +++++++--------
 .../TabControlArray.xml                       | 144 +++++++-------
 .../TextBoxArray.xml                          | 150 +++++++--------
 .../TimerArray.xml                            |  24 +--
 .../ToolBarArray.xml                          | 132 ++++++-------
 .../ToolStripArray.xml                        | 152 +++++++--------
 .../ToolStripMenuItemArray.xml                |  72 +++----
 .../TreeViewArray.xml                         | 166 ++++++++--------
 .../UNAME.xml                                 |   4 +-
 .../UpdateMode.xml                            |   2 +-
 .../VScrollBarArray.xml                       | 114 +++++------
 .../WebBrowserArray.xml                       |  70 +++----
 .../ZOrderConstants.xml                       |   2 +-
 xml/Microsoft.VisualBasic.Devices/Ports.xml   |   2 +-
 xml/Microsoft.VisualBasic.Logging/AspLog.xml  |   6 +-
 xml/Microsoft.VisualBasic.Logging/Log.xml     |   2 +-
 xml/Microsoft.VisualBasic/Collection.xml      |   2 +-
 .../AssemblyContextControlItem.xml            |   4 +-
 .../IMultiTargetingSupportService.xml         |   4 +-
 .../DesignerActionItem.xml                    |   2 +-
 ...DesignerActionListsChangedEventHandler.xml |   2 +-
 .../DesignerActionPropertyItem.xml            |   2 +-
 ...esignerActionUIStateChangeEventHandler.xml |   2 +-
 .../ViewTechnology.xml                        |   2 +-
 .../AsyncOperationManager.xml                 |   2 +-
 xml/System.ComponentModel/EditorAttribute.xml |   2 +-
 .../ICustomTypeDescriptor.xml                 |   2 +-
 .../TypeDescriptionProvider.xml               |   2 +-
 .../ClientSettingsSection.xml                 |   4 +-
 .../ConfigurationElement.xml                  |   6 +-
 .../ConfigurationProperty.xml                 |   4 +-
 .../ConfigurationSection.xml                  |  18 +-
 .../ConfigurationSectionGroup.xml             |   6 +-
 .../ExeConfigurationFileMap.xml               |   2 +-
 .../LocalFileSettingsProvider.xml             |   2 +-
 .../EntityConnectionStringBuilder.xml         |   4 +-
 .../EntityProviderFactory.xml                 |   2 +-
 xml/System.Data.Linq/DataContext.xml          |   6 +-
 xml/System.Data.SqlClient/SqlConnection.xml   |   2 +-
 xml/System.Drawing.Imaging/Metafile.xml       |   2 +-
 xml/System.Drawing/Image.xml                  |   2 +-
 .../EventArrivedEventArgs.xml                 |   2 +-
 .../EventArrivedEventHandler.xml              |   2 +-
 xml/System.Numerics/BigInteger.xml            |   2 +-
 xml/System.Reflection.Emit/DynamicMethod.xml  |   4 +-
 xml/System.Reflection/TypeAttributes.xml      |   4 +-
 .../IApplicationIdentifier.xml                |   4 +-
 xml/System.Runtime.Caching/ChangeMonitor.xml  |   2 +-
 xml/System.Runtime.Caching/MemoryCache.xml    |   2 +-
 xml/System.Runtime.Caching/ObjectCache.xml    |   4 +-
 .../CALLCONV.xml                              |   2 +-
 .../DataMemberAttribute.xml                   |   2 +-
 .../ExportOptions.xml                         |   2 +-
 .../ImportOptions.xml                         |   4 +-
 .../XsdDataContractExporter.xml               |   2 +-
 .../XsdDataContractImporter.xml               |   2 +-
 .../CngAlgorithm.xml                          |   2 +-
 .../CngAlgorithmGroup.xml                     |   2 +-
 .../CngKeyBlobFormat.xml                      |   2 +-
 .../CngProvider.xml                           |   2 +-
 .../ECDiffieHellman.xml                       |   4 +-
 xml/System.Security.Cryptography/ECDsa.xml    |   4 +-
 .../PrincipalPermissionMode.xml               |   2 +-
 .../SecurityContextSecurityToken.xml          |   2 +-
 xml/System.Threading/ReaderWriterLock.xml     |   2 +-
 xml/System.Threading/ReaderWriterLockSlim.xml |   2 +-
 xml/System.Web.Configuration/TrustSection.xml |   2 +-
 .../WebConfigurationFileMap.xml               |   2 +-
 .../DataPagerDesigner.xml                     |   2 +-
 .../ListViewDesigner.xml                      |   2 +-
 .../ScriptManagerDesigner.xml                 |   2 +-
 .../ScriptManagerProxyDesigner.xml            |   2 +-
 .../UpdatePanelDesigner.xml                   |   2 +-
 .../UpdatePanelTriggerCollectionEditor.xml    |   2 +-
 .../UpdateProgressDesigner.xml                |   2 +-
 xml/System.Web.UI.WebControls/DataPager.xml   |   2 +-
 .../DataPagerField.xml                        |   2 +-
 xml/System.Web.UI.WebControls/ListView.xml    |   2 +-
 .../SqlDataSourceView.xml                     |   2 +-
 .../ArrangedElementCollection.xml             |   2 +-
 xml/System.Windows.Forms/AccessibleObject.xml |   2 +-
 xml/System.Windows.Forms/Application.xml      |   2 +-
 xml/System.Windows.Forms/ButtonBase.xml       |   2 +-
 xml/System.Windows.Forms/CheckedListBox.xml   |   2 +-
 xml/System.Windows.Forms/Control.xml          |   6 +-
 xml/System.Windows.Forms/DataGridViewCell.xml |   4 +-
 xml/System.Windows.Forms/DataGridViewRow.xml  |   4 +-
 xml/System.Windows.Forms/Form.xml             |   2 +-
 xml/System.Windows.Forms/GroupBox.xml         |   2 +-
 xml/System.Windows.Forms/HtmlDocument.xml     |  12 +-
 xml/System.Windows.Forms/Label.xml            |   2 +-
 xml/System.Windows.Forms/LinkLabel.xml        |   2 +-
 xml/System.Windows.Forms/ListControl.xml      |   2 +-
 xml/System.Windows.Forms/ListView.xml         |  12 +-
 xml/System.Windows.Forms/MaskedTextBox.xml    |   2 +-
 xml/System.Windows.Forms/PropertyGrid.xml     |   2 +-
 xml/System.Windows.Forms/SplitContainer.xml   |   2 +-
 .../ToolStripOverflow.xml                     |   2 +-
 .../ToolStripOverflowButton.xml               |   2 +-
 .../CompileWorkflowTask.xml                   |   4 +-
 .../TypeProvider.xml                          |   8 +-
 .../WorkflowCompilerOptionsService.xml        |   4 +-
 .../IExtendedUIService2.xml                   |  12 +-
 .../WorkflowDesignerLoader.xml                |   4 +-
 .../RootedPathValidator.xml                   |   4 +-
 .../IXmlSerializable.xml                      |   2 +-
 xml/System.Xml.XPath/XPathItem.xml            |   6 +-
 xml/System.Xml/XmlNodeReader.xml              |  90 ++++-----
 xml/System.Xml/XmlTextReader.xml              |   8 +-
 xml/System.Xml/XmlValidatingReader.xml        |   4 +-
 xml/System/String.xml                         |   4 +-
 ...icrosoft.VisualBasic.Compatibility.VB6.xml |   2 +-
 xml/ns-System.Windows.Diagnostics.xml         |   2 +-
 183 files changed, 2517 insertions(+), 2517 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Hosting/ICscHostObject.xml b/xml/Microsoft.Build.Tasks.Hosting/ICscHostObject.xml
index dc69fd86d6e..7b00468a505 100644
--- a/xml/Microsoft.Build.Tasks.Hosting/ICscHostObject.xml
+++ b/xml/Microsoft.Build.Tasks.Hosting/ICscHostObject.xml
@@ -957,8 +957,8 @@
         <Parameter Name="linkResources" Type="Microsoft.Build.Framework.ITaskItem[]" />
       </Parameters>
       <Docs>
-        <param name="linkResources">The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to link to the output file.</param>
-        <summary>Creates links to the specified [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources in the output file; the resource files are not placed in the output file.</summary>
+        <param name="linkResources">The .NET Framework resources to link to the output file.</param>
+        <summary>Creates links to the specified .NET Framework resources in the output file; the resource files are not placed in the output file.</summary>
         <returns>
           <see langword="true" /> if the method was successful; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
@@ -1342,8 +1342,8 @@
         <Parameter Name="resources" Type="Microsoft.Build.Framework.ITaskItem[]" />
       </Parameters>
       <Docs>
-        <param name="resources">The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed into the output file.</param>
-        <summary>Specifies the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed into the output file.</summary>
+        <param name="resources">The .NET Framework resources to embed into the output file.</param>
+        <summary>Specifies the .NET Framework resources to embed into the output file.</summary>
         <returns>
           <see langword="true" /> if the method was successful; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml b/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
index 87f7ffa07be..66998f9545e 100644
--- a/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
+++ b/xml/Microsoft.Build.Tasks.Hosting/IVbcHostObject.xml
@@ -835,8 +835,8 @@
         <Parameter Name="linkResources" Type="Microsoft.Build.Framework.ITaskItem[]" />
       </Parameters>
       <Docs>
-        <param name="linkResources">The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to link to the output file.</param>
-        <summary>Creates links to the specified [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources in the output file; the resource files are not placed in the output file.</summary>
+        <param name="linkResources">The .NET Framework resources to link to the output file.</param>
+        <summary>Creates links to the specified .NET Framework resources in the output file; the resource files are not placed in the output file.</summary>
         <returns>
           <see langword="true" /> if the method was successful; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
@@ -1374,8 +1374,8 @@
         <Parameter Name="resources" Type="Microsoft.Build.Framework.ITaskItem[]" />
       </Parameters>
       <Docs>
-        <param name="resources">The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed into the output file.</param>
-        <summary>Specifies the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed into the output file.</summary>
+        <param name="resources">The .NET Framework resources to embed into the output file.</param>
+        <summary>Specifies the .NET Framework resources to embed into the output file.</summary>
         <returns>
           <see langword="true" /> if the method was successful; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/Microsoft.Build.Tasks/Csc.xml b/xml/Microsoft.Build.Tasks/Csc.xml
index c884aafb1b0..003300a187d 100644
--- a/xml/Microsoft.Build.Tasks/Csc.xml
+++ b/xml/Microsoft.Build.Tasks/Csc.xml
@@ -182,7 +182,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default base address for a DLL is set by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] common language runtime. For more information, see [/baseaddress (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/baseaddress-compiler-option).  
+ The default base address for a DLL is set by the .NET Framework common language runtime. For more information, see [/baseaddress (C# Compiler Options)](/dotnet/csharp/language-reference/compiler-options/baseaddress-compiler-option).  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
index 4a71d99cf8a..38003715b4e 100644
--- a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
@@ -315,7 +315,7 @@
         <ReturnType FrameworkAlternate="msbuild-15;msbuild-16;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8">Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a list of one or more file type that are associated with the ClickOnce deployment manifest. File associations only valid only when [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 3.5 or later is targeted.</summary>
+        <summary>Gets or sets a list of one or more file type that are associated with the ClickOnce deployment manifest. File associations only valid only when .NET Framework 3.5 or later is targeted.</summary>
         <value>A list of file types that are associated with the generated manifest.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
@@ -735,7 +735,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- For example, the value "5.1.2600.0" indicates that the operating system is Windows XP. If this property is not specified, the value "4.10.0.0" is used. This indicates Windows 98 Second Edition, which is the minimum supported operating system for the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].
+ For example, the value "5.1.2600.0" indicates that the operating system is Windows XP. If this property is not specified, the value "4.10.0.0" is used. This indicates Windows 98 Second Edition, which is the minimum supported operating system for the .NET Framework.
 
  If the task is generating a native manifest, this input is ignored.
 
@@ -1036,8 +1036,8 @@
         <ReturnType FrameworkAlternate="msbuild-15;msbuild-16;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8">System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the name of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] subset to target.</summary>
-        <value>The name of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] subset.</value>
+        <summary>Gets or sets the name of the .NET Framework subset to target.</summary>
+        <value>The name of the .NET Framework subset.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks/GenerateManifestBase.xml b/xml/Microsoft.Build.Tasks/GenerateManifestBase.xml
index ba4528d62a5..33a8521c494 100644
--- a/xml/Microsoft.Build.Tasks/GenerateManifestBase.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateManifestBase.xml
@@ -954,8 +954,8 @@
         <ReturnType FrameworkAlternate="msbuild-15;msbuild-16;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8">System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version for the project.</summary>
-        <value>A string that represents the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version.</value>
+        <summary>The target .NET Framework version for the project.</summary>
+        <value>A string that represents the .NET Framework version.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/Microsoft.Build.Tasks/GetFrameworkPath.xml b/xml/Microsoft.Build.Tasks/GetFrameworkPath.xml
index e9ca2d291f9..62a0f35d4c5 100644
--- a/xml/Microsoft.Build.Tasks/GetFrameworkPath.xml
+++ b/xml/Microsoft.Build.Tasks/GetFrameworkPath.xml
@@ -148,7 +148,7 @@
         <summary>
             Path to the v1.1 framework, if available
             </summary>
-        <value>The path of the folder that contains the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 1.1 assemblies.</value>
+        <value>The path of the folder that contains the .NET Framework 1.1 assemblies.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -186,7 +186,7 @@
         <summary>
             Path to the v2.0 framework, if available
             </summary>
-        <value>The path of the folder that contains the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0 assemblies.</value>
+        <value>The path of the folder that contains the .NET Framework 2.0 assemblies.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -224,7 +224,7 @@
         <summary>
             Path to the v3.0 framework, if available
             </summary>
-        <value>The path of the folder that contains the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 3.0 assemblies.</value>
+        <value>The path of the folder that contains the .NET Framework 3.0 assemblies.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -262,7 +262,7 @@
         <summary>
             Path to the v3.5 framework, if available
             </summary>
-        <value>The path of the folder that contains the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 3.5 assemblies.</value>
+        <value>The path of the folder that contains the .NET Framework 3.5 assemblies.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -637,7 +637,7 @@
         <summary>
             Path to the latest framework, whatever version it happens to be
             </summary>
-        <value>The path of the folder that contains the latest version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] assemblies.</value>
+        <value>The path of the folder that contains the latest version of the .NET Framework assemblies.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks/GetFrameworkSdkPath.xml b/xml/Microsoft.Build.Tasks/GetFrameworkSdkPath.xml
index f29ab94ec5e..ff8f0819858 100644
--- a/xml/Microsoft.Build.Tasks/GetFrameworkSdkPath.xml
+++ b/xml/Microsoft.Build.Tasks/GetFrameworkSdkPath.xml
@@ -146,7 +146,7 @@
         <summary>
             The path to the v2.0 .NET SDK if it could be found. It will be String.Empty if the SDK was not found.
             </summary>
-        <value>The path to the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0 SDK.</value>
+        <value>The path to the .NET Framework 2.0 SDK.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -184,7 +184,7 @@
         <summary>
             The path to the v3.5 .NET SDK if it could be found. It will be String.Empty if the SDK was not found.
             </summary>
-        <value>The path to the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 3.5 SDK.</value>
+        <value>The path to the .NET Framework 3.5 SDK.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -381,7 +381,7 @@
         <summary>
             The path to the latest .NET SDK if it could be found. It will be String.Empty if the SDK was not found.
             </summary>
-        <value>The path to the latest version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] SDK.</value>
+        <value>The path to the latest version of the .NET Framework SDK.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks/MSBuild.xml b/xml/Microsoft.Build.Tasks/MSBuild.xml
index a0f4dfae6dd..d6333a62677 100644
--- a/xml/Microsoft.Build.Tasks/MSBuild.xml
+++ b/xml/Microsoft.Build.Tasks/MSBuild.xml
@@ -683,7 +683,7 @@
         <summary>
             Value of ToolsVersion to use when building projects passed to this task.
             </summary>
-        <value>The target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version to build the project with.</value>
+        <value>The target .NET Framework version to build the project with.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/Microsoft.Build.Tasks/ManagedCompiler.xml b/xml/Microsoft.Build.Tasks/ManagedCompiler.xml
index 4c1d7aa6916..733ee98f686 100644
--- a/xml/Microsoft.Build.Tasks/ManagedCompiler.xml
+++ b/xml/Microsoft.Build.Tasks/ManagedCompiler.xml
@@ -675,8 +675,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resource files to link to the output file.</summary>
-        <value>The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resource files to link to the output file.</value>
+        <summary>Gets or sets the .NET Framework resource files to link to the output file.</summary>
+        <value>The .NET Framework resource files to link to the output file.</value>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
           <para>This class uses the <see cref="T:System.Security.Permissions.StrongNameIdentityPermissionAttribute" /> attribute and cannot be inherited.</para>
@@ -1032,8 +1032,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed in the output file.</summary>
-        <value>The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] resources to embed in the output file.</value>
+        <summary>Gets or sets the .NET Framework resources to embed in the output file.</summary>
+        <value>The .NET Framework resources to embed in the output file.</value>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
           <para>This class uses the <see cref="T:System.Security.Permissions.StrongNameIdentityPermissionAttribute" /> attribute and cannot be inherited.</para>
diff --git a/xml/Microsoft.Build.Utilities/ToolLocationHelper.xml b/xml/Microsoft.Build.Utilities/ToolLocationHelper.xml
index bc935871ce4..6b554105f44 100644
--- a/xml/Microsoft.Build.Utilities/ToolLocationHelper.xml
+++ b/xml/Microsoft.Build.Utilities/ToolLocationHelper.xml
@@ -419,7 +419,7 @@
             to target the .NET Framework SDK that ships with Visual Studio Dev11 or later, please use the override 
             that specifies a VisualStudioVersion. 
             </summary>
-        <returns>A string containing the name of the registry key value under the <see cref="M:Microsoft.Build.Utilities.ToolLocationHelper.GetDotNetFrameworkRootRegistryKey(Microsoft.Build.Utilities.TargetDotNetFrameworkVersion)" /> that contains the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] SDK installation path.</returns>
+        <returns>A string containing the name of the registry key value under the <see cref="M:Microsoft.Build.Utilities.ToolLocationHelper.GetDotNetFrameworkRootRegistryKey(Microsoft.Build.Utilities.TargetDotNetFrameworkVersion)" /> that contains the .NET Framework SDK installation path.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+BOFActionEnum.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+BOFActionEnum.xml
index cf9a3a2eda3..d4dce686491 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+BOFActionEnum.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+BOFActionEnum.xml
@@ -31,7 +31,7 @@
  These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+EOFActionEnum.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+EOFActionEnum.xml
index c50e68a7347..8d347443f4d 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+EOFActionEnum.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+EOFActionEnum.xml
@@ -31,7 +31,7 @@
  These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+ErrorDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+ErrorDelegate.xml
index 01311a0eb21..60c66b8c489 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+ErrorDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+ErrorDelegate.xml
@@ -47,7 +47,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FetchCompleteDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FetchCompleteDelegate.xml
index f891f6e82f2..35302cc6b3e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FetchCompleteDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FetchCompleteDelegate.xml
@@ -43,7 +43,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FieldChangeCompleteDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FieldChangeCompleteDelegate.xml
index f08e1bd3599..df7bb53a61a 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FieldChangeCompleteDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+FieldChangeCompleteDelegate.xml
@@ -47,7 +47,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+OrientationEnum.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+OrientationEnum.xml
index b26adfd6c83..75e4e41e9b8 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+OrientationEnum.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+OrientationEnum.xml
@@ -29,7 +29,7 @@
  In Visual Basic 6.0, the `Orientation` property was used to specify whether a `ADODataControl` was displayed with a horizontal or vertical orientation.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+RecordsetChangeCompleteDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+RecordsetChangeCompleteDelegate.xml
index e7b40e07e89..30b0c63cffb 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+RecordsetChangeCompleteDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+RecordsetChangeCompleteDelegate.xml
@@ -45,7 +45,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeFieldDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeFieldDelegate.xml
index a0c4991b597..11f754cfa13 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeFieldDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeFieldDelegate.xml
@@ -45,7 +45,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordDelegate.xml
index 852eca276de..c15b3ebc85c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordDelegate.xml
@@ -45,7 +45,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordsetDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordsetDelegate.xml
index c7b0d1c54a6..a9c8f3d33e4 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordsetDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillChangeRecordsetDelegate.xml
@@ -43,7 +43,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillMoveDelegate.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillMoveDelegate.xml
index 08a2d1b410a..ac2346c4037 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillMoveDelegate.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC+WillMoveDelegate.xml
@@ -43,7 +43,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC.xml
index ee1eb5f411c..1eee66ea1dd 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODC.xml
@@ -34,7 +34,7 @@
  Use this control in applications upgraded from Visual Basic 6.0 to continue to use an `ADO` data connection. For new development, you should consider using `ADO.NET` instead of `ADO`. For more information, see [Comparison of ADO.NET and ADO](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2008/904fck4k(v=vs.90)).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -63,7 +63,7 @@
  Provides compatibility with the Visual Basic 6.0 `ADO Data Control`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -108,7 +108,7 @@
  The `DataSourceListener` monitors a data set for data members that are added, removed, or changed when the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC> is connected to a data source.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -154,7 +154,7 @@
  Setting the `BackColor` property affects only the part of the control where text is displayed.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -200,7 +200,7 @@
  You can use the `BOF` and <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.EOF%2A> properties to determine whether an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> object contains rows or whether you have gone beyond the limits of an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> as you move from row to row.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -247,7 +247,7 @@
  Use this property to specify the behavior when the `MovePrevious` button is pressed and the first row of a <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> is the current row.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -296,7 +296,7 @@
  While you can change value during the life of the cursor, the change only affects the number of records in the cache after the next fetch from the data source.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
  After this period of time has elapsed without completing the command, the provider raises an exception to the calling application and cancels the command.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -394,7 +394,7 @@
  Setting this property optimizes the execution of the command.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -441,7 +441,7 @@
  Use the `ConnectionString` property to specify a data source by passing a detailed connection string that contains a series of argument = value statements separated by semicolons.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -488,7 +488,7 @@
  This property corresponds to the ADO `ConnectionTimeout` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -539,7 +539,7 @@
  This property corresponds to the ADO Command and Connection `CursorLocation` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -590,7 +590,7 @@
  Determines the cursor type to use when opening a <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -633,7 +633,7 @@
  When the disposing parameter is `true`, this method releases all resources held by any managed objects that this control references. This method invokes the `Dispose()` method of each referenced object.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -676,7 +676,7 @@
  An `EndOfRecordset` event may occur if the `MoveNext` operation fails.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -722,7 +722,7 @@
  You can use the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.BOF%2A> and `EOF` properties to determine whether an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> object contains rows or whether you have gone beyond the limits of an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> as you move from row to row.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -769,7 +769,7 @@
  Use this property to specify the behavior when the `MoveNext` button is pressed when the first row of a <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Recordset%2A> is the current row.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -802,7 +802,7 @@
  Use this event to handle exceptions that derive from the underlying OLE DB `DataSource`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -841,7 +841,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -880,7 +880,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -919,7 +919,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -997,7 +997,7 @@
  Used internally to return a count of data members for the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1037,7 +1037,7 @@
  Used internally to return the name of a data member for a <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1088,7 +1088,7 @@
  In order to maintain sufficient control over the data being updated, `ADO` provides a number of concurrency options that control how other users are granted, or refused access to the data being updated.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1135,7 +1135,7 @@
  This property corresponds to the ADO `Recordset.MaxRecords` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1186,7 +1186,7 @@
  This property corresponds to the ADO `Mode` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1225,7 +1225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1264,7 +1264,7 @@
  The `OnResize` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1318,7 +1318,7 @@
  This property corresponds to the ADO `Recordset.MaxRecords` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1361,7 +1361,7 @@
  This property setting is write-only. It may only be provided in code, it cannot be read back from the `Password` property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1400,7 +1400,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1447,7 +1447,7 @@
  By using the `Recordset` property, you can use the methods, properties, and events of the ADO `ADODB.Recordset` Object.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1486,7 +1486,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1533,7 +1533,7 @@
  The `RecordSource` contains both the name of a database table and a valid SQL string using syntax appropriate for the data source.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1570,7 +1570,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1615,7 +1615,7 @@
  The `DataSourceListener` monitors a data set for data members that are added, removed, or changed when the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC> is connected to a data source.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1670,7 +1670,7 @@
  Use this property to communicate information such as the number of the current record to the user.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1717,7 +1717,7 @@
  The user-name syntax depends on the data source. When a `UserName` and <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.Password%2A> are supplied, the control uses the values to create a connection string (<xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC.ConnectionString%2A> property).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1755,7 +1755,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1793,7 +1793,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1831,7 +1831,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1869,7 +1869,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODCArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODCArray.xml
index d74ebcb338e..6db7913d9bf 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODCArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ADODCArray.xml
@@ -42,7 +42,7 @@
  The `ADODCArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ADODC` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -86,7 +86,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODCArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODCArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -125,7 +125,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODCArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODCArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -160,7 +160,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -195,7 +195,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -230,7 +230,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -277,7 +277,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -312,7 +312,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -345,7 +345,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -382,7 +382,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -417,7 +417,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -450,7 +450,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -485,7 +485,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -520,7 +520,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -553,7 +553,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -586,7 +586,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -622,7 +622,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -658,7 +658,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -694,7 +694,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -730,7 +730,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -771,7 +771,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -824,7 +824,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -857,7 +857,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -896,7 +896,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -935,7 +935,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -974,7 +974,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1009,7 +1009,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1044,7 +1044,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1079,7 +1079,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1116,7 +1116,7 @@
  This method can be used to retrieve the index for the specified <xref:Microsoft.VisualBasic.Compatibility.VB6.ADODC>  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1151,7 +1151,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1187,7 +1187,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1225,7 +1225,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1258,7 +1258,7 @@
  This event is raised if the <xref:System.Windows.Forms.Control.ImeMode%2A> property is changed by either a programmatic modification or user interaction. For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1301,7 +1301,7 @@ MsgBox(CStr(ADODCArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1344,7 +1344,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1392,7 +1392,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1436,7 +1436,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1472,7 +1472,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1526,7 +1526,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1562,7 +1562,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1611,7 +1611,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1657,7 +1657,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1709,7 +1709,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1755,7 +1755,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1801,7 +1801,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1847,7 +1847,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1881,7 +1881,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1921,7 +1921,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1956,7 +1956,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1992,7 +1992,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2027,7 +2027,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2061,7 +2061,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2101,7 +2101,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2140,7 +2140,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2182,7 +2182,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2219,7 +2219,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2255,7 +2255,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2299,7 +2299,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  The `SetIndex` method should be called only when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2341,7 +2341,7 @@ MsgBox(CStr(ADODCArray(1).Text))
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2376,7 +2376,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2413,7 +2413,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2448,7 +2448,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2484,7 +2484,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2519,7 +2519,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2584,7 +2584,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2650,7 +2650,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2686,7 +2686,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2725,7 +2725,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2764,7 +2764,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2803,7 +2803,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2842,7 +2842,7 @@ MsgBox(CStr(ADODCArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseControlArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseControlArray.xml
index 056e7857500..1e8a9259f5c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseControlArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseControlArray.xml
@@ -34,7 +34,7 @@
  You do not typically inherit from `BaseControlArray`. To create your own control array, inherit from one of the control array classes in the `Microsoft.VisualBasic.Compatibility.VB6` namespace.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -72,7 +72,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this constructor is typically not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -105,7 +105,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this constructor is usually not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -143,7 +143,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this `Protected` method is usually not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -185,7 +185,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this `Protected` method is usually not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this `Protected` method is usually not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -266,7 +266,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. -  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this `Protected` method is usually not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -346,7 +346,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this `Protected` method is usually  not called directly but is instead called by a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -381,7 +381,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -413,7 +413,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -445,7 +445,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -481,7 +481,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -553,7 +553,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -584,7 +584,7 @@
  The <see cref="T:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray" /> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0. Because this class is not typically used to create an instance of the class, this <see langword="Protected" /> method is usually not called directly but is instead called by a derived class.  
   
  <block subset="none" type="note"><para>  
- Functions and objects in the <see cref="N:Microsoft.VisualBasic.Compatibility.VB6" /> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+ Functions and objects in the <see cref="N:Microsoft.VisualBasic.Compatibility.VB6" /> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
 </para></block></returns>
         <remarks>To be added.</remarks>
@@ -621,7 +621,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -659,7 +659,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -694,7 +694,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -730,7 +730,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -768,7 +768,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -804,7 +804,7 @@
  Design environments typically use this method to start the initialization of a component that is used on a form or used by another component. The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.System%23ComponentModel%23ISupportInitialize%23EndInit> method ends the initialization. Using the `BeginInit` and <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.System%23ComponentModel%23ISupportInitialize%23EndInit> methods prevents the control from being used before it is fully initialized. The initialization occurs at run time.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -840,7 +840,7 @@
  Design environments typically use this method to finish the initialization of a component that is used on a form or used by another component. The `EndInit` method ends the initialization. Using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.System%23ComponentModel%23ISupportInitialize%23BeginInit%2A> and `EndInit` methods prevents the control from being used before it is fully initialized. The initialization occurs at run time.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -876,7 +876,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -917,7 +917,7 @@
  The <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray> class is the base class for all control arrays that are used in applications upgraded from Visual Basic 6.0.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseOcxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseOcxArray.xml
index 0481335b74f..c4f2690c266 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseOcxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/BaseOcxArray.xml
@@ -30,7 +30,7 @@
  The `BaseOcxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 ActiveX control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -74,7 +74,7 @@
  When you instantiate a `BaseOcxArray`, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.BaseSetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -113,7 +113,7 @@
  When you instantiate a `BaseOcxArray`, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.BaseSetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -148,7 +148,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -182,7 +182,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -222,7 +222,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -256,7 +256,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -288,7 +288,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -320,7 +320,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -355,7 +355,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -388,7 +388,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -425,7 +425,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -478,7 +478,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -514,7 +514,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -548,7 +548,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -595,7 +595,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -628,7 +628,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -663,7 +663,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -698,7 +698,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -732,7 +732,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -769,7 +769,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -805,7 +805,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -840,7 +840,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -906,7 +906,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -972,7 +972,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1008,7 +1008,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/BindingCollectionEnumerator.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/BindingCollectionEnumerator.xml
index 0c3ea4999b0..f5e97a6412a 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/BindingCollectionEnumerator.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/BindingCollectionEnumerator.xml
@@ -38,7 +38,7 @@
  When an application is upgraded to Visual Basic, a `BindingCollectionEnumerator` is created to enable the `ADO`-related code.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -75,7 +75,7 @@
  When an application is upgraded to Visual Basic, a `BindingCollectionEnumerator` is created to enable the `ADO`-related code.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -114,7 +114,7 @@
  When an application is upgraded to Visual Basic, a `BindingCollectionEnumerator` is created to enable the `ADO`-related code.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
  When an application is upgraded to Visual Basic, a `BindingCollectionEnumerator` is created to enable the `ADO`-related code.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ButtonArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ButtonArray.xml
index ca53dd97550..7a771fb611f 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ButtonArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ButtonArray.xml
@@ -38,7 +38,7 @@
  The `ButtonArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `CommandButton` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ButtonArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ButtonArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ButtonArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ButtonArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -155,7 +155,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -190,7 +190,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -259,7 +259,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -294,7 +294,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.Button> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -409,7 +409,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -446,7 +446,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -480,7 +480,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -521,7 +521,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -555,7 +555,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -587,7 +587,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -689,7 +689,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -722,7 +722,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -758,7 +758,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -794,7 +794,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -830,7 +830,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -866,7 +866,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -919,7 +919,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -954,7 +954,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -989,7 +989,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1024,7 +1024,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1061,7 +1061,7 @@
  This method can be used to retrieve the index for the <xref:System.Windows.Forms.Form.AcceptButton%2A> or <xref:System.Windows.Forms.Form.CancelButton%2A>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1096,7 +1096,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1132,7 +1132,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1170,7 +1170,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1212,7 +1212,7 @@ MsgBox(CStr(ButtonArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1255,7 +1255,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1303,7 +1303,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1347,7 +1347,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1383,7 +1383,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1437,7 +1437,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1473,7 +1473,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1507,7 +1507,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1539,7 +1539,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1585,7 +1585,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1631,7 +1631,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1677,7 +1677,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1727,7 +1727,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1773,7 +1773,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1819,7 +1819,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1865,7 +1865,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1899,7 +1899,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1934,7 +1934,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1969,7 +1969,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2005,7 +2005,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2040,7 +2040,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2074,7 +2074,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2109,7 +2109,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2151,7 +2151,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2188,7 +2188,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2224,7 +2224,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2268,7 +2268,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2312,7 +2312,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  If the specified <xref:System.Windows.Forms.Button> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ButtonArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2347,7 +2347,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2384,7 +2384,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2419,7 +2419,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2455,7 +2455,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2490,7 +2490,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2525,7 +2525,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2590,7 +2590,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2656,7 +2656,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2692,7 +2692,7 @@ MsgBox(CStr(ButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckBoxArray.xml
index ce85d6f2d12..d7f6f9a90b0 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckBoxArray.xml
@@ -38,7 +38,7 @@
  The `CheckBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `CheckBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -190,7 +190,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -260,7 +260,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -294,7 +294,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -329,7 +329,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.CheckBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -444,7 +444,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -479,7 +479,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -514,7 +514,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -551,7 +551,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -585,7 +585,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -626,7 +626,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -660,7 +660,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -692,7 +692,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -724,7 +724,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -759,7 +759,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -794,7 +794,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -827,7 +827,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -863,7 +863,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -899,7 +899,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -935,7 +935,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -971,7 +971,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1024,7 +1024,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1059,7 +1059,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1094,7 +1094,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1129,7 +1129,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1166,7 +1166,7 @@
  This method can be used to retrieve the index for a <xref:System.Windows.Forms.CheckBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1201,7 +1201,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1237,7 +1237,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1275,7 +1275,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1317,7 +1317,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1360,7 +1360,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1408,7 +1408,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1452,7 +1452,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1488,7 +1488,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1542,7 +1542,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1578,7 +1578,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1612,7 +1612,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1644,7 +1644,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1692,7 +1692,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1738,7 +1738,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1784,7 +1784,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1834,7 +1834,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1880,7 +1880,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1926,7 +1926,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1972,7 +1972,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2006,7 +2006,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2041,7 +2041,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2076,7 +2076,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2112,7 +2112,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2147,7 +2147,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2181,7 +2181,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2216,7 +2216,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2258,7 +2258,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2295,7 +2295,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2331,7 +2331,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2375,7 +2375,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2419,7 +2419,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.CheckBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2454,7 +2454,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2491,7 +2491,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2526,7 +2526,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2562,7 +2562,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2597,7 +2597,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2632,7 +2632,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2697,7 +2697,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2763,7 +2763,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2799,7 +2799,7 @@ MsgBox(CStr(CheckBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckedListBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckedListBoxArray.xml
index 534796bf407..06e1b712b29 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckedListBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/CheckedListBoxArray.xml
@@ -38,7 +38,7 @@
  The `CheckedListBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `CheckedListBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckedListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckedListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckedListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckedListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.CheckedListBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -342,7 +342,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -417,7 +417,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -451,7 +451,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -483,7 +483,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -515,7 +515,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -585,7 +585,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -618,7 +618,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -651,7 +651,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -687,7 +687,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -723,7 +723,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -759,7 +759,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -795,7 +795,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -848,7 +848,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -883,7 +883,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -918,7 +918,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -950,7 +950,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -984,7 +984,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1018,7 +1018,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1053,7 +1053,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1090,7 +1090,7 @@
  This method can be used to retrieve the index for a <xref:System.Windows.Forms.CheckedListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1125,7 +1125,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1161,7 +1161,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1199,7 +1199,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1234,7 +1234,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1276,7 +1276,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1311,7 +1311,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1354,7 +1354,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1402,7 +1402,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1446,7 +1446,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1482,7 +1482,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1536,7 +1536,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1572,7 +1572,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1606,7 +1606,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1638,7 +1638,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1686,7 +1686,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1742,7 +1742,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1791,7 +1791,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1841,7 +1841,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1895,7 +1895,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1941,7 +1941,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1987,7 +1987,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2033,7 +2033,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2067,7 +2067,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2102,7 +2102,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2137,7 +2137,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2172,7 +2172,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2208,7 +2208,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2243,7 +2243,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2285,7 +2285,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2322,7 +2322,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2358,7 +2358,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2393,7 +2393,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2429,7 +2429,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2473,7 +2473,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2517,7 +2517,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.CheckedListBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.CheckedListBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2552,7 +2552,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2589,7 +2589,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2624,7 +2624,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2660,7 +2660,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2695,7 +2695,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2760,7 +2760,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2826,7 +2826,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2862,7 +2862,7 @@ MsgBox(CStr(CheckedListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ColorDialogArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ColorDialogArray.xml
index bd7f73f0082..3428cb073f1 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ColorDialogArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ColorDialogArray.xml
@@ -37,7 +37,7 @@
  The `ColorDialogArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ColorDialog` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ColorDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ColorDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ColorDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ColorDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ColorDialog> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -234,7 +234,7 @@
  This method can be used to retrieve the index for a <xref:System.Windows.Forms.ColorDialog>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -268,7 +268,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -346,7 +346,7 @@ MsgBox(CStr(ColorDialogArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -387,7 +387,7 @@ MsgBox(CStr(ColorDialogArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -430,7 +430,7 @@ MsgBox(CStr(ColorDialogArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -473,7 +473,7 @@ MsgBox(CStr(ColorDialogArray(1).Text))
  If the specified <xref:System.Windows.Forms.ColorDialog> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ColorDialogArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ComboBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ComboBoxArray.xml
index 68f988db645..b26eb172e67 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ComboBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ComboBoxArray.xml
@@ -38,7 +38,7 @@
  The `ComboBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ComboBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ComboBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ComboBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ComboBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ComboBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ComboBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -377,7 +377,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -418,7 +418,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -452,7 +452,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -484,7 +484,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -516,7 +516,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -551,7 +551,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -586,7 +586,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -621,7 +621,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -656,7 +656,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -689,7 +689,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -722,7 +722,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -758,7 +758,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -794,7 +794,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -830,7 +830,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -866,7 +866,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -899,7 +899,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -933,7 +933,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -968,7 +968,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1003,7 +1003,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1036,7 +1036,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1071,7 +1071,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1106,7 +1106,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1140,7 +1140,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1174,7 +1174,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1208,7 +1208,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1243,7 +1243,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1280,7 +1280,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ComboBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1315,7 +1315,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1350,7 +1350,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1388,7 +1388,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1423,7 +1423,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1465,7 +1465,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1508,7 +1508,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1556,7 +1556,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1600,7 +1600,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1636,7 +1636,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1690,7 +1690,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1726,7 +1726,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1760,7 +1760,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1795,7 +1795,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1842,7 +1842,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1889,7 +1889,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1937,7 +1937,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1983,7 +1983,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2029,7 +2029,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2079,7 +2079,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2125,7 +2125,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2171,7 +2171,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2217,7 +2217,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2251,7 +2251,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2286,7 +2286,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2321,7 +2321,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2356,7 +2356,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2392,7 +2392,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about handling events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2427,7 +2427,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2469,7 +2469,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2506,7 +2506,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2542,7 +2542,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2577,7 +2577,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2612,7 +2612,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2647,7 +2647,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2691,7 +2691,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2735,7 +2735,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.ComboBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ComboBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2770,7 +2770,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2807,7 +2807,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2842,7 +2842,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2878,7 +2878,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2913,7 +2913,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2948,7 +2948,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2982,7 +2982,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3047,7 +3047,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3113,7 +3113,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3149,7 +3149,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3184,7 +3184,7 @@ MsgBox(CStr(ComboBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/DBKINDENUM.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/DBKINDENUM.xml
index a95c5c02e0b..94c4e118ffd 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/DBKINDENUM.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/DBKINDENUM.xml
@@ -32,7 +32,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBox.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBox.xml
index 1a30a8b9c89..8a85cea9668 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBox.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBox.xml
@@ -36,7 +36,7 @@
  Set the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.DirList%2A>, <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.DirListCount%2A>, and <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.DirListIndex%2A> properties to enable a user to access items in a list. If you also display the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> and <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBox> controls, you can write code to synchronize them with the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control and with each other.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -67,7 +67,7 @@
  A `DirListBox` control displays directories and paths at run time.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -102,7 +102,7 @@
  The `Change` event occurs when the selection in a <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control changes, either when the user double-clicks a new directory or when you change the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.Path%2A> property setting through code.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -200,7 +200,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -251,7 +251,7 @@
  For a <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control, the `Index` number sequence is based on the current directories and subdirectories when the control is created at run time.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -296,7 +296,7 @@
  Use this property to return the number of subdirectories in the currently selected directory. The `DirListCount` property works together with the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.DirList%2A> and <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.DirListIndex%2A> properties.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
  The expression `instance.DirList(instance.DirListIndex)` returns the string for the currently selected directory.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -388,7 +388,7 @@
  When the disposing parameter is `true`, this method releases all resources held by any managed objects that this control references. This method invokes the `Dispose()` method of each referenced object.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -437,7 +437,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -486,7 +486,7 @@
  This property is not required for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> does not support items of variable height. It is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -535,7 +535,7 @@
  This property should not be used for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; trying to add or remove directories from the collection could cause an exception. It is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -585,7 +585,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -630,7 +630,7 @@
  The `OnBackColorChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -673,7 +673,7 @@
  The `OnChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -721,7 +721,7 @@
  The `OnDoubleClick` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -765,7 +765,7 @@
  The `OnDrawItem` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -809,7 +809,7 @@
  The `OnFontChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -853,7 +853,7 @@
  The `OnHandleCreated` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -897,7 +897,7 @@
  The `OnSelectedIndexChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -961,7 +961,7 @@
  Changing the value of `Path` for a <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control generates an <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox.Change> event.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -996,7 +996,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1048,7 +1048,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1098,7 +1098,7 @@
  For the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control, `Sorted` always returns false.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1147,7 +1147,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBoxArray.xml
index 5bc5755848a..c4204f1bf42 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/DirListBoxArray.xml
@@ -38,7 +38,7 @@
  The `DirListBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `DirListBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -308,7 +308,7 @@
  For more information about handling events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -446,7 +446,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -481,7 +481,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -516,7 +516,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -549,7 +549,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -582,7 +582,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -618,7 +618,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -690,7 +690,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -726,7 +726,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -761,7 +761,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -814,7 +814,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -849,7 +849,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -884,7 +884,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -919,7 +919,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -956,7 +956,7 @@
  This method can be used to retrieve the index for the selected <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -991,7 +991,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1027,7 +1027,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1065,7 +1065,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1100,7 +1100,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1142,7 +1142,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1185,7 +1185,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1233,7 +1233,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1277,7 +1277,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1313,7 +1313,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1367,7 +1367,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1403,7 +1403,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1438,7 +1438,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1487,7 +1487,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1533,7 +1533,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1585,7 +1585,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1631,7 +1631,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1677,7 +1677,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1723,7 +1723,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1757,7 +1757,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1793,7 +1793,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1828,7 +1828,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1862,7 +1862,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1905,7 +1905,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1942,7 +1942,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1978,7 +1978,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2013,7 +2013,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2048,7 +2048,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2092,7 +2092,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2136,7 +2136,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  If the specified <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2171,7 +2171,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2208,7 +2208,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2243,7 +2243,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2279,7 +2279,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2314,7 +2314,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2379,7 +2379,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2445,7 +2445,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2481,7 +2481,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2516,7 +2516,7 @@ MsgBox(CStr(DirListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBox.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBox.xml
index 7886c10e28a..d3b86774db8 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBox.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBox.xml
@@ -36,7 +36,7 @@
  If you also display the <xref:Microsoft.VisualBasic.Compatibility.VB6.DirListBox> and <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBox> controls, you can write code to synchronize them with the `DriveListBox` control and with each other.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -67,7 +67,7 @@
  A `DriveListBox` control enables a user to select a valid disk drive at run time.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -116,7 +116,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control inherits from <xref:System.Windows.Forms.ComboBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -165,7 +165,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control inherits from <xref:System.Windows.Forms.ComboBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -206,7 +206,7 @@
  When the disposing parameter is `true`, this method releases all resources held by any managed objects that this control references. This method invokes the `Dispose()` method of each referenced object.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -255,7 +255,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control inherits from <xref:System.Windows.Forms.ComboBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -304,7 +304,7 @@
  The valid drives for the `Drive` property include all drives present in or connected to the system when the control is created or refreshed at run time. The default setting of the `Drive` property is the current drive.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -355,7 +355,7 @@
  If you set the `DropDownStyle` property to <xref:System.Windows.Forms.ComboBoxStyle.DropDownList>, you can select only valid values from the list. If you set the `DropDownStyle` property to <xref:System.Windows.Forms.ComboBoxStyle.DropDown>, you can type any value in the editable area of the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -400,7 +400,7 @@
  This property is not required for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control; the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> does not support items of variable height. It is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control inherits from <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -458,7 +458,7 @@
  Use this property to retrieve a list of drives that are currently displayed in a <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -507,7 +507,7 @@
  Use this property to retrieve the name of a drive in a <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -556,7 +556,7 @@
  Use this property to limit the length of text that a user can enter into the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -597,7 +597,7 @@
  The `OnBackColorChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -641,7 +641,7 @@
  The `OnDrawItem` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -685,7 +685,7 @@
  The `OnFontChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -729,7 +729,7 @@
  The `OnHandleCreated` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -773,7 +773,7 @@
  The `OnSelectedIndexChanged` method also enables derived classes to handle the event without attaching a delegate. This is the preferred technique for handling the event in a derived class.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -815,7 +815,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -868,7 +868,7 @@
  For the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control, `Sorted` always returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -917,7 +917,7 @@
  If the `Text` is a valid drive, the value of the `Text` property is the same e as the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox.Drive%2A> property.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -966,7 +966,7 @@
  This property should not be set for the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control; it is provided only because the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control inherits from <xref:System.Windows.Forms.ComboBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1007,7 +1007,7 @@
  The `WndProc` method corresponds exactly to the Windows `WindowProc` function. For more information about processing Windows messages, see [WindowProc callback function](https://docs.microsoft.com/previous-versions/windows/desktop/legacy/ms633573(v=vs.85)).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBoxArray.xml
index 4805ca70f3e..f94eb98eedc 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/DriveListBoxArray.xml
@@ -38,7 +38,7 @@
  The `DriveListBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `DriveListBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -378,7 +378,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -413,7 +413,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -448,7 +448,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -483,7 +483,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -516,7 +516,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -583,7 +583,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -655,7 +655,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -727,7 +727,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -760,7 +760,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -795,7 +795,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -830,7 +830,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -883,7 +883,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -918,7 +918,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -953,7 +953,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -988,7 +988,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1025,7 +1025,7 @@
  This method can be used to retrieve the index for the selected <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1060,7 +1060,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1096,7 +1096,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1134,7 +1134,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1169,7 +1169,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1211,7 +1211,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1254,7 +1254,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1302,7 +1302,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1346,7 +1346,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1382,7 +1382,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1436,7 +1436,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1472,7 +1472,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1507,7 +1507,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1556,7 +1556,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1602,7 +1602,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1654,7 +1654,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1700,7 +1700,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1746,7 +1746,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1792,7 +1792,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1826,7 +1826,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1862,7 +1862,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1897,7 +1897,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1931,7 +1931,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1974,7 +1974,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2011,7 +2011,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2047,7 +2047,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2082,7 +2082,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2117,7 +2117,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2152,7 +2152,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2196,7 +2196,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2240,7 +2240,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  If the specified <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.DriveListBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2275,7 +2275,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2312,7 +2312,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2347,7 +2347,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2383,7 +2383,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2418,7 +2418,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2453,7 +2453,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2518,7 +2518,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2584,7 +2584,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2620,7 +2620,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2655,7 +2655,7 @@ MsgBox(CStr(DriveListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/FileListBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/FileListBoxArray.xml
index 0432cdeaa80..38f9e503376 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/FileListBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/FileListBoxArray.xml
@@ -38,7 +38,7 @@
  The `FileListBox` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `FileListBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -446,7 +446,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -481,7 +481,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -514,7 +514,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -547,7 +547,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -583,7 +583,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -655,7 +655,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -726,7 +726,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -779,7 +779,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -814,7 +814,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -849,7 +849,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -884,7 +884,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -921,7 +921,7 @@
  This method can be used to retrieve the index for the selected <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -956,7 +956,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -992,7 +992,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1030,7 +1030,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1065,7 +1065,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1107,7 +1107,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1150,7 +1150,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1198,7 +1198,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1242,7 +1242,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1278,7 +1278,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1332,7 +1332,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1368,7 +1368,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1403,7 +1403,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1452,7 +1452,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1498,7 +1498,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1550,7 +1550,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1596,7 +1596,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1642,7 +1642,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1688,7 +1688,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1722,7 +1722,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1758,7 +1758,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1853,7 +1853,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1887,7 +1887,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1930,7 +1930,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1967,7 +1967,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2003,7 +2003,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2038,7 +2038,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2073,7 +2073,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2117,7 +2117,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2161,7 +2161,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  If the specified <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.FileListBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2196,7 +2196,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2233,7 +2233,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2268,7 +2268,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2304,7 +2304,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2339,7 +2339,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2404,7 +2404,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2470,7 +2470,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2506,7 +2506,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2541,7 +2541,7 @@ MsgBox(CStr(FileListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/FontDialogArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/FontDialogArray.xml
index 90e0b0de2ed..cf4b66568f8 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/FontDialogArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/FontDialogArray.xml
@@ -37,7 +37,7 @@
  The `FontDialogArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `FontDialog` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.FontDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.FontDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.FontDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.FontDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.FontDialog> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -268,7 +268,7 @@
  This method can be used to retrieve the index for the selected <xref:System.Windows.Forms.FontDialog>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -302,7 +302,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -339,7 +339,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -380,7 +380,7 @@ MsgBox(CStr(FontDialogArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -421,7 +421,7 @@ MsgBox(CStr(FontDialogArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -464,7 +464,7 @@ MsgBox(CStr(FontDialogArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -507,7 +507,7 @@ MsgBox(CStr(FontDialogArray(1).Text))
  If the specified <xref:System.Windows.Forms.FontDialog> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.FontDialogArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/FormShowConstants.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/FormShowConstants.xml
index 71c1f9b5c49..af04820e993 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/FormShowConstants.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/FormShowConstants.xml
@@ -31,7 +31,7 @@
  These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/GroupBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/GroupBoxArray.xml
index 38d16ad8d37..a7618139c57 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/GroupBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/GroupBoxArray.xml
@@ -38,7 +38,7 @@
  The `GroupBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `GroupBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -155,7 +155,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -190,7 +190,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -259,7 +259,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -294,7 +294,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.GroupBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -409,7 +409,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -443,7 +443,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -484,7 +484,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -518,7 +518,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -582,7 +582,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -617,7 +617,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -652,7 +652,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -685,7 +685,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -721,7 +721,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -757,7 +757,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -793,7 +793,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -829,7 +829,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -882,7 +882,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -917,7 +917,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -952,7 +952,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -987,7 +987,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1024,7 +1024,7 @@
  This method can be used to retrieve the index for the selected <xref:System.Windows.Forms.GroupBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1059,7 +1059,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1095,7 +1095,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1133,7 +1133,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1168,7 +1168,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1210,7 +1210,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1245,7 +1245,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1299,7 +1299,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1335,7 +1335,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1369,7 +1369,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1401,7 +1401,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1453,7 +1453,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1487,7 +1487,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1522,7 +1522,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1557,7 +1557,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1593,7 +1593,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1628,7 +1628,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1662,7 +1662,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1697,7 +1697,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1739,7 +1739,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1776,7 +1776,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1812,7 +1812,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1856,7 +1856,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1900,7 +1900,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.GroupBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.GroupBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1935,7 +1935,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1972,7 +1972,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2007,7 +2007,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2043,7 +2043,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2078,7 +2078,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2143,7 +2143,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2209,7 +2209,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2245,7 +2245,7 @@ MsgBox(CStr(GroupBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/HScrollBarArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/HScrollBarArray.xml
index 8fd25c115dd..f06ede7b473 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/HScrollBarArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/HScrollBarArray.xml
@@ -38,7 +38,7 @@
  The `HScrollBarArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `HScrollBar` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.HScrollBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.HScrollBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.HScrollBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.HScrollBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -203,7 +203,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.HScrollBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -271,7 +271,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -346,7 +346,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -380,7 +380,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -412,7 +412,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -444,7 +444,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -479,7 +479,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -514,7 +514,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -547,7 +547,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -583,7 +583,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -655,7 +655,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -744,7 +744,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -779,7 +779,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -821,7 +821,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -856,7 +856,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -892,7 +892,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -930,7 +930,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.HScrollBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -972,7 +972,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1015,7 +1015,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1063,7 +1063,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1107,7 +1107,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1143,7 +1143,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1197,7 +1197,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1233,7 +1233,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1267,7 +1267,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1299,7 +1299,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1345,7 +1345,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1397,7 +1397,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1443,7 +1443,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1477,7 +1477,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1512,7 +1512,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1547,7 +1547,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1582,7 +1582,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1616,7 +1616,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1651,7 +1651,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1693,7 +1693,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1730,7 +1730,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1766,7 +1766,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1799,7 +1799,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1843,7 +1843,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1887,7 +1887,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  If the specified <xref:System.Windows.Forms.HScrollBar> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.HScrollBarArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1922,7 +1922,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1959,7 +1959,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1994,7 +1994,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2030,7 +2030,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2065,7 +2065,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2130,7 +2130,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2196,7 +2196,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2232,7 +2232,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2267,7 +2267,7 @@ MsgBox(CStr(HScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IAccessor.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IAccessor.xml
index cc84c76c026..4a64103d00e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IAccessor.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IAccessor.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -71,7 +71,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -116,7 +116,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -157,7 +157,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -194,7 +194,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IChapteredRowset.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IChapteredRowset.xml
index 31b02802b2c..7adfaeccbf7 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IChapteredRowset.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IChapteredRowset.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -71,7 +71,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -108,7 +108,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IConnectionPoint.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IConnectionPoint.xml
index c8f26cc3a63..5f477d24650 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IConnectionPoint.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IConnectionPoint.xml
@@ -35,7 +35,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -73,7 +73,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -109,7 +109,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -145,7 +145,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -181,7 +181,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -217,7 +217,7 @@
  For new development, see <xref:System.Runtime.InteropServices.ComTypes.IConnectionPoint>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnectionPoints.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnectionPoints.xml
index 42069e2db17..4a420d306bf 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnectionPoints.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnectionPoints.xml
@@ -35,7 +35,7 @@
  For new development, use <xref:System.Runtime.InteropServices.ComTypes.IEnumConnectionPoints>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -70,7 +70,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -109,7 +109,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -141,7 +141,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -176,7 +176,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnections.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnections.xml
index f0d14248b99..617f62aacb2 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnections.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IEnumConnections.xml
@@ -35,7 +35,7 @@
  For new development, use <xref:System.Runtime.InteropServices.ComTypes.IEnumConnections>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -70,7 +70,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -109,7 +109,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -141,7 +141,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -176,7 +176,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowPositionChange.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowPositionChange.xml
index af6358db7c6..8f35d759cfa 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowPositionChange.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowPositionChange.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -74,7 +74,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetInfo.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetInfo.xml
index 6347207ca2c..026b1d06e4e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetInfo.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetInfo.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -75,7 +75,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -114,7 +114,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetNotify.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetNotify.xml
index faefb6268be..4df487ddd6f 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetNotify.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/IRowsetNotify.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -128,7 +128,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -170,7 +170,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ImageListArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ImageListArray.xml
index d99e4b295a5..dc3845e7f13 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ImageListArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ImageListArray.xml
@@ -37,7 +37,7 @@
  The `ImageListArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ImageList` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.ImageListArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ImageListArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.ImageListArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ImageListArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ImageList> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -234,7 +234,7 @@
  This method can be used to retrieve the index for the selected <xref:System.Windows.Forms.ImageList>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -270,7 +270,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -311,7 +311,7 @@ MsgBox(CStr(ImageListArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -352,7 +352,7 @@ MsgBox(CStr(ImageListArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -395,7 +395,7 @@ MsgBox(CStr(ImageListArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -438,7 +438,7 @@ MsgBox(CStr(ImageListArray(1).Text))
  If the specified <xref:System.Windows.Forms.ImageList> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ImageListArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/LabelArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/LabelArray.xml
index f420825f6c3..3d23665430b 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/LabelArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/LabelArray.xml
@@ -38,7 +38,7 @@
  The `LabelArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `Label` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.LabelArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.LabelArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.LabelArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.LabelArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -226,7 +226,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.Label> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -308,7 +308,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -378,7 +378,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -412,7 +412,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -453,7 +453,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -487,7 +487,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -519,7 +519,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -551,7 +551,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -586,7 +586,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -621,7 +621,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -687,7 +687,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -723,7 +723,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -759,7 +759,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -795,7 +795,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -831,7 +831,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -884,7 +884,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -919,7 +919,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -954,7 +954,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -989,7 +989,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1026,7 +1026,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.Label>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1061,7 +1061,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1097,7 +1097,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1135,7 +1135,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1177,7 +1177,7 @@ MsgBox(CStr(LabelArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1212,7 +1212,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1266,7 +1266,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1302,7 +1302,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1336,7 +1336,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1368,7 +1368,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1414,7 +1414,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1462,7 +1462,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1512,7 +1512,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1558,7 +1558,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1610,7 +1610,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1656,7 +1656,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1702,7 +1702,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1748,7 +1748,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1782,7 +1782,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1817,7 +1817,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1852,7 +1852,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1888,7 +1888,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1923,7 +1923,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1957,7 +1957,7 @@ MsgBox(CStr(LabelArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1992,7 +1992,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2034,7 +2034,7 @@ MsgBox(CStr(LabelArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2071,7 +2071,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2107,7 +2107,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2151,7 +2151,7 @@ MsgBox(CStr(LabelArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2195,7 +2195,7 @@ MsgBox(CStr(LabelArray(1).Text))
  If the specified <xref:System.Windows.Forms.Label> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.LabelArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2230,7 +2230,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2267,7 +2267,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2302,7 +2302,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2338,7 +2338,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2373,7 +2373,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2408,7 +2408,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2473,7 +2473,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2539,7 +2539,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2575,7 +2575,7 @@ MsgBox(CStr(LabelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ListBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ListBoxArray.xml
index ddeb1a43f99..50ad25a158c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ListBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ListBoxArray.xml
@@ -38,7 +38,7 @@
  The `ListBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ListBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ListBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ListBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ListBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -273,7 +273,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -342,7 +342,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -417,7 +417,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -451,7 +451,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -483,7 +483,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -515,7 +515,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -585,7 +585,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -620,7 +620,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -655,7 +655,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -688,7 +688,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -721,7 +721,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -757,7 +757,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -793,7 +793,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -829,7 +829,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -865,7 +865,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -900,7 +900,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -953,7 +953,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -988,7 +988,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1023,7 +1023,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1057,7 +1057,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1091,7 +1091,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1125,7 +1125,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1160,7 +1160,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1197,7 +1197,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ListBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1232,7 +1232,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1268,7 +1268,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1306,7 +1306,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1341,7 +1341,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1383,7 +1383,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1426,7 +1426,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1474,7 +1474,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1518,7 +1518,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1554,7 +1554,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1608,7 +1608,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1644,7 +1644,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1678,7 +1678,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1713,7 +1713,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1745,7 +1745,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1793,7 +1793,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1841,7 +1841,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1891,7 +1891,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1936,7 +1936,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1988,7 +1988,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2034,7 +2034,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2080,7 +2080,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2126,7 +2126,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2160,7 +2160,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2195,7 +2195,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2230,7 +2230,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2265,7 +2265,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2299,7 +2299,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2334,7 +2334,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2376,7 +2376,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2413,7 +2413,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2449,7 +2449,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2484,7 +2484,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2519,7 +2519,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2563,7 +2563,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2607,7 +2607,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.ListBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ListBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2642,7 +2642,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2679,7 +2679,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2714,7 +2714,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2750,7 +2750,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2785,7 +2785,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2850,7 +2850,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2916,7 +2916,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2952,7 +2952,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2987,7 +2987,7 @@ MsgBox(CStr(ListBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ListViewArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ListViewArray.xml
index cc0bf98d8fd..69543f5008d 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ListViewArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ListViewArray.xml
@@ -37,7 +37,7 @@
  The `ListViewArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ListView` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ListViewArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ListViewArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ListViewArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ListViewArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -154,7 +154,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -188,7 +188,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -222,7 +222,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -256,7 +256,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -290,7 +290,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -324,7 +324,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -370,7 +370,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ListView> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -404,7 +404,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -436,7 +436,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -472,7 +472,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -506,7 +506,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -540,7 +540,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -574,7 +574,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -606,7 +606,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -640,7 +640,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -680,7 +680,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -714,7 +714,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -746,7 +746,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -778,7 +778,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -812,7 +812,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -846,7 +846,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -878,7 +878,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -910,7 +910,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -945,7 +945,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -980,7 +980,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1015,7 +1015,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1050,7 +1050,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1084,7 +1084,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1118,7 +1118,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1152,7 +1152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1204,7 +1204,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1238,7 +1238,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1272,7 +1272,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1306,7 +1306,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1342,7 +1342,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ListView>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1376,7 +1376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1411,7 +1411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1448,7 +1448,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1482,7 +1482,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1523,7 +1523,7 @@ MsgBox(CStr(ListViewArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1557,7 +1557,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1591,7 +1591,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1623,7 +1623,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1657,7 +1657,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1689,7 +1689,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1725,7 +1725,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1767,7 +1767,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1814,7 +1814,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1857,7 +1857,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1892,7 +1892,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1945,7 +1945,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1980,7 +1980,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2014,7 +2014,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2046,7 +2046,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2094,7 +2094,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2142,7 +2142,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2191,7 +2191,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2236,7 +2236,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2287,7 +2287,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2332,7 +2332,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2377,7 +2377,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2422,7 +2422,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2455,7 +2455,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2490,7 +2490,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2524,7 +2524,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2558,7 +2558,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2591,7 +2591,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2626,7 +2626,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2667,7 +2667,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2703,7 +2703,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2738,7 +2738,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2772,7 +2772,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2806,7 +2806,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2840,7 +2840,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2874,7 +2874,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2917,7 +2917,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2960,7 +2960,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  If the specified <xref:System.Windows.Forms.ListView> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ListViewArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2994,7 +2994,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3030,7 +3030,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3064,7 +3064,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3099,7 +3099,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3133,7 +3133,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3197,7 +3197,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3262,7 +3262,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3297,7 +3297,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3332,7 +3332,7 @@ MsgBox(CStr(ListViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/LoadResConstants.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/LoadResConstants.xml
index c20872fdca9..95293ca9044 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/LoadResConstants.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/LoadResConstants.xml
@@ -31,7 +31,7 @@
  These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/MBindingCollection.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/MBindingCollection.xml
index a1ad4540978..19e9ed57596 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/MBindingCollection.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/MBindingCollection.xml
@@ -39,7 +39,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -67,7 +67,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -122,7 +122,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -169,7 +169,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -204,7 +204,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -239,7 +239,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -274,7 +274,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -315,7 +315,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -361,7 +361,7 @@
  This method is called by the public `Dispose()` method and the <xref:System.Object.Finalize%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -400,7 +400,7 @@
  When the disposing parameter is `true`, this method releases all resources held by any managed objects that this control references. This method invokes the `Dispose()` method of each referenced object.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -433,7 +433,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -472,7 +472,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -510,7 +510,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -542,7 +542,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -577,7 +577,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -622,7 +622,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/MaskedTextBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/MaskedTextBoxArray.xml
index f5b76b299a1..56c93aac17f 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/MaskedTextBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/MaskedTextBoxArray.xml
@@ -37,7 +37,7 @@
  The `MaskedTextBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `MaskedTextBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.MaskedTextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.MaskedTextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.MaskedTextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.MaskedTextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -220,7 +220,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -266,7 +266,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.MaskedTextBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -300,7 +300,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -332,7 +332,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -368,7 +368,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -402,7 +402,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -442,7 +442,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -476,7 +476,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -508,7 +508,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -540,7 +540,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -574,7 +574,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -608,7 +608,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -640,7 +640,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -672,7 +672,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -707,7 +707,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -742,7 +742,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -777,7 +777,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -812,7 +812,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -864,7 +864,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -898,7 +898,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -932,7 +932,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -966,7 +966,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1002,7 +1002,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.MaskedTextBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1036,7 +1036,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1071,7 +1071,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1106,7 +1106,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1142,7 +1142,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1176,7 +1176,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1210,7 +1210,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1251,7 +1251,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1293,7 +1293,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1340,7 +1340,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1383,7 +1383,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1418,7 +1418,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1471,7 +1471,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1506,7 +1506,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1540,7 +1540,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1574,7 +1574,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1608,7 +1608,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1643,7 +1643,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1675,7 +1675,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1721,7 +1721,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1769,7 +1769,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1814,7 +1814,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1859,7 +1859,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1908,7 +1908,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1953,7 +1953,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1998,7 +1998,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2043,7 +2043,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2076,7 +2076,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2111,7 +2111,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2145,7 +2145,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2178,7 +2178,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2213,7 +2213,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2247,7 +2247,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2288,7 +2288,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2324,7 +2324,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2359,7 +2359,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2402,7 +2402,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  The `SetIndex` method should be called only when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2445,7 +2445,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.MaskedTextBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.MaskedTextBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2479,7 +2479,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2515,7 +2515,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2549,7 +2549,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2584,7 +2584,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2618,7 +2618,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2652,7 +2652,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2686,7 +2686,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2720,7 +2720,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2785,7 +2785,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2850,7 +2850,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2885,7 +2885,7 @@ MsgBox(CStr(MaskedTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/MenuItemArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/MenuItemArray.xml
index 03d8d36bae9..184cb2b244c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/MenuItemArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/MenuItemArray.xml
@@ -38,7 +38,7 @@
  The `MenuItemArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `MenuItem` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.MenuItemArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.MenuItemArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.MenuItemArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.MenuItemArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -168,7 +168,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.MenuItem> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -205,7 +205,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -240,7 +240,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -275,7 +275,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -312,7 +312,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.MenuItem>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -349,7 +349,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -391,7 +391,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -426,7 +426,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -461,7 +461,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -503,7 +503,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -538,7 +538,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -582,7 +582,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -626,7 +626,7 @@ MsgBox(CStr(MenuItemArray(1).Text))
  If the specified <xref:System.Windows.Forms.MenuItem> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.MenuItemArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/MouseButtonConstants.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/MouseButtonConstants.xml
index 882955f9755..4c1c2dc79ce 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/MouseButtonConstants.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/MouseButtonConstants.xml
@@ -29,7 +29,7 @@
  In Visual Basic 6.0, mouse button parameter mask constants were used to represent the state of mouse buttons in the `Button` parameter of various mouse event handlers. In Visual Basic, the parameters for mouse events have changed and these constants are no longer necessary. These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without further modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
    
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/OpenFileDialogArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/OpenFileDialogArray.xml
index d0b44c4fb37..af5e837c9f7 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/OpenFileDialogArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/OpenFileDialogArray.xml
@@ -37,7 +37,7 @@
  The `OpenFileDialogArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `OpenFileDialog` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.OpenFileDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.OpenFileDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate an <xref:Microsoft.VisualBasic.Compatibility.VB6.OpenFileDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.OpenFileDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.OpenFileDialog> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -196,7 +196,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -230,7 +230,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -266,7 +266,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.OpenFileDialog>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -298,7 +298,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -375,7 +375,7 @@ MsgBox(CStr(OpenFileDialogArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -416,7 +416,7 @@ MsgBox(CStr(OpenFileDialogArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -459,7 +459,7 @@ MsgBox(CStr(OpenFileDialogArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -502,7 +502,7 @@ MsgBox(CStr(OpenFileDialogArray(1).Text))
  If the specified <xref:System.Windows.Forms.OpenFileDialog> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.OpenFileDialogArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/PanelArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/PanelArray.xml
index ef74bd3990d..3080f35191d 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/PanelArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/PanelArray.xml
@@ -38,7 +38,7 @@
  The `PanelArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `Panel` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PanelArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PanelArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PanelArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PanelArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -155,7 +155,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -190,7 +190,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -259,7 +259,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -294,7 +294,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -341,7 +341,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.Panel> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -409,7 +409,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -446,7 +446,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -480,7 +480,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -521,7 +521,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -555,7 +555,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -587,7 +587,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -689,7 +689,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -722,7 +722,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -755,7 +755,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -791,7 +791,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -827,7 +827,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -863,7 +863,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -899,7 +899,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -952,7 +952,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -987,7 +987,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1022,7 +1022,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1057,7 +1057,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1094,7 +1094,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.Panel>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1129,7 +1129,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1165,7 +1165,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1203,7 +1203,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1238,7 +1238,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1280,7 +1280,7 @@ MsgBox(CStr(PanelArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1315,7 +1315,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1369,7 +1369,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1405,7 +1405,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1439,7 +1439,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1471,7 +1471,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1517,7 +1517,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1565,7 +1565,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1611,7 +1611,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1657,7 +1657,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1707,7 +1707,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1753,7 +1753,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1799,7 +1799,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1845,7 +1845,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1879,7 +1879,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1914,7 +1914,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1949,7 +1949,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1985,7 +1985,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2020,7 +2020,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2054,7 +2054,7 @@ MsgBox(CStr(PanelArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2089,7 +2089,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2131,7 +2131,7 @@ MsgBox(CStr(PanelArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2168,7 +2168,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2204,7 +2204,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2236,7 +2236,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2280,7 +2280,7 @@ MsgBox(CStr(PanelArray(1).Text))
  The `SetIndex` method should be called only when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2324,7 +2324,7 @@ MsgBox(CStr(PanelArray(1).Text))
  If the specified <xref:System.Windows.Forms.Panel> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.PanelArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2359,7 +2359,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2396,7 +2396,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2431,7 +2431,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2467,7 +2467,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2502,7 +2502,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2567,7 +2567,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2633,7 +2633,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2669,7 +2669,7 @@ MsgBox(CStr(PanelArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/PictureBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/PictureBoxArray.xml
index 43a41a8f5ca..0ea76d57458 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/PictureBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/PictureBoxArray.xml
@@ -38,7 +38,7 @@
  The `PictureBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `PictureBox` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PictureBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PictureBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PictureBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PictureBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -191,7 +191,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -260,7 +260,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -307,7 +307,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.PictureBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -340,7 +340,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -377,7 +377,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -452,7 +452,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -486,7 +486,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -518,7 +518,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -585,7 +585,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -620,7 +620,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -653,7 +653,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -686,7 +686,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -722,7 +722,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -758,7 +758,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -794,7 +794,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -830,7 +830,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -865,7 +865,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -902,7 +902,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.PictureBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -937,7 +937,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -973,7 +973,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1011,7 +1011,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1053,7 +1053,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1088,7 +1088,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1123,7 +1123,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1159,7 +1159,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1194,7 +1194,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1228,7 +1228,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1260,7 +1260,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1306,7 +1306,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1354,7 +1354,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1400,7 +1400,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1446,7 +1446,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1496,7 +1496,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1542,7 +1542,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1588,7 +1588,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1634,7 +1634,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1668,7 +1668,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1703,7 +1703,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1738,7 +1738,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1774,7 +1774,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1809,7 +1809,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1843,7 +1843,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1878,7 +1878,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1920,7 +1920,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1957,7 +1957,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2002,7 +2002,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2046,7 +2046,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.PictureBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.PictureBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2081,7 +2081,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2116,7 +2116,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2153,7 +2153,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2188,7 +2188,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2254,7 +2254,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2320,7 +2320,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2356,7 +2356,7 @@ MsgBox(CStr(PictureBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/PrintDialogArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/PrintDialogArray.xml
index 380379d5c30..95f034127cf 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/PrintDialogArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/PrintDialogArray.xml
@@ -37,7 +37,7 @@
  The `PrintDialogArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `PrintDialog` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PrintDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PrintDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.PrintDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.PrintDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.PrintDialog> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -234,7 +234,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.PrintDialog>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -268,7 +268,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -346,7 +346,7 @@ MsgBox(CStr(PrintDialogArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -387,7 +387,7 @@ MsgBox(CStr(PrintDialogArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -430,7 +430,7 @@ MsgBox(CStr(PrintDialogArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -473,7 +473,7 @@ MsgBox(CStr(PrintDialogArray(1).Text))
  If the specified <xref:System.Windows.Forms.PrintDialog> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.PrintDialogArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ProgressBarArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ProgressBarArray.xml
index b323cbaceaf..e3d2417c395 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ProgressBarArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ProgressBarArray.xml
@@ -37,7 +37,7 @@
  The `ProgressBarArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ProgressBar` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ProgressBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ProgressBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ProgressBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ProgressBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ProgressBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -264,7 +264,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -300,7 +300,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -374,7 +374,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -408,7 +408,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -440,7 +440,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -472,7 +472,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -506,7 +506,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -540,7 +540,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -572,7 +572,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -607,7 +607,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -642,7 +642,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -677,7 +677,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -712,7 +712,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -746,7 +746,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -780,7 +780,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -816,7 +816,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ProgressBar>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -850,7 +850,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -885,7 +885,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -922,7 +922,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -963,7 +963,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -997,7 +997,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1032,7 +1032,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1066,7 +1066,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1098,7 +1098,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1144,7 +1144,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1189,7 +1189,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1234,7 +1234,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1283,7 +1283,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1328,7 +1328,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1373,7 +1373,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1418,7 +1418,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1451,7 +1451,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1486,7 +1486,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1520,7 +1520,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1554,7 +1554,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1587,7 +1587,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1622,7 +1622,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1663,7 +1663,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1699,7 +1699,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1734,7 +1734,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1768,7 +1768,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1811,7 +1811,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1854,7 +1854,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  If the specified <xref:System.Windows.Forms.ProgressBar> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ProgressBarArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1888,7 +1888,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1924,7 +1924,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1958,7 +1958,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1993,7 +1993,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2057,7 +2057,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2122,7 +2122,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2157,7 +2157,7 @@ MsgBox(CStr(ProgressBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/RadioButtonArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/RadioButtonArray.xml
index a1a47ecfd59..0423df9359c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/RadioButtonArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/RadioButtonArray.xml
@@ -38,7 +38,7 @@
  The `RadioButtonArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `RadioButton` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.RadioButtonArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.RadioButtonArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.RadioButtonArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.RadioButtonArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -190,7 +190,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -225,7 +225,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -260,7 +260,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -294,7 +294,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -329,7 +329,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -376,7 +376,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.RadioButton> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -444,7 +444,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -479,7 +479,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -516,7 +516,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -550,7 +550,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -591,7 +591,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -625,7 +625,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -657,7 +657,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -689,7 +689,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -724,7 +724,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -759,7 +759,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -792,7 +792,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -828,7 +828,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -864,7 +864,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -900,7 +900,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -936,7 +936,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -989,7 +989,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1024,7 +1024,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1059,7 +1059,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1094,7 +1094,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1131,7 +1131,7 @@
  This method can be used to retrieve the index for a <xref:System.Windows.Forms.RadioButton>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1166,7 +1166,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1202,7 +1202,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1240,7 +1240,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1282,7 +1282,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1325,7 +1325,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1373,7 +1373,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1417,7 +1417,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1453,7 +1453,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1507,7 +1507,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1543,7 +1543,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1577,7 +1577,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1609,7 +1609,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1657,7 +1657,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1703,7 +1703,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1749,7 +1749,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1799,7 +1799,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1845,7 +1845,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1891,7 +1891,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1937,7 +1937,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1971,7 +1971,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2006,7 +2006,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2041,7 +2041,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2077,7 +2077,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2112,7 +2112,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2146,7 +2146,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2181,7 +2181,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2223,7 +2223,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2260,7 +2260,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2296,7 +2296,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2340,7 +2340,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2384,7 +2384,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  If the specified <xref:System.Windows.Forms.RadioButton> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.RadioButtonArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2419,7 +2419,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2456,7 +2456,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2491,7 +2491,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2527,7 +2527,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2562,7 +2562,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2597,7 +2597,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2662,7 +2662,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2728,7 +2728,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2764,7 +2764,7 @@ MsgBox(CStr(RadioButtonArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/RichTextBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/RichTextBoxArray.xml
index ec505cd64f7..41aa18a8435 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/RichTextBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/RichTextBoxArray.xml
@@ -37,7 +37,7 @@
  The `RichTextBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `RichTextBox` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.RichTextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.RichTextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.RichTextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.RichTextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -220,7 +220,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -254,7 +254,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -300,7 +300,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.RichTextBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -366,7 +366,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -402,7 +402,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -436,7 +436,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -468,7 +468,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -508,7 +508,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -542,7 +542,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -574,7 +574,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -606,7 +606,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -640,7 +640,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -674,7 +674,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -706,7 +706,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -740,7 +740,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -772,7 +772,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -806,7 +806,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -840,7 +840,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -874,7 +874,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -910,7 +910,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.RichTextBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -944,7 +944,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -979,7 +979,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1015,7 +1015,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1047,7 +1047,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1079,7 +1079,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1113,7 +1113,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1154,7 +1154,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1196,7 +1196,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1243,7 +1243,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1286,7 +1286,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1321,7 +1321,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1374,7 +1374,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1409,7 +1409,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1443,7 +1443,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1477,7 +1477,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1511,7 +1511,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1558,7 +1558,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1605,7 +1605,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1653,7 +1653,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1698,7 +1698,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1743,7 +1743,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1792,7 +1792,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1837,7 +1837,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1882,7 +1882,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1927,7 +1927,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1960,7 +1960,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1995,7 +1995,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2029,7 +2029,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2063,7 +2063,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2097,7 +2097,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2132,7 +2132,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2166,7 +2166,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2207,7 +2207,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2243,7 +2243,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2278,7 +2278,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2312,7 +2312,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2355,7 +2355,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2398,7 +2398,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.RichTextBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.RichTextBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2432,7 +2432,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2468,7 +2468,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2502,7 +2502,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2537,7 +2537,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2571,7 +2571,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2605,7 +2605,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2669,7 +2669,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2734,7 +2734,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2769,7 +2769,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2801,7 +2801,7 @@ MsgBox(CStr(RichTextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/SRDescriptionAttribute.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/SRDescriptionAttribute.xml
index fb093c2ec4d..993fcf5bdfd 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/SRDescriptionAttribute.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/SRDescriptionAttribute.xml
@@ -37,7 +37,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -69,7 +69,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -101,7 +101,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/SaveFileDialogArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/SaveFileDialogArray.xml
index be5a2a23bc2..91e840f3f40 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/SaveFileDialogArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/SaveFileDialogArray.xml
@@ -37,7 +37,7 @@
  The `SaveFileDialogArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `SaveFileDialog` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.SaveFileDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.SaveFileDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.SaveFileDialogArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.SaveFileDialogArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.OpenFileDialog> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -196,7 +196,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -230,7 +230,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -266,7 +266,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.SaveFileDialog>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -298,7 +298,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -375,7 +375,7 @@ MsgBox(CStr(SaveFileDialogArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -416,7 +416,7 @@ MsgBox(CStr(SaveFileDialogArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -459,7 +459,7 @@ MsgBox(CStr(SaveFileDialogArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -502,7 +502,7 @@ MsgBox(CStr(SaveFileDialogArray(1).Text))
  If the specified <xref:System.Windows.Forms.SaveFileDialog> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.SaveFileDialogArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ScaleMode.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ScaleMode.xml
index 7b5d32a3107..3c8e29d4b8c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ScaleMode.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ScaleMode.xml
@@ -29,7 +29,7 @@
  In Visual Basic 6.0, `ScaleMode` constants were used to represent various units of measurement for the `ScaleMode` property. In Visual Basic, the `ScaleMode` property is no longer supported, and these constants are no longer necessary. These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ShiftConstants.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ShiftConstants.xml
index 076d7a238e0..40f904b2c3a 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ShiftConstants.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ShiftConstants.xml
@@ -29,7 +29,7 @@
  In Visual Basic 6.0, shift parameter mask constants were used to represent the state of modifier keys in the `Shift` parameter of various key and mouse event handlers. In Visual Basic, the parameters for key and mouse events have changed, and these constants are no longer necessary. These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusBarArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusBarArray.xml
index 3baad4c1c81..c9f876819f0 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusBarArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusBarArray.xml
@@ -37,7 +37,7 @@
  The `StatusBarArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `StatusBar` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.StatusBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -264,7 +264,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -300,7 +300,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -374,7 +374,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -408,7 +408,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -442,7 +442,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -476,7 +476,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -510,7 +510,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -544,7 +544,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -576,7 +576,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -608,7 +608,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -643,7 +643,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -678,7 +678,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -713,7 +713,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -748,7 +748,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -783,7 +783,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -815,7 +815,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -849,7 +849,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -883,7 +883,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -919,7 +919,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.StatusBar>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -953,7 +953,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -987,7 +987,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1024,7 +1024,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1065,7 +1065,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1107,7 +1107,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1154,7 +1154,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1197,7 +1197,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1232,7 +1232,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1285,7 +1285,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1320,7 +1320,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1354,7 +1354,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1401,7 +1401,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1448,7 +1448,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1496,7 +1496,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1541,7 +1541,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1586,7 +1586,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1635,7 +1635,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1680,7 +1680,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1725,7 +1725,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1770,7 +1770,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1803,7 +1803,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1838,7 +1838,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1872,7 +1872,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1907,7 +1907,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1941,7 +1941,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1974,7 +1974,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2009,7 +2009,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2050,7 +2050,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2086,7 +2086,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2121,7 +2121,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2164,7 +2164,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2207,7 +2207,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  If the specified <xref:System.Windows.Forms.StatusBar> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusBarArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2241,7 +2241,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2277,7 +2277,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2311,7 +2311,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2346,7 +2346,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2380,7 +2380,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2414,7 +2414,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2478,7 +2478,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2543,7 +2543,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2578,7 +2578,7 @@ MsgBox(CStr(StatusBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusStripArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusStripArray.xml
index 6d30a01d559..d8ae2a9b5d1 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusStripArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/StatusStripArray.xml
@@ -37,7 +37,7 @@
  The `StatusStripArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `StatusBar` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusStripArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusStripArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusStripArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusStripArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -220,7 +220,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -254,7 +254,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -286,7 +286,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -320,7 +320,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -366,7 +366,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.StatusStrip> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -398,7 +398,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -434,7 +434,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -468,7 +468,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -508,7 +508,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -542,7 +542,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -576,7 +576,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -608,7 +608,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -640,7 +640,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -675,7 +675,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -710,7 +710,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -745,7 +745,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -780,7 +780,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -812,7 +812,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -844,7 +844,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -878,7 +878,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -912,7 +912,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -948,7 +948,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.StatusStrip>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -982,7 +982,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1016,7 +1016,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1053,7 +1053,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1087,7 +1087,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1128,7 +1128,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1160,7 +1160,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1192,7 +1192,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1224,7 +1224,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1266,7 +1266,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1313,7 +1313,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1356,7 +1356,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1391,7 +1391,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1424,7 +1424,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1459,7 +1459,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1511,7 +1511,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1546,7 +1546,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1580,7 +1580,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1627,7 +1627,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1674,7 +1674,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1722,7 +1722,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1767,7 +1767,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1812,7 +1812,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1861,7 +1861,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1906,7 +1906,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1951,7 +1951,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1996,7 +1996,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2029,7 +2029,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2062,7 +2062,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2095,7 +2095,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2129,7 +2129,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2163,7 +2163,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2198,7 +2198,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2233,7 +2233,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2274,7 +2274,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2310,7 +2310,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2345,7 +2345,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2377,7 +2377,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2420,7 +2420,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2463,7 +2463,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  If the specified <xref:System.Windows.Forms.StatusStrip> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.StatusStripArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2497,7 +2497,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2533,7 +2533,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2567,7 +2567,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2602,7 +2602,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2636,7 +2636,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2670,7 +2670,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2734,7 +2734,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2799,7 +2799,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2834,7 +2834,7 @@ MsgBox(CStr(StatusStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/TabControlArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/TabControlArray.xml
index 41c72e7bc57..40ebad5e916 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/TabControlArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/TabControlArray.xml
@@ -38,7 +38,7 @@
  The `TabControlArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `TabControl` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TabControlArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TabControlArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TabControlArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TabControlArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -203,7 +203,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.TabControl> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -271,7 +271,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -308,7 +308,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -342,7 +342,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -383,7 +383,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -417,7 +417,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -451,7 +451,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -485,7 +485,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -520,7 +520,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -566,7 +566,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -612,7 +612,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -647,7 +647,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -680,7 +680,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -713,7 +713,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -749,7 +749,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -785,7 +785,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -821,7 +821,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -859,7 +859,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -894,7 +894,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -927,7 +927,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -962,7 +962,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -997,7 +997,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1034,7 +1034,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.TabControl>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1069,7 +1069,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1104,7 +1104,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1142,7 +1142,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1177,7 +1177,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1219,7 +1219,7 @@ MsgBox(CStr(TabControlArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1262,7 +1262,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1310,7 +1310,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1354,7 +1354,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1390,7 +1390,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1444,7 +1444,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1480,7 +1480,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1514,7 +1514,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1561,7 +1561,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1608,7 +1608,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1656,7 +1656,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1702,7 +1702,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1748,7 +1748,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1798,7 +1798,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1844,7 +1844,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1890,7 +1890,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1936,7 +1936,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1970,7 +1970,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2005,7 +2005,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2040,7 +2040,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2075,7 +2075,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2109,7 +2109,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2144,7 +2144,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2186,7 +2186,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2223,7 +2223,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2259,7 +2259,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2293,7 +2293,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2339,7 +2339,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2374,7 +2374,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2420,7 +2420,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2464,7 +2464,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2508,7 +2508,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  If the specified <xref:System.Windows.Forms.TabControl> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.TabControlArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2543,7 +2543,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2580,7 +2580,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2615,7 +2615,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2651,7 +2651,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2686,7 +2686,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2751,7 +2751,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2817,7 +2817,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2853,7 +2853,7 @@ MsgBox(CStr(TabControlArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/TextBoxArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/TextBoxArray.xml
index fc4b77595d8..2e5441fa2ed 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/TextBoxArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/TextBoxArray.xml
@@ -38,7 +38,7 @@
  The `TextBoxArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `TextBox` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TextBoxArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TextBoxArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -197,7 +197,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -267,7 +267,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -302,7 +302,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -349,7 +349,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.TextBox> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -384,7 +384,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -417,7 +417,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -453,7 +453,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -487,7 +487,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -528,7 +528,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -562,7 +562,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -594,7 +594,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -626,7 +626,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -661,7 +661,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -696,7 +696,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -729,7 +729,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -762,7 +762,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -798,7 +798,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -834,7 +834,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -870,7 +870,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -906,7 +906,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -939,7 +939,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -974,7 +974,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1009,7 +1009,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1044,7 +1044,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1081,7 +1081,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.TextBox>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1116,7 +1116,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1151,7 +1151,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1187,7 +1187,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1224,7 +1224,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1259,7 +1259,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1301,7 +1301,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1344,7 +1344,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1392,7 +1392,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1436,7 +1436,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1472,7 +1472,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1526,7 +1526,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1562,7 +1562,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1596,7 +1596,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1631,7 +1631,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1678,7 +1678,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1725,7 +1725,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1773,7 +1773,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1819,7 +1819,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1865,7 +1865,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1915,7 +1915,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1961,7 +1961,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2007,7 +2007,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2053,7 +2053,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2087,7 +2087,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2123,7 +2123,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2158,7 +2158,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2193,7 +2193,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2227,7 +2227,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2263,7 +2263,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2297,7 +2297,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2339,7 +2339,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2376,7 +2376,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2412,7 +2412,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2456,7 +2456,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2500,7 +2500,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  If the specified <xref:System.Windows.Forms.TextBox> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.TextBoxArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2535,7 +2535,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2572,7 +2572,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2607,7 +2607,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2643,7 +2643,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2678,7 +2678,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2713,7 +2713,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2748,7 +2748,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2813,7 +2813,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2879,7 +2879,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2915,7 +2915,7 @@ MsgBox(CStr(TextBoxArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/TimerArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/TimerArray.xml
index 53d489d5668..fe4bb8ad2f5 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/TimerArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/TimerArray.xml
@@ -38,7 +38,7 @@
  The `TimerArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `Timer` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TimerArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TimerArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TimerArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TimerArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -168,7 +168,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.Timer> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -203,7 +203,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -240,7 +240,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.Timer>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -277,7 +277,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -319,7 +319,7 @@ MsgBox(CStr(TimerArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -361,7 +361,7 @@ MsgBox(CStr(TimerArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -405,7 +405,7 @@ MsgBox(CStr(TimerArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -449,7 +449,7 @@ MsgBox(CStr(TimerArray(1).Text))
  If the specified <xref:System.Windows.Forms.Timer> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.TimerArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -482,7 +482,7 @@ MsgBox(CStr(TimerArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolBarArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolBarArray.xml
index a95f27f6d1c..378d8553d77 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolBarArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolBarArray.xml
@@ -37,7 +37,7 @@
  The `ToolBarArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `ToolBar` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -218,7 +218,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -250,7 +250,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -296,7 +296,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ToolBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -330,7 +330,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -362,7 +362,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -398,7 +398,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -432,7 +432,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -472,7 +472,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -506,7 +506,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -540,7 +540,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -574,7 +574,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -608,7 +608,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -642,7 +642,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -674,7 +674,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -706,7 +706,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -741,7 +741,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -776,7 +776,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -811,7 +811,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -846,7 +846,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -878,7 +878,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -912,7 +912,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -946,7 +946,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -982,7 +982,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ToolBar>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1016,7 +1016,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1050,7 +1050,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1087,7 +1087,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1128,7 +1128,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1170,7 +1170,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1217,7 +1217,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1260,7 +1260,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1295,7 +1295,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1348,7 +1348,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1383,7 +1383,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1417,7 +1417,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1464,7 +1464,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1511,7 +1511,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1559,7 +1559,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1604,7 +1604,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1649,7 +1649,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1698,7 +1698,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1743,7 +1743,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1788,7 +1788,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1833,7 +1833,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1866,7 +1866,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1901,7 +1901,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1935,7 +1935,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1969,7 +1969,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2002,7 +2002,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2037,7 +2037,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2078,7 +2078,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2114,7 +2114,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2158,7 +2158,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2201,7 +2201,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  If the specified <xref:System.Windows.Forms.ToolBar> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolBarArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2235,7 +2235,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2271,7 +2271,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2305,7 +2305,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2340,7 +2340,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2374,7 +2374,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2438,7 +2438,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2503,7 +2503,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2538,7 +2538,7 @@ MsgBox(CStr(ToolBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripArray.xml
index 4f459b20330..28d83551374 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripArray.xml
@@ -37,7 +37,7 @@
  The `ToolStripArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `CoolBar` control array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -220,7 +220,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -254,7 +254,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -286,7 +286,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -320,7 +320,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -366,7 +366,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ToolStrip> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -398,7 +398,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -434,7 +434,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -468,7 +468,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -508,7 +508,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -542,7 +542,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -576,7 +576,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -608,7 +608,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -640,7 +640,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -675,7 +675,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -710,7 +710,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -745,7 +745,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -780,7 +780,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -812,7 +812,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -844,7 +844,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -878,7 +878,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -912,7 +912,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -948,7 +948,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ToolStrip>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -982,7 +982,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1016,7 +1016,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1053,7 +1053,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1087,7 +1087,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1128,7 +1128,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1160,7 +1160,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1192,7 +1192,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1224,7 +1224,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1266,7 +1266,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1313,7 +1313,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1356,7 +1356,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1391,7 +1391,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1424,7 +1424,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1459,7 +1459,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1511,7 +1511,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1546,7 +1546,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1580,7 +1580,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1627,7 +1627,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1674,7 +1674,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1722,7 +1722,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1767,7 +1767,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1812,7 +1812,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1861,7 +1861,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1906,7 +1906,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1951,7 +1951,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1996,7 +1996,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2029,7 +2029,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2064,7 +2064,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2096,7 +2096,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2129,7 +2129,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2164,7 +2164,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2198,7 +2198,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2233,7 +2233,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about handling events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2268,7 +2268,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2309,7 +2309,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2345,7 +2345,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2380,7 +2380,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2412,7 +2412,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2455,7 +2455,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2498,7 +2498,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  If the specified <xref:System.Windows.Forms.ToolStrip> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2532,7 +2532,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2568,7 +2568,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2602,7 +2602,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2637,7 +2637,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2671,7 +2671,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2705,7 +2705,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2769,7 +2769,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2834,7 +2834,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2869,7 +2869,7 @@ MsgBox(CStr(ToolStripArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripMenuItemArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripMenuItemArray.xml
index cd211d072c0..3e440aed44e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripMenuItemArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ToolStripMenuItemArray.xml
@@ -37,7 +37,7 @@
  The `ToolStripMenuArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `Menu` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripMenuItemArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripMenuItemArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripMenuItemArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripMenuItemArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.ToolStripMenuItem> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -266,7 +266,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -302,7 +302,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -366,7 +366,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -400,7 +400,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -432,7 +432,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -464,7 +464,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -496,7 +496,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -530,7 +530,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -564,7 +564,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -598,7 +598,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -634,7 +634,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.ToolStripMenuItem>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -670,7 +670,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -711,7 +711,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -745,7 +745,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -789,7 +789,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -834,7 +834,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -883,7 +883,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -928,7 +928,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -973,7 +973,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1018,7 +1018,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1051,7 +1051,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1083,7 +1083,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1117,7 +1117,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1159,7 +1159,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1193,7 +1193,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1236,7 +1236,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1279,7 +1279,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  If the specified <xref:System.Windows.Forms.ToolStripMenuItem> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.ToolStripMenuItemArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1313,7 +1313,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1347,7 +1347,7 @@ MsgBox(CStr(ToolStripMenuItemArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/TreeViewArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/TreeViewArray.xml
index 4490f8af9a8..8c2cbaac72d 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/TreeViewArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/TreeViewArray.xml
@@ -37,7 +37,7 @@
  The `TreeViewArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `TreeView` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TreeViewArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TreeViewArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.TreeViewArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.TreeViewArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -152,7 +152,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -184,7 +184,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -216,7 +216,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -250,7 +250,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -284,7 +284,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -318,7 +318,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -350,7 +350,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -382,7 +382,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -414,7 +414,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -446,7 +446,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -478,7 +478,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -512,7 +512,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -558,7 +558,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.TreeView> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -592,7 +592,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -624,7 +624,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -660,7 +660,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -694,7 +694,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -734,7 +734,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -768,7 +768,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -800,7 +800,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -832,7 +832,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -866,7 +866,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -900,7 +900,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -932,7 +932,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -964,7 +964,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -999,7 +999,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1034,7 +1034,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1069,7 +1069,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1104,7 +1104,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1139,7 +1139,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1171,7 +1171,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1205,7 +1205,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1239,7 +1239,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1273,7 +1273,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1309,7 +1309,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.TreeView>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1343,7 +1343,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1377,7 +1377,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1414,7 +1414,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1448,7 +1448,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1489,7 +1489,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1521,7 +1521,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1563,7 +1563,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1610,7 +1610,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1653,7 +1653,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1688,7 +1688,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1741,7 +1741,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1776,7 +1776,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1810,7 +1810,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1857,7 +1857,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1904,7 +1904,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1952,7 +1952,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1997,7 +1997,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2042,7 +2042,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2091,7 +2091,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2136,7 +2136,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2181,7 +2181,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2226,7 +2226,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2259,7 +2259,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2294,7 +2294,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2328,7 +2328,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2362,7 +2362,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2396,7 +2396,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2430,7 +2430,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2464,7 +2464,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2497,7 +2497,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2532,7 +2532,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2573,7 +2573,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2609,7 +2609,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2644,7 +2644,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2678,7 +2678,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2721,7 +2721,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2764,7 +2764,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  If the specified <xref:System.Windows.Forms.TreeView> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.TreeViewArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2798,7 +2798,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2834,7 +2834,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2868,7 +2868,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2903,7 +2903,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2937,7 +2937,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3001,7 +3001,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3066,7 +3066,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -3101,7 +3101,7 @@ MsgBox(CStr(TreeViewArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/UNAME.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/UNAME.xml
index a3af808c025..df5868cbeef 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/UNAME.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/UNAME.xml
@@ -33,7 +33,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -65,7 +65,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/UpdateMode.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/UpdateMode.xml
index ec5c625c651..be6b381a78a 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/UpdateMode.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/UpdateMode.xml
@@ -33,7 +33,7 @@
  These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/VScrollBarArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/VScrollBarArray.xml
index 8a33a46a937..cdbbd0ab4d7 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/VScrollBarArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/VScrollBarArray.xml
@@ -38,7 +38,7 @@
  The `VScrollBarArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `VScrollBar` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -82,7 +82,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.VScrollBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.VScrollBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.VScrollBarArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.VScrollBarArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -203,7 +203,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.VScrollBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -271,7 +271,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -346,7 +346,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -380,7 +380,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -412,7 +412,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -444,7 +444,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -479,7 +479,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -514,7 +514,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -547,7 +547,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -583,7 +583,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -619,7 +619,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -655,7 +655,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -744,7 +744,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -779,7 +779,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -821,7 +821,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -856,7 +856,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -892,7 +892,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -930,7 +930,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.VScrollBar> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -972,7 +972,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1015,7 +1015,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1063,7 +1063,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1107,7 +1107,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1143,7 +1143,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1197,7 +1197,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1233,7 +1233,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1267,7 +1267,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1299,7 +1299,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1345,7 +1345,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1397,7 +1397,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1443,7 +1443,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1477,7 +1477,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1512,7 +1512,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1547,7 +1547,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1582,7 +1582,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1616,7 +1616,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  The `QueryContinueDrag` event is raised when there is a change in the keyboard or mouse button state during a drag-and-drop operation. The `QueryContinueDrag` event enables the drag source to determine whether the drag-and-drop operation should be canceled.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1651,7 +1651,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1693,7 +1693,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1730,7 +1730,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1764,7 +1764,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1808,7 +1808,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1852,7 +1852,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  If the specified <xref:System.Windows.Forms.VScrollBar> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.VScrollBarArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1887,7 +1887,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1924,7 +1924,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1959,7 +1959,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1995,7 +1995,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2030,7 +2030,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2095,7 +2095,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2161,7 +2161,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2197,7 +2197,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -2232,7 +2232,7 @@ MsgBox(CStr(VScrollBarArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebBrowserArray.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebBrowserArray.xml
index 01e43c542c1..985f8e1c6d4 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebBrowserArray.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebBrowserArray.xml
@@ -37,7 +37,7 @@
  The `WebBrowserArray` class provides an equivalent for the run-time functionality of a Visual Basic 6.0 `WebBrowser` array. It does not provide the design-time features of a Visual Basic 6.0 control array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
@@ -80,7 +80,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
  When you instantiate a <xref:Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray>, you must also call the <xref:Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray.SetIndex%2A> method to create the initial element in the array.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -164,7 +164,7 @@
  The `CanExtend` method can be used to determine whether a specific <xref:System.Windows.Forms.WebBrowser> control is the base element of the control array from which the other elements were cloned.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -232,7 +232,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -272,7 +272,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -306,7 +306,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -338,7 +338,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -370,7 +370,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -404,7 +404,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -458,7 +458,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -490,7 +490,7 @@
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -524,7 +524,7 @@
  This method cannot be called from your application's code. Use the <xref:System.Object.GetType%2A> method instead.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -560,7 +560,7 @@
  This method can be used to retrieve the index for the specified <xref:System.Windows.Forms.WebBrowser>.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -596,7 +596,7 @@
  This method cannot be called from your application's code. Use `AddHandler` to hook up events for any controls that are added by using the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -637,7 +637,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
 ```  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -671,7 +671,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -705,7 +705,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -737,7 +737,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -792,7 +792,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -846,7 +846,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
-> Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+> Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -882,7 +882,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -916,7 +916,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -950,7 +950,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -984,7 +984,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1025,7 +1025,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  This method is not supported, and calling it does not raise an exception.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1061,7 +1061,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1105,7 +1105,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  The `SetIndex` method should only be called when you are creating the initial element in the control array. To add subsequent elements, call the <xref:Microsoft.VisualBasic.Compatibility.VB6.BaseControlArray.Load%2A> method and specify the `Index`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1148,7 +1148,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  If the specified <xref:System.Windows.Forms.WebBrowser> is a member of a different <xref:Microsoft.VisualBasic.Compatibility.VB6.WebBrowserArray>, `ShouldSerializeIndex` returns `false`.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1182,7 +1182,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1216,7 +1216,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1281,7 +1281,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1346,7 +1346,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
@@ -1381,7 +1381,7 @@ MsgBox(CStr(WebBrowserArray(1).Text))
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/ZOrderConstants.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/ZOrderConstants.xml
index 809eede6a56..076588cdf42 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/ZOrderConstants.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/ZOrderConstants.xml
@@ -29,7 +29,7 @@
  In Visual Basic, the Visual Basic `ZOrder` method is replaced by the <xref:System.Windows.Forms.Control.BringToFront%2A> and <xref:System.Windows.Forms.Control.SendToBack%2A> functions. These constants enable code that has been upgraded from Visual Basic 6.0 to continue to run without additional modification.  
   
 > [!NOTE]
->  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] implementation.  
+>  Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.VisualBasic.Devices/Ports.xml b/xml/Microsoft.VisualBasic.Devices/Ports.xml
index b05c2ebf55f..9fa6d72c0ad 100644
--- a/xml/Microsoft.VisualBasic.Devices/Ports.xml
+++ b/xml/Microsoft.VisualBasic.Devices/Ports.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Computer.Ports` object provides a straightforward entry point for accessing the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] serial port class, <xref:System.IO.Ports.SerialPort>.  
+ The `My.Computer.Ports` object provides a straightforward entry point for accessing the .NET Framework serial port class, <xref:System.IO.Ports.SerialPort>.  
   
  The following table lists examples of tasks involving the `My.Computer.Ports` object.  
   
diff --git a/xml/Microsoft.VisualBasic.Logging/AspLog.xml b/xml/Microsoft.VisualBasic.Logging/AspLog.xml
index aa36076129c..8b0f0066fac 100644
--- a/xml/Microsoft.VisualBasic.Logging/AspLog.xml
+++ b/xml/Microsoft.VisualBasic.Logging/AspLog.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Application.Log` object provides a straightforward entry point from which to access the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]'s logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
+ The `My.Application.Log` object provides a straightforward entry point from which to access the .NET Framework's logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
   
  The `My.Application.Log` object is available only for client applications. For Web applications, use `My.Log`. For more information, see <xref:Microsoft.VisualBasic.Logging.Log?displayProperty=nameWithType>.  
   
@@ -80,7 +80,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Log` object provides a straightforward entry point from which to access the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]'s logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
+ The `My.Log` object provides a straightforward entry point from which to access the .NET Framework's logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
   
  ]]></format>
         </remarks>
@@ -123,7 +123,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Log` object provides a straightforward entry point from which to access the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]'s logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
+ The `My.Log` object provides a straightforward entry point from which to access the .NET Framework's logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.VisualBasic.Logging/Log.xml b/xml/Microsoft.VisualBasic.Logging/Log.xml
index ea24478ce70..b832dd80499 100644
--- a/xml/Microsoft.VisualBasic.Logging/Log.xml
+++ b/xml/Microsoft.VisualBasic.Logging/Log.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `My.Application.Log` object provides a straightforward entry point from which to access the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]'s logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
+ The `My.Application.Log` object provides a straightforward entry point from which to access the .NET Framework's logging services. The `WriteEntry` and `WriteException` methods write messages to the application's log listeners. The listeners can be configured by the application's configuration file. For more information, see [Walkthrough: Changing Where My.Application.Log Writes Information](/dotnet/visual-basic/developing-apps/programming/log-info/walkthrough-changing-where-my-application-log-writes-information) and [Working with Application Logs](/dotnet/visual-basic/developing-apps/programming/log-info/working-with-application-logs).  
   
  The `My.Application.Log` object is available only for client applications. For Web applications, use `My.Log`. For more information, see <xref:Microsoft.VisualBasic.Logging.AspLog>.  
   
diff --git a/xml/Microsoft.VisualBasic/Collection.xml b/xml/Microsoft.VisualBasic/Collection.xml
index fcb8a834582..081e810e4ec 100644
--- a/xml/Microsoft.VisualBasic/Collection.xml
+++ b/xml/Microsoft.VisualBasic/Collection.xml
@@ -140,7 +140,7 @@ Dim coll As New Microsoft.VisualBasic.Collection()
 ## Remarks  
  The Visual Basic collection returned by this constructor is empty and does not have any initial capacity allocated.  
   
- Visual Basic collections are not compatible with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] collections available in the <xref:System.Collections?displayProperty=nameWithType>, <xref:System.Collections.Generic?displayProperty=nameWithType>, and <xref:System.Collections.Specialized?displayProperty=nameWithType> namespaces.  
+ Visual Basic collections are not compatible with the .NET Framework collections available in the <xref:System.Collections?displayProperty=nameWithType>, <xref:System.Collections.Generic?displayProperty=nameWithType>, and <xref:System.Collections.Specialized?displayProperty=nameWithType> namespaces.  
   
    
   
diff --git a/xml/System.Activities.Presentation.Hosting/AssemblyContextControlItem.xml b/xml/System.Activities.Presentation.Hosting/AssemblyContextControlItem.xml
index 33a4379ad73..9d5ff950cd8 100644
--- a/xml/System.Activities.Presentation.Hosting/AssemblyContextControlItem.xml
+++ b/xml/System.Activities.Presentation.Hosting/AssemblyContextControlItem.xml
@@ -93,7 +93,7 @@
       </Parameters>
       <Docs>
         <param name="assemblyName">The assembly name.</param>
-        <param name="multiTargetingService">The multi-targeting service used to get the proper version of the loaded assembly that corresponds to the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] of the current project.</param>
+        <param name="multiTargetingService">The multi-targeting service used to get the proper version of the loaded assembly that corresponds to the target .NET Framework of the current project.</param>
         <summary>Returns the currently loaded assembly using the multi-targeting support service.</summary>
         <returns>The assembly.</returns>
         <remarks>
@@ -125,7 +125,7 @@
         <Parameter Name="multiTargetingService" Type="System.Activities.Presentation.Hosting.IMultiTargetingSupportService" />
       </Parameters>
       <Docs>
-        <param name="multiTargetingService">The multi-targeting service used to get the proper versions of the loaded assemblies that correspond to the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] of the current project.</param>
+        <param name="multiTargetingService">The multi-targeting service used to get the proper versions of the loaded assemblies that correspond to the target .NET Framework of the current project.</param>
         <summary>Returns a collection of all the assemblies that have been loaded in the environment.</summary>
         <returns>A collection of all the assemblies that have been loaded in the environment.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
index 719951a86a6..4056957f9a6 100644
--- a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
+++ b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
@@ -16,9 +16,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- *Multi-targeting* is the ability to find the right version of the loaded assembly that corresponds to the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version of the current workflow project in [!INCLUDE[vs2010](~/includes/vs2010-md.md)].  
+ *Multi-targeting* is the ability to find the right version of the loaded assembly that corresponds to the target .NET Framework version of the current workflow project in [!INCLUDE[vs2010](~/includes/vs2010-md.md)].  
   
- This interface is implemented and used internally by [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components to resolve [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] assemblies in a multi-targeting aware fashion within the [!INCLUDE[vs2010](~/includes/vs2010-md.md)] hosting application. The [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
+ This interface is implemented and used internally by [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components to resolve .NET Framework assemblies in a multi-targeting aware fashion within the [!INCLUDE[vs2010](~/includes/vs2010-md.md)] hosting application. The [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ComponentModel.Design/DesignerActionItem.xml b/xml/System.ComponentModel.Design/DesignerActionItem.xml
index 2eceb3d85c7..75ed9787164 100644
--- a/xml/System.ComponentModel.Design/DesignerActionItem.xml
+++ b/xml/System.ComponentModel.Design/DesignerActionItem.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.ComponentModel.Design.DesignerActionItem> class serves as an abstract base for classes that represent individual panel items in a smart tag panel, which represents a menu-like user interface (UI) for smart tags. The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supplies derived classes that represent the different common entries in a smart tag panel, including plain text, header text, properties and methods of the associated <xref:System.ComponentModel.Design.DesignerActionList> class, and designer verbs.  
+ The <xref:System.ComponentModel.Design.DesignerActionItem> class serves as an abstract base for classes that represent individual panel items in a smart tag panel, which represents a menu-like user interface (UI) for smart tags. The .NET Framework supplies derived classes that represent the different common entries in a smart tag panel, including plain text, header text, properties and methods of the associated <xref:System.ComponentModel.Design.DesignerActionList> class, and designer verbs.  
   
  Typically, your `DesignerAction` feature is defined in a programmer-supplied class derived from <xref:System.ComponentModel.Design.DesignerActionList>, which contains a <xref:System.ComponentModel.Design.DesignerActionList.GetSortedActionItems%2A> method that groups individual panel items together to form the smart tag panel. The <xref:System.ComponentModel.Design.DesignerActionPropertyItem> and <xref:System.ComponentModel.Design.DesignerActionMethodItem> types are associated with members of the class derived from <xref:System.ComponentModel.Design.DesignerActionList>, and <xref:System.ComponentModel.Design.DesignerActionMethodItem> objects are activated when their associated panel entry is selected by the user.  
   
diff --git a/xml/System.ComponentModel.Design/DesignerActionListsChangedEventHandler.xml b/xml/System.ComponentModel.Design/DesignerActionListsChangedEventHandler.xml
index fd242684b75..766207ffa90 100644
--- a/xml/System.ComponentModel.Design/DesignerActionListsChangedEventHandler.xml
+++ b/xml/System.ComponentModel.Design/DesignerActionListsChangedEventHandler.xml
@@ -43,7 +43,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The event model in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] is based on having an event delegate that connects an event with its handler. To raise a <xref:System.ComponentModel.Design.DesignerActionService.DesignerActionListsChanged> event, two elements are needed:  
+ The event model in the .NET Framework is based on having an event delegate that connects an event with its handler. To raise a <xref:System.ComponentModel.Design.DesignerActionService.DesignerActionListsChanged> event, two elements are needed:  
   
 -   The <xref:System.ComponentModel.Design.DesignerActionListsChangedEventArgs> class, derived from <xref:System.EventArgs?displayProperty=nameWithType>, which holds the event data.  
   
diff --git a/xml/System.ComponentModel.Design/DesignerActionPropertyItem.xml b/xml/System.ComponentModel.Design/DesignerActionPropertyItem.xml
index de655df4c30..56b17ed4dcf 100644
--- a/xml/System.ComponentModel.Design/DesignerActionPropertyItem.xml
+++ b/xml/System.ComponentModel.Design/DesignerActionPropertyItem.xml
@@ -42,7 +42,7 @@
 |Boolean value|The item is displayed using a binary UI, such as a check mark.|  
 |None of the above.|The item is displayed as a non-editable text string using the data type's <xref:System.Object.ToString%2A> method.|  
   
- All fundamental types, such as <xref:System.Boolean?displayProperty=nameWithType>, and common [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] data types, such as <xref:System.String?displayProperty=nameWithType>, supply standard type converters and editors. For more information about type converters, see [How to: Implement a Type Converter](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ayybcxe5(v=vs.120)) or [Generalized Type Conversion](/previous-versions/visualstudio/visual-studio-2013/yy580hbd(v=vs.120)). For more information about type editors, see [How to: Implement a UI Type Editor](/previous-versions/visualstudio/visual-studio-2013/53c49eck(v=vs.120)).  
+ All fundamental types, such as <xref:System.Boolean?displayProperty=nameWithType>, and common .NET Framework data types, such as <xref:System.String?displayProperty=nameWithType>, supply standard type converters and editors. For more information about type converters, see [How to: Implement a Type Converter](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2013/ayybcxe5(v=vs.120)) or [Generalized Type Conversion](/previous-versions/visualstudio/visual-studio-2013/yy580hbd(v=vs.120)). For more information about type editors, see [How to: Implement a UI Type Editor](/previous-versions/visualstudio/visual-studio-2013/53c49eck(v=vs.120)).  
   
    
   
diff --git a/xml/System.ComponentModel.Design/DesignerActionUIStateChangeEventHandler.xml b/xml/System.ComponentModel.Design/DesignerActionUIStateChangeEventHandler.xml
index 6eac91102b8..0c5fb1351a9 100644
--- a/xml/System.ComponentModel.Design/DesignerActionUIStateChangeEventHandler.xml
+++ b/xml/System.ComponentModel.Design/DesignerActionUIStateChangeEventHandler.xml
@@ -37,7 +37,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The event model in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] is based on having an event delegate that connects an event with its handler. To raise a <xref:System.ComponentModel.Design.DesignerActionUIService.DesignerActionUIStateChange> event, two elements are needed:  
+ The event model in the .NET Framework is based on having an event delegate that connects an event with its handler. To raise a <xref:System.ComponentModel.Design.DesignerActionUIService.DesignerActionUIStateChange> event, two elements are needed:  
   
 -   The <xref:System.ComponentModel.Design.DesignerActionUIStateChangeEventArgs> class, derived from <xref:System.EventArgs?displayProperty=nameWithType>, which holds the event data.  
   
diff --git a/xml/System.ComponentModel.Design/ViewTechnology.xml b/xml/System.ComponentModel.Design/ViewTechnology.xml
index 195339e5d2c..67c40f115ce 100644
--- a/xml/System.ComponentModel.Design/ViewTechnology.xml
+++ b/xml/System.ComponentModel.Design/ViewTechnology.xml
@@ -46,7 +46,7 @@
   
  <xref:System.ComponentModel.Design.ViewTechnology> defines identifiers that can indicate the mode to use for controlling the display of a designer-hosted document.  
   
- You should only use the `Default` value in your designer hosting environment. In previous versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the `ViewTechnology` enumeration specified the type of UI model supported by a root designer. Because this model is not extensible, you should instead use a *view adapter* model. A view adapter is a type that adapts an object of one type to another.  
+ You should only use the `Default` value in your designer hosting environment. In previous versions of the .NET Framework, the `ViewTechnology` enumeration specified the type of UI model supported by a root designer. Because this model is not extensible, you should instead use a *view adapter* model. A view adapter is a type that adapts an object of one type to another.  
   
  For example, an HTML designer might return a `DemoDOM` tree as its view. The HTML designer returns a view technology of `Default`. A Windows Forms hosting environment would have one or more view adapter classes available. If one such class could convert the `DemoDOM` into a Windows Forms control, the hosting application can support this type of designer. If no adapter can handle the data type returned from the designer's <xref:System.ComponentModel.Design.IRootDesigner.GetView%2A> method, the load of the designer will fail, and the user will be presented with an error.  
   
diff --git a/xml/System.ComponentModel/AsyncOperationManager.xml b/xml/System.ComponentModel/AsyncOperationManager.xml
index 9e8992af34a..9841e1a8230 100644
--- a/xml/System.ComponentModel/AsyncOperationManager.xml
+++ b/xml/System.ComponentModel/AsyncOperationManager.xml
@@ -37,7 +37,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your class needs to provide asynchronous behavior according to the [Event-based Asynchronous Pattern Overview](/dotnet/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-overview), you will encounter a number of concurrency management issues. Among these is the requirement to ensure that event handlers are called on a thread or context that is appropriate for the application model (for example, Windows Forms applications, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications, console applications, and so on). The <xref:System.ComponentModel.AsyncOperationManager> provides a convenient way to create a class that runs properly under all application models supported by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+ If your class needs to provide asynchronous behavior according to the [Event-based Asynchronous Pattern Overview](/dotnet/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-overview), you will encounter a number of concurrency management issues. Among these is the requirement to ensure that event handlers are called on a thread or context that is appropriate for the application model (for example, Windows Forms applications, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications, console applications, and so on). The <xref:System.ComponentModel.AsyncOperationManager> provides a convenient way to create a class that runs properly under all application models supported by the .NET Framework.  
   
  The <xref:System.ComponentModel.AsyncOperationManager> class has one method, <xref:System.ComponentModel.AsyncOperationManager.CreateOperation%2A>, which returns an <xref:System.ComponentModel.AsyncOperation?displayProperty=nameWithType> that can be used to track the duration of a particular asynchronous task. The <xref:System.ComponentModel.AsyncOperation?displayProperty=nameWithType> for a task can be used to alert clients when a task completes. It can also be used to post progress updates and incremental results without terminating the operation.  
   
diff --git a/xml/System.ComponentModel/EditorAttribute.xml b/xml/System.ComponentModel/EditorAttribute.xml
index 2804620d080..d00d196a618 100644
--- a/xml/System.ComponentModel/EditorAttribute.xml
+++ b/xml/System.ComponentModel/EditorAttribute.xml
@@ -327,7 +327,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.ComponentModel.EditorAttribute.EditorBaseTypeName%2A> property is an assembly qualified type name. The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] provides both <xref:System.Drawing.Design.UITypeEditor> and <xref:System.ComponentModel.ComponentEditor> as valid base classes, but any value is valid here.  
+ The <xref:System.ComponentModel.EditorAttribute.EditorBaseTypeName%2A> property is an assembly qualified type name. The .NET Framework provides both <xref:System.Drawing.Design.UITypeEditor> and <xref:System.ComponentModel.ComponentEditor> as valid base classes, but any value is valid here.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ComponentModel/ICustomTypeDescriptor.xml b/xml/System.ComponentModel/ICustomTypeDescriptor.xml
index 9cc9b135be8..25a87b39c50 100644
--- a/xml/System.ComponentModel/ICustomTypeDescriptor.xml
+++ b/xml/System.ComponentModel/ICustomTypeDescriptor.xml
@@ -37,7 +37,7 @@
 ## Remarks  
  The <xref:System.ComponentModel.ICustomTypeDescriptor> interface allows an object to provide type information about itself. Typically, this interface is used when an object needs dynamic type information. In contrast, the <xref:System.ComponentModel.TypeDescriptor> class provides static type information that is obtained from metadata.  
   
- For example, <xref:System.ComponentModel.ICustomTypeDescriptor> is used in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] to provide type information for COM objects. COM objects do not support properties or attributes. Therefore, the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] uses <xref:System.ComponentModel.ICustomTypeDescriptor> to implement properties and attributes for COM objects.  
+ For example, <xref:System.ComponentModel.ICustomTypeDescriptor> is used in the .NET Framework to provide type information for COM objects. COM objects do not support properties or attributes. Therefore, the .NET Framework uses <xref:System.ComponentModel.ICustomTypeDescriptor> to implement properties and attributes for COM objects.  
   
  To provide dynamic custom type information, a class can implement <xref:System.ComponentModel.ICustomTypeDescriptor> or derive from the <xref:System.ComponentModel.CustomTypeDescriptor> class, which provides a simple implementation of this interface.  
   
diff --git a/xml/System.ComponentModel/TypeDescriptionProvider.xml b/xml/System.ComponentModel/TypeDescriptionProvider.xml
index a70e2e04665..1377ccffb53 100644
--- a/xml/System.ComponentModel/TypeDescriptionProvider.xml
+++ b/xml/System.ComponentModel/TypeDescriptionProvider.xml
@@ -332,7 +332,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An extended type descriptor is a custom type descriptor that offers properties that other objects have added to this object, but that are not actually defined on the object. For example, in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] component model, objects that implement the <xref:System.ComponentModel.IExtenderProvider> interface can attach properties to other objects that reside in the same logical container. The overloaded <xref:System.ComponentModel.TypeDescriptionProvider.GetTypeDescriptor%2A> methods do not return a type descriptor that provides these extra extended properties. The <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> method returns the set of these extended properties. The <xref:System.ComponentModel.TypeDescriptor> will automatically merge the results of these two property collections. While the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] component model supports only extended properties, <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> can be used for extended attributes as well as events, if the type description provider supports it.  
+ An extended type descriptor is a custom type descriptor that offers properties that other objects have added to this object, but that are not actually defined on the object. For example, in the .NET Framework component model, objects that implement the <xref:System.ComponentModel.IExtenderProvider> interface can attach properties to other objects that reside in the same logical container. The overloaded <xref:System.ComponentModel.TypeDescriptionProvider.GetTypeDescriptor%2A> methods do not return a type descriptor that provides these extra extended properties. The <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> method returns the set of these extended properties. The <xref:System.ComponentModel.TypeDescriptor> will automatically merge the results of these two property collections. While the .NET Framework component model supports only extended properties, <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> can be used for extended attributes as well as events, if the type description provider supports it.  
   
  <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> is `virtual` and, by default, returns a custom type descriptor that returns empty results if no parent provider was passed. If a parent provider was passed, this method will invoke the parent provider's <xref:System.ComponentModel.TypeDescriptionProvider.GetExtendedTypeDescriptor%2A> method.  
   
diff --git a/xml/System.Configuration/ClientSettingsSection.xml b/xml/System.Configuration/ClientSettingsSection.xml
index c0853d76d24..9883822e7f0 100644
--- a/xml/System.Configuration/ClientSettingsSection.xml
+++ b/xml/System.Configuration/ClientSettingsSection.xml
@@ -29,9 +29,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] contains a single default settings provider, <xref:System.Configuration.LocalFileSettingsProvider>, which stores configuration data to the local file system in files with the extension `.config`. The contents of configuration files are structured as XML documents. User-scoped settings are persisted in a file with the name `username.config`. Within this file, data is stored as elements within a `<userSettings>` section. Each of these sections is represented by a corresponding <xref:System.Configuration.ClientSettingsSection>. Each section object is owned and administered by a configuration section handler, which is an <xref:System.Configuration.IConfigurationSectionHandler>.  
+ The .NET Framework contains a single default settings provider, <xref:System.Configuration.LocalFileSettingsProvider>, which stores configuration data to the local file system in files with the extension `.config`. The contents of configuration files are structured as XML documents. User-scoped settings are persisted in a file with the name `username.config`. Within this file, data is stored as elements within a `<userSettings>` section. Each of these sections is represented by a corresponding <xref:System.Configuration.ClientSettingsSection>. Each section object is owned and administered by a configuration section handler, which is an <xref:System.Configuration.IConfigurationSectionHandler>.  
   
- The <xref:System.Configuration.ClientSettingsSection> class represents a simple extension of the <xref:System.Configuration.ConfigurationSection> class, which is used in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] support for general configuration files.  
+ The <xref:System.Configuration.ClientSettingsSection> class represents a simple extension of the <xref:System.Configuration.ConfigurationSection> class, which is used in the .NET Framework support for general configuration files.  
   
  For more information about application settings, see the topic [Application Settings for Windows Forms](/dotnet/framework/winforms/advanced/application-settings-for-windows-forms).  
   
diff --git a/xml/System.Configuration/ConfigurationElement.xml b/xml/System.Configuration/ConfigurationElement.xml
index b67aa8f8746..e55ffbd9c75 100644
--- a/xml/System.Configuration/ConfigurationElement.xml
+++ b/xml/System.Configuration/ConfigurationElement.xml
@@ -169,7 +169,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Configuration.ConfigurationElement.CurrentConfiguration%2A> property makes it easy to determine which version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] is targeted. The <xref:System.Configuration.Configuration.TargetFramework%2A> property of the top-level <xref:System.Configuration.Configuration> instance indicates the targeted framework version.  
+ The <xref:System.Configuration.ConfigurationElement.CurrentConfiguration%2A> property makes it easy to determine which version of the .NET Framework is targeted. The <xref:System.Configuration.Configuration.TargetFramework%2A> property of the top-level <xref:System.Configuration.Configuration> instance indicates the targeted framework version.  
   
  ]]></format>
         </remarks>
@@ -450,7 +450,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Configuration.ConfigurationElement.SerializeElement%2A> method and the <xref:System.Configuration.ConfigurationElement.SerializeToXmlElement%2A> method call this method in order to transform an assembly name when an earlier version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] is targeted.  
+ The <xref:System.Configuration.ConfigurationElement.SerializeElement%2A> method and the <xref:System.Configuration.ConfigurationElement.SerializeToXmlElement%2A> method call this method in order to transform an assembly name when an earlier version of the .NET Framework is targeted.  
   
  ]]></format>
         </remarks>
@@ -491,7 +491,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Configuration.ConfigurationElement.SerializeElement%2A> method and the <xref:System.Configuration.ConfigurationElement.SerializeToXmlElement%2A> method call this method in order to transform a type name when an earlier version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] is targeted.  
+ The <xref:System.Configuration.ConfigurationElement.SerializeElement%2A> method and the <xref:System.Configuration.ConfigurationElement.SerializeToXmlElement%2A> method call this method in order to transform a type name when an earlier version of the .NET Framework is targeted.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Configuration/ConfigurationProperty.xml b/xml/System.Configuration/ConfigurationProperty.xml
index 397ad99b748..fc8deccbf28 100644
--- a/xml/System.Configuration/ConfigurationProperty.xml
+++ b/xml/System.Configuration/ConfigurationProperty.xml
@@ -566,7 +566,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Indicates whether the assembly name for the configuration property requires transformation when it is serialized for an earlier version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>Indicates whether the assembly name for the configuration property requires transformation when it is serialized for an earlier version of the .NET Framework.</summary>
         <value>
           <see langword="true" /> if the property requires assembly name transformation; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -745,7 +745,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Indicates whether the type name for the configuration property requires transformation when it is serialized for an earlier version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>Indicates whether the type name for the configuration property requires transformation when it is serialized for an earlier version of the .NET Framework.</summary>
         <value>
           <see langword="true" /> if the property requires type-name transformation; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Configuration/ConfigurationSection.xml b/xml/System.Configuration/ConfigurationSection.xml
index add15f5ad13..e96adf77bbf 100644
--- a/xml/System.Configuration/ConfigurationSection.xml
+++ b/xml/System.Configuration/ConfigurationSection.xml
@@ -438,15 +438,15 @@
       <Docs>
         <param name="element">The <see cref="T:System.Configuration.ConfigurationElement" /> object that is a candidate for serialization.</param>
         <param name="elementName">The name of the <see cref="T:System.Configuration.ConfigurationElement" /> object as it occurs in XML.</param>
-        <param name="targetFramework">The target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</param>
-        <summary>Indicates whether the specified element should be serialized when the configuration object hierarchy is serialized for the specified target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <param name="targetFramework">The target version of the .NET Framework.</param>
+        <summary>Indicates whether the specified element should be serialized when the configuration object hierarchy is serialized for the specified target version of the .NET Framework.</summary>
         <returns>
           <see langword="true" /> if the <paramref name="element" /> should be serialized; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified element is valid for the specified version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. Existing configuration sections that were created for earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] do not have to be changed.  
+ Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified element is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default all configuration elements that are contained in the configuration section will be serialized for all framework versions.  
   
@@ -491,16 +491,16 @@
       <Docs>
         <param name="property">The <see cref="T:System.Configuration.ConfigurationProperty" /> object that is a candidate for serialization.</param>
         <param name="propertyName">The name of the <see cref="T:System.Configuration.ConfigurationProperty" /> object as it occurs in XML.</param>
-        <param name="targetFramework">The target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</param>
+        <param name="targetFramework">The target version of the .NET Framework.</param>
         <param name="parentConfigurationElement">The parent element of the property.</param>
-        <summary>Indicates whether the specified property should be serialized when the configuration object hierarchy is serialized for the specified target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>Indicates whether the specified property should be serialized when the configuration object hierarchy is serialized for the specified target version of the .NET Framework.</summary>
         <returns>
           <see langword="true" /> if the <paramref name="property" /> should be serialized; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified property is valid for the specified version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. Existing configuration sections that were created for earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] do not have to be changed.  
+ Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified property is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default all configuration properties that are contained in the configuration section will be serialized for all framework versions.  
   
@@ -540,15 +540,15 @@
         <Parameter Name="targetFramework" Type="System.Runtime.Versioning.FrameworkName" Index="0" FrameworkAlternate="dotnet-plat-ext-2.1;dotnet-plat-ext-2.2;dotnet-plat-ext-3.0;dotnet-plat-ext-3.1;dotnet-plat-ext-5.0;net-5.0;netcore-3.0;netcore-3.1;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="targetFramework">The target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</param>
-        <summary>Indicates whether the current <see cref="T:System.Configuration.ConfigurationSection" /> instance should be serialized when the configuration object hierarchy is serialized for the specified target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <param name="targetFramework">The target version of the .NET Framework.</param>
+        <summary>Indicates whether the current <see cref="T:System.Configuration.ConfigurationSection" /> instance should be serialized when the configuration object hierarchy is serialized for the specified target version of the .NET Framework.</summary>
         <returns>
           <see langword="true" /> if the current section should be serialized; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the configuration section is valid for the specified version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. Existing configuration sections that were created for earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] do not have to be changed.  
+ Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the configuration section is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default the configuration section will be serialized for all framework versions.  
   
diff --git a/xml/System.Configuration/ConfigurationSectionGroup.xml b/xml/System.Configuration/ConfigurationSectionGroup.xml
index 6868882e5ea..5918f6431e8 100644
--- a/xml/System.Configuration/ConfigurationSectionGroup.xml
+++ b/xml/System.Configuration/ConfigurationSectionGroup.xml
@@ -531,15 +531,15 @@
         <Parameter Name="targetFramework" Type="System.Runtime.Versioning.FrameworkName" Index="0" FrameworkAlternate="dotnet-plat-ext-2.1;dotnet-plat-ext-2.2;dotnet-plat-ext-3.0;dotnet-plat-ext-3.1;dotnet-plat-ext-5.0;net-5.0;netcore-3.0;netcore-3.1;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="targetFramework">The target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</param>
-        <summary>Indicates whether the current <see cref="T:System.Configuration.ConfigurationSectionGroup" /> instance should be serialized when the configuration object hierarchy is serialized for the specified target version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <param name="targetFramework">The target version of the .NET Framework.</param>
+        <summary>Indicates whether the current <see cref="T:System.Configuration.ConfigurationSectionGroup" /> instance should be serialized when the configuration object hierarchy is serialized for the specified target version of the .NET Framework.</summary>
         <returns>
           <see langword="true" /> if the current section group should be serialized; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section group that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the section group is valid for the specified version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. Existing configuration section groups that were created for earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] do not have to be changed.  
+ Each configuration section group that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the section group is valid for the specified version of the .NET Framework. Existing configuration section groups that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. In other words, if a configuration section group implementer does not override this method, by default the configuration section group will be serialized for all framework versions.  
   
diff --git a/xml/System.Configuration/ExeConfigurationFileMap.xml b/xml/System.Configuration/ExeConfigurationFileMap.xml
index 06d6d88f600..58cc564099e 100644
--- a/xml/System.Configuration/ExeConfigurationFileMap.xml
+++ b/xml/System.Configuration/ExeConfigurationFileMap.xml
@@ -107,7 +107,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You use this constructor when you are targeting a version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] that is earlier than the latest one that is installed on the computer. This constructor enables you to specify a machine configuration file that is appropriate to the version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] that you are targeting.  
+ You use this constructor when you are targeting a version of the .NET Framework that is earlier than the latest one that is installed on the computer. This constructor enables you to specify a machine configuration file that is appropriate to the version of the .NET Framework that you are targeting.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Configuration/LocalFileSettingsProvider.xml b/xml/System.Configuration/LocalFileSettingsProvider.xml
index e74ac49b9f2..540800edc96 100644
--- a/xml/System.Configuration/LocalFileSettingsProvider.xml
+++ b/xml/System.Configuration/LocalFileSettingsProvider.xml
@@ -32,7 +32,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Setting providers define a mechanism for storing configuration data used in the application settings architecture. The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] contains a single default settings provider, <xref:System.Configuration.LocalFileSettingsProvider>, which stores configuration data to the local file system. An application settings property or group of properties are associated to a specific settings provider through the use of the <xref:System.Configuration.SettingsProviderAttribute>.  
+ Setting providers define a mechanism for storing configuration data used in the application settings architecture. The .NET Framework contains a single default settings provider, <xref:System.Configuration.LocalFileSettingsProvider>, which stores configuration data to the local file system. An application settings property or group of properties are associated to a specific settings provider through the use of the <xref:System.Configuration.SettingsProviderAttribute>.  
   
  Typically, the client program does not explicitly access this class; rather, the application settings architecture automatically invokes the appropriate settings provider when its services are required. For example, many of the members of <xref:System.Configuration.ApplicationSettingsBase> delegate their work to the associated settings provider.  
   
diff --git a/xml/System.Data.EntityClient/EntityConnectionStringBuilder.xml b/xml/System.Data.EntityClient/EntityConnectionStringBuilder.xml
index 01d9e4bab9c..320873eaa11 100644
--- a/xml/System.Data.EntityClient/EntityConnectionStringBuilder.xml
+++ b/xml/System.Data.EntityClient/EntityConnectionStringBuilder.xml
@@ -394,8 +394,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the name of the underlying [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] data provider in the connection string.</summary>
-        <value>The invariant name of the underlying [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] data provider.</value>
+        <summary>Gets or sets the name of the underlying .NET Framework data provider in the connection string.</summary>
+        <value>The invariant name of the underlying .NET Framework data provider.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
diff --git a/xml/System.Data.EntityClient/EntityProviderFactory.xml b/xml/System.Data.EntityClient/EntityProviderFactory.xml
index 716fc173275..0675e2c1084 100644
--- a/xml/System.Data.EntityClient/EntityProviderFactory.xml
+++ b/xml/System.Data.EntityClient/EntityProviderFactory.xml
@@ -143,7 +143,7 @@
       <Parameters />
       <Docs>
         <summary>
-          <see cref="M:System.Data.EntityClient.EntityProviderFactory.CreateDataAdapter" /> is not supported in this version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+          <see cref="M:System.Data.EntityClient.EntityProviderFactory.CreateDataAdapter" /> is not supported in this version of the .NET Framework.</summary>
         <returns>A <see cref="T:System.NotSupportedException" /> object.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Data.Linq/DataContext.xml b/xml/System.Data.Linq/DataContext.xml
index 3d163369faf..f1e04728daa 100644
--- a/xml/System.Data.Linq/DataContext.xml
+++ b/xml/System.Data.Linq/DataContext.xml
@@ -58,8 +58,8 @@
         <Parameter Name="connection" Type="System.Data.IDbConnection" />
       </Parameters>
       <Docs>
-        <param name="connection">The connection used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Data.Linq.DataContext" /> class by referencing the connection used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <param name="connection">The connection used by the .NET Framework.</param>
+        <summary>Initializes a new instance of the <see cref="T:System.Data.Linq.DataContext" /> class by referencing the connection used by the .NET Framework.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1493,7 +1493,7 @@ Next
         <ReturnType>System.Data.Common.DbTransaction</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a local transaction for the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] to use to access the database.</summary>
+        <summary>Gets or sets a local transaction for the .NET Framework to use to access the database.</summary>
         <value>The transaction object used by the <see cref="T:System.Data.Linq.DataContext" /> when executing queries and commands.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
index 656e4dc418b..92b1e625f3e 100644
--- a/xml/System.Data.SqlClient/SqlConnection.xml
+++ b/xml/System.Data.SqlClient/SqlConnection.xml
@@ -590,7 +590,7 @@ using (SqlConnection connection = new SqlConnection(connectionString))
 
  The value in the `transactionName` parameter can be used in later calls to <xref:System.Data.SqlClient.SqlTransaction.Rollback%2A> and in the `savePoint` parameter of the <xref:System.Data.SqlClient.SqlTransaction.Save%2A> method.
 
- You must explicitly commit or roll back the transaction using the <xref:System.Data.SqlClient.SqlTransaction.Commit%2A> or <xref:System.Data.SqlClient.SqlTransaction.Rollback%2A> method. To make sure that the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server.
+ You must explicitly commit or roll back the transaction using the <xref:System.Data.SqlClient.SqlTransaction.Commit%2A> or <xref:System.Data.SqlClient.SqlTransaction.Rollback%2A> method. To make sure that the .NET Framework Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server.
 
  For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql).
 
diff --git a/xml/System.Drawing.Imaging/Metafile.xml b/xml/System.Drawing.Imaging/Metafile.xml
index e1e3ba3dc79..9ff54f53f60 100644
--- a/xml/System.Drawing.Imaging/Metafile.xml
+++ b/xml/System.Drawing.Imaging/Metafile.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file instead. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] does not have an encoder that you can use to save files as .wmf or .emf files.  
+ When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file instead. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
   
    
   
diff --git a/xml/System.Drawing/Image.xml b/xml/System.Drawing/Image.xml
index 92f669de4c3..e2832dfdd9f 100644
--- a/xml/System.Drawing/Image.xml
+++ b/xml/System.Drawing/Image.xml
@@ -1754,7 +1754,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If no encoder exists for the file format of the image, the Portable Network Graphics (PNG) encoder is used. When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] does not have an encoder that you can use to save files as .wmf or .emf files.  
+ If no encoder exists for the file format of the image, the Portable Network Graphics (PNG) encoder is used. When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
   
  Saving the image to the same file it was constructed from is not allowed and throws an exception.  
   
diff --git a/xml/System.Management/EventArrivedEventArgs.xml b/xml/System.Management/EventArrivedEventArgs.xml
index c877ecce7b6..9f668a4e90a 100644
--- a/xml/System.Management/EventArrivedEventArgs.xml
+++ b/xml/System.Management/EventArrivedEventArgs.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The following asynchronous example sets up a WMI timer to raise an event every second, and removes it when no longer needed. The <xref:System.Management.ManagementEventWatcher> defines several [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] events which are raised when WMI events are delivered. Delegates are attached to these events for handling the incoming data.  
+ The following asynchronous example sets up a WMI timer to raise an event every second, and removes it when no longer needed. The <xref:System.Management.ManagementEventWatcher> defines several .NET Framework events which are raised when WMI events are delivered. Delegates are attached to these events for handling the incoming data.  
   
  [!code-csharp[wminet_EventArrivedEventArgs#1](~/samples/snippets/csharp/VS_Snippets_WindowsServer/wminet_EventArrivedEventArgs/cs/EventArrivedEventArgs.cs#1)]
  [!code-vb[wminet_EventArrivedEventArgs#1](~/samples/snippets/visualbasic/VS_Snippets_WindowsServer/wminet_EventArrivedEventArgs/vb/EventArrivedEventArgs.vb#1)]  
diff --git a/xml/System.Management/EventArrivedEventHandler.xml b/xml/System.Management/EventArrivedEventHandler.xml
index 754e599d024..bcb838b7af1 100644
--- a/xml/System.Management/EventArrivedEventHandler.xml
+++ b/xml/System.Management/EventArrivedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following asynchronous example sets up a WMI timer to raise an event every second, and removes it when no longer needed. The <xref:System.Management.ManagementEventWatcher> defines several [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] events which are raised when WMI events are delivered. Delegates are attached to these events for handling the incoming data.  
+ The following asynchronous example sets up a WMI timer to raise an event every second, and removes it when no longer needed. The <xref:System.Management.ManagementEventWatcher> defines several .NET Framework events which are raised when WMI events are delivered. Delegates are attached to these events for handling the incoming data.  
   
  [!code-csharp[wminet_EventArrivedEventHandler#1](~/samples/snippets/csharp/VS_Snippets_WindowsServer/wminet_EventArrivedEventHandler/cs/EventArrivedEventHandler.cs#1)]
  [!code-vb[wminet_EventArrivedEventHandler#1](~/samples/snippets/visualbasic/VS_Snippets_WindowsServer/wminet_EventArrivedEventHandler/vb/EventArrivedEventHandler.vb#1)]  
diff --git a/xml/System.Numerics/BigInteger.xml b/xml/System.Numerics/BigInteger.xml
index 8dbc2dc77ac..27bb5bbe7e9 100644
--- a/xml/System.Numerics/BigInteger.xml
+++ b/xml/System.Numerics/BigInteger.xml
@@ -61,7 +61,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Numerics.BigInteger> type is an immutable type that represents an arbitrarily large integer whose value in theory has no upper or lower bounds. The members of the <xref:System.Numerics.BigInteger> type closely parallel those of other integral types (the <xref:System.Byte>, <xref:System.Int16>, <xref:System.Int32>, <xref:System.Int64>, <xref:System.SByte>, <xref:System.UInt16>, <xref:System.UInt32>, and <xref:System.UInt64> types). This type differs from the other integral types in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], which have a range indicated by their `MinValue` and `MaxValue` properties.  
+ The <xref:System.Numerics.BigInteger> type is an immutable type that represents an arbitrarily large integer whose value in theory has no upper or lower bounds. The members of the <xref:System.Numerics.BigInteger> type closely parallel those of other integral types (the <xref:System.Byte>, <xref:System.Int16>, <xref:System.Int32>, <xref:System.Int64>, <xref:System.SByte>, <xref:System.UInt16>, <xref:System.UInt32>, and <xref:System.UInt64> types). This type differs from the other integral types in the .NET Framework, which have a range indicated by their `MinValue` and `MaxValue` properties.  
   
 > [!NOTE]
 >  Because the <xref:System.Numerics.BigInteger> type is immutable (see [Mutability and the BigInteger Structure](#mutability)) and because it has no upper or lower bounds, an <xref:System.OutOfMemoryException> can be thrown for any operation that causes a <xref:System.Numerics.BigInteger> value to grow too large.  
diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index d56ec7421b0..cc8214b1d3e 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -65,7 +65,7 @@
 |Skipping JIT visibility checks, with restrictions|Public members of public types in any assembly.|All members of all types, only in assemblies whose trust levels are equal to or less than the trust level of the assembly that emitted the dynamic method.|  
   
 > [!NOTE]
->  Prior to the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Prior to the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  The following table shows which types and members are accessible to a dynamic method that is associated with a module or with a type in a module.  
   
@@ -255,7 +255,7 @@
     > [!IMPORTANT]
     >  If the permission has not been granted, a security exception is thrown when <xref:System.Reflection.Emit.DynamicMethod.CreateDelegate%2A> is called or when the dynamic method is invoked, not when this constructor is called. No special permissions are required to emit the dynamic method.  
   
- For example, a dynamic method that is created with `restrictedSkipVisibility` set to `true` can access a private member of any assembly on the call stack if the call stack has been granted restricted member access. If the dynamic method is created with partially trusted code on the call stack, it cannot access a private member of a type in a [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] assembly, because such assemblies are fully trusted.  
+ For example, a dynamic method that is created with `restrictedSkipVisibility` set to `true` can access a private member of any assembly on the call stack if the call stack has been granted restricted member access. If the dynamic method is created with partially trusted code on the call stack, it cannot access a private member of a type in a .NET Framework assembly, because such assemblies are fully trusted.  
   
  If `restrictedSkipVisibility` is `false`, JIT visibility checks are enforced. The code in the dynamic method has access to public methods of public classes, and exceptions are thrown if it tries to access types or members that are `private`, `protected`, or `internal`.  
   
diff --git a/xml/System.Reflection/TypeAttributes.xml b/xml/System.Reflection/TypeAttributes.xml
index f5cdacf0595..ca42fe637de 100644
--- a/xml/System.Reflection/TypeAttributes.xml
+++ b/xml/System.Reflection/TypeAttributes.xml
@@ -393,7 +393,7 @@
       </ReturnValue>
       <MemberValue>196608</MemberValue>
       <Docs>
-        <summary>LPSTR is interpreted by some implementation-specific means, which includes the possibility of throwing a <see cref="T:System.NotSupportedException" />. Not used in the Microsoft implementation of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>LPSTR is interpreted by some implementation-specific means, which includes the possibility of throwing a <see cref="T:System.NotSupportedException" />. Not used in the Microsoft implementation of the .NET Framework.</summary>
       </Docs>
     </Member>
     <Member MemberName="CustomFormatMask">
@@ -431,7 +431,7 @@
       </ReturnValue>
       <MemberValue>12582912</MemberValue>
       <Docs>
-        <summary>Used to retrieve non-standard encoding information for native interop. The meaning of the values of these 2 bits is unspecified. Not used in the Microsoft implementation of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>Used to retrieve non-standard encoding information for native interop. The meaning of the values of these 2 bits is unspecified. Not used in the Microsoft implementation of the .NET Framework.</summary>
       </Docs>
     </Member>
     <Member MemberName="ExplicitLayout">
diff --git a/xml/System.Runtime.Caching.Hosting/IApplicationIdentifier.xml b/xml/System.Runtime.Caching.Hosting/IApplicationIdentifier.xml
index 3fe2b806ecf..af3c9d42287 100644
--- a/xml/System.Runtime.Caching.Hosting/IApplicationIdentifier.xml
+++ b/xml/System.Runtime.Caching.Hosting/IApplicationIdentifier.xml
@@ -16,7 +16,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] host environment such as ASP.NET can use the <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier> interface to define strings that identify individual application domains. The host environment implements the <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier> interface. This interface is then available to <xref:System.Runtime.Caching.ObjectCache> implementations through the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property.  
+ A .NET Framework host environment such as ASP.NET can use the <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier> interface to define strings that identify individual application domains. The host environment implements the <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier> interface. This interface is then available to <xref:System.Runtime.Caching.ObjectCache> implementations through the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property.  
   
  A cache implementation uses this reference to obtain an identifier for the application domain. In ASP.NET, cache implementations use the application identifier to construct identifiers for cache performance counters. This provides names for performance counter instances that can be distinguished between application domains when multiple application domains are running.  
   
@@ -47,7 +47,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier.GetApplicationId%2A> method is typically implemented by a [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] host environment in order to construct an application identifier for an <xref:System.Runtime.Caching.ObjectCache> implementation. A <xref:System.Runtime.Caching.ObjectCache> implementation uses this information to identify the application domain that is currently running.  
+ The <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier.GetApplicationId%2A> method is typically implemented by a .NET Framework host environment in order to construct an application identifier for an <xref:System.Runtime.Caching.ObjectCache> implementation. A <xref:System.Runtime.Caching.ObjectCache> implementation uses this information to identify the application domain that is currently running.  
   
  For example, in ASP.NET, the cache uses an application identifier to construct identifiers for cache performance counters. The cache calls the <xref:System.Runtime.Caching.Hosting.IApplicationIdentifier.GetApplicationId%2A> method that is implemented by the host environment and the host returns the identifier. This provides names for performance counter instances that can be distinguished between application domains when multiple application domains are running.  
   
diff --git a/xml/System.Runtime.Caching/ChangeMonitor.xml b/xml/System.Runtime.Caching/ChangeMonitor.xml
index 43fbb24c7c5..07fce2cc768 100644
--- a/xml/System.Runtime.Caching/ChangeMonitor.xml
+++ b/xml/System.Runtime.Caching/ChangeMonitor.xml
@@ -29,7 +29,7 @@
   
  Derived <xref:System.Runtime.Caching.ChangeMonitor> classes can be customized to monitor dependency changes for specific different data stores. For example, there are cache implementations for a file system, physical memory, or a database. The <xref:System.Runtime.Caching.ChangeMonitor> class examines changes that occur outside the cache, and then alerts the cache that changes have occurred.  
   
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] includes the following classes that derive from <xref:System.Runtime.Caching.ChangeMonitor> class:  
+ The .NET Framework includes the following classes that derive from <xref:System.Runtime.Caching.ChangeMonitor> class:  
   
 -   <xref:System.Runtime.Caching.CacheEntryChangeMonitor>  
   
diff --git a/xml/System.Runtime.Caching/MemoryCache.xml b/xml/System.Runtime.Caching/MemoryCache.xml
index 32809345d20..bd2d2171021 100644
--- a/xml/System.Runtime.Caching/MemoryCache.xml
+++ b/xml/System.Runtime.Caching/MemoryCache.xml
@@ -29,7 +29,7 @@
  The <xref:System.Runtime.Caching.MemoryCache> class is a concrete implementation of the abstract <xref:System.Runtime.Caching.ObjectCache> class.  
   
 > [!NOTE]
->  The <xref:System.Runtime.Caching.MemoryCache> class is similar to the ASP.NET <xref:System.Web.Caching.Cache> class. The <xref:System.Runtime.Caching.MemoryCache> class has many properties and methods for accessing the cache that will be familiar to you if you have used the ASP.NET <xref:System.Web.Caching.Cache> class. The main differences between the <xref:System.Web.Caching.Cache> and <xref:System.Runtime.Caching.MemoryCache> classes are that the <xref:System.Runtime.Caching.MemoryCache> class has been changed to make it usable by [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] applications that are not ASP.NET applications. For example, the <xref:System.Runtime.Caching.MemoryCache> class has no dependencies on the `System.Web` assembly. Another difference is that you can create multiple instances of the <xref:System.Runtime.Caching.MemoryCache> class for use in the same application and in the same <xref:System.AppDomain> instance.  
+>  The <xref:System.Runtime.Caching.MemoryCache> class is similar to the ASP.NET <xref:System.Web.Caching.Cache> class. The <xref:System.Runtime.Caching.MemoryCache> class has many properties and methods for accessing the cache that will be familiar to you if you have used the ASP.NET <xref:System.Web.Caching.Cache> class. The main differences between the <xref:System.Web.Caching.Cache> and <xref:System.Runtime.Caching.MemoryCache> classes are that the <xref:System.Runtime.Caching.MemoryCache> class has been changed to make it usable by .NET Framework applications that are not ASP.NET applications. For example, the <xref:System.Runtime.Caching.MemoryCache> class has no dependencies on the `System.Web` assembly. Another difference is that you can create multiple instances of the <xref:System.Runtime.Caching.MemoryCache> class for use in the same application and in the same <xref:System.AppDomain> instance.  
   
  The <xref:System.Runtime.Caching.MemoryCache> class does not allow `null` as a value in the cache. Any attempt to add or change a cache entry with a value of `null` will fail.  
   
diff --git a/xml/System.Runtime.Caching/ObjectCache.xml b/xml/System.Runtime.Caching/ObjectCache.xml
index 24821941a9c..2f1c140cf4e 100644
--- a/xml/System.Runtime.Caching/ObjectCache.xml
+++ b/xml/System.Runtime.Caching/ObjectCache.xml
@@ -657,14 +657,14 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.Caching.ObjectCache.Host%2A> property is intended for use by [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] host environments and by cache implementations that implement behavior that depends on the .NET Framework host environment.  
+ The <xref:System.Runtime.Caching.ObjectCache.Host%2A> property is intended for use by .NET Framework host environments and by cache implementations that implement behavior that depends on the .NET Framework host environment.  
   
  The following table lists the set of host environment services that might be available from a managed hosting environment and that are available to <xref:System.Runtime.Caching.ObjectCache> implementations through the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property:  
   
 |Service|Description|  
 |-------------|-----------------|  
 |<xref:System.Runtime.Caching.Hosting.IApplicationIdentifier>|Lets host environments provide application domain identifiers that might be needed by a cache implementation for features such as identifying performance counters.|  
-|<xref:System.Runtime.Caching.Hosting.IFileChangeNotificationSystem>|Lets host environments provide a custom file-change notification system, instead of using the one provided in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].|  
+|<xref:System.Runtime.Caching.Hosting.IFileChangeNotificationSystem>|Lets host environments provide a custom file-change notification system, instead of using the one provided in the .NET Framework.|  
 |<xref:System.Runtime.Caching.Hosting.IMemoryCacheManager>|Lets cache implementations report cache memory consumption to the host environment. This enables host environments to centrally manage memory consumption across multiple cache implementations.|  
   
 > [!NOTE]
diff --git a/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml b/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
index 524b895f800..d448a221b28 100644
--- a/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
+++ b/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
@@ -62,7 +62,7 @@
   
 -   CC_SYSCALL is similar to CDECL in that arguments are pushed from right to left. The EAX, ECX, and EDX registers are not preserved.  
   
- These calling convention identifiers are used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[wince](~/includes/wince-md.md)] platform, and by Automation.  
+ These calling convention identifiers are used by the .NET Framework, the [!INCLUDE[wince](~/includes/wince-md.md)] platform, and by Automation.  
  
  The common language runtime throws an exception when a COM method in native code returns an HRESULT. For more information, see [How to: Map HRESULTs and Exceptions](/dotnet/framework/interop/how-to-map-hresults-and-exceptions).  
   
diff --git a/xml/System.Runtime.Serialization/DataMemberAttribute.xml b/xml/System.Runtime.Serialization/DataMemberAttribute.xml
index 08bdaf47352..8bf60789f29 100644
--- a/xml/System.Runtime.Serialization/DataMemberAttribute.xml
+++ b/xml/System.Runtime.Serialization/DataMemberAttribute.xml
@@ -150,7 +150,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], types have a concept of default values. For example, for any reference type the default value is `null`, and for an integer type it is 0. It is occasionally desirable to omit a data member from the serialized data when it is set to its default value. To do this, set the <xref:System.Runtime.Serialization.DataMemberAttribute.EmitDefaultValue%2A> property to `false` (it is `true` by default).  
+ In the .NET Framework, types have a concept of default values. For example, for any reference type the default value is `null`, and for an integer type it is 0. It is occasionally desirable to omit a data member from the serialized data when it is set to its default value. To do this, set the <xref:System.Runtime.Serialization.DataMemberAttribute.EmitDefaultValue%2A> property to `false` (it is `true` by default).  
   
 > [!NOTE]
 >  Setting the <xref:System.Runtime.Serialization.DataMemberAttribute.EmitDefaultValue%2A> property to `false` is not a recommended practice. It should only be done if there is a specific need to do so (such as for interoperability or to reduce data size).  
diff --git a/xml/System.Runtime.Serialization/ExportOptions.xml b/xml/System.Runtime.Serialization/ExportOptions.xml
index c97f000401b..f5505395abb 100644
--- a/xml/System.Runtime.Serialization/ExportOptions.xml
+++ b/xml/System.Runtime.Serialization/ExportOptions.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.Serialization.XsdDataContractExporter> is used to generate XSD schemas from a type or assembly. You can also use the <xref:System.Runtime.Serialization.XsdDataContractImporter> to generate [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] code from a schema document.  
+ The <xref:System.Runtime.Serialization.XsdDataContractExporter> is used to generate XSD schemas from a type or assembly. You can also use the <xref:System.Runtime.Serialization.XsdDataContractImporter> to generate .NET Framework code from a schema document.  
   
  For more information about importing and exporting schemas, see [Schema Import and Export](/dotnet/framework/wcf/feature-details/schema-import-and-export) and [Exporting Schemas from Classes](/dotnet/framework/wcf/feature-details/exporting-schemas-from-classes).  
   
diff --git a/xml/System.Runtime.Serialization/ImportOptions.xml b/xml/System.Runtime.Serialization/ImportOptions.xml
index 1872fd10100..1229f6a2760 100644
--- a/xml/System.Runtime.Serialization/ImportOptions.xml
+++ b/xml/System.Runtime.Serialization/ImportOptions.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.Serialization.XsdDataContractImporter> is used to generate code from XML schema using the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] CodeDOM. To generate an XML schema from an assembly, use the <xref:System.Runtime.Serialization.XsdDataContractExporter>.  
+ The <xref:System.Runtime.Serialization.XsdDataContractImporter> is used to generate code from XML schema using the .NET Framework CodeDOM. To generate an XML schema from an assembly, use the <xref:System.Runtime.Serialization.XsdDataContractExporter>.  
   
  For more information about importing and exporting schemas, see [Schema Import and Export](/dotnet/framework/wcf/feature-details/schema-import-and-export) and [Importing Schema to Generate Classes](/dotnet/framework/wcf/feature-details/importing-schema-to-generate-classes).  
   
@@ -134,7 +134,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This interface is used by [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] components, such as Windows Forms or Windows Presentation Foundation, to capture data changes for user interface updates. The generated properties raise a property-changed event when the value changes, allowing UI hooks to act accordingly.  
+ This interface is used by .NET Framework components, such as Windows Forms or Windows Presentation Foundation, to capture data changes for user interface updates. The generated properties raise a property-changed event when the value changes, allowing UI hooks to act accordingly.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Runtime.Serialization/XsdDataContractExporter.xml b/xml/System.Runtime.Serialization/XsdDataContractExporter.xml
index 5f15e438d74..e921eba1f3c 100644
--- a/xml/System.Runtime.Serialization/XsdDataContractExporter.xml
+++ b/xml/System.Runtime.Serialization/XsdDataContractExporter.xml
@@ -441,7 +441,7 @@
       </Parameters>
       <Docs>
         <param name="type">The <see cref="T:System.Type" /> to transform into an XML schema.</param>
-        <summary>Transforms the specified [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type into an XML schema definition language (XSD) schema.</summary>
+        <summary>Transforms the specified .NET Framework type into an XML schema definition language (XSD) schema.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Runtime.Serialization/XsdDataContractImporter.xml b/xml/System.Runtime.Serialization/XsdDataContractImporter.xml
index 48034bcfc58..ef6b9295f34 100644
--- a/xml/System.Runtime.Serialization/XsdDataContractImporter.xml
+++ b/xml/System.Runtime.Serialization/XsdDataContractImporter.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Runtime.Serialization.XsdDataContractImporter> if you are creating a Web service that must interoperate with an existing Web service, or to create data contract types from XML schemas. <xref:System.Runtime.Serialization.XsdDataContractImporter> will transform a set of XML schemas and create the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] types that represent the data contract in a selected programming language. To create the code, use the classes in the <xref:System.CodeDom> namespace.  
+ Use the <xref:System.Runtime.Serialization.XsdDataContractImporter> if you are creating a Web service that must interoperate with an existing Web service, or to create data contract types from XML schemas. <xref:System.Runtime.Serialization.XsdDataContractImporter> will transform a set of XML schemas and create the .NET Framework types that represent the data contract in a selected programming language. To create the code, use the classes in the <xref:System.CodeDom> namespace.  
   
  Conversely, use the <xref:System.Runtime.Serialization.XsdDataContractExporter> class when you have created a Web service that incorporates data represented by CLR types and when you need to export XML schemas for each data type to be consumed by other Web services. That is, <xref:System.Runtime.Serialization.XsdDataContractExporter> transforms a set of CLR types into a set of XML schemas.  
   
diff --git a/xml/System.Security.Cryptography/CngAlgorithm.xml b/xml/System.Security.Cryptography/CngAlgorithm.xml
index 8161f0ca113..73f279fd832 100644
--- a/xml/System.Security.Cryptography/CngAlgorithm.xml
+++ b/xml/System.Security.Cryptography/CngAlgorithm.xml
@@ -98,7 +98,7 @@
 ## Remarks  
  Instances of the <xref:System.Security.Cryptography.CngAlgorithm> class internally maintain the algorithm name that is specified by the `algorithm` parameter.  
   
- The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngAlgorithm> objects for algorithm types that are not represented by the static properties of the <xref:System.Security.Cryptography.CngAlgorithm> class. This capacity enables future [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] releases, service packs, and third-party developers to add new algorithms, which can be accessed just like the algorithms that are currently available.  
+ The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngAlgorithm> objects for algorithm types that are not represented by the static properties of the <xref:System.Security.Cryptography.CngAlgorithm> class. This capacity enables future .NET Framework releases, service packs, and third-party developers to add new algorithms, which can be accessed just like the algorithms that are currently available.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography/CngAlgorithmGroup.xml b/xml/System.Security.Cryptography/CngAlgorithmGroup.xml
index f1f78152b3e..a7185780368 100644
--- a/xml/System.Security.Cryptography/CngAlgorithmGroup.xml
+++ b/xml/System.Security.Cryptography/CngAlgorithmGroup.xml
@@ -98,7 +98,7 @@
 ## Remarks  
  Instances of the <xref:System.Security.Cryptography.CngAlgorithmGroup> class internally maintain the algorithm group name that is specified by the `algorithmGroup` parameter.  
   
- The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngAlgorithmGroup> objects for algorithm groups that are not represented by the static properties of the <xref:System.Security.Cryptography.CngAlgorithmGroup> class. This capacity enables future [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] releases, service packs, and third-party developers to add new algorithm groups, which can be accessed just like the algorithm groups that are currently available.  
+ The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngAlgorithmGroup> objects for algorithm groups that are not represented by the static properties of the <xref:System.Security.Cryptography.CngAlgorithmGroup> class. This capacity enables future .NET Framework releases, service packs, and third-party developers to add new algorithm groups, which can be accessed just like the algorithm groups that are currently available.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography/CngKeyBlobFormat.xml b/xml/System.Security.Cryptography/CngKeyBlobFormat.xml
index 2ff24351135..c0125783960 100644
--- a/xml/System.Security.Cryptography/CngKeyBlobFormat.xml
+++ b/xml/System.Security.Cryptography/CngKeyBlobFormat.xml
@@ -96,7 +96,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngKeyBlobFormat> objects for format types that are not represented by the static properties of the <xref:System.Security.Cryptography.CngKeyBlobFormat> class. This capacity allows future [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] releases, service packs, and third-party developers to add new key BLOB formats, which can be accessed just like the key BLOB formats that are currently available.  
+ The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngKeyBlobFormat> objects for format types that are not represented by the static properties of the <xref:System.Security.Cryptography.CngKeyBlobFormat> class. This capacity allows future .NET Framework releases, service packs, and third-party developers to add new key BLOB formats, which can be accessed just like the key BLOB formats that are currently available.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography/CngProvider.xml b/xml/System.Security.Cryptography/CngProvider.xml
index 8530acbbf77..d41686a1f85 100644
--- a/xml/System.Security.Cryptography/CngProvider.xml
+++ b/xml/System.Security.Cryptography/CngProvider.xml
@@ -98,7 +98,7 @@
 ## Remarks  
  Instances of the <xref:System.Security.Cryptography.CngProvider> class internally maintain the provider name specified by the `provider` parameter.  
   
- The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngProvider> objects for KSPs that are not represented by the static properties of the <xref:System.Security.Cryptography.CngProvider> class. This capacity enables future [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] releases, service packs, and third-party developers to add new providers, which can be accessed just like the providers that are currently available.  
+ The primary purpose of this constructor is to provide a method for creating <xref:System.Security.Cryptography.CngProvider> objects for KSPs that are not represented by the static properties of the <xref:System.Security.Cryptography.CngProvider> class. This capacity enables future .NET Framework releases, service packs, and third-party developers to add new providers, which can be accessed just like the providers that are currently available.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography/ECDiffieHellman.xml b/xml/System.Security.Cryptography/ECDiffieHellman.xml
index 6d8f8bba84c..c24004d128e 100644
--- a/xml/System.Security.Cryptography/ECDiffieHellman.xml
+++ b/xml/System.Security.Cryptography/ECDiffieHellman.xml
@@ -80,7 +80,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This constructor is called by classes that derive from the <xref:System.Security.Cryptography.ECDiffieHellman> class. The <xref:System.Security.Cryptography.ECDiffieHellmanCng> class is the only implementation that is currently included in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For information about how to create a new implementation of the Elliptic Curve Diffie-Hellman (ECDH) algorithm, see the <xref:System.Security.Cryptography.ECDiffieHellman.Create%2A> method.  
+ This constructor is called by classes that derive from the <xref:System.Security.Cryptography.ECDiffieHellman> class. The <xref:System.Security.Cryptography.ECDiffieHellmanCng> class is the only implementation that is currently included in the .NET Framework. For information about how to create a new implementation of the Elliptic Curve Diffie-Hellman (ECDH) algorithm, see the <xref:System.Security.Cryptography.ECDiffieHellman.Create%2A> method.  
   
  ]]></format>
         </remarks>
@@ -262,7 +262,7 @@
 ## Remarks  
  If you develop your own implementation of an <xref:System.Security.Cryptography.ECDiffieHellman> object, you can use the <xref:System.Security.Cryptography.ECDiffieHellman.Create%28System.String%29> method overload to create a custom `algorithm` string that specifies your implementation.  
   
- The `algorithm` parameter specifies the name of an implementation of the ECDH algorithm. The following strings all refer to the same implementation, which is the only implementation currently supported in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]:  
+ The `algorithm` parameter specifies the name of an implementation of the ECDH algorithm. The following strings all refer to the same implementation, which is the only implementation currently supported in the .NET Framework:  
   
 -   "ECDH"  
   
diff --git a/xml/System.Security.Cryptography/ECDsa.xml b/xml/System.Security.Cryptography/ECDsa.xml
index 7be8946e150..a1bb18ec68b 100644
--- a/xml/System.Security.Cryptography/ECDsa.xml
+++ b/xml/System.Security.Cryptography/ECDsa.xml
@@ -90,7 +90,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This constructor is called by classes that derive from the <xref:System.Security.Cryptography.ECDsa> class. The <xref:System.Security.Cryptography.ECDsaCng> class is the only implementation currently supported by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. You may provide your own custom implementation.  
+ This constructor is called by classes that derive from the <xref:System.Security.Cryptography.ECDsa> class. The <xref:System.Security.Cryptography.ECDsaCng> class is the only implementation currently supported by the .NET Framework. You may provide your own custom implementation.  
   
  ]]></format>
         </remarks>
@@ -269,7 +269,7 @@
         <Parameter Name="algorithm" Type="System.String" Index="0" FrameworkAlternate="net-5.0;netcore-2.0;netcore-2.1;netcore-2.2;netcore-3.0;netcore-3.1;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8;netstandard-2.0;netstandard-2.1;xamarinandroid-7.1;xamarinios-10.8;xamarinmac-3.0" />
       </Parameters>
       <Docs>
-        <param name="algorithm">The name of an ECDSA implementation. The following strings all refer to the same implementation, which is the only implementation currently supported in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]:  
+        <param name="algorithm">The name of an ECDSA implementation. The following strings all refer to the same implementation, which is the only implementation currently supported in the .NET Framework:  
   
 - "ECDsa"  
   
diff --git a/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml b/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
index 48027360e52..aae5fad6069 100644
--- a/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
+++ b/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
@@ -69,7 +69,7 @@ evaluationContext.Properties["Principal"]=new CustomPrincipal(identity);
 ```  
   
 ## Background  
- The role-based security in [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] enables applications to specify authorizations through code. By specifying the <xref:System.Security.Permissions.PrincipalPermission> demand, the <xref:System.Threading.Thread.CurrentPrincipal%2A> must satisfy the `PrincipalPermission` requirement. For example, that the user must be in a specific role or group. Otherwise, the thread is not authorized to execute the code, which results in an exception. WCF provides a set of <xref:System.ServiceModel.Description.PrincipalPermissionMode> selections to specify the <xref:System.Threading.Thread.CurrentPrincipal%2A> based on <xref:System.Security.SecurityContext> accordingly.  
+ The role-based security in .NET Framework enables applications to specify authorizations through code. By specifying the <xref:System.Security.Permissions.PrincipalPermission> demand, the <xref:System.Threading.Thread.CurrentPrincipal%2A> must satisfy the `PrincipalPermission` requirement. For example, that the user must be in a specific role or group. Otherwise, the thread is not authorized to execute the code, which results in an exception. WCF provides a set of <xref:System.ServiceModel.Description.PrincipalPermissionMode> selections to specify the <xref:System.Threading.Thread.CurrentPrincipal%2A> based on <xref:System.Security.SecurityContext> accordingly.  
   
    
   
diff --git a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
index e2fcad7b383..7273e63bffb 100644
--- a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
+++ b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
@@ -624,7 +624,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)], this property is emitted on the wire as an `<sc:Instance>` element. In prior versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], it was emitted as an `<sc:Generation>` element.  
+ Starting with the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)], this property is emitted on the wire as an `<sc:Instance>` element. In prior versions of the .NET Framework, it was emitted as an `<sc:Generation>` element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Threading/ReaderWriterLock.xml b/xml/System.Threading/ReaderWriterLock.xml
index 5773e25b34c..6fd98246694 100644
--- a/xml/System.Threading/ReaderWriterLock.xml
+++ b/xml/System.Threading/ReaderWriterLock.xml
@@ -52,7 +52,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] has two reader-writer locks, <xref:System.Threading.ReaderWriterLockSlim> and <xref:System.Threading.ReaderWriterLock>. <xref:System.Threading.ReaderWriterLockSlim> is recommended for all new development. <xref:System.Threading.ReaderWriterLockSlim> is similar to <xref:System.Threading.ReaderWriterLock>, but it has simplified rules for recursion and for upgrading and downgrading lock state. <xref:System.Threading.ReaderWriterLockSlim> avoids many cases of potential deadlock. In addition, the performance of <xref:System.Threading.ReaderWriterLockSlim> is significantly better than <xref:System.Threading.ReaderWriterLock>.  
+>  The .NET Framework has two reader-writer locks, <xref:System.Threading.ReaderWriterLockSlim> and <xref:System.Threading.ReaderWriterLock>. <xref:System.Threading.ReaderWriterLockSlim> is recommended for all new development. <xref:System.Threading.ReaderWriterLockSlim> is similar to <xref:System.Threading.ReaderWriterLock>, but it has simplified rules for recursion and for upgrading and downgrading lock state. <xref:System.Threading.ReaderWriterLockSlim> avoids many cases of potential deadlock. In addition, the performance of <xref:System.Threading.ReaderWriterLockSlim> is significantly better than <xref:System.Threading.ReaderWriterLock>.  
   
  <xref:System.Threading.ReaderWriterLock> is used to synchronize access to a resource. At any given time, it allows either concurrent read access for multiple threads, or write access for a single thread. In a situation where a resource is changed infrequently, a `ReaderWriterLock` provides better throughput than a simple one-at-a-time lock, such as <xref:System.Threading.Monitor>.  
   
diff --git a/xml/System.Threading/ReaderWriterLockSlim.xml b/xml/System.Threading/ReaderWriterLockSlim.xml
index 5fe16956572..a1e5e519ffc 100644
--- a/xml/System.Threading/ReaderWriterLockSlim.xml
+++ b/xml/System.Threading/ReaderWriterLockSlim.xml
@@ -64,7 +64,7 @@
 -   A thread that tries to enter read mode blocks if there are threads waiting to enter write mode or if there is a single thread in write mode.  
   
     > [!NOTE]
-    >  Blocking new readers when writers are queued is a lock fairness policy that favors writers. The current fairness policy balances fairness to readers and writers, to promote throughput in the most common scenarios. Future versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] may introduce new fairness policies.  
+    >  Blocking new readers when writers are queued is a lock fairness policy that favors writers. The current fairness policy balances fairness to readers and writers, to promote throughput in the most common scenarios. Future versions of the .NET Framework may introduce new fairness policies.  
   
 -   A thread that tries to enter upgradeable mode blocks if there is already a thread in upgradeable mode, if there are threads waiting to enter write mode, or if there is a single thread in write mode.  
   
diff --git a/xml/System.Web.Configuration/TrustSection.xml b/xml/System.Web.Configuration/TrustSection.xml
index 68c2457bcbc..62817b501da 100644
--- a/xml/System.Web.Configuration/TrustSection.xml
+++ b/xml/System.Web.Configuration/TrustSection.xml
@@ -155,7 +155,7 @@
   
 -   Partial trust application domains revert to being full trust at the application domain level.  
   
--   The legacy partial trust files located in the CONFIG directory in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the [!INCLUDE[net_v11_long](~/includes/net-v11-long-md.md)] or [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+-   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the [!INCLUDE[net_v11_long](~/includes/net-v11-long-md.md)] or [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] versions of the .NET Framework.  
   
 -   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
   
diff --git a/xml/System.Web.Configuration/WebConfigurationFileMap.xml b/xml/System.Web.Configuration/WebConfigurationFileMap.xml
index c029910e759..1727a82d895 100644
--- a/xml/System.Web.Configuration/WebConfigurationFileMap.xml
+++ b/xml/System.Web.Configuration/WebConfigurationFileMap.xml
@@ -80,7 +80,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You use this constructor when you are targeting a version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] that is earlier than the latest one that is installed on the computer. The method enables you to specify a machine configuration file that is appropriate to the version of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] that you are targeting.  
+ You use this constructor when you are targeting a version of the .NET Framework that is earlier than the latest one that is installed on the computer. The method enables you to specify a machine configuration file that is appropriate to the version of the .NET Framework that you are targeting.  
   
 > [!NOTE]
 >  Even though the constructor only accepts the path to the Machine.config file, the configuration system will also read the root Web.config file in the same directory where the Machine.config file exists.  
diff --git a/xml/System.Web.UI.Design.WebControls/DataPagerDesigner.xml b/xml/System.Web.UI.Design.WebControls/DataPagerDesigner.xml
index 26f640add09..82f30b223e4 100644
--- a/xml/System.Web.UI.Design.WebControls/DataPagerDesigner.xml
+++ b/xml/System.Web.UI.Design.WebControls/DataPagerDesigner.xml
@@ -72,7 +72,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] creates a new instance of the <xref:System.Web.UI.Design.WebControls.DataPagerDesigner> class when it creates the associated <xref:System.Web.UI.WebControls.DataPager> control or a copy of that control on the design surface.  
+ The .NET Framework creates a new instance of the <xref:System.Web.UI.Design.WebControls.DataPagerDesigner> class when it creates the associated <xref:System.Web.UI.WebControls.DataPager> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design.WebControls/ListViewDesigner.xml b/xml/System.Web.UI.Design.WebControls/ListViewDesigner.xml
index e2b3768c9cc..7b015c79dcc 100644
--- a/xml/System.Web.UI.Design.WebControls/ListViewDesigner.xml
+++ b/xml/System.Web.UI.Design.WebControls/ListViewDesigner.xml
@@ -64,7 +64,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally creates a new instance of the <xref:System.Web.UI.Design.WebControls.ListViewDesigner> class when it creates the associated <xref:System.Web.UI.WebControls.ListView> control or a copy of that control on the design surface.  
+ The .NET Framework internally creates a new instance of the <xref:System.Web.UI.Design.WebControls.ListViewDesigner> class when it creates the associated <xref:System.Web.UI.WebControls.ListView> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/ScriptManagerDesigner.xml b/xml/System.Web.UI.Design/ScriptManagerDesigner.xml
index 0c150cbde1b..d3b357a43e4 100644
--- a/xml/System.Web.UI.Design/ScriptManagerDesigner.xml
+++ b/xml/System.Web.UI.Design/ScriptManagerDesigner.xml
@@ -55,7 +55,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally constructs a new instance of the <xref:System.Web.UI.Design.ScriptManagerDesigner> class when it creates the associated <xref:System.Web.UI.ScriptManager> control or a copy of that control on the design surface.  
+ The .NET Framework internally constructs a new instance of the <xref:System.Web.UI.Design.ScriptManagerDesigner> class when it creates the associated <xref:System.Web.UI.ScriptManager> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/ScriptManagerProxyDesigner.xml b/xml/System.Web.UI.Design/ScriptManagerProxyDesigner.xml
index f27427dc313..6f1536a2b16 100644
--- a/xml/System.Web.UI.Design/ScriptManagerProxyDesigner.xml
+++ b/xml/System.Web.UI.Design/ScriptManagerProxyDesigner.xml
@@ -54,7 +54,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally constructs a new instance of the <xref:System.Web.UI.Design.ScriptManagerProxyDesigner> class when it creates the associated <xref:System.Web.UI.ScriptManagerProxy> control or a copy of that control on the design surface.  
+ The .NET Framework internally constructs a new instance of the <xref:System.Web.UI.Design.ScriptManagerProxyDesigner> class when it creates the associated <xref:System.Web.UI.ScriptManagerProxy> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/UpdatePanelDesigner.xml b/xml/System.Web.UI.Design/UpdatePanelDesigner.xml
index f3216317563..f389c0b68a5 100644
--- a/xml/System.Web.UI.Design/UpdatePanelDesigner.xml
+++ b/xml/System.Web.UI.Design/UpdatePanelDesigner.xml
@@ -54,7 +54,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelDesigner> class when it creates the associated <xref:System.Web.UI.UpdatePanel> control or a copy of that control on the design surface.  
+ The .NET Framework internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelDesigner> class when it creates the associated <xref:System.Web.UI.UpdatePanel> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/UpdatePanelTriggerCollectionEditor.xml b/xml/System.Web.UI.Design/UpdatePanelTriggerCollectionEditor.xml
index 354593bcfb2..75f9e366d7e 100644
--- a/xml/System.Web.UI.Design/UpdatePanelTriggerCollectionEditor.xml
+++ b/xml/System.Web.UI.Design/UpdatePanelTriggerCollectionEditor.xml
@@ -57,7 +57,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelTriggerCollectionEditor> class when the ellipsis button (…) is clicked on the <xref:System.Web.UI.UpdatePanel.Triggers%2A> property in the visual designer's property grid control at design time.  
+ The .NET Framework internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelTriggerCollectionEditor> class when the ellipsis button (…) is clicked on the <xref:System.Web.UI.UpdatePanel.Triggers%2A> property in the visual designer's property grid control at design time.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/UpdateProgressDesigner.xml b/xml/System.Web.UI.Design/UpdateProgressDesigner.xml
index 7a5b4daf172..4e8904f39e9 100644
--- a/xml/System.Web.UI.Design/UpdateProgressDesigner.xml
+++ b/xml/System.Web.UI.Design/UpdateProgressDesigner.xml
@@ -54,7 +54,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelDesigner> class when it creates the associated <xref:System.Web.UI.UpdatePanel> control or a copy of that control on the design surface.  
+ The .NET Framework internally constructs a new instance of the <xref:System.Web.UI.Design.UpdatePanelDesigner> class when it creates the associated <xref:System.Web.UI.UpdatePanel> control or a copy of that control on the design surface.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls/DataPager.xml b/xml/System.Web.UI.WebControls/DataPager.xml
index 97eb83270d1..b99f79f44b0 100644
--- a/xml/System.Web.UI.WebControls/DataPager.xml
+++ b/xml/System.Web.UI.WebControls/DataPager.xml
@@ -650,7 +650,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is primarily used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
+ This method is primarily used by the .NET Framework infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls/DataPagerField.xml b/xml/System.Web.UI.WebControls/DataPagerField.xml
index 2c593fd79c8..091a9f9f832 100644
--- a/xml/System.Web.UI.WebControls/DataPagerField.xml
+++ b/xml/System.Web.UI.WebControls/DataPagerField.xml
@@ -405,7 +405,7 @@
 ## Remarks  
  The <xref:System.Web.UI.WebControls.DataPagerField.LoadViewState%2A> method restores view-state information for the <xref:System.Web.UI.WebControls.DataPagerField> object that was saved by the <xref:System.Web.UI.WebControls.DataPagerField.SaveViewState%2A> method during a previous page request.  
   
- This method is primarily used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
+ This method is primarily used by the .NET Framework infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls/ListView.xml b/xml/System.Web.UI.WebControls/ListView.xml
index 59cb3b54451..9f66476f56d 100644
--- a/xml/System.Web.UI.WebControls/ListView.xml
+++ b/xml/System.Web.UI.WebControls/ListView.xml
@@ -4249,7 +4249,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This method is primarily used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).
+ This method is primarily used by the .NET Framework infrastructure and is not intended to be used directly from your code. However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).
 
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls/SqlDataSourceView.xml b/xml/System.Web.UI.WebControls/SqlDataSourceView.xml
index 1ac14620303..fcd9b252003 100644
--- a/xml/System.Web.UI.WebControls/SqlDataSourceView.xml
+++ b/xml/System.Web.UI.WebControls/SqlDataSourceView.xml
@@ -1393,7 +1393,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is primarily used by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] infrastructure and is not intended to be used directly from your code.  However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
+ This method is primarily used by the .NET Framework infrastructure and is not intended to be used directly from your code.  However, control developers can override this method to specify how a custom server control restores its view state. For more information, see [ASP.NET State Management Overview](https://docs.microsoft.com/previous-versions/aspnet/75x4ha6s(v=vs.100)).  
   
  The <xref:System.Web.UI.WebControls.SqlDataSourceView.LoadViewState%2A> method restores view-state information for the <xref:System.Web.UI.WebControls.SqlDataSourceView> object from a previous page request that was saved by the <xref:System.Web.UI.WebControls.SqlDataSourceView.SaveViewState%2A> method.  
   
diff --git a/xml/System.Windows.Forms.Layout/ArrangedElementCollection.xml b/xml/System.Windows.Forms.Layout/ArrangedElementCollection.xml
index 68f1cfd97c8..9512185f339 100644
--- a/xml/System.Windows.Forms.Layout/ArrangedElementCollection.xml
+++ b/xml/System.Windows.Forms.Layout/ArrangedElementCollection.xml
@@ -33,7 +33,7 @@
 ## Remarks  
  The <xref:System.Windows.Forms.Layout.ArrangedElementCollection> class represents a collection of objects arranged on a design surface or inside a parent <xref:System.Windows.Forms.ContainerControl?displayProperty=nameWithType>.  
   
- There are no publicly defined constructors in <xref:System.Windows.Forms.Layout.ArrangedElementCollection> because it is designed to be used only internally within the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. However, classes derived from <xref:System.Windows.Forms.Layout.ArrangedElementCollection>, such as <xref:System.Windows.Forms.Control.ControlCollection?displayProperty=nameWithType>, are available to the developer.  
+ There are no publicly defined constructors in <xref:System.Windows.Forms.Layout.ArrangedElementCollection> because it is designed to be used only internally within the .NET Framework. However, classes derived from <xref:System.Windows.Forms.Layout.ArrangedElementCollection>, such as <xref:System.Windows.Forms.Control.ControlCollection?displayProperty=nameWithType>, are available to the developer.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Forms/AccessibleObject.xml b/xml/System.Windows.Forms/AccessibleObject.xml
index b3965de5cfa..3bc049272b6 100644
--- a/xml/System.Windows.Forms/AccessibleObject.xml
+++ b/xml/System.Windows.Forms/AccessibleObject.xml
@@ -59,7 +59,7 @@
  For more information about accessibility, including information about accessibility applications, see [Windows Accessibility features](/windows/win32/winauto/about-windows-accessibility-features).
   
 > [!NOTE]
->  To use the <xref:System.Windows.Forms.AccessibleObject>, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. Windows Forms only supports Active Accessibility 2.0.  
+>  To use the <xref:System.Windows.Forms.AccessibleObject>, you must add a reference to the `Accessibility` assembly installed with the .NET Framework. Windows Forms only supports Active Accessibility 2.0.  
   
    
   
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index c4106dec4cb..e6be4b94483 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1513,7 +1513,7 @@
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
  You should never call this method if your Windows Forms code is hosted in another application, such as Internet Explorer. Only call this method in stand-alone Windows Forms applications.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index e23f0338814..76efb0bf418 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1649,7 +1649,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index be1a5a3410c..98e11b341f0 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1701,7 +1701,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Control.xml b/xml/System.Windows.Forms/Control.xml
index 4333a01b6b5..59bfc1348fa 100644
--- a/xml/System.Windows.Forms/Control.xml
+++ b/xml/System.Windows.Forms/Control.xml
@@ -493,7 +493,7 @@
  If no <xref:System.Windows.Forms.AccessibleObject> is currently assigned to the control, a new instance of one is created.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the[!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the.NET Framework.  
   
  For more information about accessible objects, see [Active Accessibility](/windows/win32/winauto/microsoft-active-accessibility).  
   
@@ -2967,7 +2967,7 @@ The following table lists Windows Forms controls and which event (<xref:System.W
  If you do not explicitly call the <xref:System.Windows.Forms.Control.CreateAccessibilityInstance%2A> method, it will be called when the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property is referenced.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
    
   
@@ -13080,7 +13080,7 @@ MyControl.Font = New Font(MyControl.Font, _
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- After dragging has begun, this method is called repeatedly by the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] until the drag operation is either canceled or completed.  
+ After dragging has begun, this method is called repeatedly by the .NET Framework until the drag operation is either canceled or completed.  
   
 > [!NOTE]
 >  Override this method if you want to change the point at which dragging is canceled or at which a drop occurs.  
diff --git a/xml/System.Windows.Forms/DataGridViewCell.xml b/xml/System.Windows.Forms/DataGridViewCell.xml
index 7afb00cfccc..48636ab6ef7 100644
--- a/xml/System.Windows.Forms/DataGridViewCell.xml
+++ b/xml/System.Windows.Forms/DataGridViewCell.xml
@@ -112,7 +112,7 @@
  If no <xref:System.Windows.Forms.AccessibleObject> is currently assigned to the control, a new instance of one is created.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
  For more information about accessible objects, see [Active Accessibility](/windows/win32/winauto/microsoft-active-accessibility).
   
@@ -579,7 +579,7 @@
  If you do not explicitly call the <xref:System.Windows.Forms.DataGridViewCell.CreateAccessibilityInstance%2A> method, it will be called when the <xref:System.Windows.Forms.DataGridViewCell.AccessibilityObject%2A> property is referenced.  
   
 > [!NOTE]
->  To get or set <xref:System.Windows.Forms.DataGridViewCell.AccessibilityObject%2A>, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set <xref:System.Windows.Forms.DataGridViewCell.AccessibilityObject%2A>, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/DataGridViewRow.xml b/xml/System.Windows.Forms/DataGridViewRow.xml
index e342635b6ec..436eee80e74 100644
--- a/xml/System.Windows.Forms/DataGridViewRow.xml
+++ b/xml/System.Windows.Forms/DataGridViewRow.xml
@@ -118,7 +118,7 @@
  If no <xref:System.Windows.Forms.AccessibleObject> is currently assigned to the control, a new instance of one is created.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.DataGridViewRow.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.DataGridViewRow.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
  For more information about accessible objects, see [Active Accessibility](/windows/win32/winauto/microsoft-active-accessibility).  
   
@@ -386,7 +386,7 @@
  If you do not explicitly call the <xref:System.Windows.Forms.DataGridViewRow.CreateAccessibilityInstance%2A> method, it will be called when the <xref:System.Windows.Forms.DataGridViewRow.AccessibilityObject%2A> property is referenced.  
   
 > [!NOTE]
->  To get or set <xref:System.Windows.Forms.DataGridViewRow.AccessibilityObject%2A>, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set <xref:System.Windows.Forms.DataGridViewRow.AccessibilityObject%2A>, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Form.xml b/xml/System.Windows.Forms/Form.xml
index ed211bd6487..c2e493c2498 100644
--- a/xml/System.Windows.Forms/Form.xml
+++ b/xml/System.Windows.Forms/Form.xml
@@ -1211,7 +1211,7 @@
 >  When the <xref:System.Windows.Forms.Form.Close%2A> method is called on a <xref:System.Windows.Forms.Form> displayed as a modeless window, you cannot call the <xref:System.Windows.Forms.Control.Show%2A> method to make the form visible, because the form's resources have already been released. To hide a form and then make it visible, use the <xref:System.Windows.Forms.Control.Hide%2A?displayProperty=nameWithType> method.  
   
 > [!CAUTION]
->  Prior to the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0, the <xref:System.Windows.Forms.Form.Closed?displayProperty=nameWithType> and <xref:System.Windows.Forms.Form.Closing?displayProperty=nameWithType> events are not raised when the <xref:System.Windows.Forms.Application.Exit%2A?displayProperty=nameWithType> method is called to exit your application. If you have validation code in either of these events that must be executed, you should call the <xref:System.Windows.Forms.Form.Close%2A?displayProperty=nameWithType> method for each open form individually before calling the <xref:System.Windows.Forms.Application.Exit%2A> method.  
+>  Prior to the .NET Framework 2.0, the <xref:System.Windows.Forms.Form.Closed?displayProperty=nameWithType> and <xref:System.Windows.Forms.Form.Closing?displayProperty=nameWithType> events are not raised when the <xref:System.Windows.Forms.Application.Exit%2A?displayProperty=nameWithType> method is called to exit your application. If you have validation code in either of these events that must be executed, you should call the <xref:System.Windows.Forms.Form.Close%2A?displayProperty=nameWithType> method for each open form individually before calling the <xref:System.Windows.Forms.Application.Exit%2A> method.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index 30e392a17f8..6315c231660 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1168,7 +1168,7 @@
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/HtmlDocument.xml b/xml/System.Windows.Forms/HtmlDocument.xml
index fb7e5375d27..ea2267df4a1 100644
--- a/xml/System.Windows.Forms/HtmlDocument.xml
+++ b/xml/System.Windows.Forms/HtmlDocument.xml
@@ -52,7 +52,7 @@
  HTML files may contain `SCRIPT` tags that encapsulate code written in one of the Active Scripting languages, such as JScript or VBScript. The <xref:System.Windows.Forms.HtmlDocument.InvokeScript%2A> method provides for execution of properties and methods defined in a `SCRIPT` tag.  
   
 > [!NOTE]
->  While most of the properties, methods, and events on <xref:System.Windows.Forms.HtmlDocument> have kept the same names as they have on the unmanaged DOM, some have been changed for consistency with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  While most of the properties, methods, and events on <xref:System.Windows.Forms.HtmlDocument> have kept the same names as they have on the unmanaged DOM, some have been changed for consistency with the .NET Framework.  
   
    
   
@@ -129,7 +129,7 @@
 ## Remarks  
  A link is active when a user is clicking on it. Change this property to change the color of the link prior to navigation.  
   
- The <xref:System.Drawing.Color> type in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
+ The <xref:System.Drawing.Color> type in the .NET Framework supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
   
  ]]></format>
         </remarks>
@@ -243,7 +243,7 @@
 ## Remarks  
  <xref:System.Windows.Forms.HtmlDocument.BackColor%2A> will display when no other element occupies that area of the screen.  
   
- The <xref:System.Drawing.Color> type in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
+ The <xref:System.Drawing.Color> type in the .NET Framework supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
   
  ]]></format>
         </remarks>
@@ -835,7 +835,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Drawing.Color><xref:System.Drawing.Color> type in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
+ The <xref:System.Drawing.Color><xref:System.Drawing.Color> type in the .NET Framework supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
   
  ]]></format>
         </remarks>
@@ -1286,7 +1286,7 @@ window.alert("Name is " + name + "; address is " + address);
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Drawing.Color> type in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
+ The <xref:System.Drawing.Color> type in the .NET Framework supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
   
  ]]></format>
         </remarks>
@@ -1847,7 +1847,7 @@ window.alert("Name is " + name + "; address is " + address);
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `Color` type in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
+ The `Color` type in the .NET Framework supports an `Alpha` value, but the HTML DOM does not. Therefore, `Alpha` will have no effect when assigned to this property.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index bf58a1c69ff..4805fdefcab 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2283,7 +2283,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index 86f05faae83..d1c6e44416d 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1706,7 +1706,7 @@
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/ListControl.xml b/xml/System.Windows.Forms/ListControl.xml
index 707da4c88ed..078510a2951 100644
--- a/xml/System.Windows.Forms/ListControl.xml
+++ b/xml/System.Windows.Forms/ListControl.xml
@@ -613,7 +613,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The format string used must follow standard [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] format specifications. For more information, see [Formatting Types in the .NET Framework](/dotnet/standard/base-types/formatting-types).  
+ The format string used must follow standard .NET Framework format specifications. For more information, see [Formatting Types in the .NET Framework](/dotnet/standard/base-types/formatting-types).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/ListView.xml b/xml/System.Windows.Forms/ListView.xml
index be5d3beedf9..f7448b02f1f 100644
--- a/xml/System.Windows.Forms/ListView.xml
+++ b/xml/System.Windows.Forms/ListView.xml
@@ -71,7 +71,7 @@
  You can also set a background image for the <xref:System.Windows.Forms.ListView> with the <xref:System.Windows.Forms.Control.BackgroundImage%2A> property. Your application must have the <xref:System.STAThreadAttribute> on its `Main` method to correctly display the background image for the <xref:System.Windows.Forms.ListView> control. In addition, if a <xref:System.Windows.Forms.ListView> control with a background image is hosted in Internet Explorer, specify comctl32.dll version 6.0 as a dependent assembly in the application manifest file to ensure the background image is property displayed.
 
 > [!NOTE]
->  Setting the <xref:System.Windows.Forms.Control.Cursor%2A> property for a <xref:System.Windows.Forms.ListView> control has no affect on the appearance of the cursor in [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] versions 1.1 and earlier.
+>  Setting the <xref:System.Windows.Forms.Control.Cursor%2A> property for a <xref:System.Windows.Forms.ListView> control has no affect on the appearance of the cursor in .NET Framework versions 1.1 and earlier.
 
  Windows XP and Windows Server 2003 provide three features that enhance the <xref:System.Windows.Forms.ListView> control when your application calls the <xref:System.Windows.Forms.Application.EnableVisualStyles%2A?displayProperty=nameWithType> method: tile view, grouping, and the insertion mark.
 
@@ -5240,7 +5240,7 @@ When this property is set to `false`, selected items in the <xref:System.Windows
  When this property is set to `true`, the <xref:System.Windows.Forms.ListView> displays a vertical scroll bar to use when the number of items exceeds the size of the client area of the control. You can use this property to ensure that the user can access all items that are available in the <xref:System.Windows.Forms.ListView> control.
 
 > [!NOTE]
->  In versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] prior to version 2.0, the column headers were not painted correctly when setting this property to `false` and resizing the control to make it larger. To work around this issue, set this property to `true` in a <xref:System.Windows.Forms.Form.ResizeBegin> event handler and set it back to `false` in a <xref:System.Windows.Forms.Form.ResizeEnd> event handler.
+>  In versions of the .NET Framework prior to version 2.0, the column headers were not painted correctly when setting this property to `false` and resizing the control to make it larger. To work around this issue, set this property to `true` in a <xref:System.Windows.Forms.Form.ResizeBegin> event handler and set it back to `false` in a <xref:System.Windows.Forms.Form.ResizeEnd> event handler.
 
  ]]></format>
         </remarks>
@@ -5938,7 +5938,7 @@ When this property is set to `false`, selected items in the <xref:System.Windows
 > [!NOTE]
 >  Setting this property has no effect when the <xref:System.Windows.Forms.ListView.Scrollable%2A> property value is `false`.
 >
->  Setting this property is not supported in versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] prior to version 2.0.
+>  Setting this property is not supported in versions of the .NET Framework prior to version 2.0.
 
 
 
@@ -6064,14 +6064,14 @@ When this property is set to `false`, selected items in the <xref:System.Windows
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether the <see cref="T:System.Windows.Forms.ListView" /> uses state image behavior that is compatible with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 1.1 or the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0.</summary>
+        <summary>Gets or sets a value indicating whether the <see cref="T:System.Windows.Forms.ListView" /> uses state image behavior that is compatible with the .NET Framework 1.1 or the .NET Framework 2.0.</summary>
         <value>
-          <see langword="true" /> if the state image behavior is compatible with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 1.1; <see langword="false" /> if the behavior is compatible with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0. The default is <see langword="true" />.</value>
+          <see langword="true" /> if the state image behavior is compatible with the .NET Framework 1.1; <see langword="false" /> if the behavior is compatible with the .NET Framework 2.0. The default is <see langword="true" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Changes to the <xref:System.Windows.Forms.ListView> control in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0 enable custom state images to be set to indicate whether an item is checked or unchecked or in an indeterminate state. With the addition of this feature, the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 2.0 has different behavior than the .NET Framework 1.1. If you have created applications that depend on the behavior in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] 1.1, be sure that the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property is set to `true`, which is the default value. In order to fully take advantage of custom state images, set <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> to `false`.
+ Changes to the <xref:System.Windows.Forms.ListView> control in the .NET Framework 2.0 enable custom state images to be set to indicate whether an item is checked or unchecked or in an indeterminate state. With the addition of this feature, the .NET Framework 2.0 has different behavior than the .NET Framework 1.1. If you have created applications that depend on the behavior in the .NET Framework 1.1, be sure that the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property is set to `true`, which is the default value. In order to fully take advantage of custom state images, set <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> to `false`.
 
 > [!NOTE]
 >  If you are using the [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer, the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property will be set to `false`.
diff --git a/xml/System.Windows.Forms/MaskedTextBox.xml b/xml/System.Windows.Forms/MaskedTextBox.xml
index 0b586e77fce..409f4a294f0 100644
--- a/xml/System.Windows.Forms/MaskedTextBox.xml
+++ b/xml/System.Windows.Forms/MaskedTextBox.xml
@@ -86,7 +86,7 @@
 ## Compatibility with Visual Basic 6.0  
  <xref:System.Windows.Forms.MaskedTextBox> was designed to retain most of the functionality of the Masked Edit control in Visual Basic 6.0. The following table lists common properties on the Masked Edit control and gives their equivalents on <xref:System.Windows.Forms.MaskedTextBox>.  
   
-|Masked Edit control (Visual Basic 6.0) property|Equivalent MaskedTextBox ([!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]) property|  
+|Masked Edit control (Visual Basic 6.0) property|Equivalent MaskedTextBox (.NET Framework) property|  
 |-------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------|  
 |`AllowPrompt` property|<xref:System.Windows.Forms.MaskedTextBox.AllowPromptAsInput%2A>|  
 |`AutoTab` property|None|  
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index 6dfa2581137..efc9994f72d 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3896,7 +3896,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/SplitContainer.xml b/xml/System.Windows.Forms/SplitContainer.xml
index e15d9c3578b..2a9e2f352d3 100644
--- a/xml/System.Windows.Forms/SplitContainer.xml
+++ b/xml/System.Windows.Forms/SplitContainer.xml
@@ -61,7 +61,7 @@
  Use the <xref:System.Windows.Forms.SplitContainer> control to divide the display area of a container (such as a <xref:System.Windows.Forms.Form>) and allow the user to resize controls that are added to the <xref:System.Windows.Forms.SplitContainer> panels. When the user passes the mouse pointer over the splitter, the cursor changes to indicate that the controls inside the <xref:System.Windows.Forms.SplitContainer> control can be resized.  
   
 > [!NOTE]
->  Previous versions of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] only support the <xref:System.Windows.Forms.Splitter> control.  
+>  Previous versions of the .NET Framework only support the <xref:System.Windows.Forms.Splitter> control.  
   
  <xref:System.Windows.Forms.SplitContainer> also eases control placement at design time. For example, to create a window similar to Windows Explorer, add a <xref:System.Windows.Forms.SplitContainer> control to a <xref:System.Windows.Forms.Form> and set its <xref:System.Windows.Forms.Control.Dock%2A> property to `DockStyle.Fill`. Add a <xref:System.Windows.Forms.TreeView> control to the <xref:System.Windows.Forms.Form> and set its <xref:System.Windows.Forms.Control.Dock%2A> property to `DockStyle.Fill`. To complete the layout, add a <xref:System.Windows.Forms.ListView> control and set its <xref:System.Windows.Forms.Control.Dock%2A> property to `DockStyle.Fill` to have the <xref:System.Windows.Forms.ListView> occupy the remaining space on the <xref:System.Windows.Forms.Form>. At run time, the user can then resize the width of both controls using the splitter. Use the <xref:System.Windows.Forms.SplitContainer.FixedPanel%2A> property to specify that a control should not be resized along with the <xref:System.Windows.Forms.Form> or other container.  
   
diff --git a/xml/System.Windows.Forms/ToolStripOverflow.xml b/xml/System.Windows.Forms/ToolStripOverflow.xml
index 0d407c3876c..e65e0e475b7 100644
--- a/xml/System.Windows.Forms/ToolStripOverflow.xml
+++ b/xml/System.Windows.Forms/ToolStripOverflow.xml
@@ -95,7 +95,7 @@
  If you do not explicitly call the <xref:System.Windows.Forms.ToolStripOverflow.CreateAccessibilityInstance%2A> method, it will be called when the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property is referenced.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
    
   
diff --git a/xml/System.Windows.Forms/ToolStripOverflowButton.xml b/xml/System.Windows.Forms/ToolStripOverflowButton.xml
index fb98588afea..cd960ff0074 100644
--- a/xml/System.Windows.Forms/ToolStripOverflowButton.xml
+++ b/xml/System.Windows.Forms/ToolStripOverflowButton.xml
@@ -61,7 +61,7 @@
  If you do not explicitly call the <xref:System.Windows.Forms.ToolStripOverflowButton.CreateAccessibilityInstance%2A> method, it will be called when the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property is referenced.  
   
 > [!NOTE]
->  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].  
+>  To get or set the <xref:System.Windows.Forms.Control.AccessibilityObject%2A> property, you must add a reference to the `Accessibility` assembly installed with the .NET Framework.  
   
    
   
diff --git a/xml/System.Workflow.ComponentModel.Compiler/CompileWorkflowTask.xml b/xml/System.Workflow.ComponentModel.Compiler/CompileWorkflowTask.xml
index 3967d8a217d..e4cb95cb43d 100644
--- a/xml/System.Workflow.ComponentModel.Compiler/CompileWorkflowTask.xml
+++ b/xml/System.Workflow.ComponentModel.Compiler/CompileWorkflowTask.xml
@@ -513,8 +513,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] of the current project.</summary>
-        <value>The target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] of the current project.</value>
+        <summary>Gets or sets the target .NET Framework of the current project.</summary>
+        <value>The target .NET Framework of the current project.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Workflow.ComponentModel.Compiler/TypeProvider.xml b/xml/System.Workflow.ComponentModel.Compiler/TypeProvider.xml
index 108cb3cde90..b17e2cbbb26 100644
--- a/xml/System.Workflow.ComponentModel.Compiler/TypeProvider.xml
+++ b/xml/System.Workflow.ComponentModel.Compiler/TypeProvider.xml
@@ -564,9 +564,9 @@
       <Docs>
         <param name="property">The property to resolve.</param>
         <param name="declaringInstance">The instance in which the specified property is declared.</param>
-        <summary>Returns a value that determines whether the specified property is supported in the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
+        <summary>Returns a value that determines whether the specified property is supported in the target .NET Framework.</summary>
         <returns>
-          <see langword="true" /> if the specified property is supported in the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the specified property is supported in the target .NET Framework; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -586,8 +586,8 @@
         <ReturnType>System.Func&lt;System.Reflection.PropertyInfo,System.Object,System.Boolean&gt;</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the delegate that references a method with two parameters and one return value that determines whether a specified property is supported in the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
-        <value>The delegate that references a method with two parameters and one return value that determines whether a specified property is supported in the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</value>
+        <summary>Gets or sets the delegate that references a method with two parameters and one return value that determines whether a specified property is supported in the target .NET Framework.</summary>
+        <value>The delegate that references a method with two parameters and one return value that determines whether a specified property is supported in the target .NET Framework.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Workflow.ComponentModel.Compiler/WorkflowCompilerOptionsService.xml b/xml/System.Workflow.ComponentModel.Compiler/WorkflowCompilerOptionsService.xml
index 0c6a598b482..dc46133ec1f 100644
--- a/xml/System.Workflow.ComponentModel.Compiler/WorkflowCompilerOptionsService.xml
+++ b/xml/System.Workflow.ComponentModel.Compiler/WorkflowCompilerOptionsService.xml
@@ -164,8 +164,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version for the compiled workflow assembly.</summary>
-        <value>The target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version for the compiled workflow assembly.</value>
+        <summary>Gets the target .NET Framework version for the compiled workflow assembly.</summary>
+        <value>The target .NET Framework version for the compiled workflow assembly.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Workflow.ComponentModel.Design/IExtendedUIService2.xml b/xml/System.Workflow.ComponentModel.Design/IExtendedUIService2.xml
index 8cd21055a6c..3ad252fc7e9 100644
--- a/xml/System.Workflow.ComponentModel.Design/IExtendedUIService2.xml
+++ b/xml/System.Workflow.ComponentModel.Design/IExtendedUIService2.xml
@@ -74,8 +74,8 @@
         <Parameter Name="reflectionType" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="reflectionType">The reflection type that depends on the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version.</param>
-        <summary>Returns the current runtime type for the specified reflection type. The reflection type depends on the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version.</summary>
+        <param name="reflectionType">The reflection type that depends on the target .NET Framework version.</param>
+        <summary>Returns the current runtime type for the specified reflection type. The reflection type depends on the target .NET Framework version.</summary>
         <returns>The current runtime type.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -97,8 +97,8 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version of the current project.</summary>
-        <returns>The target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version of the current project.</returns>
+        <summary>Returns the target .NET Framework version of the current project.</summary>
+        <returns>The target .NET Framework version of the current project.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -122,9 +122,9 @@
       </Parameters>
       <Docs>
         <param name="type">The type to check.</param>
-        <summary>Returns a value that indicates whether the specified type is supported in the current target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version.</summary>
+        <summary>Returns a value that indicates whether the specified type is supported in the current target .NET Framework version.</summary>
         <returns>
-          <see langword="true" /> if the specified type is supported in the current target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] version; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the specified type is supported in the current target .NET Framework version; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Workflow.ComponentModel.Design/WorkflowDesignerLoader.xml b/xml/System.Workflow.ComponentModel.Design/WorkflowDesignerLoader.xml
index f5de2783845..ea836087da8 100644
--- a/xml/System.Workflow.ComponentModel.Design/WorkflowDesignerLoader.xml
+++ b/xml/System.Workflow.ComponentModel.Design/WorkflowDesignerLoader.xml
@@ -630,8 +630,8 @@
         <ReturnType>System.ComponentModel.TypeDescriptionProvider</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="T:System.ComponentModel.TypeDescriptor" /> metadata of the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</summary>
-        <value>The <see cref="T:System.ComponentModel.TypeDescriptor" /> metadata of the target [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)].</value>
+        <summary>Gets the <see cref="T:System.ComponentModel.TypeDescriptor" /> metadata of the target .NET Framework.</summary>
+        <value>The <see cref="T:System.ComponentModel.TypeDescriptor" /> metadata of the target .NET Framework.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Xml.Serialization.Configuration/RootedPathValidator.xml b/xml/System.Xml.Serialization.Configuration/RootedPathValidator.xml
index 861dd278e01..4ad86f87e0b 100644
--- a/xml/System.Xml.Serialization.Configuration/RootedPathValidator.xml
+++ b/xml/System.Xml.Serialization.Configuration/RootedPathValidator.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When adding a `WebReference` object to a Web service in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], files are created by the Web service discovery process.  
+ When adding a `WebReference` object to a Web service in the .NET Framework, files are created by the Web service discovery process.  
   
  Web service clients learn where to find the Web service description (WSDL) document by adding a `WebReference` object. The Web service clients then save the discovered documents to the disk by using the `WriteAll` method. For example, the discovered documents may be .xsd schema files or service descriptions. At the end of the process, the client deletes the files. You can change the default location of the files in the temporary folder by using the `tempFilesLocation` switch in the `<xmlSerializer>` element, specified in the Machine.config configuration file, as in the following example.  
   
@@ -33,7 +33,7 @@
 </configuration>  
 ```  
   
- The value of `tempFilesLocation` must be an absolute path. If the path specified is not absolute, the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] generates a <xref:System.Configuration.ConfigurationErrorsException> exception when the configuration section is referenced.  
+ The value of `tempFilesLocation` must be an absolute path. If the path specified is not absolute, the .NET Framework generates a <xref:System.Configuration.ConfigurationErrorsException> exception when the configuration section is referenced.  
   
  The value of the property is truncated to remove leading and trailing white spaces.  
   
diff --git a/xml/System.Xml.Serialization/IXmlSerializable.xml b/xml/System.Xml.Serialization/IXmlSerializable.xml
index 418dadd7c7b..6775b3e452b 100644
--- a/xml/System.Xml.Serialization/IXmlSerializable.xml
+++ b/xml/System.Xml.Serialization/IXmlSerializable.xml
@@ -126,7 +126,7 @@
   
  If providing schema information is necessary, you should use the <xref:System.Xml.Serialization.XmlSchemaProviderAttribute> attribute. The `GetSchema` method should still return `null` (or `Nothing`).  
   
- Some [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] types as well as legacy custom types implementing the `IXmlSerializable` interface may be using `GetSchema` instead of `XmlSchemaProvider`. In this case, the method returns an accurate XML schema that describes the XML representation of the object generated by the <xref:System.Data.DataSet.WriteXml%2A> method.  
+ Some .NET Framework types as well as legacy custom types implementing the `IXmlSerializable` interface may be using `GetSchema` instead of `XmlSchemaProvider`. In this case, the method returns an accurate XML schema that describes the XML representation of the object generated by the <xref:System.Data.DataSet.WriteXml%2A> method.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Xml.XPath/XPathItem.xml b/xml/System.Xml.XPath/XPathItem.xml
index 9e96804360b..54c9bb3b547 100644
--- a/xml/System.Xml.XPath/XPathItem.xml
+++ b/xml/System.Xml.XPath/XPathItem.xml
@@ -195,7 +195,7 @@
       </ReturnValue>
       <Docs>
         <summary>When overridden in a derived class, gets the current item as a boxed object of the most appropriate .NET Framework 2.0 type according to its schema type.</summary>
-        <value>The current item as a boxed object of the most appropriate [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type.</value>
+        <value>The current item as a boxed object of the most appropriate .NET Framework type.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -673,12 +673,12 @@
       </ReturnValue>
       <Docs>
         <summary>When overridden in a derived class, gets the .NET Framework 2.0 type of the item.</summary>
-        <value>The [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type of the item. The default value is <see cref="T:System.String" />.</value>
+        <value>The .NET Framework type of the item. The default value is <see cref="T:System.String" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueType%2A> property gets the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] type of the typed value of the item.  
+ When overridden in a derived class, the <xref:System.Xml.XPath.XPathItem.ValueType%2A> property gets the .NET Framework type of the typed value of the item.  
   
  For example, an element of type `xs:int` would have a <xref:System.Xml.XPath.XPathItem.ValueType%2A> of <xref:System.Int32> by default. However, the <xref:System.Xml.XPath.XPathItem.ValueType%2A> could be any one of the valid types that can be mapped to `xs:int`, such as <xref:System.Int16> or <xref:System.Double>.  
   
diff --git a/xml/System.Xml/XmlNodeReader.xml b/xml/System.Xml/XmlNodeReader.xml
index 673767715fe..2cef376a81e 100644
--- a/xml/System.Xml/XmlNodeReader.xml
+++ b/xml/System.Xml/XmlNodeReader.xml
@@ -115,7 +115,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  For more information and examples of the code used to create an `XmlNodeReader`, see <xref:System.Xml.XmlReader> and overloads of the <xref:System.Xml.XmlReader.Create%2A> method.  
   
@@ -162,7 +162,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property is relevant to `Element`, `DocumentType` and `XmlDeclaration` nodes only. (Other node types do not have attributes.)  
   
@@ -218,7 +218,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  A networked XML document is comprised of chunks of data aggregated using various W3C standard inclusion mechanisms and therefore contains nodes that come from different places. DTD entities are an example of this, but this is not limited to DTDs. The base URI tells you where these nodes came from. If there is no base URI for the nodes being returned (for example, they were parsed from an in-memory string), String.Empty is returned.  
   
@@ -280,7 +280,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The binary content read methods include the <xref:System.Xml.XmlNodeReader.ReadContentAsBase64%2A>, <xref:System.Xml.XmlNodeReader.ReadContentAsBinHex%2A>, <xref:System.Xml.XmlNodeReader.ReadElementContentAsBase64%2A>, and <xref:System.Xml.XmlNodeReader.ReadElementContentAsBinHex%2A> methods.  
   
@@ -328,7 +328,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -373,7 +373,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method also releases any resources held while reading. If `Close` has already been called, no action is performed.  
   
@@ -439,7 +439,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -485,7 +485,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -544,7 +544,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method does not move the reader.  
   
@@ -597,7 +597,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method does not move the reader.  
   
@@ -662,7 +662,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The following XML contains an attribute in a specific namespace:  
   
@@ -730,7 +730,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -785,7 +785,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The following table lists node types that have a value to return.  
   
@@ -854,7 +854,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property applies to attribute nodes only. If the reader is not positioned on an attribute node, this property returns `false`.  
   
@@ -902,7 +902,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property enables you to determine the difference between the following:  
   
@@ -959,7 +959,7 @@ String dt4 = reader.GetAttribute("dt",http://www.w3.org/2000/xmlns/);
 ## Remarks  
 
 > [!NOTE]
-> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 This property does not move the reader.
 
@@ -1036,7 +1036,7 @@ This property does not move the reader.
 ## Remarks  
 
 > [!NOTE]
-> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 This property does not move the reader.
 
@@ -1086,7 +1086,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1145,7 +1145,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  In the following XML string, if the reader is positioned on the `href` attribute, the prefix `a` is resolved by calling `reader.LookupNamespace("a")`. The returned string is `urn:456`.  
   
@@ -1213,7 +1213,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1273,7 +1273,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlNodeReader.Name%2A>, <xref:System.Xml.XmlNodeReader.NamespaceURI%2A>, and <xref:System.Xml.XmlNodeReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1328,7 +1328,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  After calling this method, the <xref:System.Xml.XmlNodeReader.Name%2A>, <xref:System.Xml.XmlNodeReader.NamespaceURI%2A>, and <xref:System.Xml.XmlNodeReader.Prefix%2A> properties reflect the properties of that attribute.  
   
@@ -1377,7 +1377,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method to return to an element after navigating through its attributes. This method moves the reader to one of the following node types: `Element`, `DocumentType`, or `XmlDeclaration`.  
   
@@ -1435,7 +1435,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET FrameworkFor more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1491,7 +1491,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If the current node is not an attribute node, this method is equivalent to <xref:System.Xml.XmlNodeReader.MoveToFirstAttribute%2A>. If `MoveToNextAttribute` returns `true`, the reader moves to the next attribute; otherwise, the position of the reader does not change.  
   
@@ -1567,7 +1567,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1625,7 +1625,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property is relevant to `Element` and `Attribute` nodes only.  
   
@@ -1681,7 +1681,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  All node and attribute names returned from this class are atomized using the `NameTable`. When the same name is returned multiple times (for example, `Customer`), then the same `String` object is returned for that name. This makes it possible for you to write efficient code that does object comparisons on these strings instead of expensive string comparisons.  
   
@@ -1729,7 +1729,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1787,7 +1787,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -1832,7 +1832,7 @@ This property does not move the reader.
 ## Remarks  
 
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 ]]></format>
         </remarks>
@@ -1885,7 +1885,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  When a reader is first created and initialized, there is no information available. You must call `Read` to read the first node.  
   
@@ -1951,7 +1951,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  Use this method after calling <xref:System.Xml.XmlNodeReader.MoveToAttribute%2A> to read through the text or entity reference nodes that make up the attribute value. The <xref:System.Xml.XmlNodeReader.Depth%2A> of the attribute value nodes is one plus the depth of the attribute node; it increments and decrements by one when you step into and out of general entity references.  
   
@@ -2014,7 +2014,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method streams the content, decodes the Base64 content, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2085,7 +2085,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method streams the content, decodes the BinHex content, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer. This method can be called successively to read large streams of embedded text.  
   
@@ -2156,7 +2156,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the content, decodes it using Base64 encoding, and returns the decoded binary bytes (for example, an inline Base64 encoded GIF image) into the buffer. For more information, see RFC 1521, "MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies". You can obtain RFCs from the [Request for Comments Web site](https://www.rfc-editor.org).  
   
@@ -2230,7 +2230,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This method reads the element content, decodes it using BinHex encoding, and returns the decoded binary bytes (for example, an inline BinHex encoded GIF image) into the buffer.  
   
@@ -2303,7 +2303,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
@@ -2351,7 +2351,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If positioned on an element, `ReadString` concatenates all text, significant white space, white space, and CData section node types together and returns the concatenated data as the element content. It stops when any markup is encountered. This could occur in a mixed content model, or when an element end tag is read.  
   
@@ -2409,7 +2409,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  If the reader is positioned on an `EntityReference` node (`XmlNodeType.EntityReference`), if <xref:System.Xml.XmlNodeReader.Read%2A> is called after calling this method, the entity replacement text is parsed. When the entity replacement text is finished, an `EndEntity` node is returned to close the entity reference scope.  
   
@@ -2469,7 +2469,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  The <xref:System.Xml.Schema.IXmlSchemaInfo> interface represents the Post Schema Validation Infoset (PSVI) of the underlying XML node. The PSVI contents of this property are set after the node has been validated.  
   
@@ -2518,7 +2518,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  For example, suppose you have the following XML input:  
   
@@ -2766,7 +2766,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
    
   
@@ -2824,7 +2824,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  This property represents the xml:lang scope within which the current node resides. For example, here is an XML fragment with `xml:lang` set to US English in the root element:  
   
@@ -2881,7 +2881,7 @@ This property does not move the reader.
 ## Remarks  
   
 > [!NOTE]
->  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
+>  In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Xml/XmlTextReader.xml b/xml/System.Xml/XmlTextReader.xml
index a412c40afb1..cf7d39358ac 100644
--- a/xml/System.Xml/XmlTextReader.xml
+++ b/xml/System.Xml/XmlTextReader.xml
@@ -319,7 +319,7 @@
  If the file is located on a resource that requires access credentials, use the <xref:System.Xml.XmlTextReader.XmlResolver%2A> property to specify the necessary credentials.  
   
 > [!NOTE]
->  In version 1.1 of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], partially trusted code cannot set the `XmlResolver` property. The workaround is to create an <xref:System.Xml.XmlUrlResolver> with the necessary credentials, pass the URI to the <xref:System.Xml.XmlUrlResolver.GetEntity%2A?displayProperty=nameWithType> method, and then construct the `XmlTextReader` using the resulting <xref:System.IO.Stream> object. The workaround is described in the following C# code.  
+>  In version 1.1 of the .NET Framework, partially trusted code cannot set the `XmlResolver` property. The workaround is to create an <xref:System.Xml.XmlUrlResolver> with the necessary credentials, pass the URI to the <xref:System.Xml.XmlUrlResolver.GetEntity%2A?displayProperty=nameWithType> method, and then construct the `XmlTextReader` using the resulting <xref:System.IO.Stream> object. The workaround is described in the following C# code.  
   
 ```csharp  
 // Create a resolver with the necessary credentials.  
@@ -4314,7 +4314,7 @@ if (XmlNodeType.Element == reader.NodeType && "thing" == reader.Name)
 
 ## Remarks  
 
-> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
+> In the .NET Framework 2.0, the recommended practice is to create <xref:System.Xml.XmlReader> instances using the <xref:System.Xml.XmlReaderSettings> class and the <xref:System.Xml.XmlReader.Create%2A> method. This allows you to take full advantage of all the new features introduced in the .NET Framework. For more information, see the Remarks section in the <xref:System.Xml.XmlReader> reference page.
 
 ]]></format>
         </remarks>
@@ -4806,7 +4806,7 @@ This member is an explicit interface member implementation. It can be used only
         <summary>Sets the <see cref="T:System.Xml.XmlResolver" /> used for resolving DTD references.</summary>
         <value>The <see langword="XmlResolver" /> to use. If set to <see langword="null" />, external resources are not resolved.  
   
- In version 1.1 of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the caller must be fully trusted in order to specify an <see langword="XmlResolver" />.</value>
+ In version 1.1 of the .NET Framework, the caller must be fully trusted in order to specify an <see langword="XmlResolver" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -4819,7 +4819,7 @@ This member is an explicit interface member implementation. It can be used only
   
  This property can be changed at any time and takes effect on the next read operation. If this property is set to `null`, any external DTD references encountered by the reader are not resolved.  
   
- In version 1.1 of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], if this property is not set, the trust level of the application determines the default behavior.  
+ In version 1.1 of the .NET Framework, if this property is not set, the trust level of the application determines the default behavior.  
   
  `Fully trusted code:` The reader uses a default <xref:System.Xml.XmlUrlResolver> with no user credentials. If authentication is required to access a network resource, use the `XmlResolver` property to specify an `XmlResolver` with the necessary credentials.  
   
diff --git a/xml/System.Xml/XmlValidatingReader.xml b/xml/System.Xml/XmlValidatingReader.xml
index 6c3234b66cb..5170abacaa9 100644
--- a/xml/System.Xml/XmlValidatingReader.xml
+++ b/xml/System.Xml/XmlValidatingReader.xml
@@ -3851,7 +3851,7 @@ object obj = vreader.SchemaType;
         <summary>Sets the <see cref="T:System.Xml.XmlResolver" /> used for resolving external document type definition (DTD) and schema location references. The <see langword="XmlResolver" /> is also used to handle any import or include elements found in XML Schema definition language (XSD) schemas.</summary>
         <value>The <see langword="XmlResolver" /> to use. If set to <see langword="null" />, external resources are not resolved.  
   
- In version 1.1 of the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], the caller must be fully trusted to specify an <see langword="XmlResolver" />.</value>
+ In version 1.1 of the .NET Framework, the caller must be fully trusted to specify an <see langword="XmlResolver" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3864,7 +3864,7 @@ object obj = vreader.SchemaType;
   
  This property can be set at any time and takes affect after the next <xref:System.Xml.XmlValidatingReader.Read%2A> call. If this property is set to `null`, the reader assumes the user is not interested in resolving external references. In this case, the reader only validates against internal resources, if the resource is present.  
   
- In version 1.1 of [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] , if this property is not set, the trust level of the application determines the default behavior.  
+ In version 1.1 of .NET Framework , if this property is not set, the trust level of the application determines the default behavior.  
   
  `Fully trusted code:` The reader uses a default <xref:System.Xml.XmlUrlResolver> with no user credentials. If authentication is required to access a network resource, use the `XmlResolver` property to specify an `XmlResolver` with the necessary credentials.  
   
diff --git a/xml/System/String.xml b/xml/System/String.xml
index 6b9304d368f..0dc0db2b462 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -10685,7 +10685,7 @@ In the following example, the <xref:System.String.LastIndexOf%2A> method is used
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], strings are zero-based. The value of the `startIndex` parameter can range from zero to one less than the length of the string instance.
+ In the .NET Framework, strings are zero-based. The value of the `startIndex` parameter can range from zero to one less than the length of the string instance.
 
 > [!NOTE]
 > This method does not modify the value of the current instance. Instead, it returns a new string in which all characters from position `startIndex` to the end of the original string have been removed.
@@ -10768,7 +10768,7 @@ In the following example, the <xref:System.String.LastIndexOf%2A> method is used
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)], strings are zero-based. The value of the `startIndex` parameter can range from zero to one less than the length of the string instance.
+ In the .NET Framework, strings are zero-based. The value of the `startIndex` parameter can range from zero to one less than the length of the string instance.
 
 > [!NOTE]
 > This method does not modify the value of the current instance. Instead, it returns a new string in which the number of characters specified by the `count` parameter have been removed. The characters are removed at the position specified by `startIndex`.
diff --git a/xml/ns-Microsoft.VisualBasic.Compatibility.VB6.xml b/xml/ns-Microsoft.VisualBasic.Compatibility.VB6.xml
index 934981c29c5..e39402b1f89 100644
--- a/xml/ns-Microsoft.VisualBasic.Compatibility.VB6.xml
+++ b/xml/ns-Microsoft.VisualBasic.Compatibility.VB6.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)]. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.
+ Functions and objects in the <xref:Microsoft.VisualBasic.Compatibility.VB6> namespace are provided for use by the tools for upgrading from Visual Basic 6.0 to Visual Basic 2008. In most cases, these functions and objects duplicate functionality that you can find in other namespaces in the .NET Framework. They are necessary only when the Visual Basic 6.0 code model differs significantly from the .NET Framework implementation.
 
  ]]></format>
     </remarks>
diff --git a/xml/ns-System.Windows.Diagnostics.xml b/xml/ns-System.Windows.Diagnostics.xml
index 873049a16fc..6b21c4a66eb 100644
--- a/xml/ns-System.Windows.Diagnostics.xml
+++ b/xml/ns-System.Windows.Diagnostics.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The classes in this namespace support the [!INCLUDE[dnprdnshort](~/includes/dnprdnshort-md.md)] infrastructure and are not intended to be used directly from your code.  
+ The classes in this namespace support the .NET Framework infrastructure and are not intended to be used directly from your code.  
   
  ]]></format>
     </remarks>

From dc1ec5612ac69847e9fa98854d4dbe8b3d128325 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:02:02 -0800
Subject: [PATCH 012/236] dp-id-field-label

---
 xml/System.Windows.Media.Animation/BackEase.xml            | 2 +-
 xml/System.Windows.Media.Animation/BounceEase.xml          | 4 ++--
 xml/System.Windows.Media.Animation/EasingColorKeyFrame.xml | 2 +-
 xml/System.Windows.Media.Animation/EasingPointKeyFrame.xml | 2 +-
 xml/System.Windows.Media.Animation/ElasticEase.xml         | 4 ++--
 xml/System.Windows.Media.Animation/ExponentialEase.xml     | 2 +-
 xml/System.Windows.Media.Animation/PowerEase.xml           | 2 +-
 7 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Media.Animation/BackEase.xml b/xml/System.Windows.Media.Animation/BackEase.xml
index 4a635b0a3b6..c51fbb709f7 100644
--- a/xml/System.Windows.Media.Animation/BackEase.xml
+++ b/xml/System.Windows.Media.Animation/BackEase.xml
@@ -100,7 +100,7 @@ In addition to using the easing functions included in the run-time, you can crea
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.BackEase.AmplitudeProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.BackEase.AmplitudeProperty>  
   
  The larger the amplitude, the larger the retraction before and/or after the animation.  
   
diff --git a/xml/System.Windows.Media.Animation/BounceEase.xml b/xml/System.Windows.Media.Animation/BounceEase.xml
index 05dad9b0abd..9e754e75e56 100644
--- a/xml/System.Windows.Media.Animation/BounceEase.xml
+++ b/xml/System.Windows.Media.Animation/BounceEase.xml
@@ -105,7 +105,7 @@
 ## Remarks  
  This property does not include the final half-bounce.  
   
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.BounceEase.BouncesProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.BounceEase.BouncesProperty>  
   
 <a name="xamlAttributeUsage_Bounces"></a>   
 ## XAML Attribute Usage  
@@ -162,7 +162,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.BounceEase.BouncinessProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.BounceEase.BouncinessProperty>  
   
 <a name="xamlAttributeUsage_Bounciness"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Media.Animation/EasingColorKeyFrame.xml b/xml/System.Windows.Media.Animation/EasingColorKeyFrame.xml
index e5ad8a3047b..4812394c689 100644
--- a/xml/System.Windows.Media.Animation/EasingColorKeyFrame.xml
+++ b/xml/System.Windows.Media.Animation/EasingColorKeyFrame.xml
@@ -199,7 +199,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.EasingColorKeyFrame.EasingFunctionProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.EasingColorKeyFrame.EasingFunctionProperty>  
   
 <a name="xamlPropertyElementUsage_EasingFunction"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Media.Animation/EasingPointKeyFrame.xml b/xml/System.Windows.Media.Animation/EasingPointKeyFrame.xml
index d37d42d51f5..55b1fda7c19 100644
--- a/xml/System.Windows.Media.Animation/EasingPointKeyFrame.xml
+++ b/xml/System.Windows.Media.Animation/EasingPointKeyFrame.xml
@@ -206,7 +206,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.EasingPointKeyFrame.EasingFunctionProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.EasingPointKeyFrame.EasingFunctionProperty>  
   
 <a name="elementUsage_EasingFunction"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Media.Animation/ElasticEase.xml b/xml/System.Windows.Media.Animation/ElasticEase.xml
index 7db91b8de01..7e97e2c0a10 100644
--- a/xml/System.Windows.Media.Animation/ElasticEase.xml
+++ b/xml/System.Windows.Media.Animation/ElasticEase.xml
@@ -179,7 +179,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.ElasticEase.OscillationsProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.ElasticEase.OscillationsProperty>  
   
 <a name="xamlAttributeUsage_Occilations"></a>   
 ## XAML Attribute Usage  
@@ -245,7 +245,7 @@
 ## Remarks  
  The smaller the <xref:System.Windows.Media.Animation.ElasticEase.Springiness%2A> value is, the stiffer the spring and the faster the elasticity decreases in intensity over each oscillation.  
   
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.ElasticEase.SpringinessProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.ElasticEase.SpringinessProperty>  
   
  The following diagram illustrates the effect of different values of <xref:System.Windows.Media.Animation.ElasticEase.Springiness%2A>.  
   
diff --git a/xml/System.Windows.Media.Animation/ExponentialEase.xml b/xml/System.Windows.Media.Animation/ExponentialEase.xml
index 40d6358b135..69e3007358e 100644
--- a/xml/System.Windows.Media.Animation/ExponentialEase.xml
+++ b/xml/System.Windows.Media.Animation/ExponentialEase.xml
@@ -172,7 +172,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.ExponentialEase.ExponentProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.ExponentialEase.ExponentProperty>  
   
  The formula used by <xref:System.Windows.Media.Animation.ExponentialEase> is the following.  
   
diff --git a/xml/System.Windows.Media.Animation/PowerEase.xml b/xml/System.Windows.Media.Animation/PowerEase.xml
index 17fe9faa77e..a0dd86a474d 100644
--- a/xml/System.Windows.Media.Animation/PowerEase.xml
+++ b/xml/System.Windows.Media.Animation/PowerEase.xml
@@ -180,7 +180,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[DP_ID_field_label](~/includes/dp-id-field-label-md.md)] <xref:System.Windows.Media.Animation.PowerEase.PowerProperty>  
+ Dependency property identifier field: <xref:System.Windows.Media.Animation.PowerEase.PowerProperty>  
   
 <a name="xamlAttributeUsage_Power"></a>   
 ## XAML Attribute Usage  

From 5e657b7fd3265a935e98701f4c5ca88f74468a3d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:02:22 -0800
Subject: [PATCH 013/236] esql

---
 xml/System.Data.Objects/ObjectParameter.xml |  4 ++--
 xml/System.Data.Objects/ObjectQuery`1.xml   | 10 +++++-----
 xml/System.Data/EntityKey.xml               |  4 ++--
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Data.Objects/ObjectParameter.xml b/xml/System.Data.Objects/ObjectParameter.xml
index d9516b20b07..674318c7e02 100644
--- a/xml/System.Data.Objects/ObjectParameter.xml
+++ b/xml/System.Data.Objects/ObjectParameter.xml
@@ -66,7 +66,7 @@
         <Parameter Name="value" Type="System.Object" />
       </Parameters>
       <Docs>
-        <param name="name">The parameter name. This name should not include the "@" parameter marker that is used in [!INCLUDE[esql](~/includes/esql-md.md)] statements, only the actual name. The first character of the expression must be a letter. Any successive characters in the expression must be either letters, numbers, or an underscore (_) character.</param>
+        <param name="name">The parameter name. This name should not include the "@" parameter marker that is used in Entity SQL statements, only the actual name. The first character of the expression must be a letter. Any successive characters in the expression must be either letters, numbers, or an underscore (_) character.</param>
         <param name="value">The initial value (and inherently, the type) of the parameter.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Data.Objects.ObjectParameter" /> class with the specified name and value.</summary>
         <remarks>
@@ -110,7 +110,7 @@
         <Parameter Name="type" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="name">The parameter name. This name should not include the "@" parameter marker that is used in the [!INCLUDE[esql](~/includes/esql-md.md)] statements, only the actual name. The first character of the expression must be a letter. Any successive characters in the expression must be either letters, numbers, or an underscore (_) character.</param>
+        <param name="name">The parameter name. This name should not include the "@" parameter marker that is used in the Entity SQL statements, only the actual name. The first character of the expression must be a letter. Any successive characters in the expression must be either letters, numbers, or an underscore (_) character.</param>
         <param name="type">The common language runtime (CLR) type of the parameter.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Data.Objects.ObjectParameter" /> class with the specified name and type.</summary>
         <remarks>
diff --git a/xml/System.Data.Objects/ObjectQuery`1.xml b/xml/System.Data.Objects/ObjectQuery`1.xml
index c8230275e42..5817977d8d0 100644
--- a/xml/System.Data.Objects/ObjectQuery`1.xml
+++ b/xml/System.Data.Objects/ObjectQuery`1.xml
@@ -55,7 +55,7 @@
 
 -   When the <xref:System.Data.Objects.ObjectQuery%601.Execute%2A> method is explicitly called.
 
- The query itself can be created by using an [!INCLUDE[esql](~/includes/esql-md.md)] statement or a LINQ query, or it can be incrementally built by using the query builder methods included in the class. In every case, the result is a new <xref:System.Data.Objects.ObjectQuery%601> instance that, when explicitly executed or enumerated over, will send the query to the data source for execution and return the results.
+ The query itself can be created by using an Entity SQL statement or a LINQ query, or it can be incrementally built by using the query builder methods included in the class. In every case, the result is a new <xref:System.Data.Objects.ObjectQuery%601> instance that, when explicitly executed or enumerated over, will send the query to the data source for execution and return the results.
 
  An <xref:System.Data.Objects.ObjectQuery%601> is frequently of an entity type, but it can also be of <xref:System.Data.Common.DbDataRecord> type, for projections to an anonymous type, or of a primitive type, such as an integer or string. For more information, see [Object Queries](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb896241(v=vs.100)).
 
@@ -114,9 +114,9 @@
         <Parameter Name="context" Type="System.Data.Objects.ObjectContext" />
       </Parameters>
       <Docs>
-        <param name="commandText">The [!INCLUDE[esql](~/includes/esql-md.md)] query.</param>
+        <param name="commandText">The Entity SQL query.</param>
         <param name="context">The <see cref="T:System.Data.Objects.ObjectContext" /> on which to execute the query.</param>
-        <summary>Creates a new <see cref="T:System.Data.Objects.ObjectQuery`1" /> instance using the specified [!INCLUDE[esql](~/includes/esql-md.md)] command as the initial query.</summary>
+        <summary>Creates a new <see cref="T:System.Data.Objects.ObjectQuery`1" /> instance using the specified Entity SQL command as the initial query.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -155,10 +155,10 @@
         <Parameter Name="mergeOption" Type="System.Data.Objects.MergeOption" />
       </Parameters>
       <Docs>
-        <param name="commandText">The [!INCLUDE[esql](~/includes/esql-md.md)] query.</param>
+        <param name="commandText">The Entity SQL query.</param>
         <param name="context">The <see cref="T:System.Data.Objects.ObjectContext" /> on which to execute the query.</param>
         <param name="mergeOption">Specifies how the entities that are retrieved through this query should be merged with the entities that have been returned from previous queries against the same <see cref="T:System.Data.Objects.ObjectContext" />.</param>
-        <summary>Creates a new <see cref="T:System.Data.Objects.ObjectQuery`1" /> instance using the specified [!INCLUDE[esql](~/includes/esql-md.md)] command as the initial query and the specified merge option.</summary>
+        <summary>Creates a new <see cref="T:System.Data.Objects.ObjectQuery`1" /> instance using the specified Entity SQL command as the initial query and the specified merge option.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
diff --git a/xml/System.Data/EntityKey.xml b/xml/System.Data/EntityKey.xml
index ff65b5c885a..0ff4dfb980c 100644
--- a/xml/System.Data/EntityKey.xml
+++ b/xml/System.Data/EntityKey.xml
@@ -271,7 +271,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- There are various ways to get an invalid entity. The most common scenario is when an [!INCLUDE[esql](~/includes/esql-md.md)] query uses the [TREAT](/dotnet/framework/data/adonet/ef/language-reference/treat-entity-sql) operator to interpret an instance of a polymorphic type as a particular type, and the instance in question does not match. ([TREAT](/dotnet/framework/data/adonet/ef/language-reference/treat-entity-sql) is similar to the C# `as` operator). In this case, the query returns an entity that is not valid, and the entity key of the resulting entity is set to <xref:System.Data.EntityKey.EntityNotValidKey>.
+ There are various ways to get an invalid entity. The most common scenario is when an Entity SQL query uses the [TREAT](/dotnet/framework/data/adonet/ef/language-reference/treat-entity-sql) operator to interpret an instance of a polymorphic type as a particular type, and the instance in question does not match. ([TREAT](/dotnet/framework/data/adonet/ef/language-reference/treat-entity-sql) is similar to the C# `as` operator). In this case, the query returns an entity that is not valid, and the entity key of the resulting entity is set to <xref:System.Data.EntityKey.EntityNotValidKey>.
 
  ]]></format>
         </remarks>
@@ -523,7 +523,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- A read-only entity identifies an entity that is valid in every way, except that it is not associated with an actual entity set. This can occur as part of the result of an [!INCLUDE[esql](~/includes/esql-md.md)] query that constructs and returns an entity instance specified within the text of the query (as opposed to an entity that was retrieved from a database table). An entity that does not have an entity set cannot be persisted to the database until it is associated with some entity set. Therefore, the object materializer will treat this kind of entity as if the <xref:System.Data.Objects.MergeOption.NoTracking> merge option was specified, regardless of the actual merge option that was specified. An entity object will be created, but its identity will not be resolved and it will not be added to the state manager as part of the materialization process.
+ A read-only entity identifies an entity that is valid in every way, except that it is not associated with an actual entity set. This can occur as part of the result of an Entity SQL query that constructs and returns an entity instance specified within the text of the query (as opposed to an entity that was retrieved from a database table). An entity that does not have an entity set cannot be persisted to the database until it is associated with some entity set. Therefore, the object materializer will treat this kind of entity as if the <xref:System.Data.Objects.MergeOption.NoTracking> merge option was specified, regardless of the actual merge option that was specified. An entity object will be created, but its identity will not be resolved and it will not be added to the state manager as part of the materialization process.
 
  ]]></format>
         </remarks>

From 640506d30aeb60b96732caa22233b1acb80a936e Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:02:42 -0800
Subject: [PATCH 014/236] iisver

---
 .../IApplicationPreloadManager.xml                 |  6 +++---
 xml/System.Web.Hosting/IApplicationPreloadUtil.xml |  2 +-
 .../IProcessHostPreloadClient.xml                  |  6 +++---
 xml/System.Web.Hosting/ProcessHost.xml             | 14 +++++++-------
 .../IisTraceWebEventProvider.xml                   |  4 ++--
 xml/System.Web.Routing/UrlRoutingHandler.xml       |  4 ++--
 xml/System.Web/HttpContext.xml                     | 12 ++++++------
 xml/System.Web/HttpResponse.xml                    | 12 ++++++------
 xml/System.Web/HttpResponseBase.xml                |  4 ++--
 xml/System.Web/HttpResponseWrapper.xml             | 10 +++++-----
 xml/System.Web/HttpRuntime.xml                     |  4 ++--
 xml/System.Web/HttpServerUtility.xml               | 10 +++++-----
 xml/System.Web/HttpServerUtilityWrapper.xml        |  8 ++++----
 xml/System.Web/IisTraceListener.xml                |  4 ++--
 14 files changed, 50 insertions(+), 50 deletions(-)

diff --git a/xml/System.Web.Hosting/IApplicationPreloadManager.xml b/xml/System.Web.Hosting/IApplicationPreloadManager.xml
index 0ab187ba079..4e16f667947 100644
--- a/xml/System.Web.Hosting/IApplicationPreloadManager.xml
+++ b/xml/System.Web.Hosting/IApplicationPreloadManager.xml
@@ -51,7 +51,7 @@
         <param name="appId">The unique ID of the application.</param>
         <param name="enabled">
           <see langword="true" /> to indicate that the application should be preloaded; otherwise, <see langword="false" />.</param>
-        <summary>Called by [!INCLUDE[iisver](~/includes/iisver-md.md)] to notify ASP.NET whether an application should be preloaded.</summary>
+        <summary>Called by IIS 7.0 to notify ASP.NET whether an application should be preloaded.</summary>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -75,8 +75,8 @@
         <Parameter Name="preloadUtil" Type="System.Web.Hosting.IApplicationPreloadUtil" />
       </Parameters>
       <Docs>
-        <param name="preloadUtil">The handle to an unmanaged interface in [!INCLUDE[iisver](~/includes/iisver-md.md)] that ASP.NET calls to get information.</param>
-        <summary>Calls [!INCLUDE[iisver](~/includes/iisver-md.md)] to get information that is required in order to preload an application.</summary>
+        <param name="preloadUtil">The handle to an unmanaged interface in IIS 7.0 that ASP.NET calls to get information.</param>
+        <summary>Calls IIS 7.0 to get information that is required in order to preload an application.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Web.Hosting/IApplicationPreloadUtil.xml b/xml/System.Web.Hosting/IApplicationPreloadUtil.xml
index fd0df248a2b..da98712168f 100644
--- a/xml/System.Web.Hosting/IApplicationPreloadUtil.xml
+++ b/xml/System.Web.Hosting/IApplicationPreloadUtil.xml
@@ -81,7 +81,7 @@
         <param name="context">The application context.</param>
         <param name="errorCode">The numeric error code.</param>
         <param name="errorMessage">The error text.</param>
-        <summary>Reports that an error occurred in [!INCLUDE[iisver](~/includes/iisver-md.md)] while the server was preloading the ASP.NET application.</summary>
+        <summary>Reports that an error occurred in IIS 7.0 while the server was preloading the ASP.NET application.</summary>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Web.Hosting/IProcessHostPreloadClient.xml b/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
index 8bf6acc7cc3..2e1a9023a3b 100644
--- a/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
+++ b/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
@@ -16,10 +16,10 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This interface is intended primarily for use by WCF applications that are non-HTTP applications. ASP.NET developers who want to preload ASP.NET Web applications should use the simulated HTTP requests in [!INCLUDE[iisver](~/includes/iisver-md.md)] combined with the `Application_Start` method in the Global.asax file.  
+ This interface is intended primarily for use by WCF applications that are non-HTTP applications. ASP.NET developers who want to preload ASP.NET Web applications should use the simulated HTTP requests in IIS 7.0 combined with the `Application_Start` method in the Global.asax file.  
   
 > [!NOTE]
->  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on [!INCLUDE[iisver](~/includes/iisver-md.md)] and [!INCLUDE[win7](~/includes/win7-md.md)].  
+>  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and [!INCLUDE[win7](~/includes/win7-md.md)].  
   
  ]]></format>
     </remarks>
@@ -53,7 +53,7 @@
  The value of `parameters` can be `null`, a zero-length array, or a populated array.  
   
 > [!NOTE]
->  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on [!INCLUDE[iisver](~/includes/iisver-md.md)] and [!INCLUDE[win7](~/includes/win7-md.md)].  
+>  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and [!INCLUDE[win7](~/includes/win7-md.md)].  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/ProcessHost.xml b/xml/System.Web.Hosting/ProcessHost.xml
index 8253ca1b169..7265088f397 100644
--- a/xml/System.Web.Hosting/ProcessHost.xml
+++ b/xml/System.Web.Hosting/ProcessHost.xml
@@ -207,15 +207,15 @@
         <param name="appId">The unique ID of the application.</param>
         <param name="enabled">
           <see langword="true" /> to indicate the application should be preloaded; otherwise, <see langword="false" />.</param>
-        <summary>Notifies ASP.NET that a particular application that is running on [!INCLUDE[iisver](~/includes/iisver-md.md)] is configured to be preloaded.</summary>
+        <summary>Notifies ASP.NET that a particular application that is running on IIS 7.0 is configured to be preloaded.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method implements the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadState%2A> method of the <xref:System.Web.Hosting.IApplicationPreloadManager> interface. [!INCLUDE[iisver](~/includes/iisver-md.md)] calls the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadState%2A> method to notify ASP.NET whether the application that is being loaded supports preloading.  
+ This method implements the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadState%2A> method of the <xref:System.Web.Hosting.IApplicationPreloadManager> interface. IIS 7.0 calls the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadState%2A> method to notify ASP.NET whether the application that is being loaded supports preloading.  
   
 > [!NOTE]
->  This method applies only to applications that run on [!INCLUDE[iisver](~/includes/iisver-md.md)].  
+>  This method applies only to applications that run on IIS 7.0.  
   
  ]]></format>
         </remarks>
@@ -253,16 +253,16 @@
         <Parameter Name="applicationPreloadUtil" Type="System.Web.Hosting.IApplicationPreloadUtil" Index="0" FrameworkAlternate="netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="applicationPreloadUtil">The handle to an unmanaged interface in [!INCLUDE[iisver](~/includes/iisver-md.md)] that ASP.NET calls to get information.</param>
-        <summary>Creates a type that calls [!INCLUDE[iisver](~/includes/iisver-md.md)] to get information that is required in order to preload an application.</summary>
+        <param name="applicationPreloadUtil">The handle to an unmanaged interface in IIS 7.0 that ASP.NET calls to get information.</param>
+        <summary>Creates a type that calls IIS 7.0 to get information that is required in order to preload an application.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method implements the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadUtil%2A> method of the <xref:System.Web.Hosting.IApplicationPreloadManager> interface. The method creates an instance of the <xref:System.Web.Hosting.IApplicationPreloadUtil> type, which calls into [!INCLUDE[iisver](~/includes/iisver-md.md)] to get preloading information.  
+ This method implements the <xref:System.Web.Hosting.IApplicationPreloadManager.SetApplicationPreloadUtil%2A> method of the <xref:System.Web.Hosting.IApplicationPreloadManager> interface. The method creates an instance of the <xref:System.Web.Hosting.IApplicationPreloadUtil> type, which calls into IIS 7.0 to get preloading information.  
   
 > [!NOTE]
->  This method applies only to applications that run on [!INCLUDE[iisver](~/includes/iisver-md.md)].  
+>  This method applies only to applications that run on IIS 7.0.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Management/IisTraceWebEventProvider.xml b/xml/System.Web.Management/IisTraceWebEventProvider.xml
index 919f6ce00c2..9346f314eb2 100644
--- a/xml/System.Web.Management/IisTraceWebEventProvider.xml
+++ b/xml/System.Web.Management/IisTraceWebEventProvider.xml
@@ -22,12 +22,12 @@
 ## Remarks  
  ASP.NET health monitoring enables administrators to manage deployed Web applications. The <xref:System.Web.Management> namespace contains the event types that obtain health-status data and the provider types that process this data. It also contains supporting types that help you manage health events.  
   
- The <xref:System.Web.Management.IisTraceWebEventProvider> class is a customized health-event provider that processes ASP.NET tracing events by routing them through the [!INCLUDE[iisver](~/includes/iisver-md.md)] tracing infrastructure. This routing occurs only when tracing is enabled in ASP.NET.  
+ The <xref:System.Web.Management.IisTraceWebEventProvider> class is a customized health-event provider that processes ASP.NET tracing events by routing them through the IIS 7.0 tracing infrastructure. This routing occurs only when tracing is enabled in ASP.NET.  
   
  <xref:System.Web.Management.IisTraceWebEventProvider> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
 > [!NOTE]
->  This class does not route [!INCLUDE[iisver](~/includes/iisver-md.md)] trace events into ASP.NET page events.  
+>  This class does not route IIS 7.0 trace events into ASP.NET page events.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.Routing/UrlRoutingHandler.xml b/xml/System.Web.Routing/UrlRoutingHandler.xml
index 2b83f98bb7d..d22d30d1fb9 100644
--- a/xml/System.Web.Routing/UrlRoutingHandler.xml
+++ b/xml/System.Web.Routing/UrlRoutingHandler.xml
@@ -40,7 +40,7 @@
 
  To customize how ASP.NET routing handles a request for a URL with a specific file name extension, you create a class that derives from the <xref:System.Web.Routing.UrlRoutingHandler> class. For example, you can create a customized routing handler that processes requests for a file that has the extension `.abc`.
 
- To register a customized handler for a particular file name extension, you must add that handler in the Web.config file. The following example shows how to register a customized handler for an ASP.NET Web site that is running in IIS 6.0 or [!INCLUDE[iisver](~/includes/iisver-md.md)] in Classic mode.
+ To register a customized handler for a particular file name extension, you must add that handler in the Web.config file. The following example shows how to register a customized handler for an ASP.NET Web site that is running in IIS 6.0 or IIS 7.0 in Classic mode.
 
 ```
 <system.web>
@@ -51,7 +51,7 @@
 </system.web>
 ```
 
- The following example shows how to register the same handler for an ASP.NET Web site that is running in [!INCLUDE[iisver](~/includes/iisver-md.md)].
+ The following example shows how to register the same handler for an ASP.NET Web site that is running in IIS 7.0.
 
 ```
 <system.webServer>
diff --git a/xml/System.Web/HttpContext.xml b/xml/System.Web/HttpContext.xml
index df4fc6b07dd..de7de2334f2 100644
--- a/xml/System.Web/HttpContext.xml
+++ b/xml/System.Web/HttpContext.xml
@@ -573,9 +573,9 @@ End Sub
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.HttpContext.CurrentNotification%2A> property requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0. When available, the property returns a <xref:System.Web.RequestNotification> value. The value of the <xref:System.Web.HttpContext.CurrentNotification%2A> property indicates which event in the <xref:System.Web.HttpApplication> instance is currently processing the request.
+ The <xref:System.Web.HttpContext.CurrentNotification%2A> property requires the integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0. When available, the property returns a <xref:System.Web.RequestNotification> value. The value of the <xref:System.Web.HttpContext.CurrentNotification%2A> property indicates which event in the <xref:System.Web.HttpApplication> instance is currently processing the request.
 
- The <xref:System.Web.HttpContext.CurrentNotification%2A> property is not intended to be set. Instead, it is set by [!INCLUDE[iisver](~/includes/iisver-md.md)] during the processing of the request in the ASP.NET pipeline. Setting the <xref:System.Web.HttpContext.CurrentNotification%2A> property will result in a compilation error.
+ The <xref:System.Web.HttpContext.CurrentNotification%2A> property is not intended to be set. Instead, it is set by IIS 7.0 during the processing of the request in the ASP.NET pipeline. Setting the <xref:System.Web.HttpContext.CurrentNotification%2A> property will result in a compilation error.
 
  <xref:System.Web.HttpContext.CurrentNotification%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).
 
@@ -589,7 +589,7 @@ End Sub
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0.</exception>
         <altmember cref="P:System.Web.HttpContext.IsPostNotification" />
         <altmember cref="T:System.Web.RequestNotification" />
       </Docs>
@@ -1095,9 +1095,9 @@ End Sub
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.HttpContext.IsPostNotification%2A> property is only supported with the integrated mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework 3.0. When available, the property returns a Boolean value that indicates whether an event in the <xref:System.Web.HttpApplication> object has finished processing.
+ The <xref:System.Web.HttpContext.IsPostNotification%2A> property is only supported with the integrated mode in IIS 7.0 and at least the .NET Framework 3.0. When available, the property returns a Boolean value that indicates whether an event in the <xref:System.Web.HttpApplication> object has finished processing.
 
- The <xref:System.Web.HttpContext.IsPostNotification%2A> property is not intended to be set. Instead, it is provided by [!INCLUDE[iisver](~/includes/iisver-md.md)] to the ASP.NET runtime for each notification. Setting the <xref:System.Web.HttpContext.IsPostNotification%2A> property will result in a compilation error.
+ The <xref:System.Web.HttpContext.IsPostNotification%2A> property is not intended to be set. Instead, it is provided by IIS 7.0 to the ASP.NET runtime for each notification. Setting the <xref:System.Web.HttpContext.IsPostNotification%2A> property will result in a compilation error.
 
  In scenarios where multiple events of the <xref:System.Web.HttpApplication> object are handled by one event handler, you can use the <xref:System.Web.HttpContext.IsPostNotification%2A> property in combination with the <xref:System.Web.RequestNotification> enumeration to precisely determine where in the application lifecycle the current request is.
 
@@ -1113,7 +1113,7 @@ End Sub
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in IIS 7.0 and at least the .NET Framework 3.0.</exception>
         <altmember cref="P:System.Web.HttpContext.CurrentNotification" />
         <altmember cref="T:System.Web.RequestNotification" />
       </Docs>
diff --git a/xml/System.Web/HttpResponse.xml b/xml/System.Web/HttpResponse.xml
index 5de30b3fe8b..d9607dd3e03 100644
--- a/xml/System.Web/HttpResponse.xml
+++ b/xml/System.Web/HttpResponse.xml
@@ -1599,11 +1599,11 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.HttpResponse.Headers%2A> property is only supported with the [!INCLUDE[iisver](~/includes/iisver-md.md)] integrated pipeline mode and at least the .NET Framework 3.0. When you try to access the <xref:System.Web.HttpResponse.Headers%2A> property and either of these two conditions is not met, a <xref:System.PlatformNotSupportedException> is thrown.
+ The <xref:System.Web.HttpResponse.Headers%2A> property is only supported with the IIS 7.0 integrated pipeline mode and at least the .NET Framework 3.0. When you try to access the <xref:System.Web.HttpResponse.Headers%2A> property and either of these two conditions is not met, a <xref:System.PlatformNotSupportedException> is thrown.
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least .NET Framework version 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in IIS 7.0 and at least .NET Framework version 3.0.</exception>
         <related type="ExternalDocumentation" href="/previous-versions/bb515251(v=vs.140)">Upgrading ASP.NET Applications to IIS 7.0</related>
       </Docs>
     </Member>
@@ -3009,12 +3009,12 @@ Response.RedirectToRoutePermanent("Product",
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value qualifying the status code of the response.</summary>
-        <value>An integer value that represents the [!INCLUDE[iisver](~/includes/iisver-md.md)] sub status code.</value>
+        <value>An integer value that represents the IIS 7.0 sub status code.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Web.HttpResponse.SubStatusCode%2A> property is only supported with the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0. When you set the <xref:System.Web.HttpResponse.SubStatusCode%2A> property, the status is logged on [!INCLUDE[iisver](~/includes/iisver-md.md)] if failed-request tracing is configured. Independent of whether tracing is configured, the code is never sent as part of the final response to the request. For more information, see [Troubleshooting Failed Requests Using Failed Request Tracing in IIS 7.0](http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=969&p=1).
+ The <xref:System.Web.HttpResponse.SubStatusCode%2A> property is only supported with the integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0. When you set the <xref:System.Web.HttpResponse.SubStatusCode%2A> property, the status is logged on IIS 7.0 if failed-request tracing is configured. Independent of whether tracing is configured, the code is never sent as part of the final response to the request. For more information, see [Troubleshooting Failed Requests Using Failed Request Tracing in IIS 7.0](http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=969&p=1).
 
 ## Examples
  The following example sets the <xref:System.Web.HttpResponse.SubStatusCode%2A> property in an event handler for the <xref:System.Web.HttpApplication> instance of the <xref:System.Web.HttpApplication.PostAuthenticateRequest> event. Put the code file in the App_Code folder of your Web application and configure the Web.config file to register the module. For more information, see [Walkthrough: Creating and Registering a Custom HTTP Module](https://docs.microsoft.com/previous-versions/aspnet/ms227673(v=vs.100)).
@@ -3024,7 +3024,7 @@ Response.RedirectToRoutePermanent("Product",
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0.</exception>
         <exception cref="T:System.Web.HttpException">The status code is set after all HTTP headers have been sent.</exception>
         <altmember cref="P:System.Web.HttpResponse.StatusCode" />
       </Docs>
@@ -3266,7 +3266,7 @@ Response.RedirectToRoutePermanent("Product",
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies whether [!INCLUDE[iisver](~/includes/iisver-md.md)] custom errors are disabled.</summary>
+        <summary>Gets or sets a value that specifies whether IIS 7.0 custom errors are disabled.</summary>
         <value>
           <see langword="true" /> to disable IIS custom errors; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Web/HttpResponseBase.xml b/xml/System.Web/HttpResponseBase.xml
index 2ecbebdb827..0e4025d6819 100644
--- a/xml/System.Web/HttpResponseBase.xml
+++ b/xml/System.Web/HttpResponseBase.xml
@@ -2196,7 +2196,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value that qualifies the status code of the response.</summary>
-        <value>The [!INCLUDE[iisver](~/includes/iisver-md.md)] substatus code.</value>
+        <value>The IIS 7.0 substatus code.</value>
         <remarks>To be added.</remarks>
         <exception cref="T:System.NotImplementedException">Always.</exception>
       </Docs>
@@ -2409,7 +2409,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies whether [!INCLUDE[iisver](~/includes/iisver-md.md)] custom errors are disabled.</summary>
+        <summary>Gets or sets a value that specifies whether IIS 7.0 custom errors are disabled.</summary>
         <value>
           <see langword="true" /> if IIS custom errors are disabled; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Web/HttpResponseWrapper.xml b/xml/System.Web/HttpResponseWrapper.xml
index a7fec2e27e4..208186bb37f 100644
--- a/xml/System.Web/HttpResponseWrapper.xml
+++ b/xml/System.Web/HttpResponseWrapper.xml
@@ -1159,7 +1159,7 @@
         <summary>Gets the collection of response headers.</summary>
         <value>The response headers.</value>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0.</exception>
       </Docs>
     </Member>
     <Member MemberName="HeadersWritten">
@@ -2237,9 +2237,9 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value that qualifies the status code of the response.</summary>
-        <value>The [!INCLUDE[iisver](~/includes/iisver-md.md)] substatus code.</value>
+        <value>The IIS 7.0 substatus code.</value>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] and at least the .NET Framework version 3.0.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operation requires the integrated pipeline mode in IIS 7.0 and at least the .NET Framework version 3.0.</exception>
         <exception cref="T:System.Web.HttpException">The status code was set after all HTTP headers were sent.</exception>
       </Docs>
     </Member>
@@ -2463,9 +2463,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies whether [!INCLUDE[iisver](~/includes/iisver-md.md)] custom errors are disabled.</summary>
+        <summary>Gets or sets a value that specifies whether IIS 7.0 custom errors are disabled.</summary>
         <value>
-          <see langword="true" /> if [!INCLUDE[iisver](~/includes/iisver-md.md)] custom errors are disabled; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if IIS 7.0 custom errors are disabled; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Web/HttpRuntime.xml b/xml/System.Web/HttpRuntime.xml
index 44c0bde62b0..9d154378011 100644
--- a/xml/System.Web/HttpRuntime.xml
+++ b/xml/System.Web/HttpRuntime.xml
@@ -606,14 +606,14 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the current application is running in the integrated-pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</summary>
+        <summary>Gets a value that indicates whether the current application is running in the integrated-pipeline mode of IIS 7.0.</summary>
         <value>
           <see langword="true" /> if the application is running in integrated-pipeline mode; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Integrated-pipeline mode is not available in versions of IIS earlier than [!INCLUDE[iisver](~/includes/iisver-md.md)].  
+ Integrated-pipeline mode is not available in versions of IIS earlier than IIS 7.0.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web/HttpServerUtility.xml b/xml/System.Web/HttpServerUtility.xml
index 921b930f58e..700791a3563 100644
--- a/xml/System.Web/HttpServerUtility.xml
+++ b/xml/System.Web/HttpServerUtility.xml
@@ -1098,7 +1098,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -1145,7 +1145,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -1184,7 +1184,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is used when running with the integrated pipeline mode in [!INCLUDE[iisver](~/includes/iisver-md.md)] to allow request processing to be transferred from one resource type to another while executing the target request with the correct request context. For example, you can use the <xref:System.Web.HttpServerUtility.TransferRequest%2A> method to transfer a request for an ASPX page to a request for an XML page.  
+ This method is used when running with the integrated pipeline mode in IIS 7.0 to allow request processing to be transferred from one resource type to another while executing the target request with the correct request context. For example, you can use the <xref:System.Web.HttpServerUtility.TransferRequest%2A> method to transfer a request for an ASPX page to a request for an XML page.  
   
  The <xref:System.Web.HttpServerUtility.TransferRequest%2A> method performs an asynchronous child execution of the specified URL with the following conditions:  
   
@@ -1202,7 +1202,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires [!INCLUDE[iisver](~/includes/iisver-md.md)] running in integrated mode.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires IIS 7.0 running in integrated mode.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -1247,7 +1247,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
diff --git a/xml/System.Web/HttpServerUtilityWrapper.xml b/xml/System.Web/HttpServerUtilityWrapper.xml
index 221a7d739ab..f36e3abd909 100644
--- a/xml/System.Web/HttpServerUtilityWrapper.xml
+++ b/xml/System.Web/HttpServerUtilityWrapper.xml
@@ -801,7 +801,7 @@
         <param name="path">The URL of the page or handler to execute.</param>
         <summary>Asynchronously executes the end point at the specified URL.</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -836,7 +836,7 @@
           <see langword="true" /> to preserve the <see cref="P:System.Web.HttpRequest.QueryString" /> and <see cref="P:System.Web.HttpRequest.Form" /> collections; <see langword="false" /> to clear the <see cref="P:System.Web.HttpRequest.QueryString" /> and <see cref="P:System.Web.HttpRequest.Form" /> collections.</param>
         <summary>Asynchronously executes the endpoint at the specified URL and specifies whether to clear the <see cref="P:System.Web.HttpRequestBase.QueryString" /> and <see cref="P:System.Web.HttpRequestBase.Form" /> collections.</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -875,7 +875,7 @@
         <param name="headers">A collection of request headers for the new request.</param>
         <summary>Asynchronously executes the endpoint at the specified URL by using the specified HTTP method and headers.</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires [!INCLUDE[iisver](~/includes/iisver-md.md)] running in integrated mode.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires IIS 7.0 running in integrated mode.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
@@ -916,7 +916,7 @@
           <see langword="true" /> to preserve the user identity; otherwise, <see langword="false" />. Other overloads of this method call this method overload with the <paramref name="preserveUser" /> parameter set to <see langword="true" />.</param>
         <summary>Performs an asynchronous execution of the specified URL using the specified HTTP method, headers, path, and options to preserve form values and preserve the user identity.</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of [!INCLUDE[iisver](~/includes/iisver-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The request requires the integrated pipeline mode of IIS 7.0.</exception>
         <exception cref="T:System.Web.HttpException">The server is not available to handle the request.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="path" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="path" /> parameter is invalid.</exception>
diff --git a/xml/System.Web/IisTraceListener.xml b/xml/System.Web/IisTraceListener.xml
index 6a31c3e00fe..277de6c84d8 100644
--- a/xml/System.Web/IisTraceListener.xml
+++ b/xml/System.Web/IisTraceListener.xml
@@ -20,10 +20,10 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.IisTraceListener> class connects the tracing mechanism of [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] to [!INCLUDE[iisver](~/includes/iisver-md.md)]. This listener class enables developers who create [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications and who implement the <xref:System.Web.IHttpModule> and <xref:System.Web.IHttpHandler> interfaces to raise page-level, module-level, or handler-level events to the [!INCLUDE[iisver](~/includes/iisver-md.md)] infrastructure when tracing is enabled.  
+ The <xref:System.Web.IisTraceListener> class connects the tracing mechanism of [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] to IIS 7.0. This listener class enables developers who create [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications and who implement the <xref:System.Web.IHttpModule> and <xref:System.Web.IHttpHandler> interfaces to raise page-level, module-level, or handler-level events to the IIS 7.0 infrastructure when tracing is enabled.  
   
 > [!NOTE]
->  This listener class does not route [!INCLUDE[iisver](~/includes/iisver-md.md)] events to ASP.NET classes. This includes the <xref:System.Web.UI.Page> class and classes that implement the <xref:System.Web.IHttpModule> or <xref:System.Web.IHttpHandler> interface.  
+>  This listener class does not route IIS 7.0 events to ASP.NET classes. This includes the <xref:System.Web.UI.Page> class and classes that implement the <xref:System.Web.IHttpModule> or <xref:System.Web.IHttpHandler> interface.  
   
  <xref:System.Web.IisTraceListener> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   

From 1bfc40e3622561893b690f65a0cc070b12b9a6eb Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:03:02 -0800
Subject: [PATCH 015/236] infocard

---
 xml/System.IdentityModel.Selectors/CardSpaceSelector.xml    | 4 ++--
 .../UntrustedRecipientException.xml                         | 2 +-
 xml/System.ServiceModel.Description/ClientCredentials.xml   | 6 +++---
 .../ClaimTypeRequirement.xml                                | 2 +-
 .../ServiceModelSecurityTokenRequirement.xml                | 4 ++--
 5 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.IdentityModel.Selectors/CardSpaceSelector.xml b/xml/System.IdentityModel.Selectors/CardSpaceSelector.xml
index 8fd11e55dc3..842c890ab64 100644
--- a/xml/System.IdentityModel.Selectors/CardSpaceSelector.xml
+++ b/xml/System.IdentityModel.Selectors/CardSpaceSelector.xml
@@ -178,12 +178,12 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Displays the [!INCLUDE[infocard](~/includes/infocard-md.md)] management user interface that allows the user to create, delete, rename, and modify the card.</summary>
+        <summary>Displays the CardSpace management user interface that allows the user to create, delete, rename, and modify the card.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[infocard](~/includes/infocard-md.md)] does not provide programmatic access to the cards for life-cycle management for privacy and security reasons. For example, you cannot programmatically create, delete, or enumerate cards.  
+ CardSpace does not provide programmatic access to the cards for life-cycle management for privacy and security reasons. For example, you cannot programmatically create, delete, or enumerate cards.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.IdentityModel.Selectors/UntrustedRecipientException.xml b/xml/System.IdentityModel.Selectors/UntrustedRecipientException.xml
index 950e1d0866f..068745a1e0a 100644
--- a/xml/System.IdentityModel.Selectors/UntrustedRecipientException.xml
+++ b/xml/System.IdentityModel.Selectors/UntrustedRecipientException.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This exception is thrown when the user clicks "I am not satisfied with this organization's identity/policies" in the [!INCLUDE[infocard](~/includes/infocard-md.md)] user interface.  
+ This exception is thrown when the user clicks "I am not satisfied with this organization's identity/policies" in the CardSpace user interface.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel.Description/ClientCredentials.xml b/xml/System.ServiceModel.Description/ClientCredentials.xml
index 27207caf43e..cb346b25b71 100644
--- a/xml/System.ServiceModel.Description/ClientCredentials.xml
+++ b/xml/System.ServiceModel.Description/ClientCredentials.xml
@@ -419,10 +419,10 @@
         <Parameter Name="tokenSerializer" Type="System.IdentityModel.Selectors.SecurityTokenSerializer" Index="2" FrameworkAlternate="netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="requiresInfoCard">A value that determines whether [!INCLUDE[infocard](~/includes/infocard-md.md)] is required.</param>
+        <param name="requiresInfoCard">A value that determines whether CardSpace is required.</param>
         <param name="chain">An array of <see cref="T:System.IdentityModel.Selectors.CardSpacePolicyElement" /> that describes the federated security chain that the client requires a final token to unwind.</param>
         <param name="tokenSerializer">A <see cref="T:System.IdentityModel.Selectors.SecurityTokenSerializer" /> that can read a <see langword="KeyInfo" /> clause.</param>
-        <summary>Generates and returns a security token using the [!INCLUDE[infocard](~/includes/infocard-md.md)] system and the specified policy chain and token serializer.</summary>
+        <summary>Generates and returns a security token using the CardSpace system and the specified policy chain and token serializer.</summary>
         <returns>A <see cref="T:System.IdentityModel.Tokens.GenericXmlSecurityToken" /> that represents the generated security token. Returns <see langword="null" /> if <paramref name="requiresInfoCard" /> is <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -670,7 +670,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property controls whether a user interface is allowed to pop up during credential provisioning. The most common case where this currently happens is with [!INCLUDE[infocard](~/includes/infocard-md.md)].  
+ This property controls whether a user interface is allowed to pop up during credential provisioning. The most common case where this currently happens is with CardSpace.  
   
    
   
diff --git a/xml/System.ServiceModel.Security.Tokens/ClaimTypeRequirement.xml b/xml/System.ServiceModel.Security.Tokens/ClaimTypeRequirement.xml
index 34e5be395fb..976159065da 100644
--- a/xml/System.ServiceModel.Security.Tokens/ClaimTypeRequirement.xml
+++ b/xml/System.ServiceModel.Security.Tokens/ClaimTypeRequirement.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In a federated scenario, services state the requirements on incoming credentials. For example, the incoming credentials must possess a certain set of claim types. This requirement is manifested in a security policy. When a client requests a security token from a security token service (for example, [!INCLUDE[infocard](~/includes/infocard-md.md)]), it puts the requirements into a token request so that the security token service can issue the security token that satisfies the requirements accordingly.  
+ In a federated scenario, services state the requirements on incoming credentials. For example, the incoming credentials must possess a certain set of claim types. This requirement is manifested in a security policy. When a client requests a security token from a security token service (for example, CardSpace), it puts the requirements into a token request so that the security token service can issue the security token that satisfies the requirements accordingly.  
   
    
   
diff --git a/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml b/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml
index ccd6293a92e..105ca0f95f0 100644
--- a/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml
+++ b/xml/System.ServiceModel.Security.Tokens/ServiceModelSecurityTokenRequirement.xml
@@ -770,7 +770,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value that corresponds to this key is of type <xref:System.Uri>. This property can be used to display the link in the user interface (UI) similar to the way [!INCLUDE[infocard](~/includes/infocard-md.md)] does.  
+ The value that corresponds to this key is of type <xref:System.Uri>. This property can be used to display the link in the user interface (UI) similar to the way CardSpace does.  
   
  ]]></format>
         </remarks>
@@ -802,7 +802,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value that corresponds to this key is of type <xref:System.Int32>. This property can be used to display the link in the user interface (UI) similar to the way [!INCLUDE[infocard](~/includes/infocard-md.md)] does.  
+ The value that corresponds to this key is of type <xref:System.Int32>. This property can be used to display the link in the user interface (UI) similar to the way CardSpace does.  
   
  ]]></format>
         </remarks>

From db1b5964ceefb0b7c7cafd48d1b1e638552dc4af Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:03:32 -0800
Subject: [PATCH 016/236] linq-dataset

---
 xml/System.Data/DataTableExtensions.xml       | 8 ++++----
 xml/System.Data/DataView.xml                  | 4 ++--
 xml/System.Data/EnumerableRowCollection`1.xml | 2 +-
 xml/index.xml                                 | 4 ++--
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Data/DataTableExtensions.xml b/xml/System.Data/DataTableExtensions.xml
index d3dcc3f4857..f98807ebc6a 100644
--- a/xml/System.Data/DataTableExtensions.xml
+++ b/xml/System.Data/DataTableExtensions.xml
@@ -72,7 +72,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Data.DataView> enables data-binding scenarios for [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] and can be created from a typed or untyped <xref:System.Data.DataTable>, providing a default view of that table. Filtering and sorting can be set on the <xref:System.Data.DataView> after it has been created from a <xref:System.Data.DataTable>. The <xref:System.Data.DataView> is then bound to a UI control, such as a <xref:System.Windows.Forms.DataGrid> or a <xref:System.Windows.Forms.DataGridView>, providing a simple data binding model.  
+ <xref:System.Data.DataView> enables data-binding scenarios for LINQ to DataSet and can be created from a typed or untyped <xref:System.Data.DataTable>, providing a default view of that table. Filtering and sorting can be set on the <xref:System.Data.DataView> after it has been created from a <xref:System.Data.DataTable>. The <xref:System.Data.DataView> is then bound to a UI control, such as a <xref:System.Windows.Forms.DataGrid> or a <xref:System.Windows.Forms.DataGridView>, providing a simple data binding model.  
   
  For more information and examples, see [Creating a DataView Object](/dotnet/framework/data/adonet/creating-a-dataview-object-linq-to-dataset).  
   
@@ -126,14 +126,14 @@
       </Parameters>
       <Docs>
         <typeparam name="T">The type of objects in the source sequence, typically <see cref="T:System.Data.DataRow" />.</typeparam>
-        <param name="source">The source [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query from which the LINQ-enabled <see cref="T:System.Data.DataView" /> is created.</param>
-        <summary>Creates and returns a LINQ-enabled <see cref="T:System.Data.DataView" /> object representing the [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query.</summary>
+        <param name="source">The source LINQ to DataSet query from which the LINQ-enabled <see cref="T:System.Data.DataView" /> is created.</param>
+        <summary>Creates and returns a LINQ-enabled <see cref="T:System.Data.DataView" /> object representing the LINQ to DataSet query.</summary>
         <returns>A LINQ-enabled <see cref="T:System.Data.DataView" /> object.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Data.DataView> enables data binding scenarios for [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] and can be created from a [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query. The <xref:System.Data.DataView> represents the query itself, and is not a view on top of the query. The newly created <xref:System.Data.DataView> infers the filtering and sorting information from the query it is created from. The <xref:System.Data.DataView> is then bound to a UI control, such as a <xref:System.Windows.Forms.DataGrid> or a <xref:System.Windows.Forms.DataGridView>, providing a simple data-binding model.  
+ <xref:System.Data.DataView> enables data binding scenarios for LINQ to DataSet and can be created from a LINQ to DataSet query. The <xref:System.Data.DataView> represents the query itself, and is not a view on top of the query. The newly created <xref:System.Data.DataView> infers the filtering and sorting information from the query it is created from. The <xref:System.Data.DataView> is then bound to a UI control, such as a <xref:System.Windows.Forms.DataGrid> or a <xref:System.Windows.Forms.DataGridView>, providing a simple data-binding model.  
   
  The parameter `T` of the input parameter `source` can only be of type <xref:System.Data.DataRow> or a type derived from <xref:System.Data.DataRow>.  
   
diff --git a/xml/System.Data/DataView.xml b/xml/System.Data/DataView.xml
index 687204540a0..e8b4e9fafe2 100644
--- a/xml/System.Data/DataView.xml
+++ b/xml/System.Data/DataView.xml
@@ -136,7 +136,7 @@
 > [!NOTE]
 >  If you do not explicitly specify sort criteria for `DataView`, the `DataRowView` objects in `DataView` are sorted based on the index of DataView's corresponding `DataRow` in the `DataTable.Rows` `DataRowCollection`.  
   
- [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] allows developers to create complex, powerful queries over a <xref:System.Data.DataSet> by using [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)]. A [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query returns an enumeration of <xref:System.Data.DataRow> objects, however, which is not easily used in a binding scenario. <xref:System.Data.DataView> can be created from a [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query and takes on the filtering and sorting characteristics of that query. [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] extends the functionality of the <xref:System.Data.DataView> by providing [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression-based filtering and sorting, which allows for much more complex and powerful filtering and sorting operations than string-based filtering and sorting. See [Data Binding and LINQ to DataSet](/dotnet/framework/data/adonet/data-binding-and-linq-to-dataset) for more information.  
+ LINQ to DataSet allows developers to create complex, powerful queries over a <xref:System.Data.DataSet> by using [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)]. A LINQ to DataSet query returns an enumeration of <xref:System.Data.DataRow> objects, however, which is not easily used in a binding scenario. <xref:System.Data.DataView> can be created from a LINQ to DataSet query and takes on the filtering and sorting characteristics of that query. LINQ to DataSet extends the functionality of the <xref:System.Data.DataView> by providing [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression-based filtering and sorting, which allows for much more complex and powerful filtering and sorting operations than string-based filtering and sorting. See [Data Binding and LINQ to DataSet](/dotnet/framework/data/adonet/data-binding-and-linq-to-dataset) for more information.  
   
    
   
@@ -146,7 +146,7 @@
  [!code-csharp[Classic WebData DataView Example#1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/Classic WebData DataView Example/CS/source.cs#1)]
  [!code-vb[Classic WebData DataView Example#1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/Classic WebData DataView Example/VB/source.vb#1)]  
   
- The following example creates a <xref:System.Data.DataView> of online orders ordered by total due from a [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query:  
+ The following example creates a <xref:System.Data.DataView> of online orders ordered by total due from a LINQ to DataSet query:  
   
  [!code-csharp[DP DataView Samples#CreateLDVFromQuery1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/DP DataView Samples/CS/Form1.cs#createldvfromquery1)]
  [!code-vb[DP DataView Samples#CreateLDVFromQuery1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/DP DataView Samples/VB/Form1.vb#createldvfromquery1)]  
diff --git a/xml/System.Data/EnumerableRowCollection`1.xml b/xml/System.Data/EnumerableRowCollection`1.xml
index 8b3695089de..1b340467b3d 100644
--- a/xml/System.Data/EnumerableRowCollection`1.xml
+++ b/xml/System.Data/EnumerableRowCollection`1.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When used with [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] queries, `Trow` will be of type <xref:System.Data.DataRow>.  
+ When used with LINQ to DataSet queries, `Trow` will be of type <xref:System.Data.DataRow>.  
   
  This method cannot be overridden.  
   
diff --git a/xml/index.xml b/xml/index.xml
index 438d81b3a8a..8c4eb41ccf9 100644
--- a/xml/index.xml
+++ b/xml/index.xml
@@ -224282,8 +224282,8 @@
         </Parameters>
         <Docs>
           <typeparam name="T">The type of objects in the source sequence, typically <see cref="T:System.Data.DataRow" />.</typeparam>
-          <param name="source">The source [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query from which the LINQ-enabled <see cref="T:System.Data.DataView" /> is created.</param>
-          <summary>Creates and returns a LINQ-enabled <see cref="T:System.Data.DataView" /> object representing the [!INCLUDE[linq_dataset](~/includes/linq-dataset-md.md)] query.</summary>
+          <param name="source">The source LINQ to DataSet query from which the LINQ-enabled <see cref="T:System.Data.DataView" /> is created.</param>
+          <summary>Creates and returns a LINQ-enabled <see cref="T:System.Data.DataView" /> object representing the LINQ to DataSet query.</summary>
         </Docs>
         <Link Type="System.Data.DataTableExtensions" Member="M:System.Data.DataTableExtensions.AsDataView``1(System.Data.EnumerableRowCollection{``0})" />
       </Member>

From 8f4a33a095037f4e13530f66547a7ef669d9fd7a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:04:03 -0800
Subject: [PATCH 017/236] ndptecclick

---
 .../GenerateApplicationManifest.xml           |  2 +-
 .../GenerateDeploymentManifest.xml            |  2 +-
 .../LocalFileSettingsProvider.xml             |  2 +-
 .../ApplicationDeployment.xml                 | 96 +++++++++----------
 .../DeploymentDownloadException.xml           |  6 +-
 .../DeploymentProgressState.xml               | 10 +-
 .../DeploymentServiceCom.xml                  |  2 +-
 .../GetManifestCompletedEventArgs.xml         | 26 ++---
 .../InPlaceHostingManager.xml                 | 36 +++----
 .../InvalidDeploymentException.xml            |  4 +-
 .../TrustNotGrantedException.xml              |  6 +-
 xml/System.Windows.Forms/Application.xml      | 14 +--
 xml/System.Windows.Forms/FileDialog.xml       |  2 +-
 13 files changed, 104 insertions(+), 104 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
index 38003715b4e..00f99a0dd63 100644
--- a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- `EntryPoint` is an optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter that indicates the entry point for the generated manifest assembly. For a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment manifest, this input specifies the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application manifest.
+ `EntryPoint` is an optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter that indicates the entry point for the generated manifest assembly. For a ClickOnce deployment manifest, this input specifies the ClickOnce application manifest.
 
  In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the [GenerateApplicationManifest Task](/visualstudio/msbuild/generateapplicationmanifest-task) requires an `EntryPoint` when an application manifest is generated. (Assembly or native manifests do not require an `EntryPoint`.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
 
diff --git a/xml/Microsoft.Build.Tasks/GenerateDeploymentManifest.xml b/xml/Microsoft.Build.Tasks/GenerateDeploymentManifest.xml
index dcdaf7a873d..83f68ef78c9 100644
--- a/xml/Microsoft.Build.Tasks/GenerateDeploymentManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateDeploymentManifest.xml
@@ -341,7 +341,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this option for Web server security to limit the number of file name extensions that must be unblocked to enable [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application deployment. The default value is `false`.  
+ Use this option for Web server security to limit the number of file name extensions that must be unblocked to enable ClickOnce application deployment. The default value is `false`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Configuration/LocalFileSettingsProvider.xml b/xml/System.Configuration/LocalFileSettingsProvider.xml
index 540800edc96..8a240a402e8 100644
--- a/xml/System.Configuration/LocalFileSettingsProvider.xml
+++ b/xml/System.Configuration/LocalFileSettingsProvider.xml
@@ -467,7 +467,7 @@
   
  This way this method is called depends on the type of application that is being upgraded:  
   
--   Each version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is stored in its own isolated installation directory. After a new version of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is installed, and when the new version is first run, internal logic will automatically call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A> to migrate all common application settings to the new version. For more information, see [ClickOnce and Application Settings](/visualstudio/deployment/clickonce-and-application-settings).  
+-   Each version of a ClickOnce application is stored in its own isolated installation directory. After a new version of a ClickOnce application is installed, and when the new version is first run, internal logic will automatically call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A> to migrate all common application settings to the new version. For more information, see [ClickOnce and Application Settings](/visualstudio/deployment/clickonce-and-application-settings).  
   
 -   Standard Windows Forms and console applications must manually call <xref:System.Configuration.LocalFileSettingsProvider.Upgrade%2A>, because there is not a general, automatic way to determine when such an application is first run. The two common ways to do this are either from the installation program or using from the application itself, using a persisted property, often named something like `IsFirstRun`.  
   
diff --git a/xml/System.Deployment.Application/ApplicationDeployment.xml b/xml/System.Deployment.Application/ApplicationDeployment.xml
index ef93a833587..0a114c78f19 100644
--- a/xml/System.Deployment.Application/ApplicationDeployment.xml
+++ b/xml/System.Deployment.Application/ApplicationDeployment.xml
@@ -20,16 +20,16 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- You can configure your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application to check for updates and install them automatically through the `subscription` element of the deployment manifest. Some applications, however, need finer control over their updates. You may want to install required updates programmatically, and prompt users to install optional updates at their convenience. By turning off subscription updates in the deployment manifest, you can take complete control of your application's update policies. Alternatively, you can use automatic subscription in conjunction with <xref:System.Deployment.Application.ApplicationDeployment>, which enables [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] to update the application periodically, but uses <xref:System.Deployment.Application.ApplicationDeployment> to download critical updates shortly after they are released.
+ You can configure your ClickOnce application to check for updates and install them automatically through the `subscription` element of the deployment manifest. Some applications, however, need finer control over their updates. You may want to install required updates programmatically, and prompt users to install optional updates at their convenience. By turning off subscription updates in the deployment manifest, you can take complete control of your application's update policies. Alternatively, you can use automatic subscription in conjunction with <xref:System.Deployment.Application.ApplicationDeployment>, which enables ClickOnce to update the application periodically, but uses <xref:System.Deployment.Application.ApplicationDeployment> to download critical updates shortly after they are released.
 
  You can test whether your deployment has an available update by using either the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> or the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync%2A> method; the latter method raises the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateCompleted> event on successful completion. <xref:System.Deployment.Application.ApplicationDeployment.CheckForDetailedUpdate%2A> returns important information about the update, such as its version number and whether it is a required update for current users. If an update is available, you can install it by using <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> or <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A>; the latter method raises the <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> event after installation of the update is complete. For large updates, you can receive progress notifications through the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateProgressChanged> and <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged> events, and use the information in <xref:System.ComponentModel.ProgressChangedEventArgs> to notify the user of the download status.
 
  You can also use <xref:System.Deployment.Application.ApplicationDeployment> to download large files and assemblies on demand. These files must be marked as "optional" within the deployment's application manifest so that they are not downloaded during installation. You can download the files at any point during the application's duration by using the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> or the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method. You can download assemblies before they are loaded into memory by supplying an event handler for the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain> class. For more information, see [Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer](/visualstudio/deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api-using-the-designer).
 
 > [!NOTE]
->  If you update a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application while the application is running, the user will not see the updates until you call the <xref:System.Windows.Forms.Application.Restart%2A> method of the <xref:System.Windows.Forms.Application>, which will close the current running instance of the application and immediately restart it.
+>  If you update a ClickOnce application while the application is running, the user will not see the updates until you call the <xref:System.Windows.Forms.Application.Restart%2A> method of the <xref:System.Windows.Forms.Application>, which will close the current running instance of the application and immediately restart it.
 
- <xref:System.Deployment.Application.ApplicationDeployment> has no public constructor; you obtain instances of the class within a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application through the <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> property. You use the <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> property to verify that the current application is a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.
+ <xref:System.Deployment.Application.ApplicationDeployment> has no public constructor; you obtain instances of the class within a ClickOnce application through the <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> property. You use the <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> property to verify that the current application is a ClickOnce application.
 
  <xref:System.Deployment.Application.ApplicationDeployment> supports checking for updates and downloading updated files asynchronously by using the new [Event-based Asynchronous Pattern Overview](/dotnet/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-overview), which exposes completion callbacks as class events. <xref:System.Deployment.Application.ApplicationDeployment> starts and manages the threads for you, and calls your application back on the correct UI thread. Through this class, you can update without locking up the application, so that the user can continue working while the update installs. If the user must stop all work while an update takes place, consider using the synchronous methods instead.
 
@@ -203,7 +203,7 @@
  This method will block until the check has completed. To check for an update asynchronously, use the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync%2A> method instead.
 
 > [!NOTE]
->  If <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> discovers that an update is available, and the user chooses not to install it, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will prompt the user that an update is available the next time the application is run. There is no way to disable this prompting. (If the application is a required update, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will install it without prompting.)
+>  If <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> discovers that an update is available, and the user chooses not to install it, ClickOnce will prompt the user that an update is available the next time the application is run. There is no way to disable this prompting. (If the application is a required update, ClickOnce will install it without prompting.)
 
 
 
@@ -216,7 +216,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.InvalidOperationException">[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] throws this exception immediately if you call the <see cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdate" /> method while an update is already in progress.</exception>
+        <exception cref="T:System.InvalidOperationException">ClickOnce throws this exception immediately if you call the <see cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdate" /> method while an update is already in progress.</exception>
         <exception cref="T:System.Deployment.Application.DeploymentDownloadException">The deployment manifest cannot be downloaded.</exception>
         <exception cref="T:System.Deployment.Application.InvalidDeploymentException">The deployment manifest is corrupted. You will likely need to redeploy the application to fix this problem.</exception>
         <altmember cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync" />
@@ -278,7 +278,7 @@
  You can cancel an asynchronous update by calling <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsyncCancel%2A>.
 
 > [!NOTE]
->  If <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> discovers that an update is available, and the user chooses not to install it, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will prompt the user that an update is available the next time the application is run. There is no way to disable this prompting. (If the application is a required update, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will install it without prompting.)
+>  If <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A> discovers that an update is available, and the user chooses not to install it, ClickOnce will prompt the user that an update is available the next time the application is run. There is no way to disable this prompting. (If the application is a required update, ClickOnce will install it without prompting.)
 
 
 
@@ -291,7 +291,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.InvalidOperationException">[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] throws this exception immediately if you call the <see cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync" /> method while an update is already in progress.</exception>
+        <exception cref="T:System.InvalidOperationException">ClickOnce throws this exception immediately if you call the <see cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync" /> method while an update is already in progress.</exception>
         <exception cref="T:System.Deployment.Application.DeploymentDownloadException">The deployment manifest cannot be downloaded. This exception appears in the <see cref="P:System.ComponentModel.AsyncCompletedEventArgs.Error" /> property of the <see cref="E:System.Deployment.Application.ApplicationDeployment.CheckForUpdateCompleted" /> event.</exception>
         <exception cref="T:System.Deployment.Application.InvalidDeploymentException">The deployment manifest is corrupted. You will likely need to redeploy the application to fix this problem. This exception appears in the <see cref="P:System.ComponentModel.AsyncCompletedEventArgs.Error" /> property of the <see cref="E:System.Deployment.Application.ApplicationDeployment.CheckForUpdateCompleted" /> event.</exception>
         <altmember cref="M:System.Deployment.Application.ApplicationDeployment.CheckForUpdate" />
@@ -429,7 +429,7 @@
 ## Remarks
  You cannot create instances of <xref:System.Deployment.Application.ApplicationDeployment> directly in your application; you must retrieve a valid instance through the <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> property.
 
- The <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> static property is valid only from within an application that was deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. Attempts to call this property from non-[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications will throw an exception. If you are developing an application that may or may not be deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)], use the <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> property to test whether the current program is a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.
+ The <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> static property is valid only from within an application that was deployed using ClickOnce. Attempts to call this property from non-ClickOnce applications will throw an exception. If you are developing an application that may or may not be deployed using ClickOnce, use the <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> property to test whether the current program is a ClickOnce application.
 
 
 
@@ -442,7 +442,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">You attempted to call this static property from a non-[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</exception>
+        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">You attempted to call this static property from a non-ClickOnce application.</exception>
         <altmember cref="P:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed" />
       </Docs>
     </Member>
@@ -474,7 +474,7 @@
 
 
 ## Examples
- The following code example defines a method that determines whether [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] has updated the application.
+ The following code example defines a method that determines whether ClickOnce has updated the application.
 
  [!code-cpp[ClickOnceAPI#3](~/samples/snippets/cpp/VS_Snippets_Winforms/ClickOnceAPI/cpp/form1.cpp#3)]
  [!code-csharp[ClickOnceAPI#3](~/samples/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Form1.cs#3)]
@@ -502,7 +502,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the path to the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] data directory.</summary>
+        <summary>Gets the path to the ClickOnce data directory.</summary>
         <value>A string containing the path to the application's data directory on the local disk.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -527,25 +527,25 @@
         <Parameter Name="groupName" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="groupName">The named group of files to download. All files marked "optional" in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application require a group name.</param>
+        <param name="groupName">The named group of files to download. All files marked "optional" in a ClickOnce application require a group name.</param>
         <summary>Downloads a set of optional files on demand.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it.
+ In a ClickOnce application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it.
 
  To use an assembly you have downloaded with <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A>, you attach an event listener to the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain.CurrentDomain%2A>. For an example, see =[Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API Using the Designer](/visualstudio/deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api-using-the-designer).
 
- All files are downloaded to the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application cache and are therefore isolated to the current version of the application. Let's say that after an application downloads a file group, the user installs a new version of the application, but later reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded. For more information about accessing data files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).
+ All files are downloaded to the ClickOnce application cache and are therefore isolated to the current version of the application. Let's say that after an application downloads a file group, the user installs a new version of the application, but later reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded. For more information about accessing data files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).
 
- <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application running with restricted permission. However, if you attempt to load assemblies dynamically, your application will require full trust.
+ <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any ClickOnce application running with restricted permission. However, if you attempt to load assemblies dynamically, your application will require full trust.
 
  On-demand downloading of data files is currently not supported.
 
  Your application will not be responsive to user input until the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> method returns. If you need to download files without interrupting the user's workflow, use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method instead.
 
- You cannot download a single file by its file name alone. To download a single file, assign it a group name in your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment and download the group using this method.
+ You cannot download a single file by its file name alone. To download a single file, assign it a group name in your ClickOnce deployment and download the group using this method.
 
 
 
@@ -594,27 +594,27 @@
         <Parameter Name="groupName" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="groupName">The named group of files to download. All files marked "optional" in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application require a group name.</param>
+        <param name="groupName">The named group of files to download. All files marked "optional" in a ClickOnce application require a group name.</param>
         <summary>Downloads, on demand, a set of optional files in the background.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. This approach works not only for static files, but also for assemblies that an application may or may not require. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it.
+ In a ClickOnce application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. This approach works not only for static files, but also for assemblies that an application may or may not require. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it.
 
  To download assemblies on demand, attach an event listener to the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain.CurrentDomain%2A>. For an example, see [Walkthrough: Downloading Assemblies on Demand with the ClickOnce Deployment API](/visualstudio/deployment/walkthrough-downloading-assemblies-on-demand-with-the-clickonce-deployment-api).
 
- All assemblies are downloaded to the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application cache.
+ All assemblies are downloaded to the ClickOnce application cache.
 
- All static files are downloaded to the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application's data directory and are therefore isolated to the current version of the application. Let's say that after an application downloads a file group, the user installs a new version of the application, but later reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded. For more information about accessing static files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).
+ All static files are downloaded to the ClickOnce application's data directory and are therefore isolated to the current version of the application. Let's say that after an application downloads a file group, the user installs a new version of the application, but later reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded. For more information about accessing static files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).
 
  You can download multiple file groups simultaneously using <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A>. You can distinguish among them by using the <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs.Group%2A> property of the <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs> class, which is passed to the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupProgressChanged> event. If you need to pass more complex state, you can use <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> to pass in a `state` object.
 
- <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application running with restricted permission. However, if you are attempting to load assemblies dynamically, your application will require full trust.
+ <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any ClickOnce application running with restricted permission. However, if you are attempting to load assemblies dynamically, your application will require full trust.
 
  On-demand downloading of data files is currently not supported.
 
- You cannot download a single file by its file name alone. To download a single file, assign it a group name in your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment and download the group using this method.
+ You cannot download a single file by its file name alone. To download a single file, assign it a group name in your ClickOnce deployment and download the group using this method.
 
  To cancel an asynchronous download, call the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsyncCancel%2A> method.
 
@@ -651,22 +651,22 @@
         <Parameter Name="userState" Type="System.Object" />
       </Parameters>
       <Docs>
-        <param name="groupName">The named group of files to download. All files marked "optional" in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application require a group name.</param>
+        <param name="groupName">The named group of files to download. All files marked "optional" in a ClickOnce application require a group name.</param>
         <param name="userState">An arbitrary object containing state information for the asynchronous operation.</param>
         <summary>Downloads, on demand, a set of optional files in the background, and passes a piece of application state to the event callbacks.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- In a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. This approach works not only for static files, but also for assemblies that an application may or may not require. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it. To download assemblies on demand, attach an event listener to the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain.CurrentDomain%2A>.
+ In a ClickOnce application, the files marked "optional" in the application manifest are not downloaded during initialization or update. You can use the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method to download all of the files belonging to a named group on demand, so that they do not consume network resources and disk space until you are sure the user requires them. This approach works not only for static files, but also for assemblies that an application may or may not require. For example, certain users may need to use a data analysis package included in your application on a daily basis, while other users may never invoke it. To download assemblies on demand, attach an event listener to the <xref:System.AppDomain.AssemblyResolve> event on the <xref:System.AppDomain.CurrentDomain%2A>.
 
  You can download multiple file groups simultaneously by using the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method. You can distinguish among them by using the <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs.Group%2A> property of the <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs> class, which is passed to the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupProgressChanged> event. If you need to pass a more complex state, you can use
 
  <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> to pass in a `state` object.
 
- All static files are downloaded to the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application's data directory and are therefore isolated to the current version of the application. For more information about accessing static files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications). . Let's say that after an application downloads a file group, the user installs a new version of the application, but later  user reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded.
+ All static files are downloaded to the ClickOnce application's data directory and are therefore isolated to the current version of the application. For more information about accessing static files, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications). . Let's say that after an application downloads a file group, the user installs a new version of the application, but later  user reverts to the previous version of the application. In this case, the previous version will still have the copies of the files it originally downloaded.
 
- <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application running with restricted permission. However, if you are attempting to load assemblies dynamically, your application will require full trust.
+ <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> works in partially trusted applications, that is, in any ClickOnce application running with restricted permission. However, if you are attempting to load assemblies dynamically, your application will require full trust.
 
  On-demand downloading of data files is currently not supported.
 
@@ -704,7 +704,7 @@
         <Parameter Name="groupName" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="groupName">The named group of files to download. All files marked "optional" in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application require a group name.</param>
+        <param name="groupName">The named group of files to download. All files marked "optional" in a ClickOnce application require a group name.</param>
         <summary>Cancels an asynchronous file download.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
@@ -809,7 +809,7 @@
         <Parameter Name="groupName" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="groupName">The named group of files to download. All files marked "optional" in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application require a group name.</param>
+        <param name="groupName">The named group of files to download. All files marked "optional" in a ClickOnce application require a group name.</param>
         <summary>Checks whether the named file group has already been downloaded to the client computer.</summary>
         <returns>
           <see langword="true" /> if the file group has already been downloaded for the current version of this application; otherwise, <see langword="false" />. If a new version of the application has been installed, and the new version has not added, removed, or altered files in the file group, <see cref="M:System.Deployment.Application.ApplicationDeployment.IsFileGroupDownloaded(System.String)" /> returns <see langword="true" />.</returns>
@@ -819,7 +819,7 @@
 ## Remarks
  <xref:System.Deployment.Application.ApplicationDeployment.IsFileGroupDownloaded%2A> works in a partially trusted application without any security demands.
 
- When you update an application, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] copies any on-demand data files from the previous version into the new version's data directory. If you download a new version of these files, you should remove any data you want to keep from the old version and move it into the new version.
+ When you update an application, ClickOnce copies any on-demand data files from the previous version into the new version's data directory. If you download a new version of these files, you should remove any data you want to keep from the old version and move it into the new version.
 
 
 
@@ -895,14 +895,14 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether the current application is a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
+        <summary>Gets a value indicating whether the current application is a ClickOnce application.</summary>
         <value>
-          <see langword="true" /> if this is a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if this is a ClickOnce application; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- If you want your application to run both inside and outside of a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment (for example, if you need to debug your application on the local computer before deploying it), test <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> before accessing the <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> property.
+ If you want your application to run both inside and outside of a ClickOnce deployment (for example, if you need to debug your application on the local computer before deploying it), test <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> before accessing the <xref:System.Deployment.Application.ApplicationDeployment.CurrentDeployment%2A> property.
 
  <xref:System.Deployment.Application.ApplicationDeployment.IsNetworkDeployed%2A> will return `true` regardless of whether the application is installed or hosted online, and regardless of whether it was installed from a Web site, file share, or CD-ROM.
 
@@ -935,20 +935,20 @@
         <ReturnType>System.DateTime</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the date and the time [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] last checked for an application update.</summary>
+        <summary>Gets the date and the time ClickOnce last checked for an application update.</summary>
         <value>The <see cref="T:System.DateTime" /> of the last update check.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- A [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application can be configured for subscription updates. In this scenario, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] polls an application's deployment location automatically at intervals defined in the deployment manifest, and determines whether there is an update available. <xref:System.Deployment.Application.ApplicationDeployment.TimeOfLastUpdateCheck%2A> returns the time of the last update check regardless of whether it was initiated by a subscription or by an explicit check using the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A>, <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync%2A>, <xref:System.Deployment.Application.ApplicationDeployment.CheckForDetailedUpdate%2A>, <xref:System.Deployment.Application.ApplicationDeployment.Update%2A>, or <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method.
+ A ClickOnce application can be configured for subscription updates. In this scenario, ClickOnce polls an application's deployment location automatically at intervals defined in the deployment manifest, and determines whether there is an update available. <xref:System.Deployment.Application.ApplicationDeployment.TimeOfLastUpdateCheck%2A> returns the time of the last update check regardless of whether it was initiated by a subscription or by an explicit check using the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdate%2A>, <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateAsync%2A>, <xref:System.Deployment.Application.ApplicationDeployment.CheckForDetailedUpdate%2A>, <xref:System.Deployment.Application.ApplicationDeployment.Update%2A>, or <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method.
 
  If no update check has been performed since the application was installed, <xref:System.Deployment.Application.ApplicationDeployment.TimeOfLastUpdateCheck%2A> returns the installation time.
 
 
 
 ## Examples
- The following code example checks whether a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application has been checked for available updates in the past three days.
+ The following code example checks whether a ClickOnce application has been checked for available updates in the past three days.
 
  [!code-cpp[ClickOnceAPI#3](~/samples/snippets/cpp/VS_Snippets_Winforms/ClickOnceAPI/cpp/form1.cpp#3)]
  [!code-csharp[ClickOnceAPI#3](~/samples/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Form1.cs#3)]
@@ -986,15 +986,15 @@
 ## Remarks
  An application is considered updated when you publish a new version of the application to the location specified by <xref:System.Deployment.Application.ApplicationDeployment.UpdateLocation%2A>, and the version number in the application's deployment manifest is greater than the version number of the application currently installed on the user's computer.
 
- The <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> call will block until the update has been downloaded to the client computer and installed into the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] cache; during this time, the application will not be responsive to the user. If you want to maintain application responsiveness or display a progress report during download, use the <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method instead.
+ The <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> call will block until the update has been downloaded to the client computer and installed into the ClickOnce cache; during this time, the application will not be responsive to the user. If you want to maintain application responsiveness or display a progress report during download, use the <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method instead.
 
  <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> downloads all of the files that are not marked as "optional" in the application manifest. You can download optional files on demand by using the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> or the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method.
 
- [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] may already be updating the application automatically when you call the <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> method; if that happens, calls to this method will throw an <xref:System.InvalidOperationException>.
+ ClickOnce may already be updating the application automatically when you call the <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> method; if that happens, calls to this method will throw an <xref:System.InvalidOperationException>.
 
- If you have updated one or more files in your deployment, but you have not refreshed your application manifest, you will receive an <xref:System.Deployment.Application.InvalidDeploymentException>. Most of the time, redeploying your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application solves this problem. You will also receive this exception if a public-key signature on a deployment manifest or application manifest is invalid or missing.
+ If you have updated one or more files in your deployment, but you have not refreshed your application manifest, you will receive an <xref:System.Deployment.Application.InvalidDeploymentException>. Most of the time, redeploying your ClickOnce application solves this problem. You will also receive this exception if a public-key signature on a deployment manifest or application manifest is invalid or missing.
 
- An update may request a higher level of trust on the local computer than the previous version of the application. If the application uses Trusted Application Deployment, the common language runtime (CLR) trust manager examines the deployment manifest to determine whether it contains a valid trust license. If the deployment manifest does not contain a valid trust license, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] stops the installation and throws a <xref:System.Deployment.Application.TrustNotGrantedException>. The <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> method will never display a prompt asking the user whether they want to grant the application permission to run.
+ An update may request a higher level of trust on the local computer than the previous version of the application. If the application uses Trusted Application Deployment, the common language runtime (CLR) trust manager examines the deployment manifest to determine whether it contains a valid trust license. If the deployment manifest does not contain a valid trust license, ClickOnce stops the installation and throws a <xref:System.Deployment.Application.TrustNotGrantedException>. The <xref:System.Deployment.Application.ApplicationDeployment.Update%2A> method will never display a prompt asking the user whether they want to grant the application permission to run.
 
 
 
@@ -1008,7 +1008,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Deployment.Application.TrustNotGrantedException">The local computer did not grant the application the permission level it requested to execute.</exception>
-        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">Your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment is corrupted. For tips on how to diagnose and correct the problem, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).</exception>
+        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">Your ClickOnce deployment is corrupted. For tips on how to diagnose and correct the problem, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).</exception>
         <exception cref="T:System.Deployment.Application.DeploymentDownloadException">The new deployment could not be downloaded from its location on the network.</exception>
         <exception cref="T:System.InvalidOperationException">The application is currently being updated.</exception>
         <altmember cref="M:System.Deployment.Application.ApplicationDeployment.UpdateAsync" />
@@ -1044,17 +1044,17 @@
 ## Remarks
  An application is considered updated when you publish a new version of the application to the location specified by <xref:System.Deployment.Application.ApplicationDeployment.UpdateLocation%2A>, and the version number in the application's deployment manifest is greater than the version number of the application currently installed on the user's computer.
 
- While downloading the update, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will raise the <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged> event handler on the main application thread to inform you of the status of the download. When the asynchronous update finishes or encounters an exception, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] will raise the <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> event on the main application thread. Examine the <xref:System.ComponentModel.AsyncCompletedEventArgs> supplied to this event to determine whether the update succeeded.
+ While downloading the update, ClickOnce will raise the <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged> event handler on the main application thread to inform you of the status of the download. When the asynchronous update finishes or encounters an exception, ClickOnce will raise the <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> event on the main application thread. Examine the <xref:System.ComponentModel.AsyncCompletedEventArgs> supplied to this event to determine whether the update succeeded.
 
- If <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> throws an exception, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] calls <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> and sets the <xref:System.ComponentModel.AsyncCompletedEventArgs.Error%2A> property of <xref:System.ComponentModel.AsyncCompletedEventArgs> to the exception that was thrown.
+ If <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> throws an exception, ClickOnce calls <xref:System.Deployment.Application.ApplicationDeployment.UpdateCompleted> and sets the <xref:System.ComponentModel.AsyncCompletedEventArgs.Error%2A> property of <xref:System.ComponentModel.AsyncCompletedEventArgs> to the exception that was thrown.
 
  <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> will download all files in a deployment not marked as "optional" in the application manifest. You can download optional files on demand by using the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroup%2A> or the <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupAsync%2A> method.
 
- [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] may already be updating the application automatically when you call the <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method; if that happens, calls to this method will throw an <xref:System.InvalidOperationException>.
+ ClickOnce may already be updating the application automatically when you call the <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> method; if that happens, calls to this method will throw an <xref:System.InvalidOperationException>.
 
  If you have updated one or more files in your deployment, but you have not refreshed your application manifest, you will receive an <xref:System.Deployment.Application.InvalidDeploymentException>. Most of the time, rebuilding your application manifest solves this problem. You will also receive this exception if a public-key signature on a deployment manifest or application manifest is invalid or missing.
 
- An update may request a higher level of trust on the local computer than the previous version of the application. If the application uses Trusted Application Deployment, the common language runtime (CLR) trust manager examines the deployment manifest to determine whether it contains a valid trust license. If the deployment manifest does not contain a valid trust license, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] stops the installation and throws a <xref:System.Deployment.Application.TrustNotGrantedException>. <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> will never display a prompt asking the user if they want to grant the application permission to run.
+ An update may request a higher level of trust on the local computer than the previous version of the application. If the application uses Trusted Application Deployment, the common language runtime (CLR) trust manager examines the deployment manifest to determine whether it contains a valid trust license. If the deployment manifest does not contain a valid trust license, ClickOnce stops the installation and throws a <xref:System.Deployment.Application.TrustNotGrantedException>. <xref:System.Deployment.Application.ApplicationDeployment.UpdateAsync%2A> will never display a prompt asking the user if they want to grant the application permission to run.
 
 
 
@@ -1068,7 +1068,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Deployment.Application.TrustNotGrantedException">The local computer did not grant this application the permission level it requested to execute.</exception>
-        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">Your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment is corrupted. For tips on how to diagnose and correct the problem, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).</exception>
+        <exception cref="T:System.Deployment.Application.InvalidDeploymentException">Your ClickOnce deployment is corrupted. For tips on how to diagnose and correct the problem, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).</exception>
         <exception cref="T:System.Deployment.Application.DeploymentDownloadException">The new deployment could not be downloaded from its location on the network.</exception>
         <altmember cref="E:System.Deployment.Application.ApplicationDeployment.UpdateCompleted" />
         <related type="Article" href="/visualstudio/deployment/choosing-a-clickonce-update-strategy">Choosing a ClickOnce Update Strategy</related>
@@ -1122,7 +1122,7 @@
         <ReturnType>System.ComponentModel.AsyncCompletedEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] has finished upgrading the application as the result of a call to <see cref="M:System.Deployment.Application.ApplicationDeployment.UpdateAsync" />.</summary>
+        <summary>Occurs when ClickOnce has finished upgrading the application as the result of a call to <see cref="M:System.Deployment.Application.ApplicationDeployment.UpdateAsync" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
@@ -1200,7 +1200,7 @@
 
 
 ## Examples
- The following code example defines a method that determines whether [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] has updated the application.
+ The following code example defines a method that determines whether ClickOnce has updated the application.
 
  [!code-cpp[ClickOnceAPI#4](~/samples/snippets/cpp/VS_Snippets_Winforms/ClickOnceAPI/cpp/form1.cpp#4)]
  [!code-csharp[ClickOnceAPI#4](~/samples/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Form1.cs#4)]
@@ -1259,7 +1259,7 @@
         <ReturnType>System.Deployment.Application.DeploymentProgressChangedEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] has new status information for an update operation initiated by calling the <see cref="M:System.Deployment.Application.ApplicationDeployment.UpdateAsync" /> method.</summary>
+        <summary>Occurs when ClickOnce has new status information for an update operation initiated by calling the <see cref="M:System.Deployment.Application.ApplicationDeployment.UpdateAsync" /> method.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
diff --git a/xml/System.Deployment.Application/DeploymentDownloadException.xml b/xml/System.Deployment.Application/DeploymentDownloadException.xml
index f1d57227908..5f8e8474e45 100644
--- a/xml/System.Deployment.Application/DeploymentDownloadException.xml
+++ b/xml/System.Deployment.Application/DeploymentDownloadException.xml
@@ -26,15 +26,15 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- A <xref:System.Deployment.Application.DeploymentDownloadException> can indicate that a number of problems occurred when the user tried to download a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application update:
+ A <xref:System.Deployment.Application.DeploymentDownloadException> can indicate that a number of problems occurred when the user tried to download a ClickOnce application update:
 
 -   The client's computer's network connection is down.
 
 -   The Web server, FTP server, or file share hosting the update is unavailable.
 
--   One or more of the files in the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment was not found.
+-   One or more of the files in the ClickOnce deployment was not found.
 
- To obtain detailed error information about an exception, consult the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] error log. For more information, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).
+ To obtain detailed error information about an exception, consult the ClickOnce error log. For more information, see [Troubleshooting ClickOnce Deployments](/visualstudio/deployment/troubleshooting-clickonce-deployments).
 
 
 
diff --git a/xml/System.Deployment.Application/DeploymentProgressState.xml b/xml/System.Deployment.Application/DeploymentProgressState.xml
index d770af89afa..7a46f8030ec 100644
--- a/xml/System.Deployment.Application/DeploymentProgressState.xml
+++ b/xml/System.Deployment.Application/DeploymentProgressState.xml
@@ -19,12 +19,12 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Deployment.Application.DeploymentProgressState> is passed by way of the <xref:System.Deployment.Application.DownloadProgressChangedEventArgs.State%2A> member of <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs>, which is used by the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateProgressChanged>, <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged>, and <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupProgressChanged> events. Use the members of this enumeration to determine what portion of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment has already been downloaded to the local machine.  
+ <xref:System.Deployment.Application.DeploymentProgressState> is passed by way of the <xref:System.Deployment.Application.DownloadProgressChangedEventArgs.State%2A> member of <xref:System.Deployment.Application.DeploymentProgressChangedEventArgs>, which is used by the <xref:System.Deployment.Application.ApplicationDeployment.CheckForUpdateProgressChanged>, <xref:System.Deployment.Application.ApplicationDeployment.UpdateProgressChanged>, and <xref:System.Deployment.Application.ApplicationDeployment.DownloadFileGroupProgressChanged> events. Use the members of this enumeration to determine what portion of the ClickOnce deployment has already been downloaded to the local machine.  
   
    
   
 ## Examples  
- The following code example installs the latest [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application update asynchronously.  
+ The following code example installs the latest ClickOnce application update asynchronously.  
   
  [!code-cpp[ClickOnceAPI#1](~/samples/snippets/cpp/VS_Snippets_Winforms/ClickOnceAPI/cpp/form1.cpp#1)]
  [!code-csharp[ClickOnceAPI#1](~/samples/snippets/csharp/VS_Snippets_Winforms/ClickOnceAPI/CS/Form1.cs#1)]
@@ -54,7 +54,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] is downloading the DLLs and data files that comprised the application.</summary>
+        <summary>ClickOnce is downloading the DLLs and data files that comprised the application.</summary>
       </Docs>
     </Member>
     <Member MemberName="DownloadingApplicationInformation">
@@ -75,7 +75,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] is downloading the application manifest.</summary>
+        <summary>ClickOnce is downloading the application manifest.</summary>
       </Docs>
     </Member>
     <Member MemberName="DownloadingDeploymentInformation">
@@ -96,7 +96,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] is downloading the deployment manifest.</summary>
+        <summary>ClickOnce is downloading the deployment manifest.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Deployment.Application/DeploymentServiceCom.xml b/xml/System.Deployment.Application/DeploymentServiceCom.xml
index 2fe646b9811..dc1f6f0ade3 100644
--- a/xml/System.Deployment.Application/DeploymentServiceCom.xml
+++ b/xml/System.Deployment.Application/DeploymentServiceCom.xml
@@ -189,7 +189,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Removes all online-only [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications that are installed on a computer.</summary>
+        <summary>Removes all online-only ClickOnce applications that are installed on a computer.</summary>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Deployment.Application/GetManifestCompletedEventArgs.xml b/xml/System.Deployment.Application/GetManifestCompletedEventArgs.xml
index 45aa323b940..94847cf01fe 100644
--- a/xml/System.Deployment.Application/GetManifestCompletedEventArgs.xml
+++ b/xml/System.Deployment.Application/GetManifestCompletedEventArgs.xml
@@ -20,12 +20,12 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Use <xref:System.Deployment.Application.GetManifestCompletedEventArgs> to obtain information about a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application after the deployment and application manifests have been downloaded.
+ Use <xref:System.Deployment.Application.GetManifestCompletedEventArgs> to obtain information about a ClickOnce application after the deployment and application manifests have been downloaded.
 
 
 
 ## Examples
- The following code example shows how to use <xref:System.Deployment.Application.InPlaceHostingManager> to install a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application programmatically on a client machine.
+ The following code example shows how to use <xref:System.Deployment.Application.InPlaceHostingManager> to install a ClickOnce application programmatically on a client machine.
 
  [!code-csharp[System.Deployment.Application.InPlaceHostingManager#1](~/samples/snippets/csharp/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/CS/Form1.cs#1)]
  [!code-vb[System.Deployment.Application.InPlaceHostingManager#1](~/samples/snippets/visualbasic/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/VB/Form1.vb#1)]
@@ -51,7 +51,7 @@
         <ReturnType>System.ActivationContext</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the context for the current [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
+        <summary>Gets the context for the current ClickOnce application.</summary>
         <value>An <see cref="T:System.ActivationContext" /> object representing the context for the current application.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -73,7 +73,7 @@
         <ReturnType>System.ApplicationIdentity</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a description of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
+        <summary>Gets a description of the ClickOnce application.</summary>
         <value>An <see cref="T:System.ApplicationIdentity" /> object.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -95,7 +95,7 @@
         <ReturnType>System.Xml.XmlReader</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application manifest for this deployment.</summary>
+        <summary>Gets the ClickOnce application manifest for this deployment.</summary>
         <value>An <see cref="T:System.Xml.XmlReader" /> representing the application manifest.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[
@@ -132,7 +132,7 @@
         <ReturnType>System.Xml.XmlReader</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment manifest for this deployment.</summary>
+        <summary>Gets the ClickOnce deployment manifest for this deployment.</summary>
         <value>An <see cref="T:System.Xml.XmlReader" /> representing the deployment manifest.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -154,7 +154,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether this [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is cached.</summary>
+        <summary>Gets a value indicating whether this ClickOnce application is cached.</summary>
         <value>
           <see langword="true" /> if the application is cached; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -177,8 +177,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the location of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] error log.</summary>
-        <value>A <see cref="T:System.String" /> containing the location of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] error log.</value>
+        <summary>Gets the location of the ClickOnce error log.</summary>
+        <value>A <see cref="T:System.String" /> containing the location of the ClickOnce error log.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -199,8 +199,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the name of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
-        <value>A <see cref="T:System.String" /> representing the product name of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, as stored in the assembly metadata of the application's main executable file.</value>
+        <summary>Gets the name of the ClickOnce application.</summary>
+        <value>A <see cref="T:System.String" /> representing the product name of the ClickOnce application, as stored in the assembly metadata of the application's main executable file.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -243,7 +243,7 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the location of a Web page users can visit to obtain product support for the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
+        <summary>Gets the location of a Web page users can visit to obtain product support for the ClickOnce application.</summary>
         <value>A <see cref="T:System.Uri" /> containing the value found in the <c>supportUrl</c> attribute of the deployment manifest's <c>&lt;description&gt;</c> tag. For more information, see [ClickOnce Deployment Manifest](/visualstudio/deployment/clickonce-deployment-manifest).</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -265,7 +265,7 @@
         <ReturnType>System.Version</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the version of the update for the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application.</summary>
+        <summary>Gets the version of the update for the ClickOnce application.</summary>
         <value>A <see cref="T:System.Version" /> representing the version number contained within the downloaded manifest.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Deployment.Application/InPlaceHostingManager.xml b/xml/System.Deployment.Application/InPlaceHostingManager.xml
index bfca5418bf6..4775fc6672f 100644
--- a/xml/System.Deployment.Application/InPlaceHostingManager.xml
+++ b/xml/System.Deployment.Application/InPlaceHostingManager.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can use <xref:System.Deployment.Application.InPlaceHostingManager> to write programs that install [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications programmatically. For example, you can use this class in a controlled system management software (SMS) environment or in situations where you need a complex installation that performs a number of pre-installation or post-installation operations on the local computer. Generally, you will want to use the members of this class in a specific order:  
+ You can use <xref:System.Deployment.Application.InPlaceHostingManager> to write programs that install ClickOnce applications programmatically. For example, you can use this class in a controlled system management software (SMS) environment or in situations where you need a complex installation that performs a number of pre-installation or post-installation operations on the local computer. Generally, you will want to use the members of this class in a specific order:  
   
 1.  Create a new instance of <xref:System.Deployment.Application.InPlaceHostingManager>.  
   
@@ -36,9 +36,9 @@
   
 -   If you call any of these parameters out of order, they will throw an exception.  
   
- <xref:System.Deployment.Application.InPlaceHostingManager> can install a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, but cannot execute it. Some methods in this class, such as <xref:System.Deployment.Application.InPlaceHostingManager.Execute%2A>, are reserved for use when downloading a Windows Presentation Foundation-based application that runs inside a Web browser.  
+ <xref:System.Deployment.Application.InPlaceHostingManager> can install a ClickOnce application, but cannot execute it. Some methods in this class, such as <xref:System.Deployment.Application.InPlaceHostingManager.Execute%2A>, are reserved for use when downloading a Windows Presentation Foundation-based application that runs inside a Web browser.  
   
- To use <xref:System.Deployment.Application.InPlaceHostingManager> to download and install applications, you must make sure that the certificate for signing the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications you plan to install is already installed on client computers as a trusted publisher. For more information on trusted publishers, see [Trusted Application Deployment Overview](/visualstudio/deployment/trusted-application-deployment-overview).  
+ To use <xref:System.Deployment.Application.InPlaceHostingManager> to download and install applications, you must make sure that the certificate for signing the ClickOnce applications you plan to install is already installed on client computers as a trusted publisher. For more information on trusted publishers, see [Trusted Application Deployment Overview](/visualstudio/deployment/trusted-application-deployment-overview).  
   
 > [!NOTE]
 >  There is currently a product limitation that prevents <xref:System.Deployment.Application.InPlaceHostingManager> from working correctly when you debug your code using Visual Studio. If you debug your application in Visual Studio by using the F5 key, the sample will throw mysterious exceptions when you call <xref:System.Deployment.Application.InPlaceHostingManager.DownloadApplicationAsync%2A>. To debug using Visual Studio, start the application without debugging, and then attach the debugger. Alternatively, you can use another debugger, such as WinDbg.  
@@ -46,7 +46,7 @@
    
   
 ## Examples  
- The following code example shows how to use <xref:System.Deployment.Application.InPlaceHostingManager> to install a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application programmatically on a client computer.  
+ The following code example shows how to use <xref:System.Deployment.Application.InPlaceHostingManager> to install a ClickOnce application programmatically on a client computer.  
   
  [!code-csharp[System.Deployment.Application.InPlaceHostingManager#1](~/samples/snippets/csharp/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/CS/Form1.cs#1)]
  [!code-vb[System.Deployment.Application.InPlaceHostingManager#1](~/samples/snippets/visualbasic/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/VB/Form1.vb#1)]  
@@ -81,13 +81,13 @@
         <Parameter Name="deploymentManifest" Type="System.Uri" />
       </Parameters>
       <Docs>
-        <param name="deploymentManifest">A Uniform Resource Identifier (<see cref="T:System.Uri" />) to a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application's deployment manifest.</param>
+        <param name="deploymentManifest">A Uniform Resource Identifier (<see cref="T:System.Uri" />) to a ClickOnce application's deployment manifest.</param>
         <summary>Creates a new instance of <see cref="T:System.Deployment.Application.InPlaceHostingManager" /> to download and install the specified browser-hosted application.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This constructor is used when you want to download a Windows Presentation Foundation-based application that is hosted in a Web browser. To download Windows Forms-based applications that are deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)], use the <xref:System.Deployment.Application.InPlaceHostingManager.%23ctor%2A> constructor with the `launchInHostProcess` parameter set to `false`.  
+ This constructor is used when you want to download a Windows Presentation Foundation-based application that is hosted in a Web browser. To download Windows Forms-based applications that are deployed using ClickOnce, use the <xref:System.Deployment.Application.InPlaceHostingManager.%23ctor%2A> constructor with the `launchInHostProcess` parameter set to `false`.  
   
  ]]></format>
         </remarks>
@@ -95,7 +95,7 @@
           <see cref="T:System.Deployment.Application.InPlaceHostingManager" /> can be used only in Windows XP or in later versions of the Windows operating system.</exception>
         <exception cref="T:System.ArgumentNullException">Cannot pass <see langword="null" /> for the <paramref name="deploymentManifest" /> argument.</exception>
         <exception cref="T:System.ArgumentException">
-          <paramref name="deploymentManifest" /> uses a URI scheme that is not supported by [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)].</exception>
+          <paramref name="deploymentManifest" /> uses a URI scheme that is not supported by ClickOnce.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -123,7 +123,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to create an instance of <xref:System.Deployment.Application.InPlaceHostingManager> that allows you to download Windows Forms-based applications deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)].  
+ The following code example demonstrates how to create an instance of <xref:System.Deployment.Application.InPlaceHostingManager> that allows you to download Windows Forms-based applications deployed using ClickOnce.  
   
  [!code-csharp[System.Deployment.Application.InPlaceHostingManager#2](~/samples/snippets/csharp/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/CS/Form1.cs#2)]
  [!code-vb[System.Deployment.Application.InPlaceHostingManager#2](~/samples/snippets/visualbasic/VS_Snippets_Winforms/System.Deployment.Application.InPlaceHostingManager/VB/Form1.vb#2)]  
@@ -134,7 +134,7 @@
           <see cref="T:System.Deployment.Application.InPlaceHostingManager" /> can be used only in Windows XP or in later versions of the Windows operating system.</exception>
         <exception cref="T:System.ArgumentNullException">Cannot pass <see langword="null" /> for the <paramref name="deploymentManifest" /> argument.</exception>
         <exception cref="T:System.ArgumentException">
-          <paramref name="deploymentManifest" /> uses a URI scheme that is not supported by [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)].</exception>
+          <paramref name="deploymentManifest" /> uses a URI scheme that is not supported by ClickOnce.</exception>
       </Docs>
     </Member>
     <MemberGroup MemberName="AssertApplicationRequirements">
@@ -164,7 +164,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Determines whether the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application has the appropriate permissions and platform dependencies to run on the local computer.</summary>
+        <summary>Determines whether the ClickOnce application has the appropriate permissions and platform dependencies to run on the local computer.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -205,12 +205,12 @@
       </Parameters>
       <Docs>
         <param name="grantApplicationTrust">If <see langword="true" />, the application will attempt to elevate its permissions to the required level.</param>
-        <summary>Determines whether the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application has the appropriate permissions and platform dependencies to run on the local computer.</summary>
+        <summary>Determines whether the ClickOnce application has the appropriate permissions and platform dependencies to run on the local computer.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If `grantApplicationTrust` is `true`, <xref:System.Deployment.Application.InPlaceHostingManager> will grant the application elevated permissions if it requires them. This is only possible if <xref:System.Deployment.Application.InPlaceHostingManager> is able to grant those permissions. For example, if a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application is being installed as part of a larger package and the installer has been granted full trust, <xref:System.Deployment.Application.InPlaceHostingManager> will be able to grant the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application full trust. If `grantApplicationTrust` is `false`, the application will not be granted any permissions.  
+ If `grantApplicationTrust` is `true`, <xref:System.Deployment.Application.InPlaceHostingManager> will grant the application elevated permissions if it requires them. This is only possible if <xref:System.Deployment.Application.InPlaceHostingManager> is able to grant those permissions. For example, if a ClickOnce application is being installed as part of a larger package and the installer has been granted full trust, <xref:System.Deployment.Application.InPlaceHostingManager> will be able to grant the ClickOnce application full trust. If `grantApplicationTrust` is `false`, the application will not be granted any permissions.  
   
  ]]></format>
         </remarks>
@@ -405,7 +405,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Launches the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, if and only if it is a Windows Presentation Foundation-based application running in a Web browser.</summary>
+        <summary>Launches the ClickOnce application, if and only if it is a Windows Presentation Foundation-based application running in a Web browser.</summary>
         <returns>An <see cref="T:System.Runtime.Remoting.ObjectHandle" /> corresponding to the launched application.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -435,7 +435,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Downloads the deployment manifest of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application in the background, and raises an event when the operation has either completed or encountered an error.</summary>
+        <summary>Downloads the deployment manifest of the ClickOnce application in the background, and raises an event when the operation has either completed or encountered an error.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -549,15 +549,15 @@
         <Parameter Name="subscriptionId" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="subscriptionId">A string that contains a subscription identifier, which indicates the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application to remove.</param>
-        <summary>Removes a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application that includes the &lt;customUX&gt; element.</summary>
+        <param name="subscriptionId">A string that contains a subscription identifier, which indicates the ClickOnce application to remove.</param>
+        <summary>Removes a ClickOnce application that includes the &lt;customUX&gt; element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method uninstalls a previously installed [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application that uses the `<customUX>` element in the [&lt;entryPoint&gt; Element](/visualstudio/deployment/entrypoint-element-clickonce-application).  
+ This method uninstalls a previously installed ClickOnce application that uses the `<customUX>` element in the [&lt;entryPoint&gt; Element](/visualstudio/deployment/entrypoint-element-clickonce-application).  
   
- Custom installers that do not create an Add or Remove Programs entry for the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application must store the subscription identifier found in the <xref:System.Deployment.Application.GetManifestCompletedEventArgs.SubscriptionIdentity%2A> property during installation.  
+ Custom installers that do not create an Add or Remove Programs entry for the ClickOnce application must store the subscription identifier found in the <xref:System.Deployment.Application.GetManifestCompletedEventArgs.SubscriptionIdentity%2A> property during installation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Deployment.Application/InvalidDeploymentException.xml b/xml/System.Deployment.Application/InvalidDeploymentException.xml
index 9282f5d26f0..029f490bd5d 100644
--- a/xml/System.Deployment.Application/InvalidDeploymentException.xml
+++ b/xml/System.Deployment.Application/InvalidDeploymentException.xml
@@ -26,9 +26,9 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- <xref:System.Deployment.Application.InvalidDeploymentException> indicates the existence of a corrupt deployment or application manifest in a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application. The error might occur because the manifests are poorly formed, have unrecognized elements for their schemas, or have mismatched digital signatures.
+ <xref:System.Deployment.Application.InvalidDeploymentException> indicates the existence of a corrupt deployment or application manifest in a ClickOnce application. The error might occur because the manifests are poorly formed, have unrecognized elements for their schemas, or have mismatched digital signatures.
 
- You are more likely to have corruption  if you manually edit the deployment or application manifest files with a text editor. You can usually correct this problem by regenerating your [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment, which will create new deployment and application manifests. For more detailed debugging steps, see the following links.
+ You are more likely to have corruption  if you manually edit the deployment or application manifest files with a text editor. You can usually correct this problem by regenerating your ClickOnce deployment, which will create new deployment and application manifests. For more detailed debugging steps, see the following links.
 
  ]]></format>
     </remarks>
diff --git a/xml/System.Deployment.Application/TrustNotGrantedException.xml b/xml/System.Deployment.Application/TrustNotGrantedException.xml
index c2a327d102a..4acd72609e1 100644
--- a/xml/System.Deployment.Application/TrustNotGrantedException.xml
+++ b/xml/System.Deployment.Application/TrustNotGrantedException.xml
@@ -26,17 +26,17 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications are given a level of trust on client computers that prevents them from engaging in potentially malicious activity, such as deleting data from the hard drive or accessing the network. A [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application can use either permission elevation or Trusted Application Deployment to request a higher level of trust:  
+ By default, ClickOnce applications are given a level of trust on client computers that prevents them from engaging in potentially malicious activity, such as deleting data from the hard drive or accessing the network. A ClickOnce application can use either permission elevation or Trusted Application Deployment to request a higher level of trust:  
   
 -   Permission elevation asks the user to grant the application a higher level of security.  
   
--   Trusted Application Deployment matches the digital signature of the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application against a list of trusted publishers on the local machine.  
+-   Trusted Application Deployment matches the digital signature of the ClickOnce application against a list of trusted publishers on the local machine.  
   
  <xref:System.Deployment.Application.TrustNotGrantedException> will be thrown if:  
   
 -   The application uses permission elevation and the user denies the request for elevated trust; or  
   
- The application uses Trusted Application Deployment and the digital certificate used to sign the application is not listed as a trusted publisher on the local machine. If you have deployed an update to an application, and the update uses more permissions than the previous version, and [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] throws a <xref:System.Deployment.Application.TrustNotGrantedException>, the new version will not install.  
+ The application uses Trusted Application Deployment and the digital certificate used to sign the application is not listed as a trusted publisher on the local machine. If you have deployed an update to an application, and the update uses more permissions than the previous version, and ClickOnce throws a <xref:System.Deployment.Application.TrustNotGrantedException>, the new version will not install.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index e6be4b94483..dbc1cd9de44 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -213,7 +213,7 @@
   
  <xref:System.Windows.Forms.Application.ProductVersion%2A> first looks to see if the assembly containing the main executable has the `AssemblyInformationalVersion` attribute on it. If this attribute exists, it is used for both <xref:System.Windows.Forms.Application.ProductVersion%2A> and <xref:System.Windows.Forms.Application.CommonAppDataPath%2A>. If this attribute does not exist, both properties use the version of the executable file instead.  
   
- The path will be different depending on whether the Windows Forms application is deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
+ The path will be different depending on whether the Windows Forms application is deployed using ClickOnce. ClickOnce applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
   
  ]]></format>
         </remarks>
@@ -539,7 +539,7 @@
         <summary>Gets the path for the executable file that started the application, including the executable name.</summary>
         <value>The path and executable name for the executable file that started the application.  
   
- This path will be different depending on whether the Windows Forms application is deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).</value>
+ This path will be different depending on whether the Windows Forms application is deployed using ClickOnce. ClickOnce applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -856,7 +856,7 @@
   
  *Base Path*\\<xref:System.Windows.Forms.Application.CompanyName%2A>\\<xref:System.Windows.Forms.Application.ProductName%2A>\\<xref:System.Windows.Forms.Application.ProductVersion%2A>   
   
- A typical base path is C:\Documents and Settings\\*username*\Local Settings\Application Data. This path will be different, however, if the Windows Forms application is deployed by using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] creates its own application data directory that is isolated from all other applications. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
+ A typical base path is C:\Documents and Settings\\*username*\Local Settings\Application Data. This path will be different, however, if the Windows Forms application is deployed by using ClickOnce. ClickOnce creates its own application data directory that is isolated from all other applications. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
   
    
   
@@ -1294,9 +1294,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common reason for calling `Restart` is to start a new version of the application that you have downloaded through [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] using the `Update` or `UpdateAsync` method.  
+ The most common reason for calling `Restart` is to start a new version of the application that you have downloaded through ClickOnce using the `Update` or `UpdateAsync` method.  
   
- Applications are restarted in the context in which they were initially run. If your application was started using a URL pointing directly to the application's main executable file, it will be restarted using the same URL. If your application is a [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] application, it will be restarted using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)].  
+ Applications are restarted in the context in which they were initially run. If your application was started using a URL pointing directly to the application's main executable file, it will be restarted using the same URL. If your application is a ClickOnce application, it will be restarted using ClickOnce.  
   
  If your application was originally supplied command-line options when it first executed, <xref:System.Windows.Forms.Application.Restart%2A> will launch the application again with the same options.  
   
@@ -1791,7 +1791,7 @@ The high DPI mode is set once per process. For more information about setting th
         <summary>Gets the path for the executable file that started the application, not including the executable name.</summary>
         <value>The path for the executable file that started the application.  
   
- This path will be different depending on whether the Windows Forms application is deployed using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).</value>
+ This path will be different depending on whether the Windows Forms application is deployed using ClickOnce. ClickOnce applications are stored in a per-user application cache in the C:\Documents and Settings\\*username* directory. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1962,7 +1962,7 @@ The high DPI mode is set once per process. For more information about setting th
   
  Data stored in this path is part of user profile that is enabled for roaming. A roaming user works on more than one computer in a network. The user profile for a roaming user is kept on a server on the network and is loaded onto a system when the user logs on. For a user profile to be considered for roaming, the operating system must support roaming profiles and it must be enabled.  
   
- A typical base path is C:\Documents and Settings\\*username*\Application Data. This path will be different, however, if the Windows Forms application is deployed by using [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)]. [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] creates its own application data directory that is isolated from all other applications. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
+ A typical base path is C:\Documents and Settings\\*username*\Application Data. This path will be different, however, if the Windows Forms application is deployed by using ClickOnce. ClickOnce creates its own application data directory that is isolated from all other applications. For more information, see [Accessing Local and Remote Data in ClickOnce Applications](/visualstudio/deployment/accessing-local-and-remote-data-in-clickonce-applications).  
   
    
   
diff --git a/xml/System.Windows.Forms/FileDialog.xml b/xml/System.Windows.Forms/FileDialog.xml
index 3b721fb7f98..2be4c196fa6 100644
--- a/xml/System.Windows.Forms/FileDialog.xml
+++ b/xml/System.Windows.Forms/FileDialog.xml
@@ -1108,7 +1108,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Sometimes users must open and save files that use multiple file name extensions. For example, the application manifest files used by the [!INCLUDE[ndptecclick](~/includes/ndptecclick-md.md)] deployment technology end in the complex file name extension ".exe.manifest". Setting this property to `true` enables you to set the <xref:System.Windows.Forms.FileDialog.Filter%2A> property to a multi-dotted extension.  
+ Sometimes users must open and save files that use multiple file name extensions. For example, the application manifest files used by the ClickOnce deployment technology end in the complex file name extension ".exe.manifest". Setting this property to `true` enables you to set the <xref:System.Windows.Forms.FileDialog.Filter%2A> property to a multi-dotted extension.  
   
  If <xref:System.Windows.Forms.FileDialog.SupportMultiDottedExtensions%2A> is `false`, and you assign a multi-dotted extension to <xref:System.Windows.Forms.FileDialog.Filter%2A>, derived controls such as <xref:System.Windows.Forms.SaveFileDialog> will only use the last extension in the string. For example, ".manifest" will be used instead of ".exe.manifest".  
   

From 0b2ee76d33ebaaa2dc5d6c7decf09ae8fdc7f9b3 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:04:30 -0800
Subject: [PATCH 018/236] ndptecgdi

---
 .../InstalledFontCollection.xml               |  2 +-
 xml/System.Drawing/Bitmap.xml                 | 12 ++++----
 xml/System.Drawing/Font.xml                   | 30 +++++++++----------
 xml/System.Drawing/Graphics.xml               | 22 +++++++-------
 xml/System.Drawing/Image.xml                  | 10 +++----
 xml/System.Drawing/Region.xml                 |  4 +--
 xml/System.Windows.Forms/Application.xml      |  6 ++--
 xml/System.Windows.Forms/ButtonBase.xml       |  4 +--
 xml/System.Windows.Forms/CheckedListBox.xml   |  4 +--
 xml/System.Windows.Forms/GroupBox.xml         |  4 +--
 xml/System.Windows.Forms/Label.xml            |  4 +--
 xml/System.Windows.Forms/LinkLabel.xml        |  4 +--
 xml/System.Windows.Forms/PropertyGrid.xml     |  4 +--
 13 files changed, 55 insertions(+), 55 deletions(-)

diff --git a/xml/System.Drawing.Text/InstalledFontCollection.xml b/xml/System.Drawing.Text/InstalledFontCollection.xml
index 1713c0787dc..fae94a6fee1 100644
--- a/xml/System.Drawing.Text/InstalledFontCollection.xml
+++ b/xml/System.Drawing.Text/InstalledFontCollection.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  The <xref:System.Drawing.Text.InstalledFontCollection> allows you to get a list of fonts families that are installed on the computer running the application with its <xref:System.Drawing.Text.FontCollection.Families%2A> property. For additional information on fonts and text, including example code, see [Using Fonts and Text](/dotnet/framework/winforms/advanced/using-fonts-and-text).  
   
- Do not use the <xref:System.Drawing.Text.InstalledFontCollection> class to install a font to Windows. Instead use the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `AddFontResource` function. An <xref:System.Drawing.Text.InstalledFontCollection> object sees only fonts that are installed in Windows before the object is created.  
+ Do not use the <xref:System.Drawing.Text.InstalledFontCollection> class to install a font to Windows. Instead use the GDI `AddFontResource` function. An <xref:System.Drawing.Text.InstalledFontCollection> object sees only fonts that are installed in Windows before the object is created.  
   
    
   
diff --git a/xml/System.Drawing/Bitmap.xml b/xml/System.Drawing/Bitmap.xml
index 7ec087f9421..745de7d6cb3 100644
--- a/xml/System.Drawing/Bitmap.xml
+++ b/xml/System.Drawing/Bitmap.xml
@@ -891,13 +891,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Creates a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object from this <see cref="T:System.Drawing.Bitmap" />.</summary>
-        <returns>A handle to the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object that this method creates.</returns>
+        <summary>Creates a GDI bitmap object from this <see cref="T:System.Drawing.Bitmap" />.</summary>
+        <returns>A handle to the GDI bitmap object that this method creates.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You are responsible for calling the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `DeleteObject` method to free the memory used by the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object. For more information about GDI bitmaps, see [Bitmaps](https://go.microsoft.com/fwlink/?LinkId=205685) in the Windows GDI documentation.  
+ You are responsible for calling the GDI `DeleteObject` method to free the memory used by the GDI bitmap object. For more information about GDI bitmaps, see [Bitmaps](https://go.microsoft.com/fwlink/?LinkId=205685) in the Windows GDI documentation.  
   
    
   
@@ -950,13 +950,13 @@
       </Parameters>
       <Docs>
         <param name="background">A <see cref="T:System.Drawing.Color" /> structure that specifies the background color. This parameter is ignored if the bitmap is totally opaque.</param>
-        <summary>Creates a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object from this <see cref="T:System.Drawing.Bitmap" />.</summary>
-        <returns>A handle to the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object that this method creates.</returns>
+        <summary>Creates a GDI bitmap object from this <see cref="T:System.Drawing.Bitmap" />.</summary>
+        <returns>A handle to the GDI bitmap object that this method creates.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You are responsible for calling the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `DeleteObject` method to free the memory used by the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap object. For more information about GDI bitmaps, see [Bitmaps](https://go.microsoft.com/fwlink/?LinkId=205685) in the Windows GDI documentation.  
+ You are responsible for calling the GDI `DeleteObject` method to free the memory used by the GDI bitmap object. For more information about GDI bitmaps, see [Bitmaps](https://go.microsoft.com/fwlink/?LinkId=205685) in the Windows GDI documentation.  
   
    
   
diff --git a/xml/System.Drawing/Font.xml b/xml/System.Drawing/Font.xml
index d8a6ab2ff67..fb22f4ba33e 100644
--- a/xml/System.Drawing/Font.xml
+++ b/xml/System.Drawing/Font.xml
@@ -562,7 +562,7 @@
         <param name="unit">The <see cref="T:System.Drawing.GraphicsUnit" /> of the new font.</param>
         <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a  
   
- [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] character set to use for the new font.</param>
+ GDI character set to use for the new font.</param>
         <summary>Initializes a new <see cref="T:System.Drawing.Font" /> using a specified size, style, unit, and character set.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -612,7 +612,7 @@
         <param name="emSize">The em-size of the new font in the units specified by the <paramref name="unit" /> parameter.</param>
         <param name="style">The <see cref="T:System.Drawing.FontStyle" /> of the new font.</param>
         <param name="unit">The <see cref="T:System.Drawing.GraphicsUnit" /> of the new font.</param>
-        <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] character set to use for this font.</param>
+        <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a GDI character set to use for this font.</param>
         <summary>Initializes a new <see cref="T:System.Drawing.Font" /> using a specified size, style, unit, and character set.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -664,8 +664,8 @@
         <param name="unit">The <see cref="T:System.Drawing.GraphicsUnit" /> of the new font.</param>
         <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a  
   
- [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] character set to use for this font.</param>
-        <param name="gdiVerticalFont">A Boolean value indicating whether the new font is derived from a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] vertical font.</param>
+ GDI character set to use for this font.</param>
+        <param name="gdiVerticalFont">A Boolean value indicating whether the new font is derived from a GDI vertical font.</param>
         <summary>Initializes a new <see cref="T:System.Drawing.Font" /> using a specified size, style, unit, and character set.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -716,8 +716,8 @@
         <param name="emSize">The em-size of the new font in the units specified by the <paramref name="unit" /> parameter.</param>
         <param name="style">The <see cref="T:System.Drawing.FontStyle" /> of the new font.</param>
         <param name="unit">The <see cref="T:System.Drawing.GraphicsUnit" /> of the new font.</param>
-        <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] character set to use for this font.</param>
-        <param name="gdiVerticalFont">A Boolean value indicating whether the new <see cref="T:System.Drawing.Font" /> is derived from a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] vertical font.</param>
+        <param name="gdiCharSet">A <see cref="T:System.Byte" /> that specifies a GDI character set to use for this font.</param>
+        <param name="gdiVerticalFont">A Boolean value indicating whether the new <see cref="T:System.Drawing.Font" /> is derived from a GDI vertical font.</param>
         <summary>Initializes a new <see cref="T:System.Drawing.Font" /> using the specified size, style, unit, and character set.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1072,7 +1072,7 @@
         <Parameter Name="hfont" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hfont">A Windows handle to a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] font.</param>
+        <param name="hfont">A Windows handle to a GDI font.</param>
         <summary>Creates a <see cref="T:System.Drawing.Font" /> from the specified Windows handle.</summary>
         <returns>The <see cref="T:System.Drawing.Font" /> this method creates.</returns>
         <remarks>
@@ -1081,7 +1081,7 @@
 ## Examples  
  The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The code performs the following actions:  
   
--   Gets a handle to a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] font.  
+-   Gets a handle to a GDI font.  
   
 -   Creates a <xref:System.Drawing.Font> from that handle.  
   
@@ -1135,14 +1135,14 @@
         <Parameter Name="lf" Type="System.Object" />
       </Parameters>
       <Docs>
-        <param name="lf">An <see cref="T:System.Object" /> that represents the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] <see langword="LOGFONT" /> structure from which to create the <see cref="T:System.Drawing.Font" />.</param>
+        <param name="lf">An <see cref="T:System.Object" /> that represents the GDI <see langword="LOGFONT" /> structure from which to create the <see cref="T:System.Drawing.Font" />.</param>
         <summary>Creates a <see cref="T:System.Drawing.Font" /> from the specified GDI logical font (<c>LOGFONT</c>) structure.</summary>
         <returns>The <see cref="T:System.Drawing.Font" /> that this method creates.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `LOGFONT`, or logical font, is a structure that contains 14 properties that describe a particular font. 
+ A GDI `LOGFONT`, or logical font, is a structure that contains 14 properties that describe a particular font. 
   
  ]]></format>
         </remarks>
@@ -1178,7 +1178,7 @@
         <Parameter Name="hdc" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="lf">An <see cref="T:System.Object" /> that represents the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] <see langword="LOGFONT" /> structure from which to create the <see cref="T:System.Drawing.Font" />.</param>
+        <param name="lf">An <see cref="T:System.Object" /> that represents the GDI <see langword="LOGFONT" /> structure from which to create the <see cref="T:System.Drawing.Font" />.</param>
         <param name="hdc">A handle to a device context that contains additional information about the <paramref name="lf" /> structure.</param>
         <summary>Creates a <see cref="T:System.Drawing.Font" /> from the specified GDI logical font (<c>LOGFONT</c>) structure.</summary>
         <returns>The <see cref="T:System.Drawing.Font" /> that this method creates.</returns>
@@ -1186,7 +1186,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `LOGFONT`, or logical font, is a structure that contains 14 properties that describe a particular font. 
+ A GDI `LOGFONT`, or logical font, is a structure that contains 14 properties that describe a particular font. 
   
  ]]></format>
         </remarks>
@@ -1230,7 +1230,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets a byte value that specifies the GDI character set that this <see cref="T:System.Drawing.Font" /> uses.</summary>
-        <value>A byte value that specifies the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] character set that this <see cref="T:System.Drawing.Font" /> uses. The default is 1.</value>
+        <value>A byte value that specifies the GDI character set that this <see cref="T:System.Drawing.Font" /> uses. The default is 1.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1302,7 +1302,7 @@
       <Docs>
         <summary>Gets a Boolean value that indicates whether this <see cref="T:System.Drawing.Font" /> is derived from a GDI vertical font.</summary>
         <value>
-          <see langword="true" /> if this <see cref="T:System.Drawing.Font" /> is derived from a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] vertical font; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if this <see cref="T:System.Drawing.Font" /> is derived from a GDI vertical font; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2092,7 +2092,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When using this method, you must dispose of the resulting `Hfont` using the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `DeleteObject` method to ensure the resources are released.  
+ When using this method, you must dispose of the resulting `Hfont` using the GDI `DeleteObject` method to ensure the resources are released.  
   
    
   
diff --git a/xml/System.Drawing/Graphics.xml b/xml/System.Drawing/Graphics.xml
index 9656d0c64d5..c6b2202e566 100644
--- a/xml/System.Drawing/Graphics.xml
+++ b/xml/System.Drawing/Graphics.xml
@@ -12433,7 +12433,7 @@
 ## Examples  
  The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The code performs the following actions:  
   
--   Defines interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attributes for the Windows DLL file gdi32.dll, which contains the necessary [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] functions.  
+-   Defines interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attributes for the Windows DLL file gdi32.dll, which contains the necessary GDI functions.  
   
 -   Defines the `SelectPalette` and `RealizePalette` functions in that DLL as external.  
   
@@ -12504,16 +12504,16 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The device context is a Windows structure based on [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output. This method returns that device context with the exception of a font. Because a font is not selected, calls to the <xref:System.Drawing.Font.FromHdc%2A> method using a handle returned from the <xref:System.Drawing.Graphics.GetHdc%2A> method will fail.  
+ The device context is a Windows structure based on GDI that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output. This method returns that device context with the exception of a font. Because a font is not selected, calls to the <xref:System.Drawing.Font.FromHdc%2A> method using a handle returned from the <xref:System.Drawing.Graphics.GetHdc%2A> method will fail.  
   
- Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make only calls to [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
+ Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make only calls to GDI functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
   
    
   
 ## Examples  
- The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
+ The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
   
--   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] function.  
+-   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired GDI function.  
   
 -   Defines the <xref:System.Drawing.Rectangle> function in that DLL as external.  
   
@@ -12523,7 +12523,7 @@
   
 -   Defines an internal pointer type variable `hdc` and sets its value to the handle to the device context of the form.  
   
--   Draws a rectangle to the screen using the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] <xref:System.Drawing.Rectangle> function.  
+-   Draws a rectangle to the screen using the GDI <xref:System.Drawing.Rectangle> function.  
   
 -   Releases the device context represented by the `hdc` parameter.  
   
@@ -14381,16 +14381,16 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The device context is a Windows structure based on [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output.  
+ The device context is a Windows structure based on GDI that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output.  
   
- Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make calls only to [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
+ Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make calls only to GDI functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
   
    
   
 ## Examples  
- The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
+ The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
   
--   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] function, and it defines the <xref:System.Drawing.Rectangle> function in that DLL as external.  
+-   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired GDI function, and it defines the <xref:System.Drawing.Rectangle> function in that DLL as external.  
   
 -   Creates a red pen.  
   
@@ -14398,7 +14398,7 @@
   
 -   Defines an internal pointer type variable `hdc` and sets its value to the handle to the device context of the form.  
   
--   Draws a rectangle to the screen using the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] <xref:System.Drawing.Rectangle> function.  
+-   Draws a rectangle to the screen using the GDI <xref:System.Drawing.Rectangle> function.  
   
 -   Releases the device context represented by the `hdc` parameter.  
   
diff --git a/xml/System.Drawing/Image.xml b/xml/System.Drawing/Image.xml
index e2832dfdd9f..945bcf7c53d 100644
--- a/xml/System.Drawing/Image.xml
+++ b/xml/System.Drawing/Image.xml
@@ -601,14 +601,14 @@
         <Parameter Name="hbitmap" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hbitmap">The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap handle from which to create the <see cref="T:System.Drawing.Bitmap" />.</param>
+        <param name="hbitmap">The GDI bitmap handle from which to create the <see cref="T:System.Drawing.Bitmap" />.</param>
         <summary>Creates a <see cref="T:System.Drawing.Bitmap" /> from a handle to a GDI bitmap.</summary>
         <returns>The <see cref="T:System.Drawing.Bitmap" /> this method creates.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Drawing.Image.FromHbitmap%2A> method makes a copy of the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap; so you can release the incoming [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap using the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `DeleteObject` method immediately after creating the new <xref:System.Drawing.Image>.  
+ The <xref:System.Drawing.Image.FromHbitmap%2A> method makes a copy of the GDI bitmap; so you can release the incoming GDI bitmap using the GDI `DeleteObject` method immediately after creating the new <xref:System.Drawing.Image>.  
   
  ]]></format>
         </remarks>
@@ -644,15 +644,15 @@
         <Parameter Name="hpalette" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hbitmap">The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap handle from which to create the <see cref="T:System.Drawing.Bitmap" />.</param>
-        <param name="hpalette">A handle to a [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] palette used to define the bitmap colors if the bitmap specified in the <paramref name="hbitmap" /> parameter is not a device-independent bitmap (DIB).</param>
+        <param name="hbitmap">The GDI bitmap handle from which to create the <see cref="T:System.Drawing.Bitmap" />.</param>
+        <param name="hpalette">A handle to a GDI palette used to define the bitmap colors if the bitmap specified in the <paramref name="hbitmap" /> parameter is not a device-independent bitmap (DIB).</param>
         <summary>Creates a <see cref="T:System.Drawing.Bitmap" /> from a handle to a GDI bitmap and a handle to a GDI palette.</summary>
         <returns>The <see cref="T:System.Drawing.Bitmap" /> this method creates.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Drawing.Image.FromHbitmap%2A> method makes a copy of the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap; so you can release the incoming [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] bitmap using the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] `DeleteObject` method immediately after creating the new <xref:System.Drawing.Image>.  
+ The <xref:System.Drawing.Image.FromHbitmap%2A> method makes a copy of the GDI bitmap; so you can release the incoming GDI bitmap using the GDI `DeleteObject` method immediately after creating the new <xref:System.Drawing.Image>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Drawing/Region.xml b/xml/System.Drawing/Region.xml
index 1b7196863dc..9c175f5fd32 100644
--- a/xml/System.Drawing/Region.xml
+++ b/xml/System.Drawing/Region.xml
@@ -892,7 +892,7 @@
       </Parameters>
       <Docs>
         <param name="hrgn">A handle to an existing <see cref="T:System.Drawing.Region" />.</param>
-        <summary>Initializes a new <see cref="T:System.Drawing.Region" /> from a handle to the specified existing [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] region.</summary>
+        <summary>Initializes a new <see cref="T:System.Drawing.Region" /> from a handle to the specified existing GDI region.</summary>
         <returns>The new <see cref="T:System.Drawing.Region" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1003,7 +1003,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You are responsible for calling the <xref:System.Drawing.Region.ReleaseHrgn%2A> method to free the memory used by the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] region object. 
+ You are responsible for calling the <xref:System.Drawing.Region.ReleaseHrgn%2A> method to free the memory used by the GDI region object. 
       
    ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index dbc1cd9de44..aceba76c6f0 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1503,17 +1503,17 @@
         <Parameter Name="defaultValue" Type="System.Boolean" Index="0" FrameworkAlternate="net-5.0;netcore-3.0;netcore-3.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="defaultValue">The default value to use for new controls. If <see langword="true" />, new controls that support <c>UseCompatibleTextRendering</c> use the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <see cref="T:System.Drawing.Graphics" /> class for text rendering; if <see langword="false" />, new controls use the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <see cref="T:System.Windows.Forms.TextRenderer" /> class.</param>
+        <param name="defaultValue">The default value to use for new controls. If <see langword="true" />, new controls that support <c>UseCompatibleTextRendering</c> use the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <see cref="T:System.Drawing.Graphics" /> class for text rendering; if <see langword="false" />, new controls use the GDI based <see cref="T:System.Windows.Forms.TextRenderer" /> class.</param>
         <summary>Sets the application-wide default for the <c>UseCompatibleTextRendering</c> property defined on certain controls.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
+ Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the GDI graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
  You should never call this method if your Windows Forms code is hosted in another application, such as Internet Explorer. Only call this method in stand-alone Windows Forms applications.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index 76efb0bf418..7f674fbf3a6 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1640,7 +1640,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1649,7 +1649,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index 98e11b341f0..79696f37201 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1692,7 +1692,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1701,7 +1701,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index 6315c231660..f912622bb7e 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1159,7 +1159,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1168,7 +1168,7 @@
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index 4805fdefcab..c63b32c529e 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2274,7 +2274,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -2283,7 +2283,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index d1c6e44416d..9d1f0729677 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1693,7 +1693,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1706,7 +1706,7 @@
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index efc9994f72d..456c60c740f 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3887,7 +3887,7 @@ This member is an explicit interface member implementation. It can be used only
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class ([!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)]) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -3896,7 +3896,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. [!INCLUDE[ndptecgdi](~/includes/ndptecgdi-md.md)] calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>

From b8f925e516fb1646908bfcb0e5aaeb03302dc044 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:04:59 -0800
Subject: [PATCH 019/236] ndptecgdiplus

---
 xml/System.Drawing.Drawing2D/LineCap.xml      |  2 +-
 xml/System.Drawing.Drawing2D/Matrix.xml       |  2 +-
 xml/System.Drawing.Imaging/Encoder.xml        | 24 +++++++++----------
 .../ImageAttributes.xml                       |  4 ++--
 xml/System.Drawing.Imaging/Metafile.xml       |  2 +-
 .../PrivateFontCollection.xml                 |  2 +-
 xml/System.Drawing/Bitmap.xml                 |  6 ++---
 xml/System.Drawing/Brush.xml                  |  4 ++--
 xml/System.Drawing/Font.xml                   |  2 +-
 xml/System.Drawing/Graphics.xml               | 18 +++++++-------
 xml/System.Drawing/Image.xml                  | 14 +++++------
 xml/System.Windows.Forms/Application.xml      |  6 ++---
 xml/System.Windows.Forms/ButtonBase.xml       |  4 ++--
 xml/System.Windows.Forms/CheckedListBox.xml   |  4 ++--
 xml/System.Windows.Forms/GroupBox.xml         |  4 ++--
 xml/System.Windows.Forms/Label.xml            |  4 ++--
 xml/System.Windows.Forms/LinkLabel.xml        |  4 ++--
 xml/System.Windows.Forms/PropertyGrid.xml     |  4 ++--
 18 files changed, 55 insertions(+), 55 deletions(-)

diff --git a/xml/System.Drawing.Drawing2D/LineCap.xml b/xml/System.Drawing.Drawing2D/LineCap.xml
index 380d9a27b6b..34dbfbf9b66 100644
--- a/xml/System.Drawing.Drawing2D/LineCap.xml
+++ b/xml/System.Drawing.Drawing2D/LineCap.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can draw the start or end of a line in one of several shapes called line caps. [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] supports several line caps, such as round, square, diamond, and arrowhead. The following illustration shows a line with a round cap and an arrow cap.  
+ You can draw the start or end of a line in one of several shapes called line caps. GDI+ supports several line caps, such as round, square, diamond, and arrowhead. The following illustration shows a line with a round cap and an arrow cap.  
   
  ![Pens](~/add/media/pens4.gif "Pens")  
   
diff --git a/xml/System.Drawing.Drawing2D/Matrix.xml b/xml/System.Drawing.Drawing2D/Matrix.xml
index fed359f366f..e0d1a9235c9 100644
--- a/xml/System.Drawing.Drawing2D/Matrix.xml
+++ b/xml/System.Drawing.Drawing2D/Matrix.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] you can store an affine transformation in a <xref:System.Drawing.Drawing2D.Matrix> object. Because the third column of a matrix that represents an affine transformation is always (0, 0, 1), you specify only the six numbers in the first two columns when you construct a <xref:System.Drawing.Drawing2D.Matrix> object. The statement `Matrix myMatrix = new Matrix(0, 1, -1, 0, 3, 4)` constructs the matrix shown in the following figure.  
+ In GDI+ you can store an affine transformation in a <xref:System.Drawing.Drawing2D.Matrix> object. Because the third column of a matrix that represents an affine transformation is always (0, 0, 1), you specify only the six numbers in the first two columns when you construct a <xref:System.Drawing.Drawing2D.Matrix> object. The statement `Matrix myMatrix = new Matrix(0, 1, -1, 0, 3, 4)` constructs the matrix shown in the following figure.  
   
  ![Transformations](~/add/media/aboutgdip05-art10.gif "Transformations")  
   
diff --git a/xml/System.Drawing.Imaging/Encoder.xml b/xml/System.Drawing.Imaging/Encoder.xml
index b91572c66de..58dc19d17ba 100644
--- a/xml/System.Drawing.Imaging/Encoder.xml
+++ b/xml/System.Drawing.Imaging/Encoder.xml
@@ -31,7 +31,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -106,7 +106,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -175,7 +175,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -245,7 +245,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -344,7 +344,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -430,7 +430,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -520,7 +520,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -592,7 +592,7 @@
 
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -671,7 +671,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -761,7 +761,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -840,7 +840,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
@@ -910,7 +910,7 @@
 ## Remarks
  When you pass a parameter to an image encoder, the parameter is encapsulated in an <xref:System.Drawing.Imaging.EncoderParameter> object. One of the fields of the <xref:System.Drawing.Imaging.EncoderParameter> object is a GUID that specifies the category of the parameter. Use the static fields of the <xref:System.Drawing.Imaging.Encoder> class to retrieve an <xref:System.Drawing.Imaging.Encoder> that contains parameters of the desired category.
 
- The image encoders that are built into [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
+ The image encoders that are built into GDI+ receive parameters that belong to several categories. The following table lists all the categories and the GUID associated with each category.
 
  <xref:System.Drawing.Imaging.Encoder.ChrominanceTable>
  f2e455dc-09b3-4316-8260-676ada32481c
diff --git a/xml/System.Drawing.Imaging/ImageAttributes.xml b/xml/System.Drawing.Imaging/ImageAttributes.xml
index a9e5c9438cb..3b767440c2d 100644
--- a/xml/System.Drawing.Imaging/ImageAttributes.xml
+++ b/xml/System.Drawing.Imaging/ImageAttributes.xml
@@ -2099,7 +2099,7 @@
 
 5.  Pass the paths of the <xref:System.Drawing.Image> and <xref:System.Drawing.Imaging.ImageAttributes> objects to the <xref:System.Drawing.Graphics.DrawImage%2A> method.
 
- [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] will use the color-profile file to calculate the cyan component of each pixel in the image, and each pixel in the rendered image will be a shade of gray that indicates the intensity of its cyan channel.
+ GDI+ will use the color-profile file to calculate the cyan component of each pixel in the image, and each pixel in the rendered image will be a shade of gray that indicates the intensity of its cyan channel.
 
  An <xref:System.Drawing.Imaging.ImageAttributes> object maintains color and grayscale settings for five adjustment categories: default, bitmap, brush, pen, and text. For example, you can specify an output channel color-profile file for the default category and a different output channel color-profile file for the bitmap category.
 
@@ -2158,7 +2158,7 @@
 
 5.  Pass the paths of the <xref:System.Drawing.Image> and <xref:System.Drawing.Imaging.ImageAttributes> objects to the <xref:System.Drawing.Graphics.DrawImage%2A> method.
 
- [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] will use the color-profile file to calculate the cyan component of each pixel in the image, and each pixel in the rendered image will be a shade of gray that indicates the intensity of its cyan channel.
+ GDI+ will use the color-profile file to calculate the cyan component of each pixel in the image, and each pixel in the rendered image will be a shade of gray that indicates the intensity of its cyan channel.
 
  An <xref:System.Drawing.Imaging.ImageAttributes> object maintains color and grayscale settings for five adjustment categories: default, bitmap, brush, pen, and text. For example, you can specify an output channel color-profile file for the default category and a different output channel color-profile file for the bitmap category.
 
diff --git a/xml/System.Drawing.Imaging/Metafile.xml b/xml/System.Drawing.Imaging/Metafile.xml
index 9ff54f53f60..1d1b8165c80 100644
--- a/xml/System.Drawing.Imaging/Metafile.xml
+++ b/xml/System.Drawing.Imaging/Metafile.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file instead. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
+ When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file instead. This behavior occurs because the GDI+ component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
   
    
   
diff --git a/xml/System.Drawing.Text/PrivateFontCollection.xml b/xml/System.Drawing.Text/PrivateFontCollection.xml
index a30d0bdd6ea..b436f77b139 100644
--- a/xml/System.Drawing.Text/PrivateFontCollection.xml
+++ b/xml/System.Drawing.Text/PrivateFontCollection.xml
@@ -35,7 +35,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Drawing.Text.PrivateFontCollection> class allows applications to install a private version of an existing font without the requirement to replace the system version of the font. For example, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] can create a private version of the Arial font in addition to the Arial font that the system uses. <xref:System.Drawing.Text.PrivateFontCollection> can also be used to install fonts that do not exist in the operating system. This is a temporary font install that does not affect the system-installed collection. To see the installed collection, use the <xref:System.Drawing.Text.InstalledFontCollection> class.  
+ The <xref:System.Drawing.Text.PrivateFontCollection> class allows applications to install a private version of an existing font without the requirement to replace the system version of the font. For example, GDI+ can create a private version of the Arial font in addition to the Arial font that the system uses. <xref:System.Drawing.Text.PrivateFontCollection> can also be used to install fonts that do not exist in the operating system. This is a temporary font install that does not affect the system-installed collection. To see the installed collection, use the <xref:System.Drawing.Text.InstalledFontCollection> class.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Drawing/Bitmap.xml b/xml/System.Drawing/Bitmap.xml
index 745de7d6cb3..3b39f6d8865 100644
--- a/xml/System.Drawing/Bitmap.xml
+++ b/xml/System.Drawing/Bitmap.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A bitmap consists of the pixel data for a graphics image and its attributes. There are many standard formats for saving a bitmap to a file. [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] supports the following file formats: BMP, GIF, EXIF, JPG, PNG and TIFF. For more information about supported formats, see [Types of Bitmaps](/dotnet/framework/winforms/advanced/types-of-bitmaps).  
+ A bitmap consists of the pixel data for a graphics image and its attributes. There are many standard formats for saving a bitmap to a file. GDI+ supports the following file formats: BMP, GIF, EXIF, JPG, PNG and TIFF. For more information about supported formats, see [Types of Bitmaps](/dotnet/framework/winforms/advanced/types-of-bitmaps).  
   
  You can create images from files, streams, and other sources by using one of the <xref:System.Drawing.Bitmap.%23ctor%2A> constructors and save them to a stream or to the file system with the <xref:System.Drawing.Image.Save%2A> method. Images are drawn to the screen or to memory by using the <xref:System.Drawing.Graphics.DrawImage%2A> method of the <xref:System.Drawing.Graphics> object. For a list of topics about working with image files, see [Working with Images, Bitmaps, Icons, and Metafiles](/dotnet/framework/winforms/advanced/working-with-images-bitmaps-icons-and-metafiles).  
   
@@ -157,7 +157,7 @@
 ## Remarks  
  You must keep the stream open for the lifetime of the <xref:System.Drawing.Bitmap>.  
   
- Due to a limitation of the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] decoder, an <xref:System.ArgumentException?displayProperty=nameWithType> is thrown if you construct a bitmap from a .png image file with a single dimension greater than 65,535 pixels.  
+ Due to a limitation of the GDI+ decoder, an <xref:System.ArgumentException?displayProperty=nameWithType> is thrown if you construct a bitmap from a .png image file with a single dimension greater than 65,535 pixels.  
   
    
   
@@ -339,7 +339,7 @@
 ## Remarks  
  You must keep the stream open for the lifetime of the <xref:System.Drawing.Bitmap>.  
   
- Due to a limitation of the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] decoder, an <xref:System.ArgumentException?displayProperty=nameWithType> is thrown if you construct a bitmap from a .png image file with a single dimension greater than 65,535 pixels.  
+ Due to a limitation of the GDI+ decoder, an <xref:System.ArgumentException?displayProperty=nameWithType> is thrown if you construct a bitmap from a .png image file with a single dimension greater than 65,535 pixels.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Drawing/Brush.xml b/xml/System.Drawing/Brush.xml
index 065edeb9be1..00b47e1d465 100644
--- a/xml/System.Drawing/Brush.xml
+++ b/xml/System.Drawing/Brush.xml
@@ -277,8 +277,8 @@
         <Parameter Name="brush" Type="System.IntPtr" Index="0" FrameworkAlternate="dotnet-plat-ext-2.1;dotnet-plat-ext-2.2;dotnet-plat-ext-3.0;dotnet-plat-ext-3.1;dotnet-plat-ext-5.0;net-5.0;netcore-3.0;netcore-3.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="brush">A pointer to the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] brush object.</param>
-        <summary>In a derived class, sets a reference to a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] brush object.</summary>
+        <param name="brush">A pointer to the GDI+ brush object.</param>
+        <summary>In a derived class, sets a reference to a GDI+ brush object.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Drawing/Font.xml b/xml/System.Drawing/Font.xml
index fb22f4ba33e..59c1eaad0d9 100644
--- a/xml/System.Drawing/Font.xml
+++ b/xml/System.Drawing/Font.xml
@@ -1036,7 +1036,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For this method to work, the `hdc` parameter must contain a handle to a device context in which a font is selected. This method will not work with an `hdc` handle acquired from a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> object because the `hdc` handle does not have a font selected.  
+ For this method to work, the `hdc` parameter must contain a handle to a device context in which a font is selected. This method will not work with an `hdc` handle acquired from a GDI+ <xref:System.Drawing.Graphics> object because the `hdc` handle does not have a font selected.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Drawing/Graphics.xml b/xml/System.Drawing/Graphics.xml
index c6b2202e566..16a9ef520af 100644
--- a/xml/System.Drawing/Graphics.xml
+++ b/xml/System.Drawing/Graphics.xml
@@ -12018,7 +12018,7 @@
 ## Remarks  
  You should always call the <xref:System.Drawing.Graphics.Dispose%2A> method to release the <xref:System.Drawing.Graphics> and related resources created by the <xref:System.Drawing.Graphics.FromHdc%2A> method.  
   
- Even if the display device has an associated ICM color profile, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] will not use that profile by default. To enable ICM for a <xref:System.Drawing.Graphics>, construct the <xref:System.Drawing.Graphics> from an HDC after you pass the HDC (and ICM_ON) to the `SetICMMode` function. Then any drawing done by the <xref:System.Drawing.Graphics> will be adjusted according to the ICM profile associated with the display device. Enabling ICM will result in slower performance.  
+ Even if the display device has an associated ICM color profile, GDI+ will not use that profile by default. To enable ICM for a <xref:System.Drawing.Graphics>, construct the <xref:System.Drawing.Graphics> from an HDC after you pass the HDC (and ICM_ON) to the `SetICMMode` function. Then any drawing done by the <xref:System.Drawing.Graphics> will be adjusted according to the ICM profile associated with the display device. Enabling ICM will result in slower performance.  
   
  The state of the device context (mapping mode, logical unit, and the like) at the time you call <xref:System.Drawing.Graphics.FromHdc%2A> can affect rendering done by the <xref:System.Drawing.Graphics>.  
   
@@ -12089,7 +12089,7 @@
 ## Remarks  
  You should always call the <xref:System.Drawing.Graphics.Dispose%2A> method to release the <xref:System.Drawing.Graphics> and related resources created by the <xref:System.Drawing.Graphics.FromHdc%2A> method.  
   
- Even if the display device has an associated ICM color profile, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] will not use that profile by default. To enable ICM for a <xref:System.Drawing.Graphics>, construct the <xref:System.Drawing.Graphics> from an HDC after you pass the HDC (and ICM_ON) to the `SetICMMode` function. Then any drawing done by the <xref:System.Drawing.Graphics> will be adjusted according to the ICM profile associated with the display device. Enabling ICM will result in slower performance.  
+ Even if the display device has an associated ICM color profile, GDI+ will not use that profile by default. To enable ICM for a <xref:System.Drawing.Graphics>, construct the <xref:System.Drawing.Graphics> from an HDC after you pass the HDC (and ICM_ON) to the `SetICMMode` function. Then any drawing done by the <xref:System.Drawing.Graphics> will be adjusted according to the ICM profile associated with the display device. Enabling ICM will result in slower performance.  
   
  The state of the device context (mapping mode, logical unit, and the like) at the time you call <xref:System.Drawing.Graphics.FromHdc%2A> can affect rendering done by the <xref:System.Drawing.Graphics>.  
   
@@ -12426,7 +12426,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of the <xref:System.Drawing.Graphics.GetHalftonePalette%2A> method is to enable [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] to produce a better quality halftone when the display uses 8 bits per pixel. To display an image using the halftone palette, use the following procedure.  
+ The purpose of the <xref:System.Drawing.Graphics.GetHalftonePalette%2A> method is to enable GDI+ to produce a better quality halftone when the display uses 8 bits per pixel. To display an image using the halftone palette, use the following procedure.  
   
    
   
@@ -12506,12 +12506,12 @@
 ## Remarks  
  The device context is a Windows structure based on GDI that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output. This method returns that device context with the exception of a font. Because a font is not selected, calls to the <xref:System.Drawing.Font.FromHdc%2A> method using a handle returned from the <xref:System.Drawing.Graphics.GetHdc%2A> method will fail.  
   
- Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make only calls to GDI functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
+ Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make only calls to GDI functions. Calls in that scope made to GDI+ methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, GDI+ ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
   
    
   
 ## Examples  
- The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
+ The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a GDI+ <xref:System.Drawing.Graphics> method. The code performs the following actions:  
   
 -   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired GDI function.  
   
@@ -12519,7 +12519,7 @@
   
 -   Creates a red pen.  
   
--   With the pen, draws a rectangle to the screen using the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics.DrawRectangle%2A> method.  
+-   With the pen, draws a rectangle to the screen using the GDI+ <xref:System.Drawing.Graphics.DrawRectangle%2A> method.  
   
 -   Defines an internal pointer type variable `hdc` and sets its value to the handle to the device context of the form.  
   
@@ -14383,18 +14383,18 @@
 ## Remarks  
  The device context is a Windows structure based on GDI that defines a set of graphical objects and their associated attributes, as well as the graphical modes that affect output.  
   
- Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make calls only to GDI functions. Calls in that scope made to [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
+ Calls to the <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> methods must appear in pairs. During the scope of a <xref:System.Drawing.Graphics.GetHdc%2A> and <xref:System.Drawing.Graphics.ReleaseHdc%2A> method pair, you usually make calls only to GDI functions. Calls in that scope made to GDI+ methods of the <xref:System.Drawing.Graphics> that produced the `hdc` parameter fail with an `ObjectBusy` error. Also, GDI+ ignores any state changes made to the <xref:System.Drawing.Graphics> of the `hdc` parameter in subsequent operations.  
   
    
   
 ## Examples  
- The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics> method. The code performs the following actions:  
+ The following code example is designed for use with Windows Forms, and it requires <xref:System.Windows.Forms.PaintEventArgs>`e`, which is a parameter of the <xref:System.Windows.Forms.Control.Paint> event handler. The example illustrates calling a Windows GDI function to perform the same task as a GDI+ <xref:System.Drawing.Graphics> method. The code performs the following actions:  
   
 -   Defines the interoperability <xref:System.Runtime.InteropServices.DllImportAttribute> attribute for the Windows DLL file gdi32.dll. This DLL contains the desired GDI function, and it defines the <xref:System.Drawing.Rectangle> function in that DLL as external.  
   
 -   Creates a red pen.  
   
--   With the pen, draws a rectangle to the screen using the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] <xref:System.Drawing.Graphics.DrawRectangle%2A> method.  
+-   With the pen, draws a rectangle to the screen using the GDI+ <xref:System.Drawing.Graphics.DrawRectangle%2A> method.  
   
 -   Defines an internal pointer type variable `hdc` and sets its value to the handle to the device context of the form.  
   
diff --git a/xml/System.Drawing/Image.xml b/xml/System.Drawing/Image.xml
index 945bcf7c53d..f8020378d7f 100644
--- a/xml/System.Drawing/Image.xml
+++ b/xml/System.Drawing/Image.xml
@@ -382,7 +382,7 @@
   
  A multiple-page image is an image that contains more than one image. Each page contains a single image (or frame). These pages (or images, or frames) are typically displayed in succession to produce an animated sequence, such as an animated .gif file.  
   
- A multiple-resolution image is an image that contains more than one copy of an image at different resolutions. This is commonly used by MIP mapping where the displayed image size determines the resolution of the image used for drawing. [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] can support an arbitrary number of pages (or images, or frames), as well as an arbitrary number of resolutions. The defined dimensions are properties of the <xref:System.Drawing.Imaging.FrameDimension>.  
+ A multiple-resolution image is an image that contains more than one copy of an image at different resolutions. This is commonly used by MIP mapping where the displayed image size determines the resolution of the image used for drawing. GDI+ can support an arbitrary number of pages (or images, or frames), as well as an arbitrary number of resolutions. The defined dimensions are properties of the <xref:System.Drawing.Imaging.FrameDimension>.  
   
  ]]></format>
         </remarks>
@@ -453,7 +453,7 @@
   
  The file remains locked until the <xref:System.Drawing.Image> is disposed.  
   
- If the file does not have a valid image format or if [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] does not support the pixel format of the file, this method throws an <xref:System.OutOfMemoryException> exception.  
+ If the file does not have a valid image format or if GDI+ does not support the pixel format of the file, this method throws an <xref:System.OutOfMemoryException> exception.  
   
 > [!NOTE]
 >  The <xref:System.Drawing.Image> class does not support alpha transparency in bitmaps. To enable alpha transparency, use PNG images with 32 bits per pixel.  
@@ -473,7 +473,7 @@
   
  -or-  
   
- [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] does not support the pixel format of the file.</exception>
+ GDI+ does not support the pixel format of the file.</exception>
         <exception cref="T:System.IO.FileNotFoundException">The specified file does not exist.</exception>
         <exception cref="T:System.ArgumentException">
           <paramref name="filename" /> is a <see cref="T:System.Uri" />.</exception>
@@ -530,7 +530,7 @@
   
 -   TIFF  
   
- If the file does not have a valid image format or if [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] does not support the pixel format of the file, this method throws an <xref:System.OutOfMemoryException> exception.  
+ If the file does not have a valid image format or if GDI+ does not support the pixel format of the file, this method throws an <xref:System.OutOfMemoryException> exception.  
   
  The file remains locked until the <xref:System.Drawing.Image> is disposed.  
   
@@ -556,7 +556,7 @@
   
  -or-  
   
- [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] does not support the pixel format of the file.</exception>
+ GDI+ does not support the pixel format of the file.</exception>
         <exception cref="T:System.IO.FileNotFoundException">The specified file does not exist.</exception>
         <exception cref="T:System.ArgumentException">
           <paramref name="filename" /> is a <see cref="T:System.Uri" />.</exception>
@@ -967,7 +967,7 @@
   
  A multiple-page image is an image that contains more than one image. Each page contains a single image (or frame). These pages (or images, or frames) are typically displayed in succession to produce an animated sequence, such as an animated .gif file.  
   
- A multiple-resolution image is an image that contains more than one copy of an image at different resolutions. This is commonly used by MIP mapping where the displayed image size determines the resolution of the image used for drawing. [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] can support an arbitrary number of pages (or images, or frames), as well as an arbitrary number of resolutions. The defined dimensions are properties of the <xref:System.Drawing.Imaging.FrameDimension>.  
+ A multiple-resolution image is an image that contains more than one copy of an image at different resolutions. This is commonly used by MIP mapping where the displayed image size determines the resolution of the image used for drawing. GDI+ can support an arbitrary number of pages (or images, or frames), as well as an arbitrary number of resolutions. The defined dimensions are properties of the <xref:System.Drawing.Imaging.FrameDimension>.  
   
  ]]></format>
         </remarks>
@@ -1754,7 +1754,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If no encoder exists for the file format of the image, the Portable Network Graphics (PNG) encoder is used. When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file. This behavior occurs because the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
+ If no encoder exists for the file format of the image, the Portable Network Graphics (PNG) encoder is used. When you use the <xref:System.Drawing.Image.Save%2A> method to save a graphic image as a Windows Metafile Format (WMF) or Enhanced Metafile Format (EMF) file, the resulting file is saved as a Portable Network Graphics (PNG) file. This behavior occurs because the GDI+ component of the .NET Framework does not have an encoder that you can use to save files as .wmf or .emf files.  
   
  Saving the image to the same file it was constructed from is not allowed and throws an exception.  
   
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index aceba76c6f0..b28dc231ccd 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1503,17 +1503,17 @@
         <Parameter Name="defaultValue" Type="System.Boolean" Index="0" FrameworkAlternate="net-5.0;netcore-3.0;netcore-3.1;netframework-2.0;netframework-3.0;netframework-3.5;netframework-4.0;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="defaultValue">The default value to use for new controls. If <see langword="true" />, new controls that support <c>UseCompatibleTextRendering</c> use the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <see cref="T:System.Drawing.Graphics" /> class for text rendering; if <see langword="false" />, new controls use the GDI based <see cref="T:System.Windows.Forms.TextRenderer" /> class.</param>
+        <param name="defaultValue">The default value to use for new controls. If <see langword="true" />, new controls that support <c>UseCompatibleTextRendering</c> use the GDI+ based <see cref="T:System.Drawing.Graphics" /> class for text rendering; if <see langword="false" />, new controls use the GDI based <see cref="T:System.Windows.Forms.TextRenderer" /> class.</param>
         <summary>Sets the application-wide default for the <c>UseCompatibleTextRendering</c> property defined on certain controls.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the GDI graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
+ Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the GDI graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the GDI+ graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with GDI+. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
  You should never call this method if your Windows Forms code is hosted in another application, such as Internet Explorer. Only call this method in stand-alone Windows Forms applications.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index 7f674fbf3a6..68665b58d8e 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1640,7 +1640,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1649,7 +1649,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index 79696f37201..0bb609ed1a2 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1692,7 +1692,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1701,7 +1701,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index f912622bb7e..ba3b0e67cb7 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1159,7 +1159,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1168,7 +1168,7 @@
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index c63b32c529e..20117941fba 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2274,7 +2274,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -2283,7 +2283,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index 9d1f0729677..b3cc18acab4 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1693,7 +1693,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -1706,7 +1706,7 @@
   
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index 456c60c740f..8dc8d463830 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3887,7 +3887,7 @@ This member is an explicit interface member implementation. It can be used only
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class ([!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
+        <summary>Gets or sets a value that determines whether to use the <see cref="T:System.Drawing.Graphics" /> class (GDI+) or the <see cref="T:System.Windows.Forms.TextRenderer" /> class (GDI) to render text.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Drawing.Graphics" /> class should be used to perform text rendering for compatibility with versions 1.0 and 1.1. of the .NET Framework; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
@@ -3896,7 +3896,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
- The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)] based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from [!INCLUDE[ndptecgdiplus](~/includes/ndptecgdiplus-md.md)]. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
+ The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
  ]]></format>
         </remarks>

From 3b7549503bae2c3a6e9eca6c202d39f837e24e01 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:05:27 -0800
Subject: [PATCH 020/236] net-client-v40-long

---
 .../CompatibleFramework.xml                    |  2 +-
 .../CompatibleFramework.xml                    |  2 +-
 xml/System.Web.Security/MembershipProvider.xml |  6 +++---
 xml/System.Web.Security/MembershipUser.xml     | 18 +++++++++---------
 4 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
index a5a60ff7e4b..c56387fd905 100644
--- a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
+++ b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], and the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)] is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
+ A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], and the .NET Framework 4 Client Profile is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Deployment.Application/CompatibleFramework.xml b/xml/System.Deployment.Application/CompatibleFramework.xml
index efa0a2d8c19..dfd743eca86 100644
--- a/xml/System.Deployment.Application/CompatibleFramework.xml
+++ b/xml/System.Deployment.Application/CompatibleFramework.xml
@@ -47,7 +47,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the .NET Framework version is [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)], the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Client". If the .NET Framework version is [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Full".  
+ If the .NET Framework version is .NET Framework 4 Client Profile, the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Client". If the .NET Framework version is [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Full".  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Security/MembershipProvider.xml b/xml/System.Web.Security/MembershipProvider.xml
index a1ac8c80ca1..f6112e1c6dd 100644
--- a/xml/System.Web.Security/MembershipProvider.xml
+++ b/xml/System.Web.Security/MembershipProvider.xml
@@ -331,7 +331,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Configuration.Provider.ProviderException">The <see cref="P:System.Web.Configuration.MachineKeySection.ValidationKey" /> property or <see cref="P:System.Web.Configuration.MachineKeySection.DecryptionKey" /> property is set to <see langword="AutoGenerate" />.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/f1kyba5e(v=vs.100)">Implementing a Membership Provider</related>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
@@ -528,7 +528,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Configuration.Provider.ProviderException">The <see cref="P:System.Web.Configuration.MachineKeySection.ValidationKey" /> property or <see cref="P:System.Web.Configuration.MachineKeySection.DecryptionKey" /> property is set to <see langword="AutoGenerate" />.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/f1kyba5e(v=vs.100)">Implementing a Membership Provider</related>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
@@ -562,7 +562,7 @@
         <returns>A byte array that contains the encrypted password.</returns>
         <remarks>To be added.</remarks>
         <exception cref="T:System.Configuration.Provider.ProviderException">The <see cref="P:System.Web.Configuration.MachineKeySection.ValidationKey" /> property or <see cref="P:System.Web.Configuration.MachineKeySection.DecryptionKey" /> property is set to <see langword="AutoGenerate" />.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
       </Docs>
     </Member>
     <Member MemberName="FindUsersByEmail">
diff --git a/xml/System.Web.Security/MembershipUser.xml b/xml/System.Web.Security/MembershipUser.xml
index 0e8be5250db..b2d569921eb 100644
--- a/xml/System.Web.Security/MembershipUser.xml
+++ b/xml/System.Web.Security/MembershipUser.xml
@@ -181,7 +181,7 @@
  -or-
 
  <paramref name="providerName" /> is not found in the <see cref="P:System.Web.Security.Membership.Providers" /> collection.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">The constructor is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, derive your class from the type and then call the default protected constructor, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The constructor is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, derive your class from the type and then call the default protected constructor, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -247,7 +247,7 @@
  -or-
 
  <paramref name="newPassword" /> is <see langword="null" />.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <altmember cref="T:System.Web.Security.SqlMembershipProvider" />
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
@@ -316,7 +316,7 @@
  <paramref name="newPasswordAnswer" /> is an empty string.</exception>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="password" /> is <see langword="null" />.</exception>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <altmember cref="T:System.Web.Security.SqlMembershipProvider" />
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
@@ -514,7 +514,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -573,7 +573,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -714,7 +714,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -1082,7 +1082,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -1137,7 +1137,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>
@@ -1210,7 +1210,7 @@
 
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the [!INCLUDE[net_client_v40_long](~/includes/net-client-v40-long-md.md)]. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This method is not available. This can occur if the application targets the .NET Framework 4 Client Profile. To prevent this exception, override the method, or change the application to target the full version of the .NET Framework.</exception>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/aspnet/yh26yfzy(v=vs.100)">Introduction to ASP.NET Membership</related>
       </Docs>
     </Member>

From 39cfa52a67c13c39ad30366cbc7dce7212ccb659 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:05:49 -0800
Subject: [PATCH 021/236] net-core

---
 xml/System.Diagnostics/Process.xml   | 4 ++--
 xml/System.Text/EncodingProvider.xml | 2 +-
 xml/System/Console.xml               | 4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml
index 6bfb47d0f5f..bae1466875e 100644
--- a/xml/System.Diagnostics/Process.xml
+++ b/xml/System.Diagnostics/Process.xml
@@ -106,8 +106,8 @@
 >  This class contains a link demand and an inheritance demand at the class level that applies to all members. A <xref:System.Security.SecurityException> is thrown when either the immediate caller or the derived class does not have full-trust permission. For details about security demands, see [Link Demands](/dotnet/framework/misc/link-demands).  
   
 <a name="Core"></a>   
-## [!INCLUDE[net_core](~/includes/net-core-md.md)] Notes  
- In the .NET Framework, the <xref:System.Diagnostics.Process> class by default uses <xref:System.Console> encodings, which are typically code page encodings, for the input, output, and error streams. For example code, on systems whose culture is English (United States), code page 437 is the default encoding for the <xref:System.Console> class. However, [!INCLUDE[net_core](~/includes/net-core-md.md)] may make only a limited subset of these encodings available. If this is the case, it uses <xref:System.Text.Encoding.UTF8%2A?displayProperty=nameWithType> as the default encoding.  
+## .NET Core Notes  
+ In the .NET Framework, the <xref:System.Diagnostics.Process> class by default uses <xref:System.Console> encodings, which are typically code page encodings, for the input, output, and error streams. For example code, on systems whose culture is English (United States), code page 437 is the default encoding for the <xref:System.Console> class. However, .NET Core may make only a limited subset of these encodings available. If this is the case, it uses <xref:System.Text.Encoding.UTF8%2A?displayProperty=nameWithType> as the default encoding.  
   
  If a <xref:System.Diagnostics.Process> object depends on specific code page encodings, you can still make them available by doing the following *before* you call any <xref:System.Diagnostics.Process> methods:  
   
diff --git a/xml/System.Text/EncodingProvider.xml b/xml/System.Text/EncodingProvider.xml
index 98a933c397c..e06d06632da 100644
--- a/xml/System.Text/EncodingProvider.xml
+++ b/xml/System.Text/EncodingProvider.xml
@@ -80,7 +80,7 @@
 
 4.  Call an <xref:System.Text.Encoding.GetEncoding%2A?displayProperty=nameWithType> overload to retrieve the encoding. The <xref:System.Text.Encoding.GetEncoding%2A?displayProperty=nameWithType> method will call the corresponding <xref:System.Text.EncodingProvider.GetEncoding%2A?displayProperty=nameWithType> to determine whether it can supply the requested encoding.
 
- The .NET Framework Class Library provides one static property, <xref:System.Text.CodePagesEncodingProvider.Instance%2A?displayProperty=nameWithType>, that returns an <xref:System.Text.EncodingProvider> object that makes the full set of encodings available on the desktop .NET Framework Class Library available to [!INCLUDE[net_core](~/includes/net-core-md.md)] applications. In addition, you can derive from the <xref:System.Text.EncodingProvider> class to make your own encodings available.
+ The .NET Framework Class Library provides one static property, <xref:System.Text.CodePagesEncodingProvider.Instance%2A?displayProperty=nameWithType>, that returns an <xref:System.Text.EncodingProvider> object that makes the full set of encodings available on the desktop .NET Framework Class Library available to .NET Core applications. In addition, you can derive from the <xref:System.Text.EncodingProvider> class to make your own encodings available.
 
  ]]></format>
     </remarks>
diff --git a/xml/System/Console.xml b/xml/System/Console.xml
index 367ce0e823e..3efbd211a15 100644
--- a/xml/System/Console.xml
+++ b/xml/System/Console.xml
@@ -170,8 +170,8 @@
 -   Play the sound of a beep through the console speaker by calling the <xref:System.Console.Beep%2A> method.
 
 <a name="Core"></a>
-## [!INCLUDE[net_core](~/includes/net-core-md.md)] Notes
- In .NET Framework on the desktop, the <xref:System.Console> class uses the encoding returned by `GetConsoleCP` and `GetConsoleOutputCP`, which typically is a code page encoding. For example code, on systems whose culture is English (United States), code page 437 is the encoding that is used by default. However, [!INCLUDE[net_core](~/includes/net-core-md.md)] may make only a limited subset of these encodings available. Where this is the case, <xref:System.Text.Encoding.UTF8%2A?displayProperty=nameWithType> is used as the default encoding for the console.
+## .NET Core Notes
+ In .NET Framework on the desktop, the <xref:System.Console> class uses the encoding returned by `GetConsoleCP` and `GetConsoleOutputCP`, which typically is a code page encoding. For example code, on systems whose culture is English (United States), code page 437 is the encoding that is used by default. However, .NET Core may make only a limited subset of these encodings available. Where this is the case, <xref:System.Text.Encoding.UTF8%2A?displayProperty=nameWithType> is used as the default encoding for the console.
 
  If your app depends on specific code page encodings, you can still make them available by doing the following *before* you call any <xref:System.Console> methods:
 

From a8ba147458c9f1100017c58838410504be1b565e Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:06:12 -0800
Subject: [PATCH 022/236] net-native

---
 xml/System/MemberAccessException.xml | 4 ++--
 xml/System/TypeAccessException.xml   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System/MemberAccessException.xml b/xml/System/MemberAccessException.xml
index aeefc081063..a74f1a99f1c 100644
--- a/xml/System/MemberAccessException.xml
+++ b/xml/System/MemberAccessException.xml
@@ -59,13 +59,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.MemberAccessException> is the base class for <xref:System.FieldAccessException>, <xref:System.MethodAccessException>, <xref:System.MissingMemberException>, <xref:System.MissingMethodException>, and <xref:System.MissingFieldException>, and  ([!INCLUDE[net_native](~/includes/net-native-md.md)] only). These exceptions are thrown when a class member is not found or access to the member is not permitted.  
+ <xref:System.MemberAccessException> is the base class for <xref:System.FieldAccessException>, <xref:System.MethodAccessException>, <xref:System.MissingMemberException>, <xref:System.MissingMethodException>, and <xref:System.MissingFieldException>, and  (.NET Native only). These exceptions are thrown when a class member is not found or access to the member is not permitted.  
   
  <xref:System.MemberAccessException> is thrown by the following methods:  
   
  <xref:System.Reflection.MethodBase.Invoke%2A> of the <xref:System.Reflection> classes, <xref:System.Reflection.FieldInfo.GetValue%2A> of the <xref:System.Reflection.FieldInfo> class, and <xref:System.Delegate.DynamicInvoke%2A> of the <xref:System.Delegate> class.  
   
- Apps compiled by using the [!INCLUDE[net_native](~/includes/net-native-md.md)] tool chain may throw a  exception at runtime.  is an internal-only exception type derived from <xref:System.MemberAccessException>. The exception indicates that metadata needed for the successful execution of an app is not present at runtime. You should not use a `try`/`catch` block to handle the exception. Instead, you should determine what metadata is missing and modify your app's  to ensure that it is present at runtime.  
+ Apps compiled by using the .NET Native tool chain may throw a  exception at runtime.  is an internal-only exception type derived from <xref:System.MemberAccessException>. The exception indicates that metadata needed for the successful execution of an app is not present at runtime. You should not use a `try`/`catch` block to handle the exception. Instead, you should determine what metadata is missing and modify your app's  to ensure that it is present at runtime.  
   
  <xref:System.MemberAccessException> uses the HRESULT COR_E_MEMBERACCESS, that has the value 0x8013151A.  
   
diff --git a/xml/System/TypeAccessException.xml b/xml/System/TypeAccessException.xml
index a144d6627c6..2e3231499af 100644
--- a/xml/System/TypeAccessException.xml
+++ b/xml/System/TypeAccessException.xml
@@ -51,7 +51,7 @@
   
  Similarly, <xref:System.TypeAccessException> is thrown for a dynamic method that uses an internal type from another assembly. A method might not have access to its containing type, its return type, or one of its parameter types.  
   
- Apps compiled by using the [!INCLUDE[net_native](~/includes/net-native-md.md)] tool chain may throw a  exception at runtime.  is an internal-only exception type derived from <xref:System.TypeAccessException>. The exception indicates that metadata needed for the successful execution of an app is not present at runtime. You should not use a `try`/`catch` block to handle the exception. Instead, you should determine what metadata is missing and modify your app's  to ensure that it is present at runtime.  
+ Apps compiled by using the .NET Native tool chain may throw a  exception at runtime.  is an internal-only exception type derived from <xref:System.TypeAccessException>. The exception indicates that metadata needed for the successful execution of an app is not present at runtime. You should not use a `try`/`catch` block to handle the exception. Instead, you should determine what metadata is missing and modify your app's  to ensure that it is present at runtime.  
   
  ]]></format>
     </remarks>

From 325d1c8c484d500fa139910bdee38b90f4696707 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:06:35 -0800
Subject: [PATCH 023/236] net-portable

---
 xml/System.Globalization/Calendar.xml                  |  2 +-
 xml/System.Resources/ResourceManager.xml               | 10 +++++-----
 .../CaptureCollection.xml                              |  6 +++---
 xml/System.Text.RegularExpressions/GroupCollection.xml |  6 +++---
 xml/System.Text.RegularExpressions/MatchCollection.xml |  6 +++---
 5 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/xml/System.Globalization/Calendar.xml b/xml/System.Globalization/Calendar.xml
index 8c38b6d7988..7f606508b53 100644
--- a/xml/System.Globalization/Calendar.xml
+++ b/xml/System.Globalization/Calendar.xml
@@ -195,7 +195,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], the <see cref="T:System.Globalization.Calendar" /> class constructor is unavailable, and classes derived from <see cref="T:System.Globalization.Calendar" /> are not public. If you want a calendar of a specific type, such as a Gregorian calendar object, you have to retrieve it from the <see cref="P:System.Globalization.CultureInfo.Calendar" /> or <see cref="P:System.Globalization.DateTimeFormatInfo.Calendar" /> property, or from the <see cref="P:System.Globalization.CultureInfo.OptionalCalendars" /> property array.</para>
+          <para>In the Portable Class Library, the <see cref="T:System.Globalization.Calendar" /> class constructor is unavailable, and classes derived from <see cref="T:System.Globalization.Calendar" /> are not public. If you want a calendar of a specific type, such as a Gregorian calendar object, you have to retrieve it from the <see cref="P:System.Globalization.CultureInfo.Calendar" /> or <see cref="P:System.Globalization.DateTimeFormatInfo.Calendar" /> property, or from the <see cref="P:System.Globalization.CultureInfo.OptionalCalendars" /> property array.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System.Resources/ResourceManager.xml b/xml/System.Resources/ResourceManager.xml
index 567d9920d03..b56ab3fe3b7 100644
--- a/xml/System.Resources/ResourceManager.xml
+++ b/xml/System.Resources/ResourceManager.xml
@@ -314,7 +314,7 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop [!INCLUDE[net_portable](~/includes/net-portable-md.md)] projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
  For [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager> class retrieves resources from package resource index (PRI) files. A single PRI file (the application package PRI file) contains the resources for both the default culture and any localized cultures. You use the MakePRI utility to create a PRI file from one or more resource files that are in XML resource (.resw) format. For resources that are included in a Visual Studio project, Visual Studio handles the process of creating and packaging the PRI file automatically. You can then use the .NET Framework <xref:System.Resources.ResourceManager> class to access the app's or library's resources.
 
@@ -515,7 +515,7 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop [!INCLUDE[net_portable](~/includes/net-portable-md.md)] projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
  In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, <xref:System.Resources.ResourceManager> uses the `resourceSource` parameter to infer the assembly, base name, and the namespace where the resource items can be located within the app's package resource index (PRI) file. For example, given a type named MyCompany.MyProduct.MyType that is defined in `MyAssembly`, the resource manager looks for a resource set identifier named MyAssembly and looks for a scope MyCompany.MyProduct.MyType within that resource set. The resource manager searches for resource items under the default context (current culture, current high contrast setting, and so on) within this scope.
 
@@ -630,7 +630,7 @@ al /out:ru-RU\Greet.resources.dll /culture:ru-RU /embed: GreetingResources.ru-RU
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop [!INCLUDE[net_portable](~/includes/net-portable-md.md)] projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
  In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the resource manager uses the simple name of the `assembly` parameter to look up a matching resource set in the app's package resource index (PRI) file. The `baseName` parameter is used to look up a resource item within the resource set. For example, the root name for PortableLibrary1.Resource1.de-DE.resources is PortableLibrary1.Resource1.
 
@@ -1726,7 +1726,7 @@ csc GetStream.cs /resource:AppResources.resources
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop [!INCLUDE[net_portable](~/includes/net-portable-md.md)] projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
  In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%29> method returns the value of the `name` string resource, localized for the caller's current UI culture settings. The list of cultures is derived from the operating system's preferred UI language list. If the resource manager cannot match `name`, the method returns `null`.
 
@@ -1841,7 +1841,7 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 ## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop [!INCLUDE[net_portable](~/includes/net-portable-md.md)] projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
  In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method returns the value of the `name` string resource, localized for the culture specified by the `culture` parameter. If the resource is not localized for the `culture` culture, the lookup uses the entire [!INCLUDE[win8](~/includes/win8-md.md)] language fallback list, and stops after looking in the default culture. If the resource manager cannot match `name`, the method returns `null`.
 
diff --git a/xml/System.Text.RegularExpressions/CaptureCollection.xml b/xml/System.Text.RegularExpressions/CaptureCollection.xml
index 104f13d7c90..08f28744f22 100644
--- a/xml/System.Text.RegularExpressions/CaptureCollection.xml
+++ b/xml/System.Text.RegularExpressions/CaptureCollection.xml
@@ -169,7 +169,7 @@
  Because the entire collection is copied into the array starting at the given index, the destination array must be at least as large as the collection.  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
   
  ]]></format>
         </remarks>
@@ -421,7 +421,7 @@ A collection that is read-only does not allow the addition or removal of element
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>
@@ -532,7 +532,7 @@ A collection that is read-only does not allow the addition or removal of element
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Text.RegularExpressions/GroupCollection.xml b/xml/System.Text.RegularExpressions/GroupCollection.xml
index c9f88a6c746..a482af1beea 100644
--- a/xml/System.Text.RegularExpressions/GroupCollection.xml
+++ b/xml/System.Text.RegularExpressions/GroupCollection.xml
@@ -221,7 +221,7 @@
  Because the entire collection is copied into the array starting at the given index, the destination array must be at least as large as the collection.  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.GroupCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.GroupCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
   
    
   
@@ -494,7 +494,7 @@ A collection that is read-only does not allow the addition or removal of element
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>
@@ -758,7 +758,7 @@ The order of the keys in the enumerable collection is unspecified, but the imple
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.GroupCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.GroupCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Text.RegularExpressions/MatchCollection.xml b/xml/System.Text.RegularExpressions/MatchCollection.xml
index 0d26f7f6f45..e0c455bdb77 100644
--- a/xml/System.Text.RegularExpressions/MatchCollection.xml
+++ b/xml/System.Text.RegularExpressions/MatchCollection.xml
@@ -166,7 +166,7 @@
  Because the collection is copied into the array starting at the given index, the destination array must be at least as large as the entire collection.  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.CaptureCollection.System%23Collections%23ICollection%23CopyTo%2A?displayProperty=nameWithType> method instead.  
   
  Because the <xref:System.Text.RegularExpressions.MatchCollection> object is generally populated by using lazy evaluation, trying to copy the collection before it has been fully populated may throw a <xref:System.Text.RegularExpressions.RegexMatchTimeoutException> exception. This exception can be thrown if a time-out value for matching operations is in effect, and the attempt to find a single match exceeds that time-out interval.  
   
@@ -435,7 +435,7 @@ A collection that is read-only does not allow the addition or removal of element
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.MatchCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.MatchCollection.System%23Collections%23ICollection%23IsSynchronized%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>
@@ -562,7 +562,7 @@ huge
 ## Remarks  
   
 > [!WARNING]
->  This member is not present in the [!INCLUDE[net_portable](~/includes/net-portable-md.md)]. If you are developing applications that target the [!INCLUDE[net_portable](~/includes/net-portable-md.md)], use the <xref:System.Text.RegularExpressions.MatchCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
+>  This member is not present in the Portable Class Library. If you are developing applications that target the Portable Class Library, use the <xref:System.Text.RegularExpressions.MatchCollection.System%23Collections%23ICollection%23SyncRoot%2A?displayProperty=nameWithType> property instead.  
   
  ]]></format>
         </remarks>

From dd43c3d7b4e2c2573ecf5f63e46be11ea380cae5 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:07:01 -0800
Subject: [PATCH 024/236] net-v10-short

---
 xml/System.Windows.Forms/Application.xml    | 2 +-
 xml/System.Windows.Forms/ButtonBase.xml     | 2 +-
 xml/System.Windows.Forms/CheckedListBox.xml | 2 +-
 xml/System.Windows.Forms/GroupBox.xml       | 2 +-
 xml/System.Windows.Forms/Label.xml          | 2 +-
 xml/System.Windows.Forms/LinkLabel.xml      | 2 +-
 xml/System.Windows.Forms/PropertyGrid.xml   | 2 +-
 xml/System/BadImageFormatException.xml      | 2 +-
 8 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index b28dc231ccd..669bc42231a 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1511,7 +1511,7 @@
 ## Remarks  
  Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the GDI graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the GDI+ graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with GDI+. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
   
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index 68665b58d8e..8cf9dc0a0fb 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1647,7 +1647,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index 0bb609ed1a2..f136719c6c5 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1699,7 +1699,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index ba3b0e67cb7..8bb4f2e75ce 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1166,7 +1166,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index 20117941fba..ed9ae2ff997 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2281,7 +2281,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index b3cc18acab4..09aa0acef62 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1704,7 +1704,7 @@
   
  If the <xref:System.Windows.Forms.LinkLabel.UseCompatibleTextRendering%2A> property is set to `true`, the <xref:System.Windows.Forms.LinkArea> does not cover the entire text.  
   
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index 8dc8d463830..6b101067377 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3894,7 +3894,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System/BadImageFormatException.xml b/xml/System/BadImageFormatException.xml
index 721217b1587..332ea504a2d 100644
--- a/xml/System/BadImageFormatException.xml
+++ b/xml/System/BadImageFormatException.xml
@@ -81,7 +81,7 @@
 
      To address this exception, set the project's **Platform target** property to x86 (instead of x64 or AnyCPU) and recompile.
 
--   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the [!INCLUDE[net_v10_short](~/includes/net-v10-short-md.md)] or the [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or later, or when an application that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
+-   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or later, or when an application that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
 
      [!code-csharp[System.BadImageFormatException.Class#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/stringlib.cs#2)]
      [!code-vb[System.BadImageFormatException.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/stringlib.vb#2)]

From c65e933dae4c7ff7b514de89d3cb6f3df11fbef4 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:07:19 -0800
Subject: [PATCH 025/236] net-v11-long

---
 xml/System.Web.Configuration/TrustSection.xml | 2 +-
 xml/System/String.xml                         | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Web.Configuration/TrustSection.xml b/xml/System.Web.Configuration/TrustSection.xml
index 62817b501da..540726e1b97 100644
--- a/xml/System.Web.Configuration/TrustSection.xml
+++ b/xml/System.Web.Configuration/TrustSection.xml
@@ -155,7 +155,7 @@
   
 -   Partial trust application domains revert to being full trust at the application domain level.  
   
--   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the [!INCLUDE[net_v11_long](~/includes/net-v11-long-md.md)] or [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] versions of the .NET Framework.  
+-   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the .NET Framework 1.1 or [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] versions of the .NET Framework.  
   
 -   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
   
diff --git a/xml/System/String.xml b/xml/System/String.xml
index 0dc0db2b462..fd458ba4899 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -183,7 +183,7 @@ For more information about Unicode, UTF-16, code units, code points, and the <xr
 
 |.NET version|Version of the Unicode Standard|
 |----------------------------|-------------------------------------|
-|[!INCLUDE[net_v11_long](~/includes/net-v11-long-md.md)]|[The Unicode Standard, Version 4.0.0](https://www.unicode.org/versions/Unicode4.0.0/)|
+|.NET Framework 1.1|[The Unicode Standard, Version 4.0.0](https://www.unicode.org/versions/Unicode4.0.0/)|
 |.NET Framework 2.0|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|

From d78bdb9f731e43e42ba63f9921a98a45a6de4a21 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:07:39 -0800
Subject: [PATCH 026/236] net-v11-short

---
 xml/System.Windows.Forms/Application.xml    | 2 +-
 xml/System.Windows.Forms/ButtonBase.xml     | 2 +-
 xml/System.Windows.Forms/CheckedListBox.xml | 2 +-
 xml/System.Windows.Forms/GroupBox.xml       | 2 +-
 xml/System.Windows.Forms/Label.xml          | 2 +-
 xml/System.Windows.Forms/LinkLabel.xml      | 2 +-
 xml/System.Windows.Forms/PropertyGrid.xml   | 2 +-
 xml/System/BadImageFormatException.xml      | 4 ++--
 8 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index 669bc42231a..9ba7e6c47c0 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1511,7 +1511,7 @@
 ## Remarks  
  Certain Windows Forms controls can render their text using either the <xref:System.Windows.Forms.TextRenderer> class, which is based on the GDI graphics library, or the <xref:System.Drawing.Graphics> class, which is based on the GDI+ graphics library. This change was made in the .NET Framework 2.0 because of performance and localization issues with GDI+. Use <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> to set the default value of the `UseCompatibleTextRendering` property for controls that support it.  
   
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true`. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/ButtonBase.xml b/xml/System.Windows.Forms/ButtonBase.xml
index 8cf9dc0a0fb..8f71118e1d5 100644
--- a/xml/System.Windows.Forms/ButtonBase.xml
+++ b/xml/System.Windows.Forms/ButtonBase.xml
@@ -1647,7 +1647,7 @@ If you set the <xref:System.Windows.Forms.ButtonBase.ImageKey%2A> property, the
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/CheckedListBox.xml b/xml/System.Windows.Forms/CheckedListBox.xml
index f136719c6c5..98e1be7c42b 100644
--- a/xml/System.Windows.Forms/CheckedListBox.xml
+++ b/xml/System.Windows.Forms/CheckedListBox.xml
@@ -1699,7 +1699,7 @@ The <xref:System.Windows.Forms.Control.CreateParams%2A> property should not be o
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/GroupBox.xml b/xml/System.Windows.Forms/GroupBox.xml
index 8bb4f2e75ce..9e0683b8e75 100644
--- a/xml/System.Windows.Forms/GroupBox.xml
+++ b/xml/System.Windows.Forms/GroupBox.xml
@@ -1166,7 +1166,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/Label.xml b/xml/System.Windows.Forms/Label.xml
index ed9ae2ff997..b4aef54de20 100644
--- a/xml/System.Windows.Forms/Label.xml
+++ b/xml/System.Windows.Forms/Label.xml
@@ -2281,7 +2281,7 @@ If you set the <xref:System.Windows.Forms.Label.ImageKey%2A> property, the <xref
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/LinkLabel.xml b/xml/System.Windows.Forms/LinkLabel.xml
index 09aa0acef62..a780268e77a 100644
--- a/xml/System.Windows.Forms/LinkLabel.xml
+++ b/xml/System.Windows.Forms/LinkLabel.xml
@@ -1704,7 +1704,7 @@
   
  If the <xref:System.Windows.Forms.LinkLabel.UseCompatibleTextRendering%2A> property is set to `true`, the <xref:System.Windows.Forms.LinkArea> does not cover the entire text.  
   
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index 6b101067377..d364be058f9 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3894,7 +3894,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)], it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
+ The `UseCompatibleTextRendering` property is intended to provide visual compatibility between Windows Forms controls that render text using the <xref:System.Windows.Forms.TextRenderer> class and .NET Framework 1.0 and .NET Framework 1.1 applications that perform custom text rendering using the <xref:System.Drawing.Graphics> class. In most cases, if your application is not being upgraded from .NET Framework 1.0 or .NET Framework 1.1, it is recommended that you leave `UseCompatibleTextRendering` set to the default value of `false`.  
   
  The GDI based <xref:System.Windows.Forms.TextRenderer> class was introduced in the .NET Framework 2.0 to improve performance, make text look better, and improve support for international fonts. In earlier versions of the .NET Framework, the GDI+ based <xref:System.Drawing.Graphics> class was used to perform all text rendering. GDI calculates character spacing and word wrapping differently from GDI+. In a Windows Forms application that uses the <xref:System.Drawing.Graphics> class to render text, this could cause the text for controls that use <xref:System.Windows.Forms.TextRenderer> to appear different from the other text in the application. To resolve this incompatibility, you can set the `UseCompatibleTextRendering` property to `true` for a specific control. To set `UseCompatibleTextRendering` to `true` for all supported controls in the application, call the <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A?displayProperty=nameWithType> method with a parameter of `true`.  
   
diff --git a/xml/System/BadImageFormatException.xml b/xml/System/BadImageFormatException.xml
index 332ea504a2d..f678ff3c893 100644
--- a/xml/System/BadImageFormatException.xml
+++ b/xml/System/BadImageFormatException.xml
@@ -81,12 +81,12 @@
 
      To address this exception, set the project's **Platform target** property to x86 (instead of x64 or AnyCPU) and recompile.
 
--   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or later, or when an application that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
+-   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or later, or when an application that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
 
      [!code-csharp[System.BadImageFormatException.Class#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/stringlib.cs#2)]
      [!code-vb[System.BadImageFormatException.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/stringlib.vb#2)]
 
-     The following example uses reflection to load an assembly named StringLib.dll. If the source code is compiled with a [!INCLUDE[net_v11_short](~/includes/net-v11-short-md.md)] compiler, a <xref:System.BadImageFormatException> is thrown by the <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType> method.
+     The following example uses reflection to load an assembly named StringLib.dll. If the source code is compiled with a .NET Framework 1.1 compiler, a <xref:System.BadImageFormatException> is thrown by the <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType> method.
 
      [!code-csharp[System.BadImageFormatException.Class#3](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/loadstringlib.cs#3)]
      [!code-vb[System.BadImageFormatException.Class#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/loadstringlib.vb#3)]

From e008443574fdb51622ccf24bc2bf8ea5e1c94c65 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:10:55 -0800
Subject: [PATCH 027/236] net-v20-sp1-long

---
 xml/System.Globalization/SortVersion.xml      |  2 +-
 .../AssemblyBuilder.xml                       | 28 ++++-----
 xml/System.Reflection.Emit/DynamicMethod.xml  | 16 ++---
 xml/System.Reflection.Emit/ModuleBuilder.xml  | 58 +++++++++----------
 xml/System.Reflection.Emit/TypeBuilder.xml    |  4 +-
 xml/System.Reflection/ConstructorInfo.xml     |  4 +-
 xml/System.Reflection/FieldInfo.xml           |  8 +--
 xml/System.Reflection/MethodBase.xml          |  4 +-
 xml/System.Reflection/PropertyInfo.xml        | 10 ++--
 .../HMACSHA384.xml                            |  6 +-
 .../HMACSHA512.xml                            |  6 +-
 .../ReflectionPermissionAttribute.xml         |  4 +-
 .../ReflectionPermissionFlag.xml              |  2 +-
 xml/System/Activator.xml                      | 24 ++++----
 xml/System/Delegate.xml                       | 20 +++----
 xml/System/String.xml                         |  2 +-
 xml/System/Type.xml                           |  6 +-
 xml/System/TypedReference.xml                 |  2 +-
 18 files changed, 103 insertions(+), 103 deletions(-)

diff --git a/xml/System.Globalization/SortVersion.xml b/xml/System.Globalization/SortVersion.xml
index 7286fc9733c..efc793fd3f6 100644
--- a/xml/System.Globalization/SortVersion.xml
+++ b/xml/System.Globalization/SortVersion.xml
@@ -50,7 +50,7 @@
 
 ### Sorting and string comparison in the .NET Framework
 
- From the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] through the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the presence of these tables depends on the operating system:  
+ From the .NET Framework 2.0 Service Pack 1 through the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the presence of these tables depends on the operating system:  
   
 -   On [!INCLUDE[win7](~/includes/win7-md.md)] and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
   
diff --git a/xml/System.Reflection.Emit/AssemblyBuilder.xml b/xml/System.Reflection.Emit/AssemblyBuilder.xml
index f7e53147ba0..43922abba36 100644
--- a/xml/System.Reflection.Emit/AssemblyBuilder.xml
+++ b/xml/System.Reflection.Emit/AssemblyBuilder.xml
@@ -204,7 +204,7 @@
  The specified resource file must be in the directory where the assembly will be saved.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -288,7 +288,7 @@
  The specified resource file must be in the directory where the assembly will be saved.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -571,7 +571,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -657,7 +657,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -744,7 +744,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -838,7 +838,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -939,7 +939,7 @@
  The runtime calls the <xref:System.Resources.ResourceWriter.Close%2A> method when the dynamic assembly is saved.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1029,7 +1029,7 @@
  The runtime calls the <xref:System.Resources.ResourceWriter.Close%2A> method when the dynamic assembly is saved.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -1158,7 +1158,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineVersionInfoResource%2A> or <xref:System.Reflection.Emit.AssemblyBuilder.DefineUnmanagedResource%2A> after either one of the methods was called previously will throw the System.ArgumentException. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1239,7 +1239,7 @@
  The information is inferred from the `AssemblyName` object used to define this dynamic assembly. This assembly's custom attributes override information specified in the `AssemblyName` object.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1309,7 +1309,7 @@
  The structure of the version resource includes data that identifies the version, language, and distribution of the file. Installation programs use the functions in the file installation library (VER.DLL) to retrieve the version information resource from a file and to extract the version information blocks from the resource.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -3015,7 +3015,7 @@
 >  <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> cannot be used to set declarative security attributes. Use one of the overloads of <xref:System.AppDomain.DefineDynamicAssembly%2A> that takes required, optional, and refused permissions.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -3093,7 +3093,7 @@
 >  <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> cannot be used to set declarative security attributes. Use one of the overloads of <xref:System.AppDomain.DefineDynamicAssembly%2A> that takes required, optional, and refused permissions.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -3200,7 +3200,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index cc8214b1d3e..1be6e8489fb 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -65,7 +65,7 @@
 |Skipping JIT visibility checks, with restrictions|Public members of public types in any assembly.|All members of all types, only in assemblies whose trust levels are equal to or less than the trust level of the assembly that emitted the dynamic method.|  
   
 > [!NOTE]
->  Prior to the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Prior to the .NET Framework 2.0 Service Pack 1, emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  The following table shows which types and members are accessible to a dynamic method that is associated with a module or with a type in a module.  
   
@@ -335,7 +335,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -422,7 +422,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -525,7 +525,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -606,7 +606,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -784,7 +784,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -1775,7 +1775,7 @@
  This method does not demand permissions directly, but invoking the dynamic method can result in security demands, depending on the method. For example, no demands are made for anonymously hosted dynamic methods that are created with the `restrictedSkipVisibility` parameter set to `false`. On the other hand, if you create a method with `restrictedSkipVisibility` set to `true` so it can access a hidden member of a target assembly, the method will cause a demand for the permissions of the target assembly plus <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag.  
   
 > [!NOTE]
->  Prior to the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess> flag.  
+>  Prior to the .NET Framework 2.0 Service Pack 1, this method required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess> flag.  
   
    
   
diff --git a/xml/System.Reflection.Emit/ModuleBuilder.xml b/xml/System.Reflection.Emit/ModuleBuilder.xml
index 9ffdd6c0e67..2d07fd829d9 100644
--- a/xml/System.Reflection.Emit/ModuleBuilder.xml
+++ b/xml/System.Reflection.Emit/ModuleBuilder.xml
@@ -185,7 +185,7 @@
  This method should be called when the user is done with defining all the global functions within this dynamic module. After calling this function, no more new global functions or new global data are allowed.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -327,7 +327,7 @@
 >  In the .NET Framework versions 1.0 and 1.1, it is necessary to define enumerations using <xref:System.Reflection.Emit.TypeBuilder> because <xref:System.Reflection.Emit.EnumBuilder> emits enumerations whose elements are of type <xref:System.Int32> instead of the enumeration type. In the .NET Framework version 2.0, <xref:System.Reflection.Emit.EnumBuilder> emits enumerations whose elements have the correct type.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -417,7 +417,7 @@
  The global method that this method defines is not usable until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -498,7 +498,7 @@
  You cannot use the global method that this method defines until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -584,7 +584,7 @@
  You cannot use the global method that this method defines until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  The data defined by this method is not created until the <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A> method is called.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -834,7 +834,7 @@
  Some DLL import attributes (see the description of System.Runtime.InteropServices.DllImportAttribute) cannot be specified as arguments to this method. Such attributes should be set by emitting a custom attribute for the method. For example, the DLL import attribute `PreserveSig` is set by emitting a custom attribute.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -929,7 +929,7 @@
  Some DLL import attributes (see the description of <xref:System.Runtime.InteropServices.DllImportAttribute>) cannot be specified as arguments to this method. Such attributes should be set by emitting a custom attribute for the method. For example, the DLL import attribute `PreserveSig` is set by emitting a custom attribute.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1005,7 +1005,7 @@
  Use this method to embed a managed resource. To embed a manifest resource blob, use the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method. For a summary of embedding and linking managed resources and manifest resource blobs, see the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1073,7 +1073,7 @@
  Use this method to embed a managed resource. To embed a manifest resource blob, use the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method. For a summary of embedding and linking managed resources and manifest resource blobs, see the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1157,7 +1157,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1231,7 +1231,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1315,7 +1315,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1401,7 +1401,7 @@
  Type names must be unique within an assembly. It is forbidden to have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1487,7 +1487,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1577,7 +1577,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1665,7 +1665,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
    
   
@@ -1743,7 +1743,7 @@
  The data defined by this method is not created until the <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A> method is called.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -1805,7 +1805,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling `DefineVersionInfoResource` or `DefineUnmanagedResource` after either one of the methods was called previously throws <xref:System.ArgumentException>. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -1857,7 +1857,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling `DefineVersionInfoResource` or `DefineUnmanagedResource` after either one of the methods was called previously throws <xref:System.ArgumentException>. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -2996,7 +2996,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -3064,7 +3064,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -3130,7 +3130,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -3200,7 +3200,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -3259,7 +3259,7 @@
  For example, if the class initializers of one of the classes throws an exception while it is being loaded, a `TargetInvocationException` is stored in the corresponding element of the `LoaderExceptions` array.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -4121,7 +4121,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -4184,7 +4184,7 @@
  For more information about how to format `binaryAttribute`, see the Common Language Infrastructure (CLI) documentation, especially "Partition II: Metadata Definition and Semantics". The documentation is available online; see [ECMA C# and Common Language Infrastructure Standards](https://go.microsoft.com/fwlink/?LinkID=99212) on MSDN and [Standard ECMA-335 - Common Language Infrastructure (CLI)](https://go.microsoft.com/fwlink/?LinkID=65552) on the Ecma International Web site.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -4231,7 +4231,7 @@
  This method does nothing.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -4283,7 +4283,7 @@
  The compiler might generate a startup stub before calling user main. The startup stub will be the entry point. While the user main will be the user entry point so that debugger will not step into the compiler entry point.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/TypeBuilder.xml b/xml/System.Reflection.Emit/TypeBuilder.xml
index 10efea0545f..f496cce19e2 100644
--- a/xml/System.Reflection.Emit/TypeBuilder.xml
+++ b/xml/System.Reflection.Emit/TypeBuilder.xml
@@ -6553,7 +6553,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
@@ -6618,7 +6618,7 @@
 For more information on how to format `binaryAttribute`, see [ECMA C# and Common Language Infrastructure Standards](/dotnet/standard/components#applicable-standards) and [Standard ECMA-335 - Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
   
 > [!NOTE]
-> Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+> Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/ConstructorInfo.xml b/xml/System.Reflection/ConstructorInfo.xml
index 1b46f9073e5..3d1adcd1a2f 100644
--- a/xml/System.Reflection/ConstructorInfo.xml
+++ b/xml/System.Reflection/ConstructorInfo.xml
@@ -387,7 +387,7 @@
  This method is a convenience method for the following overloaded version, using default values. This method cannot be overridden.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -475,7 +475,7 @@
 >  To create an instance of a value type that has no instance constructors, use the <xref:System.Activator.CreateInstance%2A> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System.Reflection/FieldInfo.xml b/xml/System.Reflection/FieldInfo.xml
index 68044f98f78..e952437b240 100644
--- a/xml/System.Reflection/FieldInfo.xml
+++ b/xml/System.Reflection/FieldInfo.xml
@@ -831,7 +831,7 @@
 >  Access restrictions are ignored for fully trusted code. That is, private constructors, methods, fields, and properties can be accessed and invoked through reflection whenever the code is fully trusted.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -2158,7 +2158,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 >  Fully trusted code has the permissions that are needed to access and invoke private constructors, methods, fields, and properties using reflection.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -2261,7 +2261,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 >  Fully trusted code has the permissions that are needed to access and invoke private constructors, methods, fields, and properties using reflection.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -2332,7 +2332,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System.Reflection/MethodBase.xml b/xml/System.Reflection/MethodBase.xml
index b9a510ddcd0..457071541bd 100644
--- a/xml/System.Reflection/MethodBase.xml
+++ b/xml/System.Reflection/MethodBase.xml
@@ -988,7 +988,7 @@
 >  If this method overload is used to invoke an instance constructor, the object supplied for `obj` is reinitialized; that is, all instance initializers are executed. The return value is `null`. If a class constructor is invoked, the class is reinitialized; that is, all class initializers are executed. The return value is `null`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1125,7 +1125,7 @@
  If the invoked method throws an exception, `TargetInvocationException.GetException` returns the exception. This implementation throws a `NotSupportedException`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System.Reflection/PropertyInfo.xml b/xml/System.Reflection/PropertyInfo.xml
index 465006774b6..7669fb4dfd4 100644
--- a/xml/System.Reflection/PropertyInfo.xml
+++ b/xml/System.Reflection/PropertyInfo.xml
@@ -1366,7 +1366,7 @@ Console.WriteLine("CurrCult: " +
  To use the `GetValue` method, first get the class `Type`. From the `Type`, get the `PropertyInfo`. From the `PropertyInfo`, use the `GetValue` method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1477,7 +1477,7 @@ Console.WriteLine("CurrCult: " +
  To use the `GetValue` method, first get the class `Type`. From the `Type`, get the `PropertyInfo`. From the `PropertyInfo`, use the `GetValue` method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1904,7 +1904,7 @@ Console.WriteLine("CurrCult: " +
  To use the <xref:System.Reflection.PropertyInfo.SetValue%2A> method, first get a <xref:System.Type> object that represents the class. From the <xref:System.Type>, get the <xref:System.Reflection.PropertyInfo> object. From the <xref:System.Reflection.PropertyInfo> object, call the <xref:System.Reflection.PropertyInfo.SetValue%2A> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -2018,7 +2018,7 @@ Console.WriteLine("CurrCult: " +
  To use the <xref:System.Reflection.PropertyInfo.SetValue%2A> method, first get a <xref:System.Type> object that represents the class. From the <xref:System.Type>, get the <xref:System.Reflection.PropertyInfo>. From the <xref:System.Reflection.PropertyInfo>, use the <xref:System.Reflection.PropertyInfo.SetValue%2A> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -2146,7 +2146,7 @@ Console.WriteLine("CurrCult: " +
  To use the `SetValue` method, first get the class `Type`. From the `Type`, get the `PropertyInfo`. From the `PropertyInfo`, use the `SetValue` method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System.Security.Cryptography/HMACSHA384.xml b/xml/System.Security.Cryptography/HMACSHA384.xml
index c415ae566db..e337f42299f 100644
--- a/xml/System.Security.Cryptography/HMACSHA384.xml
+++ b/xml/System.Security.Cryptography/HMACSHA384.xml
@@ -453,14 +453,14 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA384" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation of the algorithm.</summary>
+        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA384" /> algorithm, which is inconsistent with the .NET Framework 2.0 Service Pack 1 implementation of the algorithm.</summary>
         <value>
-          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> to enable .NET Framework 2.0 Service Pack 1 applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of the <xref:System.Security.Cryptography.HMACSHA384.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA384> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
+ The purpose of the <xref:System.Security.Cryptography.HMACSHA384.ProduceLegacyHmacValues%2A> Boolean property is to enable .NET Framework 2.0 Service Pack 1 applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA384> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
   
 ```csharp
 public static void Test()
diff --git a/xml/System.Security.Cryptography/HMACSHA512.xml b/xml/System.Security.Cryptography/HMACSHA512.xml
index 84849dbf24b..c03dcab0a6a 100644
--- a/xml/System.Security.Cryptography/HMACSHA512.xml
+++ b/xml/System.Security.Cryptography/HMACSHA512.xml
@@ -453,14 +453,14 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA512" /> algorithm, which is inconsistent with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] implementation.</summary>
+        <summary>Provides a workaround for the .NET Framework 2.0 implementation of the <see cref="T:System.Security.Cryptography.HMACSHA512" /> algorithm, which is inconsistent with the .NET Framework 2.0 Service Pack 1 implementation.</summary>
         <value>
-          <see langword="true" /> to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> to enable .NET Framework 2.0 Service Pack 1 applications to interact with .NET Framework 2.0 applications; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of the <xref:System.Security.Cryptography.HMACSHA512.ProduceLegacyHmacValues%2A> Boolean property is to enable [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA512> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
+ The purpose of the <xref:System.Security.Cryptography.HMACSHA512.ProduceLegacyHmacValues%2A> Boolean property is to enable .NET Framework 2.0 Service Pack 1 applications to interact with .NET Framework 2.0 applications. When you set this property to `true`, the <xref:System.Security.Cryptography.HMACSHA512> object produces values that match the values produced by the .NET Framework 2.0. You should set this property only once after you create your HMAC object. You will need to reset your key afterwards, as shown in the following example.  
   
 ```csharp
 public static void Test()
diff --git a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
index bfe8d4c594f..bbb6b3fda2a 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
@@ -254,7 +254,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], emitting code no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. Some features of reflection emit, such as emitting debug symbols, still require the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, emitting code no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. Some features of reflection emit, such as emitting debug symbols, still require the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -297,7 +297,7 @@
 ## Remarks  
   
 > [!NOTE]
->  This property is introduced in the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)]. To use this property, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  This property is introduced in the .NET Framework 2.0 Service Pack 1. To use this property, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
index 7bd3ddee7f0..a43a30a9cc9 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
@@ -225,7 +225,7 @@
       </ReturnValue>
       <MemberValue>4</MemberValue>
       <Docs>
-        <summary>Emitting debug symbols is allowed. Beginning with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this flag is no longer required to emit code.</summary>
+        <summary>Emitting debug symbols is allowed. Beginning with the .NET Framework 2.0 Service Pack 1, this flag is no longer required to emit code.</summary>
       </Docs>
     </Member>
     <Member MemberName="RestrictedMemberAccess">
diff --git a/xml/System/Activator.xml b/xml/System/Activator.xml
index f40a09e374e..2112dacf37f 100644
--- a/xml/System/Activator.xml
+++ b/xml/System/Activator.xml
@@ -154,7 +154,7 @@
  For information about other exceptions that can be thrown by invoked methods, see the Exceptions section of the <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType> and <xref:System.Activator.CreateInstance%2A> methods.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -234,7 +234,7 @@
  For information about other exceptions that can be thrown by invoked methods, see the Exceptions section of the <xref:System.Reflection.Assembly.LoadFrom%2A?displayProperty=nameWithType> and <xref:System.Activator.CreateInstance%2A> methods.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -390,7 +390,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances.
 
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -563,7 +563,7 @@
  For more information on how the common language runtime identifies and loads assemblies, see [How the Runtime Locates Assemblies](/dotnet/framework/deployment/how-the-runtime-locates-assemblies). For information on using the application configuration file to define assembly locations, see [Specifying an Assembly's Location](/dotnet/framework/configure-apps/specify-assembly-location). If `assemblyName` is found, it is loaded in the default context.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -662,7 +662,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances.
 
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -766,7 +766,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances with no value.
  
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -974,7 +974,7 @@
  Use <xref:System.Runtime.Remoting.ObjectHandle.Unwrap%2A?displayProperty=nameWithType> to unwrap the return value.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1074,7 +1074,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances with no value.
  
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1178,7 +1178,7 @@
   The method returns `null` for the <xref:System.Nullable%601> instances with no value.
  
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1282,7 +1282,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances with no value.
  
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1390,7 +1390,7 @@
  The method returns `null` for the <xref:System.Nullable%601> instances with no value.
  
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1600,7 +1600,7 @@
  Use <xref:System.Runtime.Remoting.ObjectHandle.Unwrap%2A?displayProperty=nameWithType> to unwrap the return value.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System/Delegate.xml b/xml/System/Delegate.xml
index d82e4222843..203b3cd96b8 100644
--- a/xml/System/Delegate.xml
+++ b/xml/System/Delegate.xml
@@ -609,7 +609,7 @@
  This method overload is equivalent to calling the <xref:System.Delegate.CreateDelegate%28System.Type%2CSystem.Reflection.MethodInfo%2CSystem.Boolean%29> method overload and specifying `true` for `throwOnBindFailure`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -771,7 +771,7 @@
 -   If the signature of `type` begins with the second parameter of `method` and the rest of the parameter types are compatible, then the delegate is said to be closed over a null reference. When the delegate is invoked, a null reference is passed to the first parameter of `method`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -958,7 +958,7 @@
  This method overload is equivalent to calling the <xref:System.Delegate.CreateDelegate%28System.Type%2CSystem.Object%2CSystem.String%2CSystem.Boolean%2CSystem.Boolean%29> method overload, specifying `false` for `ignoreCase` and `true` for `throwOnBindFailure`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1054,7 +1054,7 @@
 >  This method overload should be used when the delegate is not closed over its first argument, because it is somewhat faster in that case.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1202,7 +1202,7 @@
  This method overload is equivalent to calling the <xref:System.Delegate.CreateDelegate%28System.Type%2CSystem.Type%2CSystem.String%2CSystem.Boolean%2CSystem.Boolean%29> method overload, specifying `false` for `ignoreCase` and `true` for `throwOnBindFailure`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1329,7 +1329,7 @@
 -   If the signature of `type` begins with the second parameter of `method` and the rest of the parameter types are compatible, then the delegate is said to be closed over a null reference. When the delegate is invoked, a null reference is passed to the first parameter of `method`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1518,7 +1518,7 @@
  This method overload is equivalent to calling the <xref:System.Delegate.CreateDelegate%28System.Type%2CSystem.Object%2CSystem.String%2CSystem.Boolean%2CSystem.Boolean%29> method overload, specifying `true` for `throwOnBindFailure`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1613,7 +1613,7 @@
  This method overload is equivalent to calling the <xref:System.Delegate.CreateDelegate%28System.Type%2CSystem.Type%2CSystem.String%2CSystem.Boolean%2CSystem.Boolean%29> method overload, specifying `true` for `throwOnBindFailure`.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1722,7 +1722,7 @@
  This method creates delegates for instance methods only. An instance method is a method that is associated with an instance of a class; a static method is a method that is associated with the class itself.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -1823,7 +1823,7 @@
  This method creates delegates for static methods only. An instance method is a method that is associated with an instance of a class; a static method is a method that is associated with the class itself.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System/String.xml b/xml/System/String.xml
index fd458ba4899..c91c43ec8dc 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -7874,7 +7874,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Intern/cs/Intern2.cs" interactive="try-dotnet-method" id="Snippet2":::
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Intern/vb/Intern2.vb" id="Snippet2":::
 
- In the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)] and [!INCLUDE[net_v30_long](~/includes/net-v30-long-md.md)], `str1` and `str2` are not equal. In all other versions, `str1` and `str2` are equal.
+ In the .NET Framework 2.0 Service Pack 1 and [!INCLUDE[net_v30_long](~/includes/net-v30-long-md.md)], `str1` and `str2` are not equal. In all other versions, `str1` and `str2` are equal.
 
 ## Performance Considerations
  If you are trying to reduce the total amount of memory your application allocates, keep in mind that interning a string has two unwanted side effects. First, the memory allocated for interned <xref:System.String> objects is not likely to be released until the common language runtime (CLR) terminates. The reason is that the CLR's reference to the interned <xref:System.String> object can persist after your application, or even your application domain, terminates. Second, to intern a string, you must first create the string. The memory used by the <xref:System.String> object must still be allocated, even though the memory will eventually be garbage collected.
diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 7517cce44b4..2f4d19e4f31 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -10360,7 +10360,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
  When you invoke an `IDispatch` member, you can specify the DispID instead of the member name, using the string format "[DispID=##]". For example, if the DispID of MyComMethod is 3, you can specify the string "[DispID=3]" instead of "MyComMethod". Invoking a member by DispID is faster than looking up the member by name. In complex aggregation scenarios, the DispID is sometimes the only way to invoke the desired member.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -10580,7 +10580,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
  When you invoke an `IDispatch` member you can specify the DispID instead of the member name, using the string format "[DispID=##]". For example, if the DispID of MyComMethod is 3, you can specify the string "[DispID=3]" instead of "MyComMethod". Invoking a member by DispID is faster than looking up the member by name. In complex aggregation scenarios, the DispID is sometimes the only way to invoke the desired member.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
@@ -10800,7 +10800,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
  This will change string "z" in the array that F holds to string "b".  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
diff --git a/xml/System/TypedReference.xml b/xml/System/TypedReference.xml
index f7d18d3bc64..1d2f9d4f9a2 100644
--- a/xml/System/TypedReference.xml
+++ b/xml/System/TypedReference.xml
@@ -240,7 +240,7 @@
  The <xref:System.TypedReference.MakeTypedReference%2A> method returns a typed reference to some terminal field, where the `target` parameter contains the field described by the first element of `flds`, the field described by the first element of `flds` contains the field described by the second element of `flds`, and so on until the terminal field is reached.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v20sp1_long](~/includes/net-v20sp1-long-md.md)], this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
 >  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   

From c0395c7115c5be89bba85a7c14e3cbf85aff4ae1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:11:19 -0800
Subject: [PATCH 028/236] net-v20sp1-short

---
 xml/System.Reflection.Emit/DynamicMethod.xml                | 2 +-
 .../ReflectionPermissionFlag.xml                            | 6 +++---
 xml/System.Text.RegularExpressions/Regex.xml                | 2 +-
 xml/System.Web.Configuration/TrustSection.xml               | 4 ++--
 xml/System/BadImageFormatException.xml                      | 2 +-
 5 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index 1be6e8489fb..7c7ee6774a8 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -65,7 +65,7 @@
 |Skipping JIT visibility checks, with restrictions|Public members of public types in any assembly.|All members of all types, only in assemblies whose trust levels are equal to or less than the trust level of the assembly that emitted the dynamic method.|  
   
 > [!NOTE]
->  Prior to the .NET Framework 2.0 Service Pack 1, emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Prior to the .NET Framework 2.0 Service Pack 1, emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The .NET Framework 2.0 SP1 allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
  The following table shows which types and members are accessible to a dynamic method that is associated with a module or with a type in a module.  
   
diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
index a43a30a9cc9..d453f4db8fd 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
@@ -56,12 +56,12 @@
 > [!CAUTION]
 >  Because <xref:System.Security.Permissions.ReflectionPermission> can provide access to private class members, we recommend that you grant <xref:System.Security.Permissions.ReflectionPermission> to Internet code only with the `RestrictedMemberAccess` flag, and not with any other flags.  
   
- The `RestrictedMemberAccess` flag is introduced in the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)]. To use this flag, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+ The `RestrictedMemberAccess` flag is introduced in the .NET Framework 2.0 SP1. To use this flag, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
   
 > [!IMPORTANT]
 >  `AllFlags` does not include the `RestrictedMemberAccess` flag. To get a mask that includes all flags in this enumeration, you must use the combination of `AllFlags` with `RestrictedMemberAccess`.  
   
- Starting with the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)], the `ReflectionEmit` flag is no longer required to emit code, unless debug symbols are emitted. To use this feature, your application should target the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] or later.  
+ Starting with the .NET Framework 2.0 SP1, the `ReflectionEmit` flag is no longer required to emit code, unless debug symbols are emitted. To use this feature, your application should target the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] or later.  
   
  Starting with the .NET Framework 2.0, the `TypeInformation` flag is no longer required to reflect on nonpublic types and members; the flag has been marked obsolete.  
   
@@ -261,7 +261,7 @@
       </ReturnValue>
       <MemberValue>8</MemberValue>
       <Docs>
-        <summary>Restricted member access is provided for partially trusted code. Partially trusted code can access nonpublic types and members, but only if the grant set of the partially trusted code includes all permissions in the grant set of the assembly that contains the nonpublic types and members being accessed. This flag is new in the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)].</summary>
+        <summary>Restricted member access is provided for partially trusted code. Partially trusted code can access nonpublic types and members, but only if the grant set of the partially trusted code includes all permissions in the grant set of the assembly that contains the nonpublic types and members being accessed. This flag is new in the .NET Framework 2.0 SP1.</summary>
       </Docs>
     </Member>
     <Member MemberName="TypeInformation">
diff --git a/xml/System.Text.RegularExpressions/Regex.xml b/xml/System.Text.RegularExpressions/Regex.xml
index a0ce969b671..39bd35385e3 100644
--- a/xml/System.Text.RegularExpressions/Regex.xml
+++ b/xml/System.Text.RegularExpressions/Regex.xml
@@ -621,7 +621,7 @@
         </remarks>
         <exception cref="T:System.ArgumentOutOfRangeException">The value in a set operation is less than zero.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework prior to the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)], regular expressions used in both static and instance method calls were cached. Beginning with the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)], only regular expressions used in static method calls are cached.</para>
+          <para>In the .NET Framework prior to the .NET Framework 2.0 SP1, regular expressions used in both static and instance method calls were cached. Beginning with the .NET Framework 2.0 SP1, only regular expressions used in static method calls are cached.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System.Web.Configuration/TrustSection.xml b/xml/System.Web.Configuration/TrustSection.xml
index 540726e1b97..7db432e80e3 100644
--- a/xml/System.Web.Configuration/TrustSection.xml
+++ b/xml/System.Web.Configuration/TrustSection.xml
@@ -155,9 +155,9 @@
   
 -   Partial trust application domains revert to being full trust at the application domain level.  
   
--   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the .NET Framework 1.1 or [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] versions of the .NET Framework.  
+-   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the .NET Framework 1.1 or .NET Framework 2.0 SP1 versions of the .NET Framework.  
   
--   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
+-   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the .NET Framework 2.0 SP1 sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
   
 -   If the ASP.NET application is running in partial trust and the security policy file for the trust level maps to one of the default partial trust configuration files, ASP.NET automatically chooses the corresponding legacy configuration file. For example, if the security policy would ordinarily be loaded from Web_mediumtrust.config, then in legacy mode ASP.NET will instead load security policy from Legacy.web_mediumtrust.config.  
   
diff --git a/xml/System/BadImageFormatException.xml b/xml/System/BadImageFormatException.xml
index f678ff3c893..16b6175caa1 100644
--- a/xml/System/BadImageFormatException.xml
+++ b/xml/System/BadImageFormatException.xml
@@ -81,7 +81,7 @@
 
      To address this exception, set the project's **Platform target** property to x86 (instead of x64 or AnyCPU) and recompile.
 
--   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or later, or when an application that was developed using the [!INCLUDE[net_v20SP1_short](~/includes/net-v20sp1-short-md.md)] or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
+-   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the .NET Framework 2.0 SP1 or later, or when an application that was developed using the .NET Framework 2.0 SP1 or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
 
      [!code-csharp[System.BadImageFormatException.Class#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/stringlib.cs#2)]
      [!code-vb[System.BadImageFormatException.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/stringlib.vb#2)]

From f01451e3d42132c7df71ff2d3df3041f484c9f1d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:11:42 -0800
Subject: [PATCH 029/236] net-v30-long

---
 xml/System/String.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System/String.xml b/xml/System/String.xml
index c91c43ec8dc..b934d313f44 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -7874,7 +7874,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Intern/cs/Intern2.cs" interactive="try-dotnet-method" id="Snippet2":::
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Intern/vb/Intern2.vb" id="Snippet2":::
 
- In the .NET Framework 2.0 Service Pack 1 and [!INCLUDE[net_v30_long](~/includes/net-v30-long-md.md)], `str1` and `str2` are not equal. In all other versions, `str1` and `str2` are equal.
+ In the .NET Framework 2.0 Service Pack 1 and .NET Framework 3.0, `str1` and `str2` are not equal. In all other versions, `str1` and `str2` are equal.
 
 ## Performance Considerations
  If you are trying to reduce the total amount of memory your application allocates, keep in mind that interning a string has two unwanted side effects. First, the memory allocated for interned <xref:System.String> objects is not likely to be released until the common language runtime (CLR) terminates. The reason is that the CLR's reference to the interned <xref:System.String> object can persist after your application, or even your application domain, terminates. Second, to intern a string, you must first create the string. The memory used by the <xref:System.String> object must still be allocated, even though the memory will eventually be garbage collected.

From 7d3269ef12456e626bf31f3029775c478352797f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:12:26 -0800
Subject: [PATCH 030/236] net-v30-short

---
 xml/System.Web.Compilation/BuildManager.xml                 | 6 +++---
 xml/System.Windows.Markup/IAddChild.xml                     | 2 +-
 xml/System.Windows.Markup/IReceiveMarkupExtension.xml       | 2 +-
 .../UsableDuringInitializationAttribute.xml                 | 2 +-
 xml/System.Windows.Markup/XamlParseException.xml            | 4 ++--
 xml/System.Windows.Markup/XamlReader.xml                    | 2 +-
 xml/System.Windows.Markup/XmlAttributeProperties.xml        | 2 +-
 7 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/xml/System.Web.Compilation/BuildManager.xml b/xml/System.Web.Compilation/BuildManager.xml
index a6461c0f399..7ae8a043e69 100644
--- a/xml/System.Web.Compilation/BuildManager.xml
+++ b/xml/System.Web.Compilation/BuildManager.xml
@@ -760,11 +760,11 @@
  If the Web site does have a Web.config file, ASP.NET determines the target framework by examining the Web.config file.  
   
 ## Web Sites that Target the .NET Framework 2.0  
- Web applications that target the .NET Framework 2.0 are compiled as if the target were the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)]. The build process does not differentiate between the .NET Framework 2.0 and the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)].  
+ Web applications that target the .NET Framework 2.0 are compiled as if the target were the .NET Framework 3.0. The build process does not differentiate between the .NET Framework 2.0 and the .NET Framework 3.0 because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the .NET Framework 3.0.  
   
- This normally will not cause any problems. Visual Studio prevents you from creating references to [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] features in a project that is targeted for the .NET Framework 2.0. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for .NET Framework 2.0, because WCF was introduced with the [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and is not compatible with the .NET Framework 2.0.  
+ This normally will not cause any problems. Visual Studio prevents you from creating references to .NET Framework 3.0 features in a project that is targeted for the .NET Framework 2.0. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for .NET Framework 2.0, because WCF was introduced with the .NET Framework 3.0 and is not compatible with the .NET Framework 2.0.  
   
- If you plan to deploy a Web site in a .NET Framework 2.0 run-time environment and you use a tool other than Visual Studio to reference features that are compatible only with [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)], the project might build without generating errors or warnings. However, the application might generate errors when the Web site runs on the .NET Framework 2.0.  
+ If you plan to deploy a Web site in a .NET Framework 2.0 run-time environment and you use a tool other than Visual Studio to reference features that are compatible only with .NET Framework 3.0, the project might build without generating errors or warnings. However, the application might generate errors when the Web site runs on the .NET Framework 2.0.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/IAddChild.xml b/xml/System.Windows.Markup/IAddChild.xml
index cd0cb559f5b..90cac362ea5 100644
--- a/xml/System.Windows.Markup/IAddChild.xml
+++ b/xml/System.Windows.Markup/IAddChild.xml
@@ -24,7 +24,7 @@
   
  The main remaining scenario for <xref:System.Windows.Markup.IAddChild> is to support a <xref:System.Windows.FrameworkElementFactory> that can handle child object creation, which is an advanced scenario. See <xref:System.Windows.FrameworkElementFactory>.  
   
- Callers in .NET Framework 4.5 Beta targeted applications that attempt to use the <xref:System.Windows.Markup.IAddChild> API for one of its original [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] era purposes (WPF content model, XAML processing) should expect that many current <xref:System.Windows.Markup.IAddChild>-implementing classes will return <xref:System.NotImplementedException> or similar results for the <xref:System.Windows.Markup.IAddChild> API.  
+ Callers in .NET Framework 4.5 Beta targeted applications that attempt to use the <xref:System.Windows.Markup.IAddChild> API for one of its original .NET Framework 3.0 era purposes (WPF content model, XAML processing) should expect that many current <xref:System.Windows.Markup.IAddChild>-implementing classes will return <xref:System.NotImplementedException> or similar results for the <xref:System.Windows.Markup.IAddChild> API.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
index 03e904fc15b..1c13579596a 100644
--- a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
+++ b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)], <xref:System.Windows.Markup.IReceiveMarkupExtension> was a WPF-specific technique for permitting types to enter a different codepath whenever any of its XAML-accessible members where set as markup extensions during XAML parsing. In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], this interface is obsolete, and is replaced with a .NET Framework XAML Services implementation for how markup extensions can receive services or types can invoke markup-extension specific setter logic.  
+ In .NET Framework 3.0, <xref:System.Windows.Markup.IReceiveMarkupExtension> was a WPF-specific technique for permitting types to enter a different codepath whenever any of its XAML-accessible members where set as markup extensions during XAML parsing. In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], this interface is obsolete, and is replaced with a .NET Framework XAML Services implementation for how markup extensions can receive services or types can invoke markup-extension specific setter logic.  
   
  For [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] implementations, if types want to perform special processing when setting properties by markup extension rather than by other means, types should be defined with <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute> attributes applied. The attribute specifies a callback, which is typically defined as a private member of the type.  
   
diff --git a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
index dcab2d0574e..047f2fb0858 100644
--- a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
+++ b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
@@ -39,7 +39,7 @@
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.UsableDuringInitializationAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- In WPF XAML for [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
+ In WPF XAML for .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XamlParseException.xml b/xml/System.Windows.Markup/XamlParseException.xml
index 54a69043751..7bb729680dd 100644
--- a/xml/System.Windows.Markup/XamlParseException.xml
+++ b/xml/System.Windows.Markup/XamlParseException.xml
@@ -28,11 +28,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Markup.XamlParseException> is used only for the WPF-implemented XAML parser that performs the XAML parsing and loading for WPF applications. Specifically, the exception is only relevant when an application targets [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. The exception can also originate from user code in run-time calls to APIs that hook up the WPF-implemented XAML parser to load XAML from within a running WPF application (for example, calls to <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>).  
+ <xref:System.Windows.Markup.XamlParseException> is used only for the WPF-implemented XAML parser that performs the XAML parsing and loading for WPF applications. Specifically, the exception is only relevant when an application targets .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. The exception can also originate from user code in run-time calls to APIs that hook up the WPF-implemented XAML parser to load XAML from within a running WPF application (for example, calls to <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>).  
   
  For [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Xaml.XamlParseException> exception that typically reports XAML processing exceptions is defined in a different namespace (<xref:System.Xaml>) and a different assembly (System.Xaml).  
   
- Unless you are writing an equivalent to the WPF XAML parser or working with [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] targeting, you generally will not throw <xref:System.Windows.Markup.XamlParseException> from your own code. However, handling for the exception is sometimes necessary. For application scenarios, where you may want to suppress XAML parse errors, a <xref:System.Windows.Threading.Dispatcher> <xref:System.Windows.Threading.Dispatcher.UnhandledException> event handler at the application level is one way to handle a run-time <xref:System.Windows.Markup.XamlParseException>. Whether to suppress exceptions or let them surface to user code depends on how you design your application for purposes of loading XAML, and the trust level that you assign to the XAML your application loads. For more information, see [XAML Security Considerations](/dotnet/framework/xaml-services/xaml-security-considerations) or "XAML Security" section of [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+ Unless you are writing an equivalent to the WPF XAML parser or working with .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] targeting, you generally will not throw <xref:System.Windows.Markup.XamlParseException> from your own code. However, handling for the exception is sometimes necessary. For application scenarios, where you may want to suppress XAML parse errors, a <xref:System.Windows.Threading.Dispatcher> <xref:System.Windows.Threading.Dispatcher.UnhandledException> event handler at the application level is one way to handle a run-time <xref:System.Windows.Markup.XamlParseException>. Whether to suppress exceptions or let them surface to user code depends on how you design your application for purposes of loading XAML, and the trust level that you assign to the XAML your application loads. For more information, see [XAML Security Considerations](/dotnet/framework/xaml-services/xaml-security-considerations) or "XAML Security" section of [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  For pages of an application, when the <xref:System.Windows.Markup.XamlParseException> is thrown, it is usually in the context of the `InitializeComponent` call made by your page class, which is the entry point for the WPF application model's usage of the WPF XAML parser at the per-page level. Therefore another possible handling strategy is to place `try/catch` blocks in `InitializeComponent`. However, this technique does not integrate well with templates, visual design surfaces and other generated sources that hook up `InitializeComponent`.  
   
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index 7e9a8a37b48..000129c5bfa 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -57,7 +57,7 @@
 -   If you are not relying on any WPF types or the BAML form of XAML, and are not using another specific technology's XAML reader or XAML writer implementation for reasons that are specific to that framework, use the System.Xaml XAML readers and XAML writers.  
   
 ## System.Xaml Backing Implementation in .NET 4  
- <xref:System.Windows.Markup.XamlReader> is the callable API surface for the WPF framework-level XAML parser. The same underlying XAML parser also performs the run-time XAML loading and parsing for WPF applications that target [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)].  
+ <xref:System.Windows.Markup.XamlReader> is the callable API surface for the WPF framework-level XAML parser. The same underlying XAML parser also performs the run-time XAML loading and parsing for WPF applications that target .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)].  
   
  If you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the external API is the same, but parts of the implementation are built on the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] general XAML implementation in the System.Xaml assembly, which improves many of the technical and reporting aspects of parsing XAML. Targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] necessarily entails including System.Xaml as a reference, and details of implementation such as the exceptions reported may come from System.Xaml defined types.  
   
diff --git a/xml/System.Windows.Markup/XmlAttributeProperties.xml b/xml/System.Windows.Markup/XmlAttributeProperties.xml
index 30c6002e7e2..0b0fb5b5acc 100644
--- a/xml/System.Windows.Markup/XmlAttributeProperties.xml
+++ b/xml/System.Windows.Markup/XmlAttributeProperties.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  This class implements attached property support for <xref:System.Windows.Markup.XmlAttributeProperties.XmlNamespaceMaps%2A>, <xref:System.Windows.Markup.XmlAttributeProperties.XmlnsDefinition%2A>, and <xref:System.Windows.Markup.XmlAttributeProperties.XmlnsDictionary%2A> and <xref:System.Windows.Markup.XmlAttributeProperties.XmlSpace%2A>.  
   
- These properties are generally only used by the WPF XAML parser implementation for [!INCLUDE[net_v30_short](~/includes/net-v30-short-md.md)] and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. Actual user code attached property calls from XAML markup is not the primary scenario. The properties are implemented as attached properties primarily so that the properties can better support the property inheritance concept for dependency properties through all possible object graphs. As such, this is really an infrastructure support class. For more information, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
+ These properties are generally only used by the WPF XAML parser implementation for .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. Actual user code attached property calls from XAML markup is not the primary scenario. The properties are implemented as attached properties primarily so that the properties can better support the property inheritance concept for dependency properties through all possible object graphs. As such, this is really an infrastructure support class. For more information, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
   
  ]]></format>
     </remarks>

From 68c5acf1a9dc250ce57812c53fc859d6f1738f62 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:14:00 -0800
Subject: [PATCH 031/236] net-v35-long

---
 xml/System.Diagnostics/Process.xml            |  4 +-
 xml/System.Globalization/CultureInfo.xml      | 18 +++---
 .../AssemblyBuilder.xml                       | 28 ++++-----
 xml/System.Reflection.Emit/DynamicMethod.xml  | 18 +++---
 xml/System.Reflection.Emit/ModuleBuilder.xml  | 58 +++++++++----------
 .../SignatureHelper.xml                       |  2 +-
 xml/System.Reflection.Emit/TypeBuilder.xml    |  6 +-
 xml/System.Reflection/Assembly.xml            |  2 +-
 xml/System.Reflection/ConstructorInfo.xml     |  4 +-
 xml/System.Reflection/FieldInfo.xml           |  8 +--
 xml/System.Reflection/MethodBase.xml          |  4 +-
 xml/System.Reflection/PropertyInfo.xml        | 10 ++--
 .../ReflectionPermissionAttribute.xml         |  4 +-
 .../ReflectionPermissionFlag.xml              |  2 +-
 .../ProtocolCollection.xml                    | 24 ++++----
 xml/System.Web.Hosting/AppDomainInfo.xml      | 12 ++--
 xml/System.Web.Hosting/AppDomainInfoEnum.xml  | 10 ++--
 xml/System.Web.Hosting/IAdphManager.xml       |  8 +--
 xml/System.Web.Hosting/IAppDomainInfo.xml     | 12 ++--
 xml/System.Web.Hosting/IAppDomainInfoEnum.xml | 10 ++--
 xml/System.Web.Hosting/IApplicationHost.xml   | 16 ++---
 .../IListenerChannelCallback.xml              | 14 ++---
 xml/System.Web.Hosting/IPphManager.xml        |  8 +--
 xml/System.Web.Hosting/IProcessHost.xml       |  4 +-
 .../IProcessHostFactoryHelper.xml             |  4 +-
 .../IProcessHostIdleAndHealthCheck.xml        |  6 +-
 .../IProcessHostSupportFunctions.xml          |  8 +--
 .../IProcessPingCallback.xml                  |  4 +-
 xml/System.Web.Hosting/ProcessHost.xml        | 14 ++---
 .../ProcessHostFactoryHelper.xml              |  8 +--
 .../ProcessProtocolHandler.xml                | 12 ++--
 .../IisTraceWebEventProvider.xml              | 12 ++--
 xml/System.Web/IisTraceListener.xml           | 26 ++++-----
 xml/System.Web/RequestNotification.xml        |  2 +-
 xml/System/Activator.xml                      | 24 ++++----
 xml/System/AppDomain.xml                      |  4 +-
 xml/System/AppDomainSetup.xml                 |  4 +-
 xml/System/Delegate.xml                       | 20 +++----
 xml/System/String.xml                         |  2 +-
 xml/System/TimeZoneInfo.xml                   |  2 +-
 xml/System/Type.xml                           |  6 +-
 xml/System/TypedReference.xml                 |  2 +-
 42 files changed, 223 insertions(+), 223 deletions(-)

diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml
index bae1466875e..cbe5987cc50 100644
--- a/xml/System.Diagnostics/Process.xml
+++ b/xml/System.Diagnostics/Process.xml
@@ -6219,7 +6219,7 @@ The file specified in the <paramref name="fileName" /> could not be found.
  This method instructs the <xref:System.Diagnostics.Process> component to wait an infinite amount of time for the process and event handlers to exit. This can cause an application to stop responding. For example, if you call <xref:System.Diagnostics.Process.CloseMainWindow%2A> for a process that has a user interface, the request to the operating system to terminate the associated process might not be handled if the process is written to never enter its message loop.  
   
 > [!NOTE]
->  In the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions, the <xref:System.Diagnostics.Process.WaitForExit> overload waited for <xref:System.Int32.MaxValue> milliseconds (approximately 24 days), not indefinitely. Also, previous versions did not wait for the event handlers to exit if the full <xref:System.Int32.MaxValue> time was reached.  
+>  In the .NET Framework 3.5 and earlier versions, the <xref:System.Diagnostics.Process.WaitForExit> overload waited for <xref:System.Int32.MaxValue> milliseconds (approximately 24 days), not indefinitely. Also, previous versions did not wait for the event handlers to exit if the full <xref:System.Int32.MaxValue> time was reached.  
   
  This overload ensures that all processing has been completed, including the handling of asynchronous events for redirected standard output. You should use this overload after a call to the <xref:System.Diagnostics.Process.WaitForExit%28System.Int32%29> overload when standard output has been redirected to asynchronous event handlers.  
   
@@ -6301,7 +6301,7 @@ The file specified in the <paramref name="fileName" /> could not be found.
  This method instructs the <xref:System.Diagnostics.Process> component to wait a finite amount of time for the process to exit. If the associated process does not exit by the end of the interval because the request to terminate is denied, `false` is returned to the calling procedure. You can specify <xref:System.Threading.Timeout.Infinite?displayProperty=nameWithType> for `milliseconds`, and <xref:System.Diagnostics.Process.WaitForExit%28System.Int32%29?displayProperty=nameWithType> will behave the same as the <xref:System.Diagnostics.Process.WaitForExit> overload. If you pass 0 (zero) to the method, it returns `true` only if the process has already exited; otherwise, it immediately returns `false`.  
   
 > [!NOTE]
->  In the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions, if `milliseconds` was -1, the <xref:System.Diagnostics.Process.WaitForExit%28System.Int32%29> overload waited for <xref:System.Int32.MaxValue> milliseconds (approximately 24 days), not indefinitely.  
+>  In the .NET Framework 3.5 and earlier versions, if `milliseconds` was -1, the <xref:System.Diagnostics.Process.WaitForExit%28System.Int32%29> overload waited for <xref:System.Int32.MaxValue> milliseconds (approximately 24 days), not indefinitely.  
   
  When standard output has been redirected to asynchronous event handlers, it is possible that output processing will not have completed when this method returns. To ensure that asynchronous event handling has been completed, call the <xref:System.Diagnostics.Process.WaitForExit> overload that takes no parameter after receiving a `true` from this overload. To help ensure that the <xref:System.Diagnostics.Process.Exited> event is handled correctly in Windows Forms applications, set the <xref:System.Diagnostics.Process.SynchronizingObject%2A> property.  
   
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index 968bfbfd5d3..9f3ab6f8d6a 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -459,7 +459,7 @@ Predefined culture identifiers for cultures available on Windows system are list
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> is not a valid culture identifier. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -553,7 +553,7 @@ For a list of predefined culture names on Windows systems, see the **Language ta
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> is not a valid culture name. For more information, see the Notes to Callers section.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -641,7 +641,7 @@ Predefined culture identifiers available on Windows systems are listed in the **
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> is not a valid culture identifier. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -725,7 +725,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> is not a valid culture name. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -1068,7 +1068,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
         <exception cref="T:System.NullReferenceException">
           <paramref name="name" /> is null.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="Overload:System.Globalization.CultureInfo.#ctor" />
         <altmember cref="P:System.Globalization.CultureInfo.Parent" />
@@ -2143,7 +2143,7 @@ csc /resource:GreetingStrings.resources Example1.cs
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> specifies a culture that is not supported. See the Notes to Caller section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="M:System.Globalization.CultureInfo.ClearCachedData" />
@@ -2208,7 +2208,7 @@ For a list of predefined culture names on Windows systems, see the **Language ta
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> specifies a culture that is not supported. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.Name" />
       </Docs>
@@ -2318,7 +2318,7 @@ Setting `predefinedOnly` to `true` will ensure a culture is created only if the
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> or <paramref name="altName" /> specifies a culture that is not supported. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> or <paramref name="altName" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> or <paramref name="altName" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.Name" />
         <altmember cref="M:System.Globalization.CultureInfo.ClearCachedData" />
@@ -2386,7 +2386,7 @@ Setting `predefinedOnly` to `true` will ensure a culture is created only if the
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> does not correspond to a supported culture.</exception>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> does not correspond to the name of a supported culture. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> does not correspond to the name of a supported culture. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.TextInfo" />
         <altmember cref="T:System.Globalization.CultureAndRegionInfoBuilder" />
diff --git a/xml/System.Reflection.Emit/AssemblyBuilder.xml b/xml/System.Reflection.Emit/AssemblyBuilder.xml
index 43922abba36..8ac2e916935 100644
--- a/xml/System.Reflection.Emit/AssemblyBuilder.xml
+++ b/xml/System.Reflection.Emit/AssemblyBuilder.xml
@@ -204,7 +204,7 @@
  The specified resource file must be in the directory where the assembly will be saved.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -288,7 +288,7 @@
  The specified resource file must be in the directory where the assembly will be saved.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -571,7 +571,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -657,7 +657,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -744,7 +744,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -838,7 +838,7 @@
 >  To suppress optimizations when debugging dynamic modules, apply the <xref:System.Diagnostics.DebuggableAttribute> attribute to the dynamic assembly before calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>. Create an instance of <xref:System.Diagnostics.DebuggableAttribute> with the <xref:System.Diagnostics.DebuggableAttribute.DebuggingModes.DisableOptimizations> flag and apply it using the <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> method. The attribute must be applied to the dynamic assembly. It has no effect if applied to the module.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -939,7 +939,7 @@
  The runtime calls the <xref:System.Resources.ResourceWriter.Close%2A> method when the dynamic assembly is saved.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1029,7 +1029,7 @@
  The runtime calls the <xref:System.Resources.ResourceWriter.Close%2A> method when the dynamic assembly is saved.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1158,7 +1158,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling <xref:System.Reflection.Emit.AssemblyBuilder.DefineVersionInfoResource%2A> or <xref:System.Reflection.Emit.AssemblyBuilder.DefineUnmanagedResource%2A> after either one of the methods was called previously will throw the System.ArgumentException. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1239,7 +1239,7 @@
  The information is inferred from the `AssemblyName` object used to define this dynamic assembly. This assembly's custom attributes override information specified in the `AssemblyName` object.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1309,7 +1309,7 @@
  The structure of the version resource includes data that identifies the version, language, and distribution of the file. Installation programs use the functions in the file installation library (VER.DLL) to retrieve the version information resource from a file and to extract the version information blocks from the resource.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -3015,7 +3015,7 @@
 >  <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> cannot be used to set declarative security attributes. Use one of the overloads of <xref:System.AppDomain.DefineDynamicAssembly%2A> that takes required, optional, and refused permissions.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -3093,7 +3093,7 @@
 >  <xref:System.Reflection.Emit.AssemblyBuilder.SetCustomAttribute%2A> cannot be used to set declarative security attributes. Use one of the overloads of <xref:System.AppDomain.DefineDynamicAssembly%2A> that takes required, optional, and refused permissions.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -3200,7 +3200,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/DynamicMethod.xml b/xml/System.Reflection.Emit/DynamicMethod.xml
index 7c7ee6774a8..f46abaf96e7 100644
--- a/xml/System.Reflection.Emit/DynamicMethod.xml
+++ b/xml/System.Reflection.Emit/DynamicMethod.xml
@@ -65,7 +65,7 @@
 |Skipping JIT visibility checks, with restrictions|Public members of public types in any assembly.|All members of all types, only in assemblies whose trust levels are equal to or less than the trust level of the assembly that emitted the dynamic method.|  
   
 > [!NOTE]
->  Prior to the .NET Framework 2.0 Service Pack 1, emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The .NET Framework 2.0 SP1 allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Prior to the .NET Framework 2.0 Service Pack 1, emitting code required <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. This permission is included by default in the FullTrust and LocalIntranet named permission sets, but not in the Internet permission set. Therefore, in earlier versions of the .NET Framework a library can be used with Internet permissions only if it has the <xref:System.Security.SecurityCriticalAttribute> attribute and also executes an <xref:System.Security.PermissionSet.Assert%2A> for <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>. Such libraries require careful security review because coding errors could result in security holes. The .NET Framework 2.0 SP1 allows code to be emitted in partial trust scenarios without issuing any security demands, because generating code is not inherently a privileged operation. That is, the generated code has no more permissions than the assembly that emits it. This allows libraries that emit code to be security transparent and removes the need to assert <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit>, which simplifies the task of writing a secure library. To use this feature, your application should target the .NET Framework 3.5 or later.  
   
  The following table shows which types and members are accessible to a dynamic method that is associated with a module or with a type in a module.  
   
@@ -178,7 +178,7 @@
  This constructor specifies the method attributes <xref:System.Reflection.MethodAttributes.Public?displayProperty=nameWithType> and <xref:System.Reflection.MethodAttributes.Static?displayProperty=nameWithType>, and the calling convention <xref:System.Reflection.CallingConventions.Standard?displayProperty=nameWithType>.  
   
 > [!NOTE]
->  This constructor was introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  This constructor was introduced in the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -264,7 +264,7 @@
  This constructor specifies the method attributes <xref:System.Reflection.MethodAttributes.Public?displayProperty=nameWithType> and <xref:System.Reflection.MethodAttributes.Static?displayProperty=nameWithType>, and the calling convention <xref:System.Reflection.CallingConventions.Standard?displayProperty=nameWithType>.  
   
 > [!NOTE]
->  This constructor was introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  This constructor was introduced in the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -335,7 +335,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -422,7 +422,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -525,7 +525,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -606,7 +606,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `m` is a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -784,7 +784,7 @@
 >  For backward compatibility, this constructor demands <xref:System.Security.Permissions.SecurityPermission> with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlEvidence?displayProperty=nameWithType> flag if the following conditions are both true: `owner` is in a module other than the calling module, and the demand for <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.MemberAccess?displayProperty=nameWithType> flag has failed. If the demand for <xref:System.Security.Permissions.SecurityPermission> succeeds, the operation is allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/ModuleBuilder.xml b/xml/System.Reflection.Emit/ModuleBuilder.xml
index 2d07fd829d9..2c46e5fa15e 100644
--- a/xml/System.Reflection.Emit/ModuleBuilder.xml
+++ b/xml/System.Reflection.Emit/ModuleBuilder.xml
@@ -185,7 +185,7 @@
  This method should be called when the user is done with defining all the global functions within this dynamic module. After calling this function, no more new global functions or new global data are allowed.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -327,7 +327,7 @@
 >  In the .NET Framework versions 1.0 and 1.1, it is necessary to define enumerations using <xref:System.Reflection.Emit.TypeBuilder> because <xref:System.Reflection.Emit.EnumBuilder> emits enumerations whose elements are of type <xref:System.Int32> instead of the enumeration type. In the .NET Framework version 2.0, <xref:System.Reflection.Emit.EnumBuilder> emits enumerations whose elements have the correct type.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -417,7 +417,7 @@
  The global method that this method defines is not usable until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -498,7 +498,7 @@
  You cannot use the global method that this method defines until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -584,7 +584,7 @@
  You cannot use the global method that this method defines until you call <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A>.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -654,7 +654,7 @@
  The data defined by this method is not created until the <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A> method is called.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -834,7 +834,7 @@
  Some DLL import attributes (see the description of System.Runtime.InteropServices.DllImportAttribute) cannot be specified as arguments to this method. Such attributes should be set by emitting a custom attribute for the method. For example, the DLL import attribute `PreserveSig` is set by emitting a custom attribute.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -929,7 +929,7 @@
  Some DLL import attributes (see the description of <xref:System.Runtime.InteropServices.DllImportAttribute>) cannot be specified as arguments to this method. Such attributes should be set by emitting a custom attribute for the method. For example, the DLL import attribute `PreserveSig` is set by emitting a custom attribute.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1005,7 +1005,7 @@
  Use this method to embed a managed resource. To embed a manifest resource blob, use the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method. For a summary of embedding and linking managed resources and manifest resource blobs, see the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1073,7 +1073,7 @@
  Use this method to embed a managed resource. To embed a manifest resource blob, use the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method. For a summary of embedding and linking managed resources and manifest resource blobs, see the <xref:System.Reflection.Emit.ModuleBuilder.DefineManifestResource%2A> method.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1157,7 +1157,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1231,7 +1231,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1315,7 +1315,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1401,7 +1401,7 @@
  Type names must be unique within an assembly. It is forbidden to have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1487,7 +1487,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1577,7 +1577,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1665,7 +1665,7 @@
  Type names must be unique within an assembly. You cannot have two types with the same name in two different modules of an assembly.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1743,7 +1743,7 @@
  The data defined by this method is not created until the <xref:System.Reflection.Emit.ModuleBuilder.CreateGlobalFunctions%2A> method is called.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1805,7 +1805,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling `DefineVersionInfoResource` or `DefineUnmanagedResource` after either one of the methods was called previously throws <xref:System.ArgumentException>. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1857,7 +1857,7 @@
  An assembly can be associated with only one unmanaged resource. This means that calling `DefineVersionInfoResource` or `DefineUnmanagedResource` after either one of the methods was called previously throws <xref:System.ArgumentException>. Multiple unmanaged resources need to be merged with a tool such as the Microsoft ResMerge utility (not supplied with the common language runtime).  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -2996,7 +2996,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -3064,7 +3064,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -3130,7 +3130,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -3200,7 +3200,7 @@
  Do not use this method to generate array types, pointer types, or byref types. Use the <xref:System.Reflection.Emit.TypeBuilder.MakeArrayType%2A?displayProperty=nameWithType>, <xref:System.Reflection.Emit.TypeBuilder.MakePointerType%2A?displayProperty=nameWithType>, and <xref:System.Reflection.Emit.TypeBuilder.MakeByRefType%2A?displayProperty=nameWithType> methods instead.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -3259,7 +3259,7 @@
  For example, if the class initializers of one of the classes throws an exception while it is being loaded, a `TargetInvocationException` is stored in the corresponding element of the `LoaderExceptions` array.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -4121,7 +4121,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -4184,7 +4184,7 @@
  For more information about how to format `binaryAttribute`, see the Common Language Infrastructure (CLI) documentation, especially "Partition II: Metadata Definition and Semantics". The documentation is available online; see [ECMA C# and Common Language Infrastructure Standards](https://go.microsoft.com/fwlink/?LinkID=99212) on MSDN and [Standard ECMA-335 - Common Language Infrastructure (CLI)](https://go.microsoft.com/fwlink/?LinkID=65552) on the Ecma International Web site.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -4231,7 +4231,7 @@
  This method does nothing.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -4283,7 +4283,7 @@
  The compiler might generate a startup stub before calling user main. The startup stub will be the entry point. While the user main will be the user entry point so that debugger will not step into the compiler entry point.  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/SignatureHelper.xml b/xml/System.Reflection.Emit/SignatureHelper.xml
index 3f6a3566ae8..40d9d9b4e0f 100644
--- a/xml/System.Reflection.Emit/SignatureHelper.xml
+++ b/xml/System.Reflection.Emit/SignatureHelper.xml
@@ -1077,7 +1077,7 @@
  If a property has no custom modifiers, use the <xref:System.Reflection.Emit.SignatureHelper.GetPropertySigHelper%28System.Reflection.Module%2CSystem.Type%2CSystem.Type%5B%5D%29> method overload.  
   
 > [!NOTE]
->  This method overload is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  This method overload is introduced in the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/TypeBuilder.xml b/xml/System.Reflection.Emit/TypeBuilder.xml
index f496cce19e2..905f3c7d0b9 100644
--- a/xml/System.Reflection.Emit/TypeBuilder.xml
+++ b/xml/System.Reflection.Emit/TypeBuilder.xml
@@ -2965,7 +2965,7 @@
 > [!NOTE]
 > For more information on custom modifiers, see [ECMA C# and Common Language Infrastructure Standards](/dotnet/standard/components#applicable-standards) and [Standard ECMA-335 - Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
   
- This method overload is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+ This method overload is introduced in the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -6553,7 +6553,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -6618,7 +6618,7 @@
 For more information on how to format `binaryAttribute`, see [ECMA C# and Common Language Infrastructure Standards](/dotnet/standard/components#applicable-standards) and [Standard ECMA-335 - Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm).
   
 > [!NOTE]
-> Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+> Starting with the .NET Framework 2.0 Service Pack 1, this member no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).) To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/Assembly.xml b/xml/System.Reflection/Assembly.xml
index fef3cb1c006..a89d8c910b1 100644
--- a/xml/System.Reflection/Assembly.xml
+++ b/xml/System.Reflection/Assembly.xml
@@ -6244,7 +6244,7 @@ In .NET 5.0 and later versions, for bundled assemblies, the value returned is an
 ## Remarks
  Use this method to load a local assembly that the operating system has flagged as having been loaded from the Web (for example, a temporary file that was downloaded from the Internet or intranet). Before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], such assemblies were automatically loaded into a sandboxed application domain. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], they are loaded with full trust.
 
- As an alternative to using this method, you can apply the [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element) in your application configuration file. This causes the common language runtime to revert to the security policy of the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)].
+ As an alternative to using this method, you can apply the [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element) in your application configuration file. This causes the common language runtime to revert to the security policy of the .NET Framework 3.5.
 
 > [!CAUTION]
 >  If you use either of these solutions, you must be certain that it is safe to load `assemblyFile` with full trust.
diff --git a/xml/System.Reflection/ConstructorInfo.xml b/xml/System.Reflection/ConstructorInfo.xml
index 3d1adcd1a2f..9cf8b9cd7bb 100644
--- a/xml/System.Reflection/ConstructorInfo.xml
+++ b/xml/System.Reflection/ConstructorInfo.xml
@@ -389,7 +389,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -477,7 +477,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/FieldInfo.xml b/xml/System.Reflection/FieldInfo.xml
index e952437b240..ff56051b2d9 100644
--- a/xml/System.Reflection/FieldInfo.xml
+++ b/xml/System.Reflection/FieldInfo.xml
@@ -833,7 +833,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -2160,7 +2160,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -2263,7 +2263,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -2334,7 +2334,7 @@ This method cannot be used to set values of static, init-only (`readonly` in C#)
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/MethodBase.xml b/xml/System.Reflection/MethodBase.xml
index 457071541bd..0cdd9b60081 100644
--- a/xml/System.Reflection/MethodBase.xml
+++ b/xml/System.Reflection/MethodBase.xml
@@ -990,7 +990,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  If a parameter of the current method is a value type, and the corresponding argument in `parameters` is `null`, the runtime passes a zero-initialized instance of the value type.  
   
@@ -1127,7 +1127,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
diff --git a/xml/System.Reflection/PropertyInfo.xml b/xml/System.Reflection/PropertyInfo.xml
index 7669fb4dfd4..c4cee50f6e1 100644
--- a/xml/System.Reflection/PropertyInfo.xml
+++ b/xml/System.Reflection/PropertyInfo.xml
@@ -1368,7 +1368,7 @@ Console.WriteLine("CurrCult: " +
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -1479,7 +1479,7 @@ Console.WriteLine("CurrCult: " +
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1906,7 +1906,7 @@ Console.WriteLine("CurrCult: " +
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -2020,7 +2020,7 @@ Console.WriteLine("CurrCult: " +
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -2148,7 +2148,7 @@ Console.WriteLine("CurrCult: " +
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
index bbb6b3fda2a..57802b4cb21 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionAttribute.xml
@@ -256,7 +256,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, emitting code no longer requires <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. Some features of reflection emit, such as emitting debug symbols, still require the <xref:System.Security.Permissions.ReflectionPermissionFlag.ReflectionEmit?displayProperty=nameWithType> flag. (See [Security Issues in Reflection Emit](/dotnet/framework/reflection-and-codedom/security-issues-in-reflection-emit).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -297,7 +297,7 @@
 ## Remarks  
   
 > [!NOTE]
->  This property is introduced in the .NET Framework 2.0 Service Pack 1. To use this property, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  This property is introduced in the .NET Framework 2.0 Service Pack 1. To use this property, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
index d453f4db8fd..9d09b54bd6d 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
@@ -56,7 +56,7 @@
 > [!CAUTION]
 >  Because <xref:System.Security.Permissions.ReflectionPermission> can provide access to private class members, we recommend that you grant <xref:System.Security.Permissions.ReflectionPermission> to Internet code only with the `RestrictedMemberAccess` flag, and not with any other flags.  
   
- The `RestrictedMemberAccess` flag is introduced in the .NET Framework 2.0 SP1. To use this flag, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+ The `RestrictedMemberAccess` flag is introduced in the .NET Framework 2.0 SP1. To use this flag, your application should target the .NET Framework 3.5 or later.  
   
 > [!IMPORTANT]
 >  `AllFlags` does not include the `RestrictedMemberAccess` flag. To get a mask that includes all flags in this enumeration, you must use the combination of `AllFlags` with `RestrictedMemberAccess`.  
diff --git a/xml/System.Web.Configuration/ProtocolCollection.xml b/xml/System.Web.Configuration/ProtocolCollection.xml
index 8fe9a946a36..35cf58b3f3c 100644
--- a/xml/System.Web.Configuration/ProtocolCollection.xml
+++ b/xml/System.Web.Configuration/ProtocolCollection.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.%23ctor%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.%23ctor%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -91,7 +91,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Add%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Add%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.AllKeys%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.AllKeys%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Clear%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Clear%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -218,7 +218,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -251,7 +251,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -285,7 +285,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Item%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -331,7 +331,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -363,7 +363,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -396,7 +396,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.Remove%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -429,7 +429,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Configuration.ProtocolCollection.RemoveAt%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Configuration.ProtocolCollection.RemoveAt%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/AppDomainInfo.xml b/xml/System.Web.Hosting/AppDomainInfo.xml
index e9ef521f8f7..e3ab6eacb25 100644
--- a/xml/System.Web.Hosting/AppDomainInfo.xml
+++ b/xml/System.Web.Hosting/AppDomainInfo.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo.GetId%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo.GetId%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -92,7 +92,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo.GetPhysicalPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo.GetPhysicalPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -126,7 +126,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo.GetSiteId%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo.GetSiteId%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -160,7 +160,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo.GetVirtualPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo.GetVirtualPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -195,7 +195,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfo.IsIdle%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfo.IsIdle%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/AppDomainInfoEnum.xml b/xml/System.Web.Hosting/AppDomainInfoEnum.xml
index fc5129b5d2d..5b0f1cb6352 100644
--- a/xml/System.Web.Hosting/AppDomainInfoEnum.xml
+++ b/xml/System.Web.Hosting/AppDomainInfoEnum.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfoEnum> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfoEnum> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfoEnum.Count%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfoEnum.Count%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -92,7 +92,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfoEnum.GetData%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfoEnum.GetData%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -126,7 +126,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfoEnum.MoveNext%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfoEnum.MoveNext%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -159,7 +159,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.AppDomainInfoEnum.Reset%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.AppDomainInfoEnum.Reset%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IAdphManager.xml b/xml/System.Web.Hosting/IAdphManager.xml
index 3bbcab6de87..3c8ebb69a99 100644
--- a/xml/System.Web.Hosting/IAdphManager.xml
+++ b/xml/System.Web.Hosting/IAdphManager.xml
@@ -17,7 +17,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAdphManager> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAdphManager> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -54,7 +54,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAdphManager.StartAppDomainProtocolListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAdphManager.StartAppDomainProtocolListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -91,7 +91,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAdphManager.StopAppDomainProtocol%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAdphManager.StopAppDomainProtocol%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -130,7 +130,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAdphManager.StopAppDomainProtocolListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAdphManager.StopAppDomainProtocolListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IAppDomainInfo.xml b/xml/System.Web.Hosting/IAppDomainInfo.xml
index 22402a16d76..64be00f4b55 100644
--- a/xml/System.Web.Hosting/IAppDomainInfo.xml
+++ b/xml/System.Web.Hosting/IAppDomainInfo.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo.GetId%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo.GetId%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -89,7 +89,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo.GetPhysicalPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo.GetPhysicalPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -120,7 +120,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo.GetSiteId%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo.GetSiteId%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo.GetVirtualPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo.GetVirtualPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -183,7 +183,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfo.IsIdle%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfo.IsIdle%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IAppDomainInfoEnum.xml b/xml/System.Web.Hosting/IAppDomainInfoEnum.xml
index e49e7ceb227..3638c230c54 100644
--- a/xml/System.Web.Hosting/IAppDomainInfoEnum.xml
+++ b/xml/System.Web.Hosting/IAppDomainInfoEnum.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfoEnum> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfoEnum> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfoEnum.Count%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfoEnum.Count%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -89,7 +89,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfoEnum.GetData%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfoEnum.GetData%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -121,7 +121,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfoEnum.MoveNext%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfoEnum.MoveNext%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IAppDomainInfoEnum.Reset%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IAppDomainInfoEnum.Reset%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IApplicationHost.xml b/xml/System.Web.Hosting/IApplicationHost.xml
index 6c3d2b80cc7..45c1fc1c418 100644
--- a/xml/System.Web.Hosting/IApplicationHost.xml
+++ b/xml/System.Web.Hosting/IApplicationHost.xml
@@ -17,7 +17,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -48,7 +48,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetConfigMapPathFactory%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetConfigMapPathFactory%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -79,7 +79,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetConfigToken%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetConfigToken%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -110,7 +110,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetPhysicalPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetPhysicalPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -141,7 +141,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetSiteID%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetSiteID%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -172,7 +172,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetSiteName%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetSiteName%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -203,7 +203,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.GetVirtualPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.GetVirtualPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -233,7 +233,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IApplicationHost.MessageReceived%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IApplicationHost.MessageReceived%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IListenerChannelCallback.xml b/xml/System.Web.Hosting/IListenerChannelCallback.xml
index c7a01e687e3..b6c69570b7f 100644
--- a/xml/System.Web.Hosting/IListenerChannelCallback.xml
+++ b/xml/System.Web.Hosting/IListenerChannelCallback.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -62,7 +62,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback.GetBlob%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.GetBlob%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -93,7 +93,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback.GetBlobLength%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.GetBlobLength%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -124,7 +124,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback.GetId%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.GetId%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -156,7 +156,7 @@
 ## Remarks  
  This method supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.  
   
- <xref:System.Web.Hosting.IListenerChannelCallback.ReportMessageReceived%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.ReportMessageReceived%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -186,7 +186,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback.ReportStarted%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.ReportStarted%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -219,7 +219,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IListenerChannelCallback.ReportStopped%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IListenerChannelCallback.ReportStopped%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IPphManager.xml b/xml/System.Web.Hosting/IPphManager.xml
index 145604769f7..fd130d99503 100644
--- a/xml/System.Web.Hosting/IPphManager.xml
+++ b/xml/System.Web.Hosting/IPphManager.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IPphManager> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IPphManager> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -62,7 +62,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IPphManager.StartProcessProtocolListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IPphManager.StartProcessProtocolListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -98,7 +98,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IPphManager.StopProcessProtocol%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IPphManager.StopProcessProtocol%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -136,7 +136,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IPphManager.StopProcessProtocolListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IPphManager.StopProcessProtocolListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IProcessHost.xml b/xml/System.Web.Hosting/IProcessHost.xml
index e590a3ea4e1..79597805000 100644
--- a/xml/System.Web.Hosting/IProcessHost.xml
+++ b/xml/System.Web.Hosting/IProcessHost.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHost> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHost> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -109,7 +109,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHost.ShutdownApplication%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHost.ShutdownApplication%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IProcessHostFactoryHelper.xml b/xml/System.Web.Hosting/IProcessHostFactoryHelper.xml
index 3269d291517..f256ad5d301 100644
--- a/xml/System.Web.Hosting/IProcessHostFactoryHelper.xml
+++ b/xml/System.Web.Hosting/IProcessHostFactoryHelper.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostFactoryHelper> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostFactoryHelper> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -61,7 +61,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostFactoryHelper.GetProcessHost%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostFactoryHelper.GetProcessHost%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IProcessHostIdleAndHealthCheck.xml b/xml/System.Web.Hosting/IProcessHostIdleAndHealthCheck.xml
index c9b76b81c43..f75ef32d8a4 100644
--- a/xml/System.Web.Hosting/IProcessHostIdleAndHealthCheck.xml
+++ b/xml/System.Web.Hosting/IProcessHostIdleAndHealthCheck.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -59,7 +59,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck.IsIdle%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck.IsIdle%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -92,7 +92,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck.Ping%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostIdleAndHealthCheck.Ping%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IProcessHostSupportFunctions.xml b/xml/System.Web.Hosting/IProcessHostSupportFunctions.xml
index ae0fb03bdb1..9fd3f5b926f 100644
--- a/xml/System.Web.Hosting/IProcessHostSupportFunctions.xml
+++ b/xml/System.Web.Hosting/IProcessHostSupportFunctions.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostSupportFunctions> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostSupportFunctions> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -96,7 +96,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostSupportFunctions.GetApplicationProperties%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostSupportFunctions.GetApplicationProperties%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -130,7 +130,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostSupportFunctions.GetConfigToken%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostSupportFunctions.GetConfigToken%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -215,7 +215,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessHostSupportFunctions.MapPath%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessHostSupportFunctions.MapPath%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/IProcessPingCallback.xml b/xml/System.Web.Hosting/IProcessPingCallback.xml
index 6e0ecf3b824..4aa18d6e55a 100644
--- a/xml/System.Web.Hosting/IProcessPingCallback.xml
+++ b/xml/System.Web.Hosting/IProcessPingCallback.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessPingCallback> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessPingCallback> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -57,7 +57,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.IProcessPingCallback.Respond%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.IProcessPingCallback.Respond%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/ProcessHost.xml b/xml/System.Web.Hosting/ProcessHost.xml
index 7265088f397..ec522710116 100644
--- a/xml/System.Web.Hosting/ProcessHost.xml
+++ b/xml/System.Web.Hosting/ProcessHost.xml
@@ -41,7 +41,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -101,7 +101,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.InitializeLifetimeService%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.InitializeLifetimeService%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -136,7 +136,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.IsIdle%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.IsIdle%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -172,7 +172,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.Ping%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.Ping%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -325,7 +325,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.ShutdownApplication%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.ShutdownApplication%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -462,7 +462,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.StopAppDomainProtocol%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.StopAppDomainProtocol%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -535,7 +535,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHost.StopProcessProtocol%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHost.StopProcessProtocol%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/ProcessHostFactoryHelper.xml b/xml/System.Web.Hosting/ProcessHostFactoryHelper.xml
index f79a0776e4a..9ae2a7d6ad6 100644
--- a/xml/System.Web.Hosting/ProcessHostFactoryHelper.xml
+++ b/xml/System.Web.Hosting/ProcessHostFactoryHelper.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHostFactoryHelper> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHostFactoryHelper> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHostFactoryHelper.%23ctor%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHostFactoryHelper.%23ctor%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -93,7 +93,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHostFactoryHelper.GetProcessHost%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHostFactoryHelper.GetProcessHost%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -125,7 +125,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessHostFactoryHelper.InitializeLifetimeService%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessHostFactoryHelper.InitializeLifetimeService%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Hosting/ProcessProtocolHandler.xml b/xml/System.Web.Hosting/ProcessProtocolHandler.xml
index 5ff9f9ddcc0..5263678b7df 100644
--- a/xml/System.Web.Hosting/ProcessProtocolHandler.xml
+++ b/xml/System.Web.Hosting/ProcessProtocolHandler.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -52,7 +52,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler.%23ctor%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler.%23ctor%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -83,7 +83,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler.InitializeLifetimeService%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler.InitializeLifetimeService%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler.StartListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler.StartListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -154,7 +154,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler.StopListenerChannel%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler.StopListenerChannel%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -188,7 +188,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Hosting.ProcessProtocolHandler.StopProtocol%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Hosting.ProcessProtocolHandler.StopProtocol%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Management/IisTraceWebEventProvider.xml b/xml/System.Web.Management/IisTraceWebEventProvider.xml
index 9346f314eb2..88f4f7ebb76 100644
--- a/xml/System.Web.Management/IisTraceWebEventProvider.xml
+++ b/xml/System.Web.Management/IisTraceWebEventProvider.xml
@@ -24,7 +24,7 @@
   
  The <xref:System.Web.Management.IisTraceWebEventProvider> class is a customized health-event provider that processes ASP.NET tracing events by routing them through the IIS 7.0 tracing infrastructure. This routing occurs only when tracing is enabled in ASP.NET.  
   
- <xref:System.Web.Management.IisTraceWebEventProvider> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
 > [!NOTE]
 >  This class does not route IIS 7.0 trace events into ASP.NET page events.  
@@ -54,7 +54,7 @@
 ## Remarks  
  The <xref:System.Web.Management.IisTraceWebEventProvider.%23ctor%2A> constructor is not intended to be used directly from your code. It is called by ASP.NET.  
   
- <xref:System.Web.Management.IisTraceWebEventProvider.%23ctor%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider.%23ctor%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -85,7 +85,7 @@
 ## Remarks  
  When this method is called, all the events in the buffer are immediately moved from the buffer to the event log. This occurs regardless of how much time has elapsed since the last event was written or how many events are in the buffer. The time of the last written event is reset to the time of the flushing action.  
   
- <xref:System.Web.Management.IisTraceWebEventProvider.Flush%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider.Flush%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -119,7 +119,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Management.IisTraceWebEventProvider.Initialize%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider.Initialize%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -151,7 +151,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.Management.IisTraceWebEventProvider.ProcessEvent%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider.ProcessEvent%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -182,7 +182,7 @@
 ## Remarks  
  The method performs tasks that enable the application to end normally. An example of such a task is closing resources.  
   
- <xref:System.Web.Management.IisTraceWebEventProvider.Shutdown%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.Management.IisTraceWebEventProvider.Shutdown%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web/IisTraceListener.xml b/xml/System.Web/IisTraceListener.xml
index 277de6c84d8..91ca0b4a7e0 100644
--- a/xml/System.Web/IisTraceListener.xml
+++ b/xml/System.Web/IisTraceListener.xml
@@ -25,7 +25,7 @@
 > [!NOTE]
 >  This listener class does not route IIS 7.0 events to ASP.NET classes. This includes the <xref:System.Web.UI.Page> class and classes that implement the <xref:System.Web.IHttpModule> or <xref:System.Web.IHttpHandler> interface.  
   
- <xref:System.Web.IisTraceListener> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
     </remarks>
@@ -50,7 +50,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.%23ctor%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.%23ctor%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -67,7 +67,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -109,7 +109,7 @@
 ## Remarks  
  This method is not intended to be called directly by application code. The members of the <xref:System.Diagnostics.Debug?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace?displayProperty=nameWithType>, and <xref:System.Diagnostics.TraceSource?displayProperty=nameWithType> classes use this method to write trace data.  
   
- <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -158,7 +158,7 @@
 ## Remarks  
  This method is not intended to be called directly by application code. The members of the <xref:System.Diagnostics.Debug?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace?displayProperty=nameWithType>, and <xref:System.Diagnostics.TraceSource?displayProperty=nameWithType> classes use this method to write trace data.  
   
- <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceData%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -175,7 +175,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -217,7 +217,7 @@
 ## Remarks  
  This method is not intended to be called directly by application code. The members of the <xref:System.Diagnostics.Debug?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace?displayProperty=nameWithType>, and <xref:System.Diagnostics.TraceSource?displayProperty=nameWithType> classes use this method to write trace data.  
   
- <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -268,7 +268,7 @@
 ## Remarks  
  This method is not intended to be called directly by application code. The members of the <xref:System.Diagnostics.Debug?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace?displayProperty=nameWithType>, and <xref:System.Diagnostics.TraceSource?displayProperty=nameWithType> classes use this method to write trace data.  
   
- <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.TraceEvent%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -285,7 +285,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.Write%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.Write%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -317,7 +317,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.Write%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.Write%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -353,7 +353,7 @@
 ## Remarks  
  This overload of the <xref:System.Web.IisTraceListener.Write%2A> method is provided for compatibility. This method does not use any values passed in the `category` parameter.  
   
- <xref:System.Web.IisTraceListener.Write%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.Write%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -394,7 +394,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.WriteLine%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.WriteLine%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
@@ -428,7 +428,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.IisTraceListener.WriteLine%2A> is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ <xref:System.Web.IisTraceListener.WriteLine%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web/RequestNotification.xml b/xml/System.Web/RequestNotification.xml
index d9fac3de4f0..da5853e51c8 100644
--- a/xml/System.Web/RequestNotification.xml
+++ b/xml/System.Web/RequestNotification.xml
@@ -27,7 +27,7 @@
 ## Remarks  
  The <xref:System.Web.RequestNotification> enumeration is used with the <xref:System.Web.HttpContext.CurrentNotification%2A> property of the <xref:System.Web.HttpContext> class to determine what event in the pipeline is currently processing. To determine when all the handlers for a specific event of the <xref:System.Web.HttpApplication> instance have finished processing, use the <xref:System.Web.HttpContext.IsPostNotification%2A> property.  
   
- The <xref:System.Web.RequestNotification> type is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
+ The <xref:System.Web.RequestNotification> type is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
    
   
diff --git a/xml/System/Activator.xml b/xml/System/Activator.xml
index 2112dacf37f..e636c9cbfca 100644
--- a/xml/System/Activator.xml
+++ b/xml/System/Activator.xml
@@ -156,7 +156,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -236,7 +236,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -392,7 +392,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -565,7 +565,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -664,7 +664,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -768,7 +768,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -976,7 +976,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1076,7 +1076,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1180,7 +1180,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1284,7 +1284,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1392,7 +1392,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1602,7 +1602,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to create nonpublic types and members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the assembly that contains the nonpublic types and members is restricted to the caller's grant set or to a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index 288be3919ec..e3b9792f9ce 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -3185,7 +3185,7 @@
   
  This method should be used only to define a dynamic assembly in the current application domain. For more information about this restriction, see the <xref:System.AppDomain.Load%28System.Reflection.AssemblyName%29> method overload.  
   
- This method overload is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)].  
+ This method overload is introduced in the .NET Framework 3.5.  
   
    
   
@@ -4210,7 +4210,7 @@
   
  If `isSynchronized` is `true`, the following methods of the resulting <xref:System.Reflection.Emit.AssemblyBuilder> will be synchronized: <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule%2A>, <xref:System.Reflection.Emit.AssemblyBuilder.DefineResource%2A>, <xref:System.Reflection.Emit.AssemblyBuilder.AddResourceFile%2A>, <xref:System.Reflection.Emit.AssemblyBuilder.GetDynamicModule%2A>, <xref:System.Reflection.Emit.AssemblyBuilder.SetEntryPoint%2A>, and <xref:System.Reflection.Emit.AssemblyBuilder.Save%2A>. If two of these methods are called on different threads, one will block until the other is completed.  
   
- This method overload is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)].  
+ This method overload is introduced in the .NET Framework 3.5.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index 6bcdac46e23..82317022361 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1224,7 +1224,7 @@
 ## Remarks  
  Disabling interface caching has a significant impact on the performance of interop calls.  
   
- This member is introduced in the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)].  
+ This member is introduced in the .NET Framework 3.5.  
   
  ]]></format>
         </remarks>
@@ -1262,7 +1262,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Major versions of the .NET Framework sometimes introduce breaking changes from the previous version. For example, the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] introduces a small number of breaking changes from the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]. Use the <xref:System.AppDomainSetup.SetCompatibilitySwitches%2A> method to specify that one or more of these breaking changes should be rolled back for the application domain, to make the behavior compatible with the previous version of the .NET Framework.  
+ Major versions of the .NET Framework sometimes introduce breaking changes from the previous version. For example, the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] introduces a small number of breaking changes from the .NET Framework 3.5. Use the <xref:System.AppDomainSetup.SetCompatibilitySwitches%2A> method to specify that one or more of these breaking changes should be rolled back for the application domain, to make the behavior compatible with the previous version of the .NET Framework.  
   
  Each time you call this method, it replaces the existing switch settings. To erase the settings, specify `null` for the `switches` parameter.  
   
diff --git a/xml/System/Delegate.xml b/xml/System/Delegate.xml
index 203b3cd96b8..643e3ce3890 100644
--- a/xml/System/Delegate.xml
+++ b/xml/System/Delegate.xml
@@ -611,7 +611,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
 ## Compatible Parameter Types and Return Type  
  In the .NET Framework version 2.0, the parameter types and return type of a delegate created using this method overload must be compatible with the parameter types and return type of the method the delegate represents; the types do not have to match exactly. This represents a relaxation of the binding behavior in the .NET Framework version 1.0 and 1.1, where the types must match exactly.  
@@ -773,7 +773,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
 ## Compatible Parameter Types and Return Type  
  The parameter types and return type of a delegate must be compatible with the parameter types and return type of the method the delegate represents; the types do not have to match exactly.  
@@ -960,7 +960,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1056,7 +1056,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
 ## Compatible Parameter Types and Return Type  
  The parameter types and return type of a delegate must be compatible with the parameter types and return type of the method the delegate represents; the types do not have to match exactly.  
@@ -1204,7 +1204,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1331,7 +1331,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
 ## Compatible Parameter Types and Return Type  
  The parameter types and return type of a delegate must be compatible with the parameter types and return type of the method the delegate represents; the types do not have to match exactly.  
@@ -1520,7 +1520,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1615,7 +1615,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1724,7 +1724,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -1825,7 +1825,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public methods if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public methods is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System/String.xml b/xml/System/String.xml
index b934d313f44..d8af161c50b 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -185,7 +185,7 @@ For more information about Unicode, UTF-16, code units, code points, and the <xr
 |----------------------------|-------------------------------------|
 |.NET Framework 1.1|[The Unicode Standard, Version 4.0.0](https://www.unicode.org/versions/Unicode4.0.0/)|
 |.NET Framework 2.0|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
-|[!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)]|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
+|.NET Framework 3.5|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 7|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 8 and later Windows operating systems|[The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/)|
diff --git a/xml/System/TimeZoneInfo.xml b/xml/System/TimeZoneInfo.xml
index 524148b842a..5ece37a135c 100644
--- a/xml/System/TimeZoneInfo.xml
+++ b/xml/System/TimeZoneInfo.xml
@@ -909,7 +909,7 @@
  If `dateTime` corresponds to an ambiguous local time, this method assumes that it is standard local time. If `dateTime` corresponds to an invalid local time, the method throws an <xref:System.ArgumentException>.  
   
 > [!NOTE]
->  If the current computer's local time zone includes multiple adjustment rules, this overload of the <xref:System.TimeZoneInfo.ConvertTimeToUtc%2A> method can return results that differ from the <xref:System.TimeZone.ToUniversalTime%2A?displayProperty=nameWithType> and <xref:System.DateTime.ToUniversalTime%2A?displayProperty=nameWithType> methods. <xref:System.TimeZone.ToUniversalTime%2A?displayProperty=nameWithType> always applies the current adjustment rule to time zone conversion, whether or not `dateTime` lies within its date range. And when executing on [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)], <xref:System.DateTime.ToUniversalTime%2A?displayProperty=nameWithType> also applies the current adjustment rule to time zone conversion, whether or not `dateTime` lies within its date range.  
+>  If the current computer's local time zone includes multiple adjustment rules, this overload of the <xref:System.TimeZoneInfo.ConvertTimeToUtc%2A> method can return results that differ from the <xref:System.TimeZone.ToUniversalTime%2A?displayProperty=nameWithType> and <xref:System.DateTime.ToUniversalTime%2A?displayProperty=nameWithType> methods. <xref:System.TimeZone.ToUniversalTime%2A?displayProperty=nameWithType> always applies the current adjustment rule to time zone conversion, whether or not `dateTime` lies within its date range. And when executing on .NET Framework 3.5, <xref:System.DateTime.ToUniversalTime%2A?displayProperty=nameWithType> also applies the current adjustment rule to time zone conversion, whether or not `dateTime` lies within its date range.  
   
  If the UTC equivalent of `dateTime` is earlier than <xref:System.DateTime.MinValue?displayProperty=nameWithType> or later that <xref:System.DateTime.MaxValue?displayProperty=nameWithType>, this method returns <xref:System.DateTime.MinValue> or <xref:System.DateTime.MaxValue>, respectively.  
   
diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 2f4d19e4f31..41fc556ed37 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -10362,7 +10362,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
    
   
@@ -10582,7 +10582,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
@@ -10802,7 +10802,7 @@ Type.GetType("System.Collections.Generic.Dictionary`2[System.String,[MyType,MyAs
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System/TypedReference.xml b/xml/System/TypedReference.xml
index 1d2f9d4f9a2..61c5d44a0d3 100644
--- a/xml/System/TypedReference.xml
+++ b/xml/System/TypedReference.xml
@@ -242,7 +242,7 @@
 > [!NOTE]
 >  Starting with the .NET Framework 2.0 Service Pack 1, this method can be used to access non-public members if the caller has been granted <xref:System.Security.Permissions.ReflectionPermission> with the <xref:System.Security.Permissions.ReflectionPermissionFlag.RestrictedMemberAccess?displayProperty=nameWithType> flag and if the grant set of the non-public members is restricted to the caller's grant set, or a subset thereof. (See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).)  
 >   
->  To use this functionality, your application should target the [!INCLUDE[net_v35_long](~/includes/net-v35-long-md.md)] or later.  
+>  To use this functionality, your application should target the .NET Framework 3.5 or later.  
   
  ]]></format>
         </remarks>

From 1952dae9511247506de069d5f35fcb07317490d1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:14:37 -0800
Subject: [PATCH 032/236] net-v35-short

---
 xml/System.Globalization/DateTimeFormatInfo.xml      |  2 +-
 xml/System.Globalization/NumberFormatInfo.xml        |  2 +-
 .../ReflectionPermissionFlag.xml                     |  2 +-
 xml/System.Web.Compilation/BuildManager.xml          |  4 ++--
 xml/System.Web.RegularExpressions/TagRegex.xml       |  2 +-
 xml/System.Windows.Markup/ParserContext.xml          |  2 +-
 .../UsableDuringInitializationAttribute.xml          |  2 +-
 xml/System.Windows.Markup/XamlParseException.xml     |  4 ++--
 xml/System.Windows.Markup/XamlReader.xml             |  2 +-
 xml/System.Windows.Markup/XmlAttributeProperties.xml |  2 +-
 xml/System.Workflow.Activities/ReceiveActivity.xml   |  2 +-
 xml/System.Workflow.Activities/SendActivity.xml      |  2 +-
 xml/System/AppDomain.xml                             |  6 +++---
 xml/System/AppDomainSetup.xml                        |  6 +++---
 xml/System/BadImageFormatException.xml               |  2 +-
 xml/System/ConsoleCancelEventArgs.xml                |  2 +-
 xml/System/DateTime.xml                              | 10 +++++-----
 xml/System/DateTimeOffset.xml                        | 10 +++++-----
 xml/System/String.xml                                | 12 ++++++------
 xml/System/TimeSpan.xml                              |  2 +-
 20 files changed, 39 insertions(+), 39 deletions(-)

diff --git a/xml/System.Globalization/DateTimeFormatInfo.xml b/xml/System.Globalization/DateTimeFormatInfo.xml
index bc584107bd3..658c56be10e 100644
--- a/xml/System.Globalization/DateTimeFormatInfo.xml
+++ b/xml/System.Globalization/DateTimeFormatInfo.xml
@@ -157,7 +157,7 @@
  [!code-vb[System.Globalization.DateTimeFormatInfo.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.datetimeformatinfo.class/vb/create1.vb#2)]  
   
 > [!NOTE]
->  In the .NET Framework versions 1.0 through [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], trying to retrieve a <xref:System.Globalization.DateTimeFormatInfo> object that  reflects the formatting conventions of a neutral culture throws a <xref:System.NotSupportedException> exception.  
+>  In the .NET Framework versions 1.0 through .NET Framework 3.5, trying to retrieve a <xref:System.Globalization.DateTimeFormatInfo> object that  reflects the formatting conventions of a neutral culture throws a <xref:System.NotSupportedException> exception.  
   
  However, a neutral culture lacks culture-specific formatting information, because it is independent of a specific country/region. Instead of populating the <xref:System.Globalization.DateTimeFormatInfo> object with generic values, the .NET Framework returns a <xref:System.Globalization.DateTimeFormatInfo> object that reflects the formatting conventions of a specific culture that is a child of the neutral culture. For example, the <xref:System.Globalization.DateTimeFormatInfo> object for the neutral en culture reflects the formatting conventions of the en-US culture, and the <xref:System.Globalization.DateTimeFormatInfo> object for the fr culture reflects the formatting conventions of the fr-FR culture.  
   
diff --git a/xml/System.Globalization/NumberFormatInfo.xml b/xml/System.Globalization/NumberFormatInfo.xml
index 4d57d6ab786..0a602e26bd0 100644
--- a/xml/System.Globalization/NumberFormatInfo.xml
+++ b/xml/System.Globalization/NumberFormatInfo.xml
@@ -177,7 +177,7 @@
  A neutral culture represents a culture or language that is independent of a country/region. It is typically the parent of one or more specific cultures. For example, fr is a neutral culture for the French language and the parent of the fr-FR culture. You create a <xref:System.Globalization.NumberFormatInfo> object that represents the formatting conventions of a neutral culture in the same way that you create a <xref:System.Globalization.NumberFormatInfo> object that represents the formatting conventions of a specific culture.  
   
 > [!NOTE]
->  In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, trying to retrieve a <xref:System.Globalization.NumberFormatInfo> object that reflects the formatting conventions of a neutral culture throws a <xref:System.NotSupportedException> exception.  
+>  In the .NET Framework 3.5 and earlier versions, trying to retrieve a <xref:System.Globalization.NumberFormatInfo> object that reflects the formatting conventions of a neutral culture throws a <xref:System.NotSupportedException> exception.  
   
  However, because it is independent of a specific country/region, a neutral culture lacks culture-specific formatting information. Rather than populating the <xref:System.Globalization.NumberFormatInfo> object with generic values, the .NET Framework returns a <xref:System.Globalization.NumberFormatInfo> object that reflects the formatting conventions of a specific culture that is a child of the neutral culture. For example, the <xref:System.Globalization.NumberFormatInfo> object for the neutral en culture reflects the formatting conventions of the en-US culture, and the <xref:System.Globalization.NumberFormatInfo> object for the fr culture reflects the formatting conventions of the fr-FR culture.  
   
diff --git a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
index 9d09b54bd6d..007a8570e47 100644
--- a/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
+++ b/xml/System.Security.Permissions/ReflectionPermissionFlag.xml
@@ -61,7 +61,7 @@
 > [!IMPORTANT]
 >  `AllFlags` does not include the `RestrictedMemberAccess` flag. To get a mask that includes all flags in this enumeration, you must use the combination of `AllFlags` with `RestrictedMemberAccess`.  
   
- Starting with the .NET Framework 2.0 SP1, the `ReflectionEmit` flag is no longer required to emit code, unless debug symbols are emitted. To use this feature, your application should target the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] or later.  
+ Starting with the .NET Framework 2.0 SP1, the `ReflectionEmit` flag is no longer required to emit code, unless debug symbols are emitted. To use this feature, your application should target the .NET Framework 3.5 or later.  
   
  Starting with the .NET Framework 2.0, the `TypeInformation` flag is no longer required to reflect on nonpublic types and members; the flag has been marked obsolete.  
   
diff --git a/xml/System.Web.Compilation/BuildManager.xml b/xml/System.Web.Compilation/BuildManager.xml
index 7ae8a043e69..678c9089669 100644
--- a/xml/System.Web.Compilation/BuildManager.xml
+++ b/xml/System.Web.Compilation/BuildManager.xml
@@ -753,14 +753,14 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property supports the ASP.NET multi-targeting feature, which enables you to use the latest version of Visual Studio to develop applications that will run with earlier versions of the .NET Framework. A build provider can use this property to make sure that the provider generates code that is appropriate for the targeted version of the .NET Framework. For example, you might want to generate different code depending on whether a Web site targets the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] or the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information about multi-targeting, see [.NET Framework Multi-Targeting for ASP.NET Web Projects](https://docs.microsoft.com/previous-versions/aspnet/bb398791(v=vs.100)).  
+ This property supports the ASP.NET multi-targeting feature, which enables you to use the latest version of Visual Studio to develop applications that will run with earlier versions of the .NET Framework. A build provider can use this property to make sure that the provider generates code that is appropriate for the targeted version of the .NET Framework. For example, you might want to generate different code depending on whether a Web site targets the .NET Framework 3.5 or the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information about multi-targeting, see [.NET Framework Multi-Targeting for ASP.NET Web Projects](https://docs.microsoft.com/previous-versions/aspnet/bb398791(v=vs.100)).  
   
  If the Web site does not have a Web.config file, ASP.NET assumes that the target framework version is the version that is associated with the IIS application pool that the site is running under. For a file-system Web site that is running in Visual Studio, the default framework version is the current version of the .NET Framework.  
   
  If the Web site does have a Web.config file, ASP.NET determines the target framework by examining the Web.config file.  
   
 ## Web Sites that Target the .NET Framework 2.0  
- Web applications that target the .NET Framework 2.0 are compiled as if the target were the .NET Framework 3.0. The build process does not differentiate between the .NET Framework 2.0 and the .NET Framework 3.0 because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the .NET Framework 3.0.  
+ Web applications that target the .NET Framework 2.0 are compiled as if the target were the .NET Framework 3.0. The build process does not differentiate between the .NET Framework 2.0 and the .NET Framework 3.0 because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the .NET Framework 3.5, the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the .NET Framework 3.0.  
   
  This normally will not cause any problems. Visual Studio prevents you from creating references to .NET Framework 3.0 features in a project that is targeted for the .NET Framework 2.0. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for .NET Framework 2.0, because WCF was introduced with the .NET Framework 3.0 and is not compatible with the .NET Framework 2.0.  
   
diff --git a/xml/System.Web.RegularExpressions/TagRegex.xml b/xml/System.Web.RegularExpressions/TagRegex.xml
index 00db40380de..ae373020b61 100644
--- a/xml/System.Web.RegularExpressions/TagRegex.xml
+++ b/xml/System.Web.RegularExpressions/TagRegex.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.RegularExpressions.TagRegex> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex35?displayProperty=nameWithType> class for applications that target the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions.  
+ The <xref:System.Web.RegularExpressions.TagRegex> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex35?displayProperty=nameWithType> class for applications that target the .NET Framework 3.5 and earlier versions.  
   
 > [!NOTE]
 >  The <xref:System.Web.RegularExpressions> classes are used internally by the .NET Framework to parse ASP.NET pages.  
diff --git a/xml/System.Windows.Markup/ParserContext.xml b/xml/System.Windows.Markup/ParserContext.xml
index 6dc2b1f30c9..ed0336a3611 100644
--- a/xml/System.Windows.Markup/ParserContext.xml
+++ b/xml/System.Windows.Markup/ParserContext.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The XAML parser that this context refers to is the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] era XAML parser API that is specific to the WPF implementation, as exposed in <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType>.  
+ The XAML parser that this context refers to is the .NET Framework 3.5 era XAML parser API that is specific to the WPF implementation, as exposed in <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType>.  
   
  The XAML system in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] uses a more sophisticated XAML type system and thus also uses a different type of context for XAML processing operations. For more information, see <xref:System.Xaml.XamlSchemaContext>.  
   
diff --git a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
index 047f2fb0858..b39152b9f33 100644
--- a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
+++ b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
@@ -39,7 +39,7 @@
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.UsableDuringInitializationAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- In WPF XAML for .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)], top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
+ In WPF XAML for .NET Framework 3.0 and .NET Framework 3.5, top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XamlParseException.xml b/xml/System.Windows.Markup/XamlParseException.xml
index 7bb729680dd..ff6f5d45309 100644
--- a/xml/System.Windows.Markup/XamlParseException.xml
+++ b/xml/System.Windows.Markup/XamlParseException.xml
@@ -28,11 +28,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Markup.XamlParseException> is used only for the WPF-implemented XAML parser that performs the XAML parsing and loading for WPF applications. Specifically, the exception is only relevant when an application targets .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. The exception can also originate from user code in run-time calls to APIs that hook up the WPF-implemented XAML parser to load XAML from within a running WPF application (for example, calls to <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>).  
+ <xref:System.Windows.Markup.XamlParseException> is used only for the WPF-implemented XAML parser that performs the XAML parsing and loading for WPF applications. Specifically, the exception is only relevant when an application targets .NET Framework 3.0 and .NET Framework 3.5. The exception can also originate from user code in run-time calls to APIs that hook up the WPF-implemented XAML parser to load XAML from within a running WPF application (for example, calls to <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>).  
   
  For [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Xaml.XamlParseException> exception that typically reports XAML processing exceptions is defined in a different namespace (<xref:System.Xaml>) and a different assembly (System.Xaml).  
   
- Unless you are writing an equivalent to the WPF XAML parser or working with .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] targeting, you generally will not throw <xref:System.Windows.Markup.XamlParseException> from your own code. However, handling for the exception is sometimes necessary. For application scenarios, where you may want to suppress XAML parse errors, a <xref:System.Windows.Threading.Dispatcher> <xref:System.Windows.Threading.Dispatcher.UnhandledException> event handler at the application level is one way to handle a run-time <xref:System.Windows.Markup.XamlParseException>. Whether to suppress exceptions or let them surface to user code depends on how you design your application for purposes of loading XAML, and the trust level that you assign to the XAML your application loads. For more information, see [XAML Security Considerations](/dotnet/framework/xaml-services/xaml-security-considerations) or "XAML Security" section of [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+ Unless you are writing an equivalent to the WPF XAML parser or working with .NET Framework 3.0 and .NET Framework 3.5 targeting, you generally will not throw <xref:System.Windows.Markup.XamlParseException> from your own code. However, handling for the exception is sometimes necessary. For application scenarios, where you may want to suppress XAML parse errors, a <xref:System.Windows.Threading.Dispatcher> <xref:System.Windows.Threading.Dispatcher.UnhandledException> event handler at the application level is one way to handle a run-time <xref:System.Windows.Markup.XamlParseException>. Whether to suppress exceptions or let them surface to user code depends on how you design your application for purposes of loading XAML, and the trust level that you assign to the XAML your application loads. For more information, see [XAML Security Considerations](/dotnet/framework/xaml-services/xaml-security-considerations) or "XAML Security" section of [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  For pages of an application, when the <xref:System.Windows.Markup.XamlParseException> is thrown, it is usually in the context of the `InitializeComponent` call made by your page class, which is the entry point for the WPF application model's usage of the WPF XAML parser at the per-page level. Therefore another possible handling strategy is to place `try/catch` blocks in `InitializeComponent`. However, this technique does not integrate well with templates, visual design surfaces and other generated sources that hook up `InitializeComponent`.  
   
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index 000129c5bfa..a650481c95e 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -57,7 +57,7 @@
 -   If you are not relying on any WPF types or the BAML form of XAML, and are not using another specific technology's XAML reader or XAML writer implementation for reasons that are specific to that framework, use the System.Xaml XAML readers and XAML writers.  
   
 ## System.Xaml Backing Implementation in .NET 4  
- <xref:System.Windows.Markup.XamlReader> is the callable API surface for the WPF framework-level XAML parser. The same underlying XAML parser also performs the run-time XAML loading and parsing for WPF applications that target .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)].  
+ <xref:System.Windows.Markup.XamlReader> is the callable API surface for the WPF framework-level XAML parser. The same underlying XAML parser also performs the run-time XAML loading and parsing for WPF applications that target .NET Framework 3.0 and .NET Framework 3.5.  
   
  If you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the external API is the same, but parts of the implementation are built on the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] general XAML implementation in the System.Xaml assembly, which improves many of the technical and reporting aspects of parsing XAML. Targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] necessarily entails including System.Xaml as a reference, and details of implementation such as the exceptions reported may come from System.Xaml defined types.  
   
diff --git a/xml/System.Windows.Markup/XmlAttributeProperties.xml b/xml/System.Windows.Markup/XmlAttributeProperties.xml
index 0b0fb5b5acc..b987262d6d4 100644
--- a/xml/System.Windows.Markup/XmlAttributeProperties.xml
+++ b/xml/System.Windows.Markup/XmlAttributeProperties.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  This class implements attached property support for <xref:System.Windows.Markup.XmlAttributeProperties.XmlNamespaceMaps%2A>, <xref:System.Windows.Markup.XmlAttributeProperties.XmlnsDefinition%2A>, and <xref:System.Windows.Markup.XmlAttributeProperties.XmlnsDictionary%2A> and <xref:System.Windows.Markup.XmlAttributeProperties.XmlSpace%2A>.  
   
- These properties are generally only used by the WPF XAML parser implementation for .NET Framework 3.0 and [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. Actual user code attached property calls from XAML markup is not the primary scenario. The properties are implemented as attached properties primarily so that the properties can better support the property inheritance concept for dependency properties through all possible object graphs. As such, this is really an infrastructure support class. For more information, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
+ These properties are generally only used by the WPF XAML parser implementation for .NET Framework 3.0 and .NET Framework 3.5. Actual user code attached property calls from XAML markup is not the primary scenario. The properties are implemented as attached properties primarily so that the properties can better support the property inheritance concept for dependency properties through all possible object graphs. As such, this is really an infrastructure support class. For more information, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Workflow.Activities/ReceiveActivity.xml b/xml/System.Workflow.Activities/ReceiveActivity.xml
index 7869f4466af..2a0f3093dc0 100644
--- a/xml/System.Workflow.Activities/ReceiveActivity.xml
+++ b/xml/System.Workflow.Activities/ReceiveActivity.xml
@@ -73,7 +73,7 @@
 >  To ensure that persistence performs properly and does not persist transient messages, make sure that child activities of the <xref:System.Workflow.Activities.ReceiveActivity> do not persist by themselves. This can occur if the child activities go idle when a persistence provider was created with `UnloadOnIdle` set to `true`, for instance.  
   
 > [!NOTE]
->  This activity is part of [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Receive>.  
+>  This activity is part of .NET Framework 3.5. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Receive>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Workflow.Activities/SendActivity.xml b/xml/System.Workflow.Activities/SendActivity.xml
index 10470d77167..df20d376f4e 100644
--- a/xml/System.Workflow.Activities/SendActivity.xml
+++ b/xml/System.Workflow.Activities/SendActivity.xml
@@ -62,7 +62,7 @@
      The <xref:System.Workflow.Activities.SendActivity> activity sends a message and waits until a response or a fault is received from the service. During execution, the send activity throws all of the faults that were received from the server. <xref:System.Workflow.ComponentModel.FaultHandlerActivity> activities can be used to handle the faults in the client workflow.  
   
 > [!NOTE]
->  This activity is part of [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)]. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Send>.  
+>  This activity is part of .NET Framework 3.5. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Send>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index e3b9792f9ce..062b1c28c77 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -6160,10 +6160,10 @@
   
 |Switch|Meaning|  
 |------------|-------------|  
-|"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
-|"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] are enabled in this application domain. Its success requires sort00001000.dll to be installed. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
+|"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the .NET Framework 3.5 is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
+|"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the .NET Framework 3.5 are enabled in this application domain. Its success requires sort00001000.dll to be installed. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
 |"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and Unicode 5.0 are enabled in this application domain. Its success requires sort00060101.dll to be installed.|  
-|"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] is enabled in this application domain.  See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
+|"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the .NET Framework 3.5 is enabled in this application domain.  See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
 |"UseRandomizedStringHashAlgorithm"|The runtime calculates hash codes for strings on a per application domain basis instead of using a single hashing algorithm that produces a consistent hash code across application domains. See [&lt;UseRandomizedStringHashAlgorithm&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/userandomizedstringhashalgorithm-element).|  
   
  ]]></format>
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index 82317022361..aa59f72490a 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1272,10 +1272,10 @@
   
 |Switch|Meaning|  
 |------------|-------------|  
-|"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
-|"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00001000.dll dynamic link library to be available on the local system. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
+|"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the .NET Framework 3.5 is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
+|"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the .NET Framework 3.5 are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00001000.dll dynamic link library to be available on the local system. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
 |"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and Unicode 5.0 are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00060101.dll dynamic link library to be available on the local system.|  
-|"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] is enabled in this application domain. See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
+|"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the .NET Framework 3.5 is enabled in this application domain. See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
 |"UseRandomizedStringHashAlgorithm"|The runtime calculates hash codes for strings on a per application domain basis instead of using a single hashing algorithm that produces a consistent hash code across application domains. See [&lt;UseRandomizedStringHashAlgorithm&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/userandomizedstringhashalgorithm-element).|  
   
  ]]></format>
diff --git a/xml/System/BadImageFormatException.xml b/xml/System/BadImageFormatException.xml
index 16b6175caa1..6464b7917ba 100644
--- a/xml/System/BadImageFormatException.xml
+++ b/xml/System/BadImageFormatException.xml
@@ -81,7 +81,7 @@
 
      To address this exception, set the project's **Platform target** property to x86 (instead of x64 or AnyCPU) and recompile.
 
--   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the .NET Framework 2.0 SP1 or later, or when an application that was developed using the .NET Framework 2.0 SP1 or [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
+-   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the .NET Framework 2.0 SP1 or later, or when an application that was developed using the .NET Framework 2.0 SP1 or .NET Framework 3.5 tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
 
      [!code-csharp[System.BadImageFormatException.Class#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/stringlib.cs#2)]
      [!code-vb[System.BadImageFormatException.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/stringlib.vb#2)]
diff --git a/xml/System/ConsoleCancelEventArgs.xml b/xml/System/ConsoleCancelEventArgs.xml
index c2dad88bbca..8b464f099cf 100644
--- a/xml/System/ConsoleCancelEventArgs.xml
+++ b/xml/System/ConsoleCancelEventArgs.xml
@@ -114,7 +114,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
+          <para>In the .NET Framework 3.5 and [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
         </block>
         <altmember cref="T:System.ConsoleCancelEventHandler" />
         <altmember cref="T:System.ConsoleKey" />
diff --git a/xml/System/DateTime.xml b/xml/System/DateTime.xml
index 8a631a5faf3..b0db6e776ec 100644
--- a/xml/System/DateTime.xml
+++ b/xml/System/DateTime.xml
@@ -5560,7 +5560,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
   
  The hour component and the AM/PM designator in <paramref name="s" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -5765,7 +5765,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
         <exception cref="T:System.ArgumentException">
           <paramref name="style" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values. For example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -5891,7 +5891,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
         <exception cref="T:System.ArgumentException">
           <paramref name="style" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values. For example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -8949,7 +8949,7 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
   
  <paramref name="styles" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values (for example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />).</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.ParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -9065,7 +9065,7 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
   
  <paramref name="styles" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values (for example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />).</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.ParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
diff --git a/xml/System/DateTimeOffset.xml b/xml/System/DateTimeOffset.xml
index 2e3e926263b..981d8e7e11b 100644
--- a/xml/System/DateTimeOffset.xml
+++ b/xml/System/DateTimeOffset.xml
@@ -3891,7 +3891,7 @@ The following example parses an array of strings that are expected to conform to
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -4192,7 +4192,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -4317,7 +4317,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -6160,7 +6160,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  <paramref name="styles" /> includes mutually exclusive <see cref="T:System.Globalization.DateTimeStyles" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.ParseExact" />
       </Docs>
@@ -6271,7 +6271,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  <paramref name="styles" /> includes mutually exclusive <see cref="T:System.Globalization.DateTimeStyles" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System/String.xml b/xml/System/String.xml
index d8af161c50b..69d6227c8d8 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -11272,7 +11272,7 @@ The following example demonstrates how to extract individual words from a block
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.Concat(System.Object)" />
@@ -11413,7 +11413,7 @@ The following table shows some examples.
         <exception cref="T:System.ArgumentOutOfRangeException">
           <paramref name="count" /> is negative.</exception>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="T:System.Array" />
@@ -11532,7 +11532,7 @@ To pass `null` for the `char[] separator` parameter, you must indicate the type
         <exception cref="T:System.ArgumentException">
           <paramref name="options" /> is not one of the <see cref="T:System.StringSplitOptions" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
       </Docs>
     </Member>
@@ -11697,7 +11697,7 @@ Note that the method is called with the `options` argument set to <xref:System.S
         <exception cref="T:System.ArgumentException">
           <paramref name="options" /> is not one of the <see cref="T:System.StringSplitOptions" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
       </Docs>
     </Member>
@@ -11845,7 +11845,7 @@ The following example uses the <xref:System.StringSplitOptions> enumeration to i
         <exception cref="T:System.ArgumentException">
           <paramref name="options" /> is not one of the <see cref="T:System.StringSplitOptions" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
       </Docs>
     </Member>
@@ -12010,7 +12010,7 @@ The following example uses the <xref:System.StringSplitOptions> enumeration to i
         <exception cref="T:System.ArgumentException">
           <paramref name="options" /> is not one of the <see cref="T:System.StringSplitOptions" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
+          <para>In .NET Framework 3.5 and earlier versions, if the <see cref="M:System.String.Split(System.Char[])" /> method is passed a <paramref name="separator" /> that is <see langword="null" /> or contains no characters, the method uses a slightly different set of white-space characters to split the string than the <see cref="M:System.String.Trim(System.Char[])" /> method does to trim the string. Starting with .NET Framework 4, both methods use an identical set of Unicode white-space characters.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System/TimeSpan.xml b/xml/System/TimeSpan.xml
index 911ba1ba0b5..29488d9cdef 100644
--- a/xml/System/TimeSpan.xml
+++ b/xml/System/TimeSpan.xml
@@ -131,7 +131,7 @@
  Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.TimeSpan> structure supports culture-sensitive formatting through the overloads of its <xref:System.TimeSpan.ToString%2A> method, which converts a <xref:System.TimeSpan> value to its string representation. The default <xref:System.TimeSpan.ToString?displayProperty=nameWithType> method returns a time interval by using an invariant format that is identical to its return value in previous versions of the .NET Framework. The <xref:System.TimeSpan.ToString%28System.String%29?displayProperty=nameWithType> overload lets you specify a format string that defines the string representation of the time interval. The <xref:System.TimeSpan.ToString%28System.String%2CSystem.IFormatProvider%29?displayProperty=nameWithType> overload lets you specify a format string and the culture whose formatting conventions are used to create the string representation of the time interval. <xref:System.TimeSpan> supports both standard and custom format strings. (For more information, see [Standard TimeSpan Format Strings](/dotnet/standard/base-types/standard-timespan-format-strings) and [Custom TimeSpan Format Strings](/dotnet/standard/base-types/custom-timespan-format-strings).) However, only standard format strings are culture-sensitive.  
   
 ## Restoring Legacy TimeSpan Formatting  
- In some cases, code that successfully formats <xref:System.TimeSpan> values in [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions fails in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. This is most common in code that calls a [<TimeSpan_LegacyFormatMode> element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) method to format a <xref:System.TimeSpan> value with a format string. The following example successfully formats a <xref:System.TimeSpan> value in [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions, but throws an exception in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions. Note that it attempts to format a <xref:System.TimeSpan> value by using an unsupported format specifier, which is ignored in [!INCLUDE[net_v35_short](~/includes/net-v35-short-md.md)] and earlier versions.  
+ In some cases, code that successfully formats <xref:System.TimeSpan> values in .NET Framework 3.5 and earlier versions fails in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. This is most common in code that calls a [<TimeSpan_LegacyFormatMode> element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) method to format a <xref:System.TimeSpan> value with a format string. The following example successfully formats a <xref:System.TimeSpan> value in .NET Framework 3.5 and earlier versions, but throws an exception in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions. Note that it attempts to format a <xref:System.TimeSpan> value by using an unsupported format specifier, which is ignored in .NET Framework 3.5 and earlier versions.  
   
  [!code-csharp-interactive[System.TimeSpan.Class.Legacy#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.timespan.class.legacy/cs/legacycode1.cs#1)]
  [!code-vb[System.TimeSpan.Class.Legacy#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.timespan.class.legacy/vb/legacycode1.vb#1)]  

From 4717b7475569f53e65950caad956d2cb77789ee0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:15:12 -0800
Subject: [PATCH 033/236] net-v35sp1-long

---
 .../CompatibleFramework.xml                   |  2 +-
 xml/System.Text/StringBuilder.xml             | 26 +++++++++----------
 .../ContentPresenter.xml                      |  2 +-
 xml/System/String.xml                         |  2 +-
 4 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
index c56387fd905..56f7e5e49ff 100644
--- a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
+++ b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], and the .NET Framework 4 Client Profile is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
+ A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the .NET Framework 3.5 Service Pack 1, and the .NET Framework 4 Client Profile is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Text/StringBuilder.xml b/xml/System.Text/StringBuilder.xml
index 7ea94488b54..38e7a4203ab 100644
--- a/xml/System.Text/StringBuilder.xml
+++ b/xml/System.Text/StringBuilder.xml
@@ -4229,7 +4229,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Boolean" />
       </Docs>
@@ -4289,7 +4289,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Byte" />
       </Docs>
@@ -4477,7 +4477,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Decimal" />
       </Docs>
@@ -4537,7 +4537,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Double" />
       </Docs>
@@ -4597,7 +4597,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int16" />
       </Docs>
@@ -4657,7 +4657,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int32" />
       </Docs>
@@ -4717,7 +4717,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int64" />
       </Docs>
@@ -4780,7 +4780,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Object" />
       </Docs>
@@ -4890,7 +4890,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.SByte" />
       </Docs>
@@ -4950,7 +4950,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Single" />
       </Docs>
@@ -5085,7 +5085,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt16" />
       </Docs>
@@ -5152,7 +5152,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt32" />
       </Docs>
@@ -5218,7 +5218,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)] and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt64" />
       </Docs>
diff --git a/xml/System.Windows.Controls/ContentPresenter.xml b/xml/System.Windows.Controls/ContentPresenter.xml
index bc4bd7a929b..2b243679c09 100644
--- a/xml/System.Windows.Controls/ContentPresenter.xml
+++ b/xml/System.Windows.Controls/ContentPresenter.xml
@@ -248,7 +248,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property should only be used when the <xref:System.Windows.Controls.ContentPresenter> is in a template. When a template contains a <xref:System.Windows.Controls.ContentPresenter> with <xref:System.Windows.Controls.ContentPresenter.ContentSource%2A> set to "`Abc`", the <xref:System.Windows.Controls.ContentPresenter.Content%2A>, <xref:System.Windows.Controls.ContentPresenter.ContentTemplate%2A>, and <xref:System.Windows.Controls.ContentPresenter.ContentTemplateSelector%2A> properties of the <xref:System.Windows.Controls.ContentPresenter> are automatically aliased to `Abc`, `AbcTemplate`, and `AbcTemplateSelector`, respectively.  Beginning with the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], setting <xref:System.Windows.Controls.ContentPresenter.ContentSource%2A> to "`Abc`" also causes the <xref:System.Windows.Controls.ContentPresenter.ContentStringFormat%2A> property to be aliased to `AbcStringFormat`.  
+ This property should only be used when the <xref:System.Windows.Controls.ContentPresenter> is in a template. When a template contains a <xref:System.Windows.Controls.ContentPresenter> with <xref:System.Windows.Controls.ContentPresenter.ContentSource%2A> set to "`Abc`", the <xref:System.Windows.Controls.ContentPresenter.Content%2A>, <xref:System.Windows.Controls.ContentPresenter.ContentTemplate%2A>, and <xref:System.Windows.Controls.ContentPresenter.ContentTemplateSelector%2A> properties of the <xref:System.Windows.Controls.ContentPresenter> are automatically aliased to `Abc`, `AbcTemplate`, and `AbcTemplateSelector`, respectively.  Beginning with the .NET Framework 3.5 Service Pack 1, setting <xref:System.Windows.Controls.ContentPresenter.ContentSource%2A> to "`Abc`" also causes the <xref:System.Windows.Controls.ContentPresenter.ContentStringFormat%2A> property to be aliased to `AbcStringFormat`.  
   
  The two most useful values for this property are "Content" and "Header".  
   
diff --git a/xml/System/String.xml b/xml/System/String.xml
index 69d6227c8d8..66dc2137c71 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -7869,7 +7869,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
 
 ## Version considerations
 
- In the [!INCLUDE[net_v35SP1_long](~/includes/net-v35sp1-long-md.md)], the <xref:System.String.Intern%2A> method reverts to its behavior in .NET Framework 1.0 and 1.1 with regard to interning the empty string. In the following example, the variable `str1` is assigned a reference to <xref:System.String.Empty?displayProperty=nameWithtype>, and the variable `str2` is assigned the reference to <xref:System.String.Empty?displayProperty=nameWithtype> that is returned by calling the <xref:System.String.Intern%2A> method after converting a <xref:System.Text.StringBuilder> object whose value is <xref:System.String.Empty?displayProperty=nameWithtype> to a string. Then the references contained in `str1` and `str2` are compared for equality.
+ In the .NET Framework 3.5 Service Pack 1, the <xref:System.String.Intern%2A> method reverts to its behavior in .NET Framework 1.0 and 1.1 with regard to interning the empty string. In the following example, the variable `str1` is assigned a reference to <xref:System.String.Empty?displayProperty=nameWithtype>, and the variable `str2` is assigned the reference to <xref:System.String.Empty?displayProperty=nameWithtype> that is returned by calling the <xref:System.String.Intern%2A> method after converting a <xref:System.Text.StringBuilder> object whose value is <xref:System.String.Empty?displayProperty=nameWithtype> to a string. Then the references contained in `str1` and `str2` are compared for equality.
 
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Intern/cs/Intern2.cs" interactive="try-dotnet-method" id="Snippet2":::
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Intern/vb/Intern2.vb" id="Snippet2":::

From 56e5bbf1974c14fdf1668fce4af7a0597086b385 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:15:57 -0800
Subject: [PATCH 034/236] net-v35sp1-short

---
 xml/System.Web.RegularExpressions/TagRegex35.xml | 2 +-
 xml/System/String.xml                            | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Web.RegularExpressions/TagRegex35.xml b/xml/System.Web.RegularExpressions/TagRegex35.xml
index c6b7148ef11..dec22b982b5 100644
--- a/xml/System.Web.RegularExpressions/TagRegex35.xml
+++ b/xml/System.Web.RegularExpressions/TagRegex35.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.RegularExpressions.TagRegex35> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex?displayProperty=nameWithType> class for applications that target the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions.  
+ The <xref:System.Web.RegularExpressions.TagRegex35> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the .NET Framework 3.5 SP1 and earlier versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex?displayProperty=nameWithType> class for applications that target the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions.  
   
 > [!NOTE]
 >  The <xref:System.Web.RegularExpressions> classes are used internally by the .NET Framework to parse ASP.NET pages.  
diff --git a/xml/System/String.xml b/xml/System/String.xml
index 66dc2137c71..8210ae23429 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -14477,7 +14477,7 @@ The following example uses the <xref:System.String.Trim?displayProperty=nameWith
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions maintain an internal list of white-space characters that this method trims. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintain an internal list of white-space characters that this method trims. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="M:System.String.TrimEnd(System.Char[])" />
         <altmember cref="M:System.String.TrimStart(System.Char[])" />
@@ -14612,7 +14612,7 @@ The following example uses the `Trim(System.Char[])` method to remove space, ast
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.TrimEnd(System.Char[])" />
@@ -14784,7 +14784,7 @@ The following example demonstrates how you can use the `TrimEnd(System.Char[])`
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.Trim(System.Char[])" />
@@ -14966,7 +14966,7 @@ The following example then illustrates a call to the `StripComments` method.
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v35SP1_short](~/includes/net-v35sp1-short-md.md)] and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.Trim(System.Char[])" />

From c65e1cf1f1f8326506312487e2acff80ef3bf1fc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:19:47 -0800
Subject: [PATCH 035/236] net-v40-long

---
 xml/Microsoft.Win32/Registry.xml              |  4 +--
 xml/Microsoft.Win32/RegistryKey.xml           |  2 +-
 xml/Microsoft.Win32/RegistryValueKind.xml     |  2 +-
 xml/System.Collections.Generic/HashSet`1.xml  |  2 +-
 xml/System.ComponentModel/TypeConverter.xml   |  4 +--
 .../ConfigurationProperty.xml                 |  2 +-
 .../ConfigurationSection.xml                  |  6 ++---
 .../ConfigurationSectionGroup.xml             |  2 +-
 xml/System.Data.SqlClient/SqlConnection.xml   |  2 +-
 .../CompatibleFramework.xml                   |  2 +-
 xml/System.Diagnostics/Debugger.xml           |  2 +-
 xml/System.Globalization/CharUnicodeInfo.xml  |  2 +-
 xml/System.Globalization/CultureInfo.xml      | 22 ++++++++--------
 .../AssemblyBuilder.xml                       |  2 +-
 xml/System.Reflection.Emit/FieldBuilder.xml   |  2 +-
 xml/System.Reflection.Emit/ILGenerator.xml    |  4 +--
 .../ParameterBuilder.xml                      |  2 +-
 .../PropertyBuilder.xml                       |  2 +-
 xml/System.Reflection/Assembly.xml            | 10 +++----
 xml/System.Reflection/AssemblyName.xml        |  4 +--
 ...ocessCorruptedStateExceptionsAttribute.xml |  2 +-
 .../RuntimeEnvironment.xml                    |  2 +-
 .../TargetFrameworkAttribute.xml              |  4 +--
 .../EnvironmentPermission.xml                 |  2 +-
 .../FileIOPermission.xml                      |  2 +-
 .../GacIdentityPermission.xml                 |  2 +-
 .../GacIdentityPermissionAttribute.xml        |  2 +-
 .../PublisherIdentityPermission.xml           |  2 +-
 .../PublisherIdentityPermissionAttribute.xml  |  2 +-
 .../RegistryPermission.xml                    |  2 +-
 .../SecurityAction.xml                        |  2 +-
 .../SiteIdentityPermission.xml                |  4 +--
 .../SiteIdentityPermissionAttribute.xml       |  2 +-
 .../StrongNameIdentityPermission.xml          |  2 +-
 .../StrongNameIdentityPermissionAttribute.xml |  2 +-
 .../UrlIdentityPermission.xml                 |  4 +--
 .../UrlIdentityPermissionAttribute.xml        |  2 +-
 .../ZoneIdentityPermission.xml                |  2 +-
 .../ZoneIdentityPermissionAttribute.xml       |  2 +-
 xml/System.Security.Policy/EvidenceBase.xml   |  2 +-
 .../IApplicationTrustManager.xml              |  2 +-
 xml/System.Security.Policy/PolicyLevel.xml    |  2 +-
 .../AllowPartiallyTrustedCallersAttribute.xml |  2 +-
 xml/System.Security/HostSecurityManager.xml   |  2 +-
 .../SecurityCriticalAttribute.xml             |  2 +-
 xml/System.Security/SecurityManager.xml       | 20 +++++++-------
 xml/System.Security/SecurityRuleSet.xml       |  2 +-
 xml/System.Text/StringBuilder.xml             | 26 +++++++++----------
 xml/System.Threading.Tasks/TaskScheduler.xml  |  2 +-
 .../CancellationTokenSource.xml               |  2 +-
 xml/System.Threading/Monitor.xml              |  2 +-
 xml/System.Threading/Thread.xml               |  6 ++---
 xml/System.Threading/ThreadPool.xml           |  2 +-
 .../HttpRuntimeSection.xml                    |  2 +-
 .../TagRegex.xml                              |  2 +-
 xml/System.Windows.Forms/SplitContainer.xml   |  2 +-
 .../AmbientAttribute.xml                      |  2 +-
 .../ConstructorArgumentAttribute.xml          |  2 +-
 .../ContentWrapperAttribute.xml               |  2 +-
 .../DateTimeValueSerializer.xml               |  2 +-
 .../DependsOnAttribute.xml                    |  2 +-
 .../DictionaryKeyPropertyAttribute.xml        |  2 +-
 .../IComponentConnector.xml                   |  2 +-
 xml/System.Windows.Markup/INameScope.xml      |  2 +-
 .../IProvideValueTarget.xml                   |  2 +-
 .../IReceiveMarkupExtension.xml               |  2 +-
 xml/System.Windows.Markup/IUriContext.xml     |  2 +-
 .../IValueSerializerContext.xml               |  2 +-
 .../IXamlTypeResolver.xml                     |  2 +-
 .../MarkupExtensionReturnTypeAttribute.xml    |  2 +-
 .../NameScopePropertyAttribute.xml            |  2 +-
 xml/System.Windows.Markup/NullExtension.xml   |  2 +-
 .../RootNamespaceAttribute.xml                |  2 +-
 .../RuntimeNamePropertyAttribute.xml          |  2 +-
 .../TrimSurroundingWhitespaceAttribute.xml    |  2 +-
 .../UsableDuringInitializationAttribute.xml   |  2 +-
 xml/System.Windows.Markup/ValueSerializer.xml |  2 +-
 .../ValueSerializerAttribute.xml              |  2 +-
 ...itespaceSignificantCollectionAttribute.xml |  2 +-
 .../XmlLangPropertyAttribute.xml              |  2 +-
 .../XmlnsCompatibleWithAttribute.xml          |  2 +-
 .../XmlnsDefinitionAttribute.xml              |  2 +-
 .../XmlnsPrefixAttribute.xml                  |  2 +-
 xml/System/AppDomain.xml                      | 24 ++++++++---------
 xml/System/AppDomainManager.xml               |  2 +-
 xml/System/AppDomainSetup.xml                 |  4 +--
 xml/System/Char.xml                           |  6 ++---
 xml/System/Console.xml                        |  4 +--
 xml/System/Delegate.xml                       |  2 +-
 xml/System/MethodAccessException.xml          |  2 +-
 xml/System/ResolveEventArgs.xml               |  2 +-
 xml/System/ResolveEventHandler.xml            |  2 +-
 xml/System/String.xml                         |  2 +-
 xml/System/TimeSpan.xml                       |  4 +--
 xml/System/Type.xml                           |  2 +-
 xml/ns-System.Runtime.Caching.xml             |  2 +-
 96 files changed, 158 insertions(+), 158 deletions(-)

diff --git a/xml/Microsoft.Win32/Registry.xml b/xml/Microsoft.Win32/Registry.xml
index 86fca0438b5..992e6ee8c91 100644
--- a/xml/Microsoft.Win32/Registry.xml
+++ b/xml/Microsoft.Win32/Registry.xml
@@ -589,7 +589,7 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the `valueName` parameter is no longer restricted to a maximum of 255 characters; however, the `keyName` parameter continues to have the 255-character restriction.
+ Starting with the .NET Framework 4, the `valueName` parameter is no longer restricted to a maximum of 255 characters; however, the `keyName` parameter continues to have the 255-character restriction.
 
  Because many values can be stored in each key in the registry, you must use the `valueName` parameter to specify the particular value you want to set.
 
@@ -687,7 +687,7 @@ The <xref:Microsoft.Win32.Registry> class also contains `static` <xref:Microsoft
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the `valueName` parameter is no longer restricted to a maximum of 255 characters; however, the `keyName` parameter continues have the 255-character restriction.
+ Starting with the .NET Framework 4, the `valueName` parameter is no longer restricted to a maximum of 255 characters; however, the `keyName` parameter continues have the 255-character restriction.
 
  Because many values can be stored in each key in the registry, you must use the `valueName` parameter to specify the particular value you want to set.
 
diff --git a/xml/Microsoft.Win32/RegistryKey.xml b/xml/Microsoft.Win32/RegistryKey.xml
index 2eebaa8f561..fcda5ef934d 100644
--- a/xml/Microsoft.Win32/RegistryKey.xml
+++ b/xml/Microsoft.Win32/RegistryKey.xml
@@ -66,7 +66,7 @@
 > [!CAUTION]
 >  Do not expose <xref:Microsoft.Win32.RegistryKey> objects in such a way that a malicious program could create thousands of meaningless subkeys or key/value pairs. For example, do not allow callers to enter arbitrary keys or values.  
   
- Starting in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the length of a registry key is no longer limited to 255 characters.  
+ Starting in the .NET Framework 4, the length of a registry key is no longer limited to 255 characters.  
   
    
   
diff --git a/xml/Microsoft.Win32/RegistryValueKind.xml b/xml/Microsoft.Win32/RegistryValueKind.xml
index 5b24740fea0..121e2d3d0c7 100644
--- a/xml/Microsoft.Win32/RegistryValueKind.xml
+++ b/xml/Microsoft.Win32/RegistryValueKind.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.Win32.RegistryValueKind> enumeration defines the set of supported registry data types and the value that is used for unsupported types (Unknown). Starting in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you can specify not to use a data type with the None value.  
+ The <xref:Microsoft.Win32.RegistryValueKind> enumeration defines the set of supported registry data types and the value that is used for unsupported types (Unknown). Starting in the .NET Framework 4, you can specify not to use a data type with the None value.  
   
  Use the <xref:Microsoft.Win32.RegistryKey.GetValueKind%2A?displayProperty=nameWithType> method to determine the data type of a registry key value before retrieving the value. When you set a registry key value, use the <xref:Microsoft.Win32.RegistryKey.SetValue%2A> method to specify the registry data type explicitly.  
   
diff --git a/xml/System.Collections.Generic/HashSet`1.xml b/xml/System.Collections.Generic/HashSet`1.xml
index 2c609ff187a..40f0c2146e0 100644
--- a/xml/System.Collections.Generic/HashSet`1.xml
+++ b/xml/System.Collections.Generic/HashSet`1.xml
@@ -134,7 +134,7 @@
   
 **.NET Framework only:** For very large <xref:System.Collections.Generic.HashSet%601> objects, you can increase the maximum capacity to 2 billion elements on a 64-bit system by setting the `enabled` attribute of the [`<gcAllowVeryLargeObjects>`](/dotnet/framework/configure-apps/file-schema/runtime/gcallowverylargeobjects-element) configuration element to `true` in the run-time environment.  
   
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Collections.Generic.HashSet%601> class implements the <xref:System.Collections.Generic.ISet%601> interface.  
+ Starting with the .NET Framework 4, the <xref:System.Collections.Generic.HashSet%601> class implements the <xref:System.Collections.Generic.ISet%601> interface.  
   
 ## HashSet and LINQ Set Operations  
  LINQ provides access to the `Distinct`, `Union`, `Intersect` and `Except` set operations on any data source that implements the <xref:System.Collections.IEnumerable> or <xref:System.Linq.IQueryable> interfaces.  <xref:System.Collections.Generic.HashSet%601> provides a larger and more robust collection of set operations. For example, <xref:System.Collections.Generic.HashSet%601> provides comparisons such as <xref:System.Collections.Generic.HashSet%601.IsSubsetOf%2A> and <xref:System.Collections.Generic.HashSet%601.IsSupersetOf%2A>.  
diff --git a/xml/System.ComponentModel/TypeConverter.xml b/xml/System.ComponentModel/TypeConverter.xml
index a76c01709c6..a31ef6b4ec4 100644
--- a/xml/System.ComponentModel/TypeConverter.xml
+++ b/xml/System.ComponentModel/TypeConverter.xml
@@ -2279,7 +2279,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting in [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method catches exceptions from the <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> and <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> methods. If the input value type causes <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> to return `false`, or if the input value causes <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> to raise an exception, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method returns `false`.  
+ Starting in .NET Framework 4, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method catches exceptions from the <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> and <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> methods. If the input value type causes <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> to return `false`, or if the input value causes <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> to raise an exception, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method returns `false`.  
   
  To enable the legacy behavior, insert the following lines into the configuration file of the application, for example, application1.exe.config.  
   
@@ -2350,7 +2350,7 @@
 ## Remarks  
  Use the `context` parameter to extract additional information about the environment from which this converter is invoked. This parameter can be `null`, so always check it. Also, properties on the context object can return `null`.  
   
- Starting in [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method catches exceptions from the <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> and <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> methods. If the input value type causes <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> to return `false`, or if the input value causes <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> to raise an exception, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method returns `false`.  
+ Starting in .NET Framework 4, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method catches exceptions from the <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> and <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> methods. If the input value type causes <xref:System.ComponentModel.TypeConverter.CanConvertFrom%2A> to return `false`, or if the input value causes <xref:System.ComponentModel.TypeConverter.ConvertFrom%2A> to raise an exception, the <xref:System.ComponentModel.TypeConverter.IsValid%2A> method returns `false`.  
   
  To enable the legacy behavior, insert the following lines into the configuration file of the application, for example, application1.exe.config.  
   
diff --git a/xml/System.Configuration/ConfigurationProperty.xml b/xml/System.Configuration/ConfigurationProperty.xml
index fc8deccbf28..0bdff2c5585 100644
--- a/xml/System.Configuration/ConfigurationProperty.xml
+++ b/xml/System.Configuration/ConfigurationProperty.xml
@@ -791,7 +791,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If you are creating a configuration property for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later versions, and if the property value should not be serialized to XML when an earlier version of the framework is targeted, set this property to `true`.  
+ If you are creating a configuration property for the .NET Framework 4 or later versions, and if the property value should not be serialized to XML when an earlier version of the framework is targeted, set this property to `true`.  
   
  You use <xref:System.Configuration.ConfigurationPropertyOptions> to set this property when you call a constructor that includes a <xref:System.Configuration.ConfigurationPropertyOptions> parameter.  
   
diff --git a/xml/System.Configuration/ConfigurationSection.xml b/xml/System.Configuration/ConfigurationSection.xml
index e96adf77bbf..fd9ccaea9b3 100644
--- a/xml/System.Configuration/ConfigurationSection.xml
+++ b/xml/System.Configuration/ConfigurationSection.xml
@@ -446,7 +446,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified element is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
+ Each configuration section that is created for the .NET Framework 4 and later versions must explicitly override this method and return `true`, but only if the specified element is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default all configuration elements that are contained in the configuration section will be serialized for all framework versions.  
   
@@ -500,7 +500,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the specified property is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
+ Each configuration section that is created for the .NET Framework 4 and later versions must explicitly override this method and return `true`, but only if the specified property is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default all configuration properties that are contained in the configuration section will be serialized for all framework versions.  
   
@@ -548,7 +548,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the configuration section is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
+ Each configuration section that is created for the .NET Framework 4 and later versions must explicitly override this method and return `true`, but only if the configuration section is valid for the specified version of the .NET Framework. Existing configuration sections that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. If you implement a configuration section and you do not override this method, by default the configuration section will be serialized for all framework versions.  
   
diff --git a/xml/System.Configuration/ConfigurationSectionGroup.xml b/xml/System.Configuration/ConfigurationSectionGroup.xml
index 5918f6431e8..143e10dc1c0 100644
--- a/xml/System.Configuration/ConfigurationSectionGroup.xml
+++ b/xml/System.Configuration/ConfigurationSectionGroup.xml
@@ -539,7 +539,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each configuration section group that is created for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later versions must explicitly override this method and return `true`, but only if the section group is valid for the specified version of the .NET Framework. Existing configuration section groups that were created for earlier versions of the .NET Framework do not have to be changed.  
+ Each configuration section group that is created for the .NET Framework 4 and later versions must explicitly override this method and return `true`, but only if the section group is valid for the specified version of the .NET Framework. Existing configuration section groups that were created for earlier versions of the .NET Framework do not have to be changed.  
   
  The base type contains a default implementation of this method that always returns `true`. In other words, if a configuration section group implementer does not override this method, by default the configuration section group will be serialized for all framework versions.  
   
diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
index 92b1e625f3e..38198f15279 100644
--- a/xml/System.Data.SqlClient/SqlConnection.xml
+++ b/xml/System.Data.SqlClient/SqlConnection.xml
@@ -1399,7 +1399,7 @@ The connection string contains <see langword="Context Connection=true" />.
 |PoolBlockingPeriod|Auto|Sets the blocking period behavior for a connection pool. See <xref:System.Data.SqlClient.SqlConnectionStringBuilder.PoolBlockingPeriod> property for details.|
 |Pooling|'true'|When the value of this key is set to true, any newly created connection will be added to the pool when closed by the application. In a next attempt to open the same connection, that connection will be drawn from the pool.<br /><br /> Connections are considered the same if they have the same connection string. Different connections have different connection strings.<br /><br /> The value of this key can be "true", "false", "yes", or "no".|
 |Replication|'false'|`true` if replication is supported using the connection.|
-|Transaction Binding|Implicit Unbind|Controls connection association with an enlisted `System.Transactions` transaction.<br /><br /> Possible values are:<br /><br /> `Transaction Binding=Implicit Unbind;`<br /><br /> `Transaction Binding=Explicit Unbind;`<br /><br /> Implicit Unbind causes the connection to detach from the transaction when it ends. After detaching, additional requests on the connection are performed in autocommit mode. The `System.Transactions.Transaction.Current` property is not checked when executing requests while the transaction is active. After the transaction has ended, additional requests are performed in autocommit mode.<br /><br /> If the system ends the transaction (in the scope of a using block) before the last command completes, it will throw <xref:System.InvalidOperationException>.<br /><br /> Explicit Unbind causes the connection to remain attached to the transaction until the connection is closed or an explicit `SqlConnection.TransactionEnlist(null)` is called. Beginning in [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], changes to Implicit Unbind make Explicit Unbind obsolete. An `InvalidOperationException` is thrown if `Transaction.Current` is not the enlisted transaction or if the enlisted transaction is not active.|
+|Transaction Binding|Implicit Unbind|Controls connection association with an enlisted `System.Transactions` transaction.<br /><br /> Possible values are:<br /><br /> `Transaction Binding=Implicit Unbind;`<br /><br /> `Transaction Binding=Explicit Unbind;`<br /><br /> Implicit Unbind causes the connection to detach from the transaction when it ends. After detaching, additional requests on the connection are performed in autocommit mode. The `System.Transactions.Transaction.Current` property is not checked when executing requests while the transaction is active. After the transaction has ended, additional requests are performed in autocommit mode.<br /><br /> If the system ends the transaction (in the scope of a using block) before the last command completes, it will throw <xref:System.InvalidOperationException>.<br /><br /> Explicit Unbind causes the connection to remain attached to the transaction until the connection is closed or an explicit `SqlConnection.TransactionEnlist(null)` is called. Beginning in .NET Framework 4, changes to Implicit Unbind make Explicit Unbind obsolete. An `InvalidOperationException` is thrown if `Transaction.Current` is not the enlisted transaction or if the enlisted transaction is not active.|
 |TransparentNetworkIPResolution|See description.|When the value of this key is set to `true`, the application is required to retrieve all IP addresses for a particular DNS entry and attempt to connect with the first one in the list. If the connection is not established within 0.5 seconds, the application will try to connect to all others in parallel. When the first answers, the application will establish the connection with the respondent IP address.<br /><br /> If the `MultiSubnetFailover` key is set to `true`, `TransparentNetworkIPResolution` is ignored.<br /><br /> If the `Failover Partner` key is set, `TransparentNetworkIPResolution` is ignored.<br /><br /> The value of this key must be `true`, `false`, `yes`, or `no`.<br /><br /> A value of `yes` is treated the same as a value of `true`.<br /><br /> A value of `no` is treated the same as a value of `false`.<br /><br /> The default values are as follows:<br /><br /> <ul><li>`false` when:<br /><br /> <ul><li>Connecting to Azure SQL Database where the data source ends with:<br /><br /> <ul><li>.database.chinacloudapi.cn</li><li>.database.usgovcloudapi.net</li><li>.database.cloudapi.de</li><li>.database.windows.net</li></ul></li><li>`Authentication` is 'Active Directory Password' or 'Active Directory Integrated'</li></ul></li><li>`true` in all other cases.</li></ul>|
 |TrustServerCertificate|'false'|When set to `true`, SSL is used to encrypt the channel when bypassing walking the certificate chain to validate trust. If TrustServerCertificate is set to `true` and Encrypt is set to `false`, the channel is not encrypted. Recognized values are `true`, `false`, `yes`, and `no`. For more information, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax).|
 |Type System Version|N/A|A string value that indicates the type system the application expects. The functionality available to a client application is dependent on the version of SQL Server and the compatibility level of the database. Explicitly setting the type system version that the client application was written for avoids potential problems that could cause an application to break if a different version of SQL Server is used. **Note:**  The type system version cannot be set for common language runtime (CLR) code executing in-process in SQL Server. For more information, see [SQL Server Common Language Runtime Integration](/dotnet/framework/data/adonet/sql/sql-server-common-language-runtime-integration). <br /><br /> Possible values are:<br /><br /> `Type System Version=SQL Server 2012;`<br /><br /> `Type System Version=SQL Server 2008;`<br /><br /> `Type System Version=SQL Server 2005;`<br /><br /> `Type System Version=Latest;`<br /><br /> `Type System Version=SQL Server 2012;` specifies that the application will require version 11.0.0.0 of Microsoft.SqlServer.Types.dll. The other `Type System Version` settings will require version 10.0.0.0 of Microsoft.SqlServer.Types.dll.<br /><br /> `Latest` is obsolete and should not be used. `Latest` is equivalent to `Type System Version=SQL Server 2008;`.|
diff --git a/xml/System.Deployment.Application/CompatibleFramework.xml b/xml/System.Deployment.Application/CompatibleFramework.xml
index dfd743eca86..cb4c30a0e97 100644
--- a/xml/System.Deployment.Application/CompatibleFramework.xml
+++ b/xml/System.Deployment.Application/CompatibleFramework.xml
@@ -47,7 +47,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the .NET Framework version is .NET Framework 4 Client Profile, the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Client". If the .NET Framework version is [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Full".  
+ If the .NET Framework version is .NET Framework 4 Client Profile, the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Client". If the .NET Framework version is .NET Framework 4, the <xref:System.Deployment.Application.CompatibleFramework.Profile%2A> property returns "Full".  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Diagnostics/Debugger.xml b/xml/System.Diagnostics/Debugger.xml
index 0ecce8fb0a1..420e4d59b8b 100644
--- a/xml/System.Diagnostics/Debugger.xml
+++ b/xml/System.Diagnostics/Debugger.xml
@@ -144,7 +144,7 @@
  If no debugger is attached, users are asked if they want to attach a debugger. If users say yes, the debugger is started. If a debugger is attached, the debugger is signaled with a user breakpoint event, and the debugger suspends execution of the process just as if a debugger breakpoint had been hit.  
   
 > [!WARNING]
->  Starting with [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the runtime no longer exercises tight control of launching the debugger for the <xref:System.Diagnostics.Debugger.Break%2A> method, but instead reports an error to the Windows Error Reporting (WER) subsystem. WER provides many settings to customize the problem reporting experience, so a lot of factors will influence  the way WER responds to an error such as operating system version, process, session, user, machine and domain. If you're having unexpected results when calling  the <xref:System.Diagnostics.Debugger.Break%2A> method,  check the  WER settings on your machine. For more information on how to customize WER, see [WER Settings](/windows/win32/wer/wer-settings). If you want to ensure the debugger is launched regardless of the WER settings, be sure to call the <xref:System.Diagnostics.Debugger.Launch%2A> method instead.  
+>  Starting with .NET Framework 4, the runtime no longer exercises tight control of launching the debugger for the <xref:System.Diagnostics.Debugger.Break%2A> method, but instead reports an error to the Windows Error Reporting (WER) subsystem. WER provides many settings to customize the problem reporting experience, so a lot of factors will influence  the way WER responds to an error such as operating system version, process, session, user, machine and domain. If you're having unexpected results when calling  the <xref:System.Diagnostics.Debugger.Break%2A> method,  check the  WER settings on your machine. For more information on how to customize WER, see [WER Settings](/windows/win32/wer/wer-settings). If you want to ensure the debugger is launched regardless of the WER settings, be sure to call the <xref:System.Diagnostics.Debugger.Launch%2A> method instead.  
   
    
   
diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 5f80c133c0e..95efbc09271 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -93,7 +93,7 @@ When using this class in your applications, keep in mind the following programmi
 
 | .NET Framework version | Unicode Standard version |
 | - | - |
-| [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
+| .NET Framework 4 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v45](~/includes/net-v45-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v451](~/includes/net-v451-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v452](~/includes/net-v452-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index 9f3ab6f8d6a..ef671980ea8 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -459,7 +459,7 @@ Predefined culture identifiers for cultures available on Windows system are list
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> is not a valid culture identifier. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the .NET Framework 4, this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -553,7 +553,7 @@ For a list of predefined culture names on Windows systems, see the **Language ta
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> is not a valid culture name. For more information, see the Notes to Callers section.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the .NET Framework 4, this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -641,7 +641,7 @@ Predefined culture identifiers available on Windows systems are listed in the **
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> is not a valid culture identifier. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the .NET Framework 4, this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -725,7 +725,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> is not a valid culture name. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the .NET Framework 4, this constructor throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="P:System.Globalization.CultureInfo.UseUserOverride" />
@@ -1068,7 +1068,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
         <exception cref="T:System.NullReferenceException">
           <paramref name="name" /> is null.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the .NET Framework 4, this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="Overload:System.Globalization.CultureInfo.#ctor" />
         <altmember cref="P:System.Globalization.CultureInfo.Parent" />
@@ -1555,7 +1555,7 @@ In .NET Framework and .NET Core apps, the current UI culture is a per-thread set
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and previous versions, by default, the culture of all threads is set to the Windows system culture. For applications whose current culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property enables an application to define the default culture of all threads in an application domain.  
+ In the .NET Framework 4 and previous versions, by default, the culture of all threads is set to the Windows system culture. For applications whose current culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property enables an application to define the default culture of all threads in an application domain.  
   
 > [!IMPORTANT]
 >  If you have not explicitly set the culture of any existing threads executing in an application domain, setting the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property in that application domain or, if no default value is defined, by the default system culture. Because of this, we recommend that you always explicitly set the culture of your main application thread, and not rely on the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to define the culture of the main application thread.  
@@ -1634,7 +1634,7 @@ In .NET Framework and .NET Core apps, the current UI culture is a per-thread set
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and previous versions, by default, the UI culture of all threads is set to the Windows system culture. For applications whose current UI culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property lets you define the default UI culture of all threads in an application domain.  
+ In the .NET Framework 4 and previous versions, by default, the UI culture of all threads is set to the Windows system culture. For applications whose current UI culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property lets you define the default UI culture of all threads in an application domain.  
   
 > [!IMPORTANT]
 >  If you have not explicitly set the UI culture of any existing threads executing in an application domain, setting the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property in that application domain or, if no default value is defined, by the default system culture. Because of this, we recommend that you always explicitly set the culture of your main application thread and do not rely on the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property to define the culture of the main application thread.  
@@ -2143,7 +2143,7 @@ csc /resource:GreetingStrings.resources Example1.cs
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="culture" /> specifies a culture that is not supported. See the Notes to Caller section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="culture" /> is not a valid culture identifier. Starting with the .NET Framework 4, this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="culture" /> from the operating system; if the operating system does not support that culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.LCID" />
         <altmember cref="M:System.Globalization.CultureInfo.ClearCachedData" />
@@ -2208,7 +2208,7 @@ For a list of predefined culture names on Windows systems, see the **Language ta
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> specifies a culture that is not supported. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> is not a valid culture name. Starting with the .NET Framework 4, this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.Name" />
       </Docs>
@@ -2318,7 +2318,7 @@ Setting `predefinedOnly` to `true` will ensure a culture is created only if the
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> or <paramref name="altName" /> specifies a culture that is not supported. See the Notes to Callers section for more information.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> or <paramref name="altName" /> is not a valid culture name. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception. Starting with apps that run under the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> or <paramref name="altName" /> is not a valid culture name. Starting with the .NET Framework 4, this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception. Starting with apps that run under the .NET Framework 4 or later on Windows 7 or later, the method attempts to retrieve a <see cref="T:System.Globalization.CultureInfo" /> object whose identifier is <paramref name="name" /> from the operating system; if the operating system does not support that culture, and if <paramref name="name" /> is not the name of a supplementary or replacement culture, the method throws a <see cref="T:System.Globalization.CultureNotFoundException" /> exception.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.Name" />
         <altmember cref="M:System.Globalization.CultureInfo.ClearCachedData" />
@@ -2386,7 +2386,7 @@ Setting `predefinedOnly` to `true` will ensure a culture is created only if the
         <exception cref="T:System.Globalization.CultureNotFoundException">
           <paramref name="name" /> does not correspond to a supported culture.</exception>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> does not correspond to the name of a supported culture. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
+          <para>The .NET Framework 3.5 and earlier versions throw an <see cref="T:System.ArgumentException" /> if <paramref name="name" /> does not correspond to the name of a supported culture. Starting with the .NET Framework 4, this method throws a <see cref="T:System.Globalization.CultureNotFoundException" />.</para>
         </block>
         <altmember cref="P:System.Globalization.CultureInfo.TextInfo" />
         <altmember cref="T:System.Globalization.CultureAndRegionInfoBuilder" />
diff --git a/xml/System.Reflection.Emit/AssemblyBuilder.xml b/xml/System.Reflection.Emit/AssemblyBuilder.xml
index 8ac2e916935..2574998f84e 100644
--- a/xml/System.Reflection.Emit/AssemblyBuilder.xml
+++ b/xml/System.Reflection.Emit/AssemblyBuilder.xml
@@ -2948,7 +2948,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] always enforces level 2 transparency (<xref:System.Security.SecurityRuleSet.Level2?displayProperty=nameWithType>) for the dynamic assemblies it generates.  
+ The .NET Framework 4 always enforces level 2 transparency (<xref:System.Security.SecurityRuleSet.Level2?displayProperty=nameWithType>) for the dynamic assemblies it generates.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/FieldBuilder.xml b/xml/System.Reflection.Emit/FieldBuilder.xml
index fb839ce0223..647a4b7749a 100644
--- a/xml/System.Reflection.Emit/FieldBuilder.xml
+++ b/xml/System.Reflection.Emit/FieldBuilder.xml
@@ -657,7 +657,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the field type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], `defaultValue` can be non-null for a reference type as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a field of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
+ `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the field type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the .NET Framework 4, `defaultValue` can be non-null for a reference type as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a field of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/ILGenerator.xml b/xml/System.Reflection.Emit/ILGenerator.xml
index 59e6dffb64b..b885170004a 100644
--- a/xml/System.Reflection.Emit/ILGenerator.xml
+++ b/xml/System.Reflection.Emit/ILGenerator.xml
@@ -957,7 +957,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />. This exception is new in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)].</exception>
+          <paramref name="con" /> is <see langword="null" />. This exception is new in the .NET Framework 4.</exception>
       </Docs>
     </Member>
     <Member MemberName="Emit">
@@ -1079,7 +1079,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">
-          <paramref name="con" /> is <see langword="null" />. This exception is new in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)].</exception>
+          <paramref name="con" /> is <see langword="null" />. This exception is new in the .NET Framework 4.</exception>
       </Docs>
     </Member>
     <Member MemberName="Emit">
diff --git a/xml/System.Reflection.Emit/ParameterBuilder.xml b/xml/System.Reflection.Emit/ParameterBuilder.xml
index e1bace46259..490f42c2d4f 100644
--- a/xml/System.Reflection.Emit/ParameterBuilder.xml
+++ b/xml/System.Reflection.Emit/ParameterBuilder.xml
@@ -398,7 +398,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the parameter type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], `defaultValue` can be non-null for a reference type as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a parameter of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
+ `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the parameter type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the .NET Framework 4, `defaultValue` can be non-null for a reference type as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a parameter of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection.Emit/PropertyBuilder.xml b/xml/System.Reflection.Emit/PropertyBuilder.xml
index 7576ea042e1..271c8efd169 100644
--- a/xml/System.Reflection.Emit/PropertyBuilder.xml
+++ b/xml/System.Reflection.Emit/PropertyBuilder.xml
@@ -1019,7 +1019,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the property type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], `defaultValue` can be non-null for reference types as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a property of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
+ `defaultValue` is restricted to the following types: `Boolean`, `SByte`, `Int16`, `Int32`, `Int64`, `Byte`, `UInt16`, `UInt32`, `UInt64`, `Single`, `Double`, `DateTime`, `Char`, `String`, and `Enum`. If the property type is a reference type, CLS compliance requires `defaultValue` to be `null`. However, starting with the .NET Framework 4, `defaultValue` can be non-null for reference types as long as the value can be assigned to that reference type. For example, an `Int32` value can be assigned to a property of type <xref:System.Object>. This is not CLS-compliant, but it can be useful in interop scenarios.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/Assembly.xml b/xml/System.Reflection/Assembly.xml
index a89d8c910b1..53483024d8e 100644
--- a/xml/System.Reflection/Assembly.xml
+++ b/xml/System.Reflection/Assembly.xml
@@ -2657,7 +2657,7 @@ In .NET 5.0 and later versions, for bundled assemblies, this method throws an ex
 ## Remarks
 
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property of an <xref:System.Reflection.AssemblyName> object that is returned by this method is <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.None?displayProperty=nameWithType> if there is no hash algorithm for the referenced assembly, or if the hash algorithm of the referenced assembly is not identified by the <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm?displayProperty=nameWithType> enumeration. In previous versions of the .NET Framework, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property returned <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.SHA1?displayProperty=nameWithType> in this situation.
+>  Starting with the .NET Framework 4, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property of an <xref:System.Reflection.AssemblyName> object that is returned by this method is <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.None?displayProperty=nameWithType> if there is no hash algorithm for the referenced assembly, or if the hash algorithm of the referenced assembly is not identified by the <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm?displayProperty=nameWithType> enumeration. In previous versions of the .NET Framework, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property returned <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.SHA1?displayProperty=nameWithType> in this situation.
 
 
 
@@ -4228,7 +4228,7 @@ To load the correct assembly, it's recommended to call the `Load` method by pass
  Version 2.0 or later of the common language runtime is currently loaded and <paramref name="rawAssembly" /> was compiled with a later version.</exception>
         <exception cref="T:System.IO.FileLoadException">An assembly or module was loaded twice with two different evidences.</exception>
         <exception cref="T:System.NotSupportedException">
-          <paramref name="securityEvidence" /> is not <see langword="null" />.  By default, legacy CAS policy is not enabled in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]; when it is not enabled, <paramref name="securityEvidence" /> must be <see langword="null" />.</exception>
+          <paramref name="securityEvidence" /> is not <see langword="null" />.  By default, legacy CAS policy is not enabled in the .NET Framework 4; when it is not enabled, <paramref name="securityEvidence" /> must be <see langword="null" />.</exception>
       </Docs>
     </Member>
     <Member MemberName="Load">
@@ -4453,7 +4453,7 @@ The ability to execute code in remote assemblies is disabled. See <see href="htt
 
  Version 2.0 or later of the common language runtime is currently loaded and <paramref name="path" /> was compiled with a later version.</exception>
         <exception cref="T:System.NotSupportedException">
-          <paramref name="securityEvidence" /> is not <see langword="null" />. By default, legacy CAS policy is not enabled in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]; when it is not enabled, <paramref name="securityEvidence" /> must be <see langword="null" />.</exception>
+          <paramref name="securityEvidence" /> is not <see langword="null" />. By default, legacy CAS policy is not enabled in the .NET Framework 4; when it is not enabled, <paramref name="securityEvidence" /> must be <see langword="null" />.</exception>
       </Docs>
     </Member>
     <MemberGroup MemberName="LoadFrom">
@@ -5983,7 +5983,7 @@ In .NET 5.0 and later versions, for bundled assemblies, the value returned is an
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- By default, assemblies that you compile with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] have [level 2](/dotnet/framework/misc/security-transparent-code-level-2) transparency, although you can explicitly make them [level 1](/dotnet/framework/misc/security-transparent-code-level-1) instead. Assemblies that were compiled with earlier versions of the .NET Framework have level 1 transparency.
+ By default, assemblies that you compile with the .NET Framework 4 have [level 2](/dotnet/framework/misc/security-transparent-code-level-2) transparency, although you can explicitly make them [level 1](/dotnet/framework/misc/security-transparent-code-level-1) instead. Assemblies that were compiled with earlier versions of the .NET Framework have level 1 transparency.
 
  See [Security Changes](/dotnet/framework/security/security-changes).
 
@@ -6242,7 +6242,7 @@ In .NET 5.0 and later versions, for bundled assemblies, the value returned is an
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Use this method to load a local assembly that the operating system has flagged as having been loaded from the Web (for example, a temporary file that was downloaded from the Internet or intranet). Before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], such assemblies were automatically loaded into a sandboxed application domain. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], they are loaded with full trust.
+ Use this method to load a local assembly that the operating system has flagged as having been loaded from the Web (for example, a temporary file that was downloaded from the Internet or intranet). Before the .NET Framework 4, such assemblies were automatically loaded into a sandboxed application domain. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], they are loaded with full trust.
 
  As an alternative to using this method, you can apply the [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element) in your application configuration file. This causes the common language runtime to revert to the security policy of the .NET Framework 3.5.
 
diff --git a/xml/System.Reflection/AssemblyName.xml b/xml/System.Reflection/AssemblyName.xml
index 310ac586eaa..93d2c76bb3d 100644
--- a/xml/System.Reflection/AssemblyName.xml
+++ b/xml/System.Reflection/AssemblyName.xml
@@ -1040,7 +1040,7 @@ mylib, Version=1.2.1900.0, Culture=neutral, PublicKeyToken=a14f3033def15840
 ## Remarks  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property of an <xref:System.Reflection.AssemblyName> object that is returned by the <xref:System.Reflection.Assembly.GetReferencedAssemblies%2A?displayProperty=nameWithType> method is <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.None?displayProperty=nameWithType> if there is no hash algorithm for the referenced assembly, or if the hash algorithm of the referenced assembly is not identified by the <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm?displayProperty=nameWithType> enumeration. In previous versions of the .NET Framework, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property returned <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.SHA1?displayProperty=nameWithType> in this situation.  
+>  Starting with the .NET Framework 4, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property of an <xref:System.Reflection.AssemblyName> object that is returned by the <xref:System.Reflection.Assembly.GetReferencedAssemblies%2A?displayProperty=nameWithType> method is <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.None?displayProperty=nameWithType> if there is no hash algorithm for the referenced assembly, or if the hash algorithm of the referenced assembly is not identified by the <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm?displayProperty=nameWithType> enumeration. In previous versions of the .NET Framework, the <xref:System.Reflection.AssemblyName.HashAlgorithm%2A> property returned <xref:System.Configuration.Assemblies.AssemblyHashAlgorithm.SHA1?displayProperty=nameWithType> in this situation.  
   
    
   
@@ -1262,7 +1262,7 @@ mylib, Version=1.2.1900.0, Culture=neutral, PublicKeyToken=a14f3033def15840
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this property always returns <xref:System.Reflection.ProcessorArchitecture.None?displayProperty=nameWithType> for reference assemblies.  
+ Beginning with the .NET Framework 4, this property always returns <xref:System.Reflection.ProcessorArchitecture.None?displayProperty=nameWithType> for reference assemblies.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml b/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
index 3e196ca0786..9df2c29c6ee 100644
--- a/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
+++ b/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
@@ -46,7 +46,7 @@
   
  By default, the common language runtime (CLR) does not deliver these exceptions to managed code, and the `try`/`catch` blocks (and other exception-handling clauses) are not invoked for them. If you are absolutely sure that you want to maintain your handling of these exceptions, you must apply the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute to the method whose exception-handling clauses you want to execute. The CLR delivers the corrupted process state exception to applicable exception clauses only in methods that have both the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> and <xref:System.Security.SecurityCriticalAttribute> attributes.  
   
- You can also add the [\<legacyCorruptedStateExceptionsPolicy>](/dotnet/framework/configure-apps/file-schema/runtime/legacycorruptedstateexceptionspolicy-element) element to your application's configuration file. This will ensure that corrupted state exceptions are delivered to your exception handlers without the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> or <xref:System.Security.SecurityCriticalAttribute> attribute. This configuration element has no effect on applications that were compiled in versions previous to the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] but are running in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later; corrupted state exceptions will continue to be delivered for those applications. The <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute is ignored when it is encountered in partially trusted or transparent code, because a trusted host should not allow an untrusted add-in to catch and ignore these serious exceptions.  
+ You can also add the [\<legacyCorruptedStateExceptionsPolicy>](/dotnet/framework/configure-apps/file-schema/runtime/legacycorruptedstateexceptionspolicy-element) element to your application's configuration file. This will ensure that corrupted state exceptions are delivered to your exception handlers without the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> or <xref:System.Security.SecurityCriticalAttribute> attribute. This configuration element has no effect on applications that were compiled in versions previous to the .NET Framework 4 but are running in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later; corrupted state exceptions will continue to be delivered for those applications. The <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute is ignored when it is encountered in partially trusted or transparent code, because a trusted host should not allow an untrusted add-in to catch and ignore these serious exceptions.  
   
  For more information about corrupted process state exceptions, see the entry [Handling Corrupted State Exceptions](https://go.microsoft.com/fwlink/?LinkID=179681) in the CLR Inside Out blog.  
  
diff --git a/xml/System.Runtime.InteropServices/RuntimeEnvironment.xml b/xml/System.Runtime.InteropServices/RuntimeEnvironment.xml
index df9370a3ab5..168abd5f1c3 100644
--- a/xml/System.Runtime.InteropServices/RuntimeEnvironment.xml
+++ b/xml/System.Runtime.InteropServices/RuntimeEnvironment.xml
@@ -255,7 +255,7 @@
 |CLSID_CorMetaDataDispenser|IID_IMetaDataDispenser, IID_IMetaDataDispenserEx|  
 |CLSID_CorMetaDataDispenserRuntime|IID_IMetaDataDispenser, IID_IMetaDataDispenserEx|  
 |CLSID_CorRuntimeHost|IID_CorRuntimeHost|  
-|CLSID_CLRRuntimeHost|IID_CLRRuntimeHost (not valid for the common language runtime that is provided by the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]), IID_CLRRuntimeHost3|  
+|CLSID_CLRRuntimeHost|IID_CLRRuntimeHost (not valid for the common language runtime that is provided by the .NET Framework 4), IID_CLRRuntimeHost3|  
 |CLSID_TypeNameFactory|IID_TypeNameFactory|  
 |CLSID_CLRStrongName|IID_CLRStrongName|  
   
diff --git a/xml/System.Runtime.Versioning/TargetFrameworkAttribute.xml b/xml/System.Runtime.Versioning/TargetFrameworkAttribute.xml
index e0501ae7271..4fb4332e1b0 100644
--- a/xml/System.Runtime.Versioning/TargetFrameworkAttribute.xml
+++ b/xml/System.Runtime.Versioning/TargetFrameworkAttribute.xml
@@ -46,12 +46,12 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.Versioning.TargetFrameworkAttribute> class provides an attribute that you can apply to an assembly to indicate the version of the .NET runtime against which the assembly was built. For example, the following example applies the `TargetFrameworkAttribute` to an assembly to indicate that it was built using [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)].  
+ The <xref:System.Runtime.Versioning.TargetFrameworkAttribute> class provides an attribute that you can apply to an assembly to indicate the version of the .NET runtime against which the assembly was built. For example, the following example applies the `TargetFrameworkAttribute` to an assembly to indicate that it was built using .NET Framework 4.  
   
  [!code-csharp[System.Runtime.Versioning.TargetFrameworkAttribute#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.runtime.versioning.targetframeworkattribute/cs/declare1.cs#1)]
  [!code-vb[System.Runtime.Versioning.TargetFrameworkAttribute#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.runtime.versioning.targetframeworkattribute/vb/declare1.vb#1)]  
   
- The <xref:System.Runtime.Versioning.TargetFrameworkAttribute> class constructor has a single parameter, `frameworkName`, that specifies the .NET version against which the assembly was built. This parameter maps to the <xref:System.Runtime.Versioning.TargetFrameworkAttribute.FrameworkName%2A> property. In addition, the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute can specify a <xref:System.Runtime.Versioning.TargetFrameworkAttribute.FrameworkDisplayName%2A> property to provide a more descriptive .NET version string that is suitable for displaying to clients of the assembly. The following example applies the `TargetFrameworkAttribute` to an assembly and assigns both property values to indicate that the assembly was built using [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)].  
+ The <xref:System.Runtime.Versioning.TargetFrameworkAttribute> class constructor has a single parameter, `frameworkName`, that specifies the .NET version against which the assembly was built. This parameter maps to the <xref:System.Runtime.Versioning.TargetFrameworkAttribute.FrameworkName%2A> property. In addition, the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute can specify a <xref:System.Runtime.Versioning.TargetFrameworkAttribute.FrameworkDisplayName%2A> property to provide a more descriptive .NET version string that is suitable for displaying to clients of the assembly. The following example applies the `TargetFrameworkAttribute` to an assembly and assigns both property values to indicate that the assembly was built using .NET Framework 4.  
   
  [!code-csharp[System.Runtime.Versioning.TargetFrameworkAttribute#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.runtime.versioning.targetframeworkattribute/cs/declare2.cs#2)]
  [!code-vb[System.Runtime.Versioning.TargetFrameworkAttribute#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.runtime.versioning.targetframeworkattribute/vb/declare2.vb#2)]  
diff --git a/xml/System.Security.Permissions/EnvironmentPermission.xml b/xml/System.Security.Permissions/EnvironmentPermission.xml
index a67186de5e3..98d7eb2c096 100644
--- a/xml/System.Security.Permissions/EnvironmentPermission.xml
+++ b/xml/System.Security.Permissions/EnvironmentPermission.xml
@@ -55,7 +55,7 @@
  Environment variable names are designated by one or more case-insensitive name lists separated by semicolons, with separate lists for read and write access to the named variables. Write access includes the ability to create and delete environment variables as well as to change existing values.  
   
 > [!NOTE]
->  In versions of the .NET Framework before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
+>  In versions of the .NET Framework before the .NET Framework 4, you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Permissions/FileIOPermission.xml b/xml/System.Security.Permissions/FileIOPermission.xml
index 8c797dcf82e..9b97e656d51 100644
--- a/xml/System.Security.Permissions/FileIOPermission.xml
+++ b/xml/System.Security.Permissions/FileIOPermission.xml
@@ -75,7 +75,7 @@
  Access to a folder implies access to all the files it contains, as well as access to all the files and folders in its subfolders. For example, `Read` access to C:\folder1\ implies `Read` access to C:\folder1\file1.txt, C:\folder1\folder2\\, C:\folder1\folder2\file2.txt, and so on.  
   
 > [!NOTE]
->  In versions of the .NET Framework before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
+>  In versions of the .NET Framework before the .NET Framework 4, you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
   
    
   
diff --git a/xml/System.Security.Permissions/GacIdentityPermission.xml b/xml/System.Security.Permissions/GacIdentityPermission.xml
index 702102d6357..a4a5e824ca0 100644
--- a/xml/System.Security.Permissions/GacIdentityPermission.xml
+++ b/xml/System.Security.Permissions/GacIdentityPermission.xml
@@ -50,7 +50,7 @@
  Files are either in the global assembly cache, or they are not. There are no variations to the permission granted, so all <xref:System.Security.Permissions.GacIdentityPermission> objects are equal.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. Starting with the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/GacIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/GacIdentityPermissionAttribute.xml
index 53a756f771e..9d53cc3f8db 100644
--- a/xml/System.Security.Permissions/GacIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/GacIdentityPermissionAttribute.xml
@@ -61,7 +61,7 @@
  The security information declared by a security attribute is stored in the metadata of the attribute target and is accessed by the system at run time. Security attributes are used only for declarative security. For imperative security, use the corresponding permission class, <xref:System.Security.Permissions.GacIdentityPermission>.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/PublisherIdentityPermission.xml b/xml/System.Security.Permissions/PublisherIdentityPermission.xml
index 147032c765f..4306897ee82 100644
--- a/xml/System.Security.Permissions/PublisherIdentityPermission.xml
+++ b/xml/System.Security.Permissions/PublisherIdentityPermission.xml
@@ -50,7 +50,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an <xref:System.Security.Permissions.PermissionState.Unrestricted> permission state value. Starting with the .NET Framework version 2.0, identity permissions can have any permission state value. This means that in 2.0 and later versions, identity permissions have the same behavior as permissions that implement the <xref:System.Security.Permissions.IUnrestrictedPermission> interface. That is, a demand for an identity always succeeds, regardless of the identity of the assembly, if the assembly has been granted full trust.  
 >   
diff --git a/xml/System.Security.Permissions/PublisherIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/PublisherIdentityPermissionAttribute.xml
index 90ac5606877..d28bfd1e847 100644
--- a/xml/System.Security.Permissions/PublisherIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/PublisherIdentityPermissionAttribute.xml
@@ -62,7 +62,7 @@
  The security information declared by a security attribute is stored in the metadata of the attribute target and is accessed by the system at run time. Security attributes are used only for declarative security. For imperative security, use the corresponding permission class.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an <xref:System.Security.Permissions.PermissionState.Unrestricted> permission state value. Starting with the .NET Framework version 2.0, identity permissions can have any permission state value. This means that in 2.0 and later versions, identity permissions have the same behavior as permissions that implement the <xref:System.Security.Permissions.IUnrestrictedPermission> interface.  
   
diff --git a/xml/System.Security.Permissions/RegistryPermission.xml b/xml/System.Security.Permissions/RegistryPermission.xml
index 8c2be001c8e..8286169dfa0 100644
--- a/xml/System.Security.Permissions/RegistryPermission.xml
+++ b/xml/System.Security.Permissions/RegistryPermission.xml
@@ -59,7 +59,7 @@
  Registry permission is defined in terms of canonical absolute paths; checks should always be made with canonical pathnames. Key access implies access to all values it contains and all variables under it.  
   
 > [!NOTE]
->  In versions of the .NET Framework before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
+>  In versions of the .NET Framework before the .NET Framework 4, you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Permissions/SecurityAction.xml b/xml/System.Security.Permissions/SecurityAction.xml
index 2e68cbbd196..6f5402d29dd 100644
--- a/xml/System.Security.Permissions/SecurityAction.xml
+++ b/xml/System.Security.Permissions/SecurityAction.xml
@@ -71,7 +71,7 @@
  The following table describes the time that each security action takes place and the targets that it supports.  
   
 > [!IMPORTANT]
->  In the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], runtime support has been removed for enforcing the Deny, RequestMinimum, RequestOptional, and RequestRefuse permission requests. These requests should not be used in code that is based on [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  In the .NET Framework 4, runtime support has been removed for enforcing the Deny, RequestMinimum, RequestOptional, and RequestRefuse permission requests. These requests should not be used in code that is based on [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
 
  You should not use `LinkDemand` in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. Instead, use the <xref:System.Security.SecurityCriticalAttribute> to restrict usage to fully trusted applications, or use `Demand` to restrict partially trusted callers.  
   
diff --git a/xml/System.Security.Permissions/SiteIdentityPermission.xml b/xml/System.Security.Permissions/SiteIdentityPermission.xml
index 5ed9bd13ed6..ac5f7183653 100644
--- a/xml/System.Security.Permissions/SiteIdentityPermission.xml
+++ b/xml/System.Security.Permissions/SiteIdentityPermission.xml
@@ -53,12 +53,12 @@
  Sites can be matched exactly, or by a wildcard ("\*") prefix at the dot delimiter. For example, the site name string `*.fourthcoffee.com` matches `fourthcoffee.com` as well as `www.fourthcoffee.com`. Without a wildcard, the site name must be a precise match. The site name string \* will match any site, but will not match code that has no site evidence.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective, even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. Starting with the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
 > [!NOTE]
->  In versions of the .NET Framework before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
+>  In versions of the .NET Framework before the .NET Framework 4, you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
   
 > [!NOTE]
 >  In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an <xref:System.Security.Permissions.PermissionState.Unrestricted> permission state value. Starting with the .NET Framework version 2.0, identity permissions can have any permission state value. This means that in 2.0 and later versions, identity permissions have the same behavior as permissions that implement the <xref:System.Security.Permissions.IUnrestrictedPermission> interface.  
diff --git a/xml/System.Security.Permissions/SiteIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/SiteIdentityPermissionAttribute.xml
index 3a5e7d1d542..c3f1498f8b4 100644
--- a/xml/System.Security.Permissions/SiteIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/SiteIdentityPermissionAttribute.xml
@@ -60,7 +60,7 @@
  Sites can be matched exactly, or by a wildcard ("\*") prefix at the dot delimiter. For example, the site name string `*.fourthcoffee.com` matches `fourthcoffee.com` as well as `www.fourthcoffee.com`. Without a wildcard, the site name must be a precise match. The site name string \* will match any site, but will not match code that has no site evidence.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/StrongNameIdentityPermission.xml b/xml/System.Security.Permissions/StrongNameIdentityPermission.xml
index 193e1e84dbb..61877dddd11 100644
--- a/xml/System.Security.Permissions/StrongNameIdentityPermission.xml
+++ b/xml/System.Security.Permissions/StrongNameIdentityPermission.xml
@@ -50,7 +50,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an <xref:System.Security.Permissions.PermissionState.Unrestricted> permission state value. In the .NET Framework version 2.0 and later, identity permissions can have any permission state value.  This means that in version 2.0 and later versions, identity permissions have the same behavior as permissions that implement the <xref:System.Security.Permissions.IUnrestrictedPermission> interface. That is, a demand for an identity always succeeds, regardless of the identity of the assembly, if the assembly has been granted full trust.  
   
diff --git a/xml/System.Security.Permissions/StrongNameIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/StrongNameIdentityPermissionAttribute.xml
index 40d1b2a6250..3b267b503c7 100644
--- a/xml/System.Security.Permissions/StrongNameIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/StrongNameIdentityPermissionAttribute.xml
@@ -56,7 +56,7 @@
 > Partially trusted code is no longer supported. This attribute has no effect in .NET Core.
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective, even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0 and later, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/UrlIdentityPermission.xml b/xml/System.Security.Permissions/UrlIdentityPermission.xml
index 60fced228f7..c259c00de38 100644
--- a/xml/System.Security.Permissions/UrlIdentityPermission.xml
+++ b/xml/System.Security.Permissions/UrlIdentityPermission.xml
@@ -53,12 +53,12 @@
  URLs can be matched exactly or by a wildcard in the final position, for example: `http://www.fourthcoffee.com/process/*`. URLs can also contain a wildcard ("\*") prefix at the dot delimiter. For example, the URL name string `http://www.fourthcoffee.com/process/grind.htm/` is a subset of `http://*.fourthcoffee.com/process/grind.htm/` and `http://*.com/process/grind.htm/`.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. Starting with the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. That is, a demand for an identity always succeeds, regardless of the identity of the assembly, if the assembly has been granted full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
 > [!NOTE]
->  In versions of the .NET Framework before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
+>  In versions of the .NET Framework before the .NET Framework 4, you could use the <xref:System.Security.CodeAccessPermission.Deny%2A?displayProperty=nameWithType> method to prevent inadvertent access to system resources by trusted code. <xref:System.Security.CodeAccessPermission.Deny%2A> is now obsolete, and access to resources is now determined solely by the granted permission set for an assembly. To limit access to files, you must run partially trusted code in a sandbox and assign it permissions only to resources that the code is allowed to access. For information about running an application in a sandbox, see [How to: Run Partially Trusted Code in a Sandbox](/dotnet/framework/misc/how-to-run-partially-trusted-code-in-a-sandbox).  
   
 > [!NOTE]
 >  In the .NET Framework versions 1.0 and 1.1, identity permissions cannot have an <xref:System.Security.Permissions.PermissionState.Unrestricted> permission state value. Starting with the .NET Framework version 2.0, identity permissions can have any permission state value. This means that in 2.0 and later versions, identity permissions have the same behavior as permissions that implement the <xref:System.Security.Permissions.IUnrestrictedPermission> interface.  
diff --git a/xml/System.Security.Permissions/UrlIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/UrlIdentityPermissionAttribute.xml
index 2c91adac32a..7558c5d7448 100644
--- a/xml/System.Security.Permissions/UrlIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/UrlIdentityPermissionAttribute.xml
@@ -60,7 +60,7 @@
  The scope of the declaration that is allowed depends on the <xref:System.Security.Permissions.SecurityAction> that is used.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/ZoneIdentityPermission.xml b/xml/System.Security.Permissions/ZoneIdentityPermission.xml
index bde4cbaeafd..b0392a94f85 100644
--- a/xml/System.Security.Permissions/ZoneIdentityPermission.xml
+++ b/xml/System.Security.Permissions/ZoneIdentityPermission.xml
@@ -61,7 +61,7 @@
 -   Local Machine zone: The Local Machine zone is an implicit zone that is used for content that exists on the user's computer. The content found on the user's computer, except for content cached by Internet Explorer on the local system, is treated with a very high level of trust.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective, even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. Starting with the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Permissions/ZoneIdentityPermissionAttribute.xml b/xml/System.Security.Permissions/ZoneIdentityPermissionAttribute.xml
index 8f2d0b3497e..ccccc890e28 100644
--- a/xml/System.Security.Permissions/ZoneIdentityPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/ZoneIdentityPermissionAttribute.xml
@@ -58,7 +58,7 @@
  The scope of the declaration that is allowed depends on the <xref:System.Security.Permissions.SecurityAction> that is used.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], identity permissions are not used.  
+>  Starting with the .NET Framework 4, identity permissions are not used.  
 >   
 >  In the .NET Framework versions 1.0 and 1.1, demands on the identity permissions are effective even when the calling assembly is fully trusted. That is, although the calling assembly has full trust, a demand for an identity permission fails if the assembly does not meet the demanded criteria. In the .NET Framework version 2.0, demands for identity permissions are ineffective if the calling assembly has full trust. This assures consistency for all permissions, eliminating the treatment of identity permissions as a special case.  
   
diff --git a/xml/System.Security.Policy/EvidenceBase.xml b/xml/System.Security.Policy/EvidenceBase.xml
index b90253cd441..d9d3db2b732 100644
--- a/xml/System.Security.Policy/EvidenceBase.xml
+++ b/xml/System.Security.Policy/EvidenceBase.xml
@@ -42,7 +42,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Before the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], almost any object could be used as an evidence object if the hosting code wanted to apply it as evidence. For example, some .NET Framework code recognized <xref:System.Uri?displayProperty=nameWithType> objects as evidence. The common language runtime (CLR) considered evidence objects as <xref:System.Object?displayProperty=nameWithType> references, and did not apply any type safety to them.  
+ Before the .NET Framework 4, almost any object could be used as an evidence object if the hosting code wanted to apply it as evidence. For example, some .NET Framework code recognized <xref:System.Uri?displayProperty=nameWithType> objects as evidence. The common language runtime (CLR) considered evidence objects as <xref:System.Object?displayProperty=nameWithType> references, and did not apply any type safety to them.  
   
  This presented a problem because there were implicit restrictions on which types could be used as evidence objects. Specifically, any object used as evidence had to be serializable and could not be `null`. If these requirements were not met, the CLR threw an exception whenever an operation that required one of these assumptions was performed.  
   
diff --git a/xml/System.Security.Policy/IApplicationTrustManager.xml b/xml/System.Security.Policy/IApplicationTrustManager.xml
index 7a50f80d557..c5c52318019 100644
--- a/xml/System.Security.Policy/IApplicationTrustManager.xml
+++ b/xml/System.Security.Policy/IApplicationTrustManager.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  Trust managers must implement the <xref:System.Security.Policy.IApplicationTrustManager> interface. The host calls the <xref:System.Security.Policy.IApplicationTrustManager.DetermineApplicationTrust%2A?displayProperty=nameWithType> method to determine whether an application should be executed and which permissions should be granted to the application.  
   
- In the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and later, there is only one trust manager, which can be a custom implementation of the <xref:System.Security.Policy.IApplicationTrustManager> interface. The default trust manager implementation prompts the user for permission to install the application and to elevate the permissions granted to the application. Other trust manager implementations might provide different user experiences. For example, an implementation might check an enterprise list for trusted applications instead of prompting the user for that information.  
+ In the .NET Framework 4 and later, there is only one trust manager, which can be a custom implementation of the <xref:System.Security.Policy.IApplicationTrustManager> interface. The default trust manager implementation prompts the user for permission to install the application and to elevate the permissions granted to the application. Other trust manager implementations might provide different user experiences. For example, an implementation might check an enterprise list for trusted applications instead of prompting the user for that information.  
   
    
   
diff --git a/xml/System.Security.Policy/PolicyLevel.xml b/xml/System.Security.Policy/PolicyLevel.xml
index 7bc3b0978c4..61fa5ad97dd 100644
--- a/xml/System.Security.Policy/PolicyLevel.xml
+++ b/xml/System.Security.Policy/PolicyLevel.xml
@@ -47,7 +47,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the common language runtime (CLR) is moving away from providing security policy for computers. We recommend that you use [Windows Software Restriction Policies (SRP)](https://go.microsoft.com/fwlink/?LinkId=178101) or [AppLocker](https://go.microsoft.com/fwlink/?LinkId=178102) as a replacement for CLR security policy. The information in this topic applies to the .NET Framework version 3.5 and earlier; it does not apply to the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  Starting with the .NET Framework 4, the common language runtime (CLR) is moving away from providing security policy for computers. We recommend that you use [Windows Software Restriction Policies (SRP)](https://go.microsoft.com/fwlink/?LinkId=178101) or [AppLocker](https://go.microsoft.com/fwlink/?LinkId=178102) as a replacement for CLR security policy. The information in this topic applies to the .NET Framework version 3.5 and earlier; it does not apply to the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
   
  The highest level of security policy is enterprise-wide. Successive lower levels of hierarchy represent further policy restrictions, but can never grant more permissions than allowed by higher levels. The following policy levels are implemented:  
   
diff --git a/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml b/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
index 3d4bb9908d0..177e9332062 100644
--- a/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
+++ b/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
@@ -56,7 +56,7 @@
 > Partially trusted code is no longer supported. This attribute has no effect in .NET Core.
   
 > [!NOTE]
->  The [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] introduces new security rules that affect the behavior of the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> attribute (see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2)). In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], all code defaults to security-transparent, that is, partially trusted. However, you can annotate individual types and members to assign them other transparency attributes. For this and other security changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  The .NET Framework 4 introduces new security rules that affect the behavior of the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> attribute (see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2)). In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], all code defaults to security-transparent, that is, partially trusted. However, you can annotate individual types and members to assign them other transparency attributes. For this and other security changes, see [Security Changes](/dotnet/framework/security/security-changes).  
   
  .NET Framework version 2.0 () assemblies must be strong-named to effectively use the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> (APTCA) attribute. [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] () assemblies do not have to be strong-named for the APTCA attribute to be effective, and they can contain transparent, security-critical and security-safe-critical code. For more information about applying attributes at the assembly level, see [Applying Attributes](/dotnet/standard/attributes/applying-attributes).  
   
diff --git a/xml/System.Security/HostSecurityManager.xml b/xml/System.Security/HostSecurityManager.xml
index d760de1783c..7f38ec25e40 100644
--- a/xml/System.Security/HostSecurityManager.xml
+++ b/xml/System.Security/HostSecurityManager.xml
@@ -217,7 +217,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="Flags">
diff --git a/xml/System.Security/SecurityCriticalAttribute.xml b/xml/System.Security/SecurityCriticalAttribute.xml
index fb4e578f3d1..233649af420 100644
--- a/xml/System.Security/SecurityCriticalAttribute.xml
+++ b/xml/System.Security/SecurityCriticalAttribute.xml
@@ -153,7 +153,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This constructor is provided for compatibility with the .NET Framework version 2.0 transparency model. It does not apply to the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. For more information, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
+ This constructor is provided for compatibility with the .NET Framework version 2.0 transparency model. It does not apply to the .NET Framework 4. For more information, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security/SecurityManager.xml b/xml/System.Security/SecurityManager.xml
index 5a251daa213..2187c17d0a5 100644
--- a/xml/System.Security/SecurityManager.xml
+++ b/xml/System.Security/SecurityManager.xml
@@ -196,7 +196,7 @@
 ## Remarks  
   
 > [!NOTE]
->  In the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the host evidence in `evidence` must contain <xref:System.Security.Policy.Zone?displayProperty=nameWithType> evidence.  
+>  In the .NET Framework 4, the host evidence in `evidence` must contain <xref:System.Security.Policy.Zone?displayProperty=nameWithType> evidence.  
 >   
 >  The following table shows the permission sets that are returned for each zone.  
   
@@ -404,7 +404,7 @@
  -or-  
   
  The code that calls this method does not have <see cref="F:System.Security.Permissions.FileIOPermissionAccess.PathDiscovery" />.</exception>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="LoadPolicyLevelFromString">
@@ -516,7 +516,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
         <exception cref="T:System.Security.SecurityException">The code that calls this method does not have <see cref="F:System.Security.Permissions.SecurityPermissionFlag.ControlPolicy" />.</exception>
       </Docs>
     </Member>
@@ -585,7 +585,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="ResolvePolicy">
@@ -642,7 +642,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="ResolvePolicy">
@@ -708,7 +708,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
         <exception cref="T:System.Security.Policy.PolicyException">Policy fails to grant the minimum required permissions specified by the <paramref name="reqdPset" /> parameter.</exception>
       </Docs>
     </Member>
@@ -769,7 +769,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="ResolveSystemPolicy">
@@ -826,7 +826,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="SavePolicy">
@@ -880,7 +880,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
         <exception cref="T:System.Security.SecurityException">The code that calls this method does not have <see cref="F:System.Security.Permissions.SecurityPermissionFlag.ControlPolicy" />.</exception>
       </Docs>
     </Member>
@@ -939,7 +939,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.Security.SecurityException">The code that calls this method does not have <see cref="F:System.Security.Permissions.SecurityPermissionFlag.ControlPolicy" />.</exception>
-        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
+        <exception cref="T:System.NotSupportedException">This method uses code access security (CAS) policy, which is obsolete in the .NET Framework 4. To enable CAS policy for compatibility with earlier versions of the .NET Framework, use the [&lt;legacyCasPolicy&gt; element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).</exception>
       </Docs>
     </Member>
     <Member MemberName="SecurityEnabled">
diff --git a/xml/System.Security/SecurityRuleSet.xml b/xml/System.Security/SecurityRuleSet.xml
index 05d1d1a5e2a..2152778cc0b 100644
--- a/xml/System.Security/SecurityRuleSet.xml
+++ b/xml/System.Security/SecurityRuleSet.xml
@@ -35,7 +35,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This enumeration indicates which set of security rules the common language runtime should enforce for an assembly. For example, an assembly that is marked with `[SecurityRules(SecurityRuleSet.Level1)]` uses the .NET Framework version 2.0 transparency rules, where public security-critical types and members are treated as security-safe-critical outside the assembly. This requires security-critical types and members to perform a link demand for full trust to enforce security-critical behavior when they are accessed by external callers. Typically, level 1 rules should be used only for compatibility, such as for  .NET Framework 2.0 assemblies. By default, .NET Framework 2.0 assemblies become level 2 assemblies when they are recompiled for the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. To compile these assemblies as level 1, you must mark them explicitly as level 1. For more information about level 1 behavior, see [Security-Transparent Code, Level 1](/dotnet/framework/misc/security-transparent-code-level-1). For information about level 2 behavior, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
+ This enumeration indicates which set of security rules the common language runtime should enforce for an assembly. For example, an assembly that is marked with `[SecurityRules(SecurityRuleSet.Level1)]` uses the .NET Framework version 2.0 transparency rules, where public security-critical types and members are treated as security-safe-critical outside the assembly. This requires security-critical types and members to perform a link demand for full trust to enforce security-critical behavior when they are accessed by external callers. Typically, level 1 rules should be used only for compatibility, such as for  .NET Framework 2.0 assemblies. By default, .NET Framework 2.0 assemblies become level 2 assemblies when they are recompiled for the .NET Framework 4. To compile these assemblies as level 1, you must mark them explicitly as level 1. For more information about level 1 behavior, see [Security-Transparent Code, Level 1](/dotnet/framework/misc/security-transparent-code-level-1). For information about level 2 behavior, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Text/StringBuilder.xml b/xml/System.Text/StringBuilder.xml
index 38e7a4203ab..dd5677195b6 100644
--- a/xml/System.Text/StringBuilder.xml
+++ b/xml/System.Text/StringBuilder.xml
@@ -4229,7 +4229,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Boolean" />
       </Docs>
@@ -4289,7 +4289,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Byte" />
       </Docs>
@@ -4477,7 +4477,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Decimal" />
       </Docs>
@@ -4537,7 +4537,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Double" />
       </Docs>
@@ -4597,7 +4597,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int16" />
       </Docs>
@@ -4657,7 +4657,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int32" />
       </Docs>
@@ -4717,7 +4717,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Int64" />
       </Docs>
@@ -4780,7 +4780,7 @@ foreach (ReadOnlyMemory<char> chunk in sb.GetChunks())
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Object" />
       </Docs>
@@ -4890,7 +4890,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.SByte" />
       </Docs>
@@ -4950,7 +4950,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.Single" />
       </Docs>
@@ -5085,7 +5085,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt16" />
       </Docs>
@@ -5152,7 +5152,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt32" />
       </Docs>
@@ -5218,7 +5218,7 @@ The existing characters are shifted to make room for the character sequence in t
           <paramref name="index" /> is less than zero or greater than the length of this instance.</exception>
         <exception cref="T:System.OutOfMemoryException">Enlarging the value of this instance would exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />.</exception>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
+          <para>In the .NET Framework 3.5 Service Pack 1 and earlier versions, calls to this method threw an <see cref="T:System.ArgumentOutOfRangeException" /> if inserting <paramref name="value" /> would cause the object's total length to exceed <see cref="P:System.Text.StringBuilder.MaxCapacity" />. Starting with the .NET Framework 4, the method throws an <see cref="T:System.OutOfMemoryException" />.</para>
         </block>
         <altmember cref="T:System.UInt64" />
       </Docs>
diff --git a/xml/System.Threading.Tasks/TaskScheduler.xml b/xml/System.Threading.Tasks/TaskScheduler.xml
index 31a82a50be6..aa6125a2d9f 100644
--- a/xml/System.Threading.Tasks/TaskScheduler.xml
+++ b/xml/System.Threading.Tasks/TaskScheduler.xml
@@ -832,7 +832,7 @@ protected override IEnumerable<Task> GetScheduledTasks()
 ## Remarks  
  This application domain-wide event provides a mechanism to prevent exception escalation policy (which, by default, terminates the process) from triggering.  
   
- To make it easier for developers to write asynchronous code based on tasks, the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] changes the default exception behavior for unobserved exceptions. Although unobserved exceptions still raise the <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException> exception, the process does not terminate by default. Instead, the exception is handled by the runtime after the event is raised, regardless of whether an event handler observes the exception. This behavior can be configured. Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the [`<ThrowUnobservedTaskExceptions>`](/dotnet/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element) configuration element to revert to the behavior of the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] and terminate the process:  
+ To make it easier for developers to write asynchronous code based on tasks, the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] changes the default exception behavior for unobserved exceptions. Although unobserved exceptions still raise the <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException> exception, the process does not terminate by default. Instead, the exception is handled by the runtime after the event is raised, regardless of whether an event handler observes the exception. This behavior can be configured. Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the [`<ThrowUnobservedTaskExceptions>`](/dotnet/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element) configuration element to revert to the behavior of the .NET Framework 4 and terminate the process:  
   
 ```xml  
 <configuration>   
diff --git a/xml/System.Threading/CancellationTokenSource.xml b/xml/System.Threading/CancellationTokenSource.xml
index 5fc6ab7cefc..13c970d68eb 100644
--- a/xml/System.Threading/CancellationTokenSource.xml
+++ b/xml/System.Threading/CancellationTokenSource.xml
@@ -57,7 +57,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the .NET Framework uses a unified model for cooperative cancellation of asynchronous or long-running synchronous operations that involves two objects:  
+ Starting with the .NET Framework 4, the .NET Framework uses a unified model for cooperative cancellation of asynchronous or long-running synchronous operations that involves two objects:  
   
 -   A <xref:System.Threading.CancellationTokenSource> object, which provides a cancellation token through its <xref:System.Threading.CancellationTokenSource.Token%2A> property and sends a cancellation message by calling its <xref:System.Threading.CancellationTokenSource.Cancel%2A> or <xref:System.Threading.CancellationTokenSource.CancelAfter%2A> method.  
   
diff --git a/xml/System.Threading/Monitor.xml b/xml/System.Threading/Monitor.xml
index 85d8144e345..1aba55152fd 100644
--- a/xml/System.Threading/Monitor.xml
+++ b/xml/System.Threading/Monitor.xml
@@ -82,7 +82,7 @@
 |<xref:System.Threading.Monitor.Pulse%2A> (signal), <xref:System.Threading.Monitor.PulseAll%2A>|Sends a signal to one or more waiting threads. The signal notifies a waiting thread that the state of the locked object has changed, and the owner of the lock is ready to release the lock. The waiting thread is placed in the object's ready queue so that it might eventually receive the lock for the object. Once the thread has the lock, it can check the new state of the object to see if the required state has been reached.|  
 |<xref:System.Threading.Monitor.Exit%2A>|Releases the lock on an object. This action also marks the end of a critical section protected by the locked object.|  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], there are two sets of overloads for the <xref:System.Threading.Monitor.Enter%2A> and <xref:System.Threading.Monitor.TryEnter%2A> methods. One set of overloads has a `ref` (in C#) or `ByRef` (in Visual Basic) <xref:System.Boolean> parameter that is atomically set to `true` if the lock is acquired, even if an exception is thrown when acquiring the lock. Use these overloads if it is critical to release the lock in all cases, even when the resources the lock is protecting might not be in a consistent state.  
+ Beginning with the .NET Framework 4, there are two sets of overloads for the <xref:System.Threading.Monitor.Enter%2A> and <xref:System.Threading.Monitor.TryEnter%2A> methods. One set of overloads has a `ref` (in C#) or `ByRef` (in Visual Basic) <xref:System.Boolean> parameter that is atomically set to `true` if the lock is acquired, even if an exception is thrown when acquiring the lock. Use these overloads if it is critical to release the lock in all cases, even when the resources the lock is protecting might not be in a consistent state.  
   
 <a name="Lock"></a>   
 ## The lock object  
diff --git a/xml/System.Threading/Thread.xml b/xml/System.Threading/Thread.xml
index cf807f6fb42..2dea87dce89 100644
--- a/xml/System.Threading/Thread.xml
+++ b/xml/System.Threading/Thread.xml
@@ -432,7 +432,7 @@ Main thread: ThreadProc.Join has returned.  Press Enter to end program.
  Avoid using this constructor overload. The default stack size used by the <xref:System.Threading.Thread.%23ctor%28System.Threading.ParameterizedThreadStart%29> constructor overload is the recommended stack size for threads. If a thread has memory problems, the most likely cause is programming error, such as infinite recursion.  
   
 > [!IMPORTANT]
-> Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], only fully trusted code can set `maxStackSize` to a value that is greater than the default stack size (1 megabyte). If a larger value is specified for `maxStackSize` when code is running with partial trust, `maxStackSize` is ignored and the default stack size is used. No exception is thrown. Code at any trust level can set `maxStackSize` to a value that is less than the default stack size.  
+> Beginning with the .NET Framework 4, only fully trusted code can set `maxStackSize` to a value that is greater than the default stack size (1 megabyte). If a larger value is specified for `maxStackSize` when code is running with partial trust, `maxStackSize` is ignored and the default stack size is used. No exception is thrown. Code at any trust level can set `maxStackSize` to a value that is less than the default stack size.  
   
 > [!NOTE]
 > If you are developing a fully trusted library that will be used by partially trusted code, and you need to start a thread that requires a large stack, you must assert full trust before creating the thread, or the default stack size will be used. Do not do this unless you fully control the code that runs on the thread.  
@@ -509,7 +509,7 @@ Main thread: ThreadProc.Join has returned.  Press Enter to end program.
  Avoid using this constructor overload. The default stack size used by the <xref:System.Threading.Thread.%23ctor%28System.Threading.ThreadStart%29> constructor overload is the recommended stack size for threads. If a thread has memory problems, the most likely cause is programming error, such as infinite recursion.  
   
 > [!IMPORTANT]
-> Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], only fully trusted code can set `maxStackSize` to a value that is greater than the default stack size (1 megabyte). If a larger value is specified for `maxStackSize` when code is running with partial trust, `maxStackSize` is ignored and the default stack size is used. No exception is thrown. Code at any trust level can set `maxStackSize` to a value that is less than the default stack size.  
+> Beginning with the .NET Framework 4, only fully trusted code can set `maxStackSize` to a value that is greater than the default stack size (1 megabyte). If a larger value is specified for `maxStackSize` when code is running with partial trust, `maxStackSize` is ignored and the default stack size is used. No exception is thrown. Code at any trust level can set `maxStackSize` to a value that is less than the default stack size.  
   
 > [!NOTE]
 > If you are developing a fully trusted library that will be used by partially trusted code, and you need to start a thread that requires a large stack, you must assert full trust before creating the thread, or the default stack size will be used. Do not do this unless you fully control the code that runs on the thread.  
@@ -1190,7 +1190,7 @@ This method is obsolete. On .NET 5.0 and later versions, calling this method pro
 > The <xref:System.Threading.Thread.CurrentCulture> property doesn't work reliably when used with any thread other than the current thread. In .NET Framework, reading the property is reliable, although setting it for a thread other than the current thread is not. On .NET Core, an <xref:System.InvalidOperationException> is thrown if a thread attempts to read or write the <xref:System.Threading.Thread.CurrentCulture> property on a different thread.
 > We recommend that you use the <xref:System.Globalization.CultureInfo.CurrentCulture?displayProperty=nameWithType> property to retrieve and set the current culture.
 
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you can set the <xref:System.Threading.Thread.CurrentCulture%2A> property to a neutral culture. This is because the behavior of the <xref:System.Globalization.CultureInfo> class has changed: When it represents a neutral culture, its property values (in particular, the <xref:System.Globalization.CultureInfo.Calendar%2A>, <xref:System.Globalization.CultureInfo.CompareInfo%2A>, <xref:System.Globalization.CultureInfo.DateTimeFormat%2A>, <xref:System.Globalization.CultureInfo.NumberFormat%2A>, and <xref:System.Globalization.CultureInfo.TextInfo%2A> properties) now reflect the specific culture that is associated with the neutral culture. In earlier versions of the .NET Framework, the <xref:System.Threading.Thread.CurrentCulture%2A> property threw a <xref:System.NotSupportedException> exception when a neutral culture was assigned.  
+ Beginning with the .NET Framework 4, you can set the <xref:System.Threading.Thread.CurrentCulture%2A> property to a neutral culture. This is because the behavior of the <xref:System.Globalization.CultureInfo> class has changed: When it represents a neutral culture, its property values (in particular, the <xref:System.Globalization.CultureInfo.Calendar%2A>, <xref:System.Globalization.CultureInfo.CompareInfo%2A>, <xref:System.Globalization.CultureInfo.DateTimeFormat%2A>, <xref:System.Globalization.CultureInfo.NumberFormat%2A>, and <xref:System.Globalization.CultureInfo.TextInfo%2A> properties) now reflect the specific culture that is associated with the neutral culture. In earlier versions of the .NET Framework, the <xref:System.Threading.Thread.CurrentCulture%2A> property threw a <xref:System.NotSupportedException> exception when a neutral culture was assigned.  
   
 ## Examples  
  The following example shows the threading statement that allows the user interface of a Windows Forms application to display in the culture that is set in Control Panel. Additional code is needed.  
diff --git a/xml/System.Threading/ThreadPool.xml b/xml/System.Threading/ThreadPool.xml
index d5830832e32..d49638c5061 100644
--- a/xml/System.Threading/ThreadPool.xml
+++ b/xml/System.Threading/ThreadPool.xml
@@ -73,7 +73,7 @@
   
  Timer-queue timers and registered wait operations also use the thread pool. Their callback functions are queued to the thread pool.  
   
- There is one thread pool per process. Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the default size of the thread pool for a process depends on several factors, such as the size of the virtual address space. A process can call the <xref:System.Threading.ThreadPool.GetMaxThreads%2A> method to determine the number of threads. The number of threads in the thread pool can be changed by using the <xref:System.Threading.ThreadPool.SetMaxThreads%2A> method. Each thread uses the default stack size and runs at the default priority.  
+ There is one thread pool per process. Beginning with the .NET Framework 4, the default size of the thread pool for a process depends on several factors, such as the size of the virtual address space. A process can call the <xref:System.Threading.ThreadPool.GetMaxThreads%2A> method to determine the number of threads. The number of threads in the thread pool can be changed by using the <xref:System.Threading.ThreadPool.SetMaxThreads%2A> method. Each thread uses the default stack size and runs at the default priority.  
   
 > [!NOTE]
 >  Unmanaged code that hosts the .NET Framework can change the size of the thread pool by using the `CorSetMaxThreads` function, defined in the mscoree.h file.  
diff --git a/xml/System.Web.Configuration/HttpRuntimeSection.xml b/xml/System.Web.Configuration/HttpRuntimeSection.xml
index 987899904d8..0a76c8286d7 100644
--- a/xml/System.Web.Configuration/HttpRuntimeSection.xml
+++ b/xml/System.Web.Configuration/HttpRuntimeSection.xml
@@ -1093,7 +1093,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.Configuration.HttpRuntimeSection.RequestValidationMode%2A> property specifies which ASP.NET approach to validation will be used. This can be the algorithm that is used in versions of ASP.NET earlier than version 4, or the version that is used in [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. The property can be set to the following values:  
+ The <xref:System.Web.Configuration.HttpRuntimeSection.RequestValidationMode%2A> property specifies which ASP.NET approach to validation will be used. This can be the algorithm that is used in versions of ASP.NET earlier than version 4, or the version that is used in .NET Framework 4. The property can be set to the following values:  
   
 -   `4.5 (the default).` In this mode, values are lazily loaded, that is, they are not read until they are requested.  
   
diff --git a/xml/System.Web.RegularExpressions/TagRegex.xml b/xml/System.Web.RegularExpressions/TagRegex.xml
index ae373020b61..a3d1413cdcb 100644
--- a/xml/System.Web.RegularExpressions/TagRegex.xml
+++ b/xml/System.Web.RegularExpressions/TagRegex.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.RegularExpressions.TagRegex> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] or later versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex35?displayProperty=nameWithType> class for applications that target the .NET Framework 3.5 and earlier versions.  
+ The <xref:System.Web.RegularExpressions.TagRegex> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the .NET Framework 4 or later versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex35?displayProperty=nameWithType> class for applications that target the .NET Framework 3.5 and earlier versions.  
   
 > [!NOTE]
 >  The <xref:System.Web.RegularExpressions> classes are used internally by the .NET Framework to parse ASP.NET pages.  
diff --git a/xml/System.Windows.Forms/SplitContainer.xml b/xml/System.Windows.Forms/SplitContainer.xml
index 2a9e2f352d3..f088b0acb5e 100644
--- a/xml/System.Windows.Forms/SplitContainer.xml
+++ b/xml/System.Windows.Forms/SplitContainer.xml
@@ -2622,7 +2622,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When the user presses the TAB key, the input focus is set to the next control in the tab order of the form. Set <xref:System.Windows.Forms.SplitContainer.TabStop%2A> to `true` to give input focus to a splitter so that it can be moved with the arrow keys as well as with the mouse. Starting in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], setting <xref:System.Windows.Forms.SplitContainer.TabStop%2A> to `false` excludes the splitter and any of the controls that are contained in the <xref:System.Windows.Forms.SplitContainer> from the collection of controls in the tab order. To enable controls to get focus by using the TAB key, create a control that inherits from <xref:System.Windows.Forms.SplitContainer>. Create a new property named `TabStop` and override the <xref:System.Windows.Forms.SplitContainer.ProcessTabKey%2A> method. The following example demonstrates how to accomplish this.  
+ When the user presses the TAB key, the input focus is set to the next control in the tab order of the form. Set <xref:System.Windows.Forms.SplitContainer.TabStop%2A> to `true` to give input focus to a splitter so that it can be moved with the arrow keys as well as with the mouse. Starting in the .NET Framework 4, setting <xref:System.Windows.Forms.SplitContainer.TabStop%2A> to `false` excludes the splitter and any of the controls that are contained in the <xref:System.Windows.Forms.SplitContainer> from the collection of controls in the tab order. To enable controls to get focus by using the TAB key, create a control that inherits from <xref:System.Windows.Forms.SplitContainer>. Create a new property named `TabStop` and override the <xref:System.Windows.Forms.SplitContainer.ProcessTabKey%2A> method. The following example demonstrates how to accomplish this.  
   
  [!code-csharp[SplitContainerTabStop#1](~/samples/snippets/csharp/VS_Snippets_Winforms/splitcontainertabstop/cs/program.cs#1)]
  [!code-vb[SplitContainerTabStop#1](~/samples/snippets/visualbasic/VS_Snippets_Winforms/splitcontainertabstop/vb/module1.vb#1)]  
diff --git a/xml/System.Windows.Markup/AmbientAttribute.xml b/xml/System.Windows.Markup/AmbientAttribute.xml
index 153bcb486c6..a083837a272 100644
--- a/xml/System.Windows.Markup/AmbientAttribute.xml
+++ b/xml/System.Windows.Markup/AmbientAttribute.xml
@@ -52,7 +52,7 @@
   
  <xref:System.Windows.Markup.AmbientAttribute> can also be applied to a CLR method, to support attributing a XAML attachable property as ambient. This is potentially necessary because in a CLR implementation a XAML attached property is implemented/represented to reflection as an accessor pattern with `get` and `set` methods. No actual CLR property to attribute exists, so restricting usage for <xref:System.AttributeTargets> to `Property` would not have enabled specifying an attachable member as ambient. For an attachable member that you want to report as ambient, attribute the `get` accessor. You should not attempt to attribute methods that are not specifically support methods of attachable members.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.AmbientAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.AmbientAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  Ambient types (types where <xref:System.Windows.Markup.AmbientAttribute> is applied at type level) can be used for certain XAML processing situations where the type of a property needs to be resolved out of order.  
   
diff --git a/xml/System.Windows.Markup/ConstructorArgumentAttribute.xml b/xml/System.Windows.Markup/ConstructorArgumentAttribute.xml
index 767ae617ce7..b42b170bdbe 100644
--- a/xml/System.Windows.Markup/ConstructorArgumentAttribute.xml
+++ b/xml/System.Windows.Markup/ConstructorArgumentAttribute.xml
@@ -46,7 +46,7 @@
   
  Consumers of <xref:System.Windows.Markup.ConstructorArgumentAttribute> may throw in cases where <xref:System.Windows.Markup.ConstructorArgumentAttribute.ArgumentName%2A> does not resolve to type backing, or when applied to a type that does not have the appropriate construction arguments and arity.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.ConstructorArgumentAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.ConstructorArgumentAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  For more information about markup extensions and WPF, see [Markup Extensions and WPF XAML](/dotnet/framework/wpf/advanced/markup-extensions-and-wpf-xaml).  
diff --git a/xml/System.Windows.Markup/ContentWrapperAttribute.xml b/xml/System.Windows.Markup/ContentWrapperAttribute.xml
index 0538417a142..088fecb19bb 100644
--- a/xml/System.Windows.Markup/ContentWrapperAttribute.xml
+++ b/xml/System.Windows.Markup/ContentWrapperAttribute.xml
@@ -46,7 +46,7 @@
   
  <xref:System.Windows.Documents.InlineCollection> is an example of a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] class that has the <xref:System.Windows.Markup.ContentWrapperAttribute> attribute applied. In this case there are two separate attributed wrapper classes.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.ContentWrapperAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.ContentWrapperAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/DateTimeValueSerializer.xml b/xml/System.Windows.Markup/DateTimeValueSerializer.xml
index 1d67f6bb0fd..a2b0c849418 100644
--- a/xml/System.Windows.Markup/DateTimeValueSerializer.xml
+++ b/xml/System.Windows.Markup/DateTimeValueSerializer.xml
@@ -36,7 +36,7 @@
 ## Remarks  
  <xref:System.Windows.Markup.ValueSerializer> is used rather than <xref:System.ComponentModel.TypeConverter> for cases where type conversion requires additional state. <xref:System.Windows.Markup.DateTimeValueSerializer> is not attributed to a type with <xref:System.Windows.Markup.ValueSerializerAttribute>. This is because <xref:System.DateTime> is in mscorlib, and mscorlib cannot take dependencies on attribute classes that it does not define itself. Instead, usage of <xref:System.Windows.Markup.DateTimeValueSerializer> is special-cased into XAML processor behavior in .NET Framework XAML Services behavior.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.DateTimeValueSerializer> is in the System.Xaml assembly. See [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.DateTimeValueSerializer> is in the System.Xaml assembly. See [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/DependsOnAttribute.xml b/xml/System.Windows.Markup/DependsOnAttribute.xml
index 24cd6c96d53..181d454fc65 100644
--- a/xml/System.Windows.Markup/DependsOnAttribute.xml
+++ b/xml/System.Windows.Markup/DependsOnAttribute.xml
@@ -46,7 +46,7 @@
   
  Applying this attribute to a property definition ensures that the dependent properties are processed first in XAML object writing. It is part of the general rules of XAML markup that attribute values applied for a created object should be able to be processed in any order. Usages of <xref:System.Windows.Markup.DependsOnAttribute> specify the exceptional cases of properties on types where a specific order of parsing must be followed for valid object creation.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.DependsOnAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.DependsOnAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  The <xref:System.Windows.Setter.Value%2A> property on the <xref:System.Windows.Setter> class is an example of a property in WPF where the <xref:System.Windows.Markup.DependsOnAttribute> attribute is applied.  <xref:System.Windows.Setter.Value%2A> depends on <xref:System.Windows.Setter.Property%2A> and <xref:System.Windows.Setter.TargetName%2A> being processed first, otherwise there is no way to know what type is supposed to be created for value converter cases.  
diff --git a/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml b/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
index 006270ebd31..73556c4a68c 100644
--- a/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
+++ b/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
@@ -40,7 +40,7 @@
 ## Remarks  
  Items in an <xref:System.Collections.IDictionary> dictionary (such as the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.ResourceDictionary>) require a key. In XAML, the key is typically specified by `x:Key` attribute in the XAML markup for each item in the <xref:System.Collections.IDictionary>. The <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is applied to classes that work with an implicit key, where the key to use for <xref:System.Collections.IDictionary> inclusion comes from a different property value in the class. Instances of the class applying the <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> can be included in an <xref:System.Collections.IDictionary> without an explicit key so long as the property referenced by <xref:System.Collections.IDictionary> has a value that is valid as a key in that dictionary implementation.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  The following list references examples of WPF APIs where this attribute is applied:  
diff --git a/xml/System.Windows.Markup/IComponentConnector.xml b/xml/System.Windows.Markup/IComponentConnector.xml
index 364c06dc28a..c87eac58d20 100644
--- a/xml/System.Windows.Markup/IComponentConnector.xml
+++ b/xml/System.Windows.Markup/IComponentConnector.xml
@@ -35,7 +35,7 @@
   
  Implementations of <xref:System.Windows.Markup.IComponentConnector.InitializeComponent%2A> are widely observable as part of the infrastructure provided by frameworks or technologies that use XAML combined with application and programming models. For example, whenever you look at the generated classes for XAML root elements in WPF pages and applications, you will see <xref:System.Windows.Markup.IComponentConnector.InitializeComponent%2A> defined in the output. That method also exists in the compiled assembly and plays a role in the WPF application model of loading the XAML UI content at XAML parse time. For more information on the WPF integration of the `InitializeComponent` concept, see [Application Management Overview](/dotnet/framework/wpf/app-development/application-management-overview) or [Code-Behind and XAML in WPF](/dotnet/framework/wpf/advanced/code-behind-and-xaml-in-wpf).  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.IComponentConnector> is in the System.Xaml assembly. . For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.IComponentConnector> is in the System.Xaml assembly. . For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 > [!TIP]
 >  A failure to resolve <xref:System.Windows.Markup.IComponentConnector> during an attempted build is often an indicator that you have not updated your WPF project correctly. In particular, the project is not referencing the System.Xaml assembly for a project that targets [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. Try running the `devenv /upgrade` option for the project, or otherwise adjust the project assembly references so that System.Xaml is in the reference list.  
diff --git a/xml/System.Windows.Markup/INameScope.xml b/xml/System.Windows.Markup/INameScope.xml
index 1437f503ef6..08ebb702337 100644
--- a/xml/System.Windows.Markup/INameScope.xml
+++ b/xml/System.Windows.Markup/INameScope.xml
@@ -33,7 +33,7 @@
 ## Remarks  
  This interface is implemented by classes that have child elements that are intended to be reused through the template or defer metaphor. Templates, factories and similar constructs must have unique XAML namescopes that are separate from a main object graph and root XAML. The principle here is that there should be no name collisions when objects created from those child elements are introduced to an application's object graph, and so that DOM operations and XAML reference techniques that rely on the name identifier can rely on name uniqueness in each XAML namescope.  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.INameScope> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.INameScope> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  This interface is implemented by the WPF class <xref:System.Windows.NameScope>. Most XAML namescope operations in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] operate by using <xref:System.Windows.NameScope> instances, but information is occasionally communicated internally by using <xref:System.Windows.Markup.INameScope> references.  
diff --git a/xml/System.Windows.Markup/IProvideValueTarget.xml b/xml/System.Windows.Markup/IProvideValueTarget.xml
index da6112f09ef..e7798558526 100644
--- a/xml/System.Windows.Markup/IProvideValueTarget.xml
+++ b/xml/System.Windows.Markup/IProvideValueTarget.xml
@@ -60,7 +60,7 @@
 > [!NOTE]
 >  Do not use the type of <xref:System.Windows.Markup.IProvideValueTarget.TargetProperty%2A> to determine which precise type a markup extension or type converter should return. That is not a best practice. Your return type should be consistent with attributing (<xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> for markup extensions) or patterns (class name of the type converter).  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.IProvideValueTarget> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.IProvideValueTarget> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  This service supports framework features such as binding on a dependency property.  
diff --git a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
index 1c13579596a..5185aa019ae 100644
--- a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
+++ b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
@@ -26,7 +26,7 @@
 ## Remarks  
  In .NET Framework 3.0, <xref:System.Windows.Markup.IReceiveMarkupExtension> was a WPF-specific technique for permitting types to enter a different codepath whenever any of its XAML-accessible members where set as markup extensions during XAML parsing. In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], this interface is obsolete, and is replaced with a .NET Framework XAML Services implementation for how markup extensions can receive services or types can invoke markup-extension specific setter logic.  
   
- For [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] implementations, if types want to perform special processing when setting properties by markup extension rather than by other means, types should be defined with <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute> attributes applied. The attribute specifies a callback, which is typically defined as a private member of the type.  
+ For .NET Framework 4 implementations, if types want to perform special processing when setting properties by markup extension rather than by other means, types should be defined with <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute> attributes applied. The attribute specifies a callback, which is typically defined as a private member of the type.  
   
  In infrastructure implementations of WPF classes, most cases where <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute> is applied reference a `ReceiveMarkupExtension` method that previously implemented this interface, but now instead use context through the callback.  
   
diff --git a/xml/System.Windows.Markup/IUriContext.xml b/xml/System.Windows.Markup/IUriContext.xml
index 740294ed1e6..3faaca241ed 100644
--- a/xml/System.Windows.Markup/IUriContext.xml
+++ b/xml/System.Windows.Markup/IUriContext.xml
@@ -42,7 +42,7 @@
   
  <xref:System.Windows.Markup.IUriContext> is not just for value conversion and service context. Class logic for UI elements or other classes that support containment might also implement <xref:System.Windows.Markup.IUriContext> services as a recognized pattern that child elements can call for base URI information, or store base URI information that is obtained from XAML parsing of the root element.  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly PresentationCore. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.IUriContext> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly PresentationCore. In .NET Framework 4, <xref:System.Windows.Markup.IUriContext> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  Example scenarios for <xref:System.Windows.Markup.IUriContext> exist in WPF.  
diff --git a/xml/System.Windows.Markup/IValueSerializerContext.xml b/xml/System.Windows.Markup/IValueSerializerContext.xml
index 94581358b27..e1a15d1bedb 100644
--- a/xml/System.Windows.Markup/IValueSerializerContext.xml
+++ b/xml/System.Windows.Markup/IValueSerializerContext.xml
@@ -42,7 +42,7 @@
   
  Public types in WPF that implement a <xref:System.Windows.Markup.ValueSerializer> and thus use <xref:System.Windows.Markup.IValueSerializerContext> for context are found in the <xref:System.Windows.Converters> and <xref:System.Windows.Media.Converters> namespaces.  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.IValueSerializerContext> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.IValueSerializerContext> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/IXamlTypeResolver.xml b/xml/System.Windows.Markup/IXamlTypeResolver.xml
index f5c617751a5..b9356dd4107 100644
--- a/xml/System.Windows.Markup/IXamlTypeResolver.xml
+++ b/xml/System.Windows.Markup/IXamlTypeResolver.xml
@@ -35,7 +35,7 @@
   
  Type converters and markup extensions can query for <xref:System.Windows.Markup.IXamlTypeResolver> as a service on the service context that is provided by a XAML object writer, when the XAML object writer invokes value conversion behavior. For more information, see [Type Converters and Markup Extensions for XAML](/dotnet/framework/xaml-services/type-converters-and-markup-extensions-for-xaml) and [Service Contexts Available to Type Converters and Markup Extensions](/dotnet/framework/xaml-services/service-contexts-available-to-type-converters-and-markup-extensions).  
   
- In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.IXamlTypeResolver> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.IXamlTypeResolver> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml b/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
index 6f13abee96d..efbbcb8086e 100644
--- a/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
+++ b/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
@@ -36,7 +36,7 @@
 ## Remarks  
  A <xref:System.Windows.Markup.MarkupExtension> derived custom class should apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to indicate a possible type-safe return type that is returned by its <xref:System.Windows.Markup.MarkupExtension.ProvideValue%2A> implementation. In other words, if a markup extension always returns a more specific type than type of <xref:System.Object>, and casting to that type is a primary scenario, the markup extension class should attribute with <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> and report that type.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  For more information on patterns for implementing a custom XAML markup extension, see <xref:System.Windows.Markup.MarkupExtension> and [Type Converters and Markup Extensions for XAML](/dotnet/framework/xaml-services/type-converters-and-markup-extensions-for-xaml).  
   
diff --git a/xml/System.Windows.Markup/NameScopePropertyAttribute.xml b/xml/System.Windows.Markup/NameScopePropertyAttribute.xml
index aa4a1a3e9ee..7b637376c13 100644
--- a/xml/System.Windows.Markup/NameScopePropertyAttribute.xml
+++ b/xml/System.Windows.Markup/NameScopePropertyAttribute.xml
@@ -44,7 +44,7 @@
   
  There are two forms for this attribute: property name only, or type and property. The latter form should be used only for cases where the property that holds the XAML name scope is an attachable member. The attached member technique has the advantage that service classes can implement a XAML namescope concept that can support several different object types. Those object types then do not need to be explicitly related in class inheritance.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.NameScopePropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.NameScopePropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  In WPF, this attribute is applied to only a single type, <xref:System.Windows.DependencyObject>. In this case the attributed property is the service class <xref:System.Windows.NameScope> and its <xref:System.Windows.NameScope.NameScope%2A?displayProperty=nameWithType> attached property.  
diff --git a/xml/System.Windows.Markup/NullExtension.xml b/xml/System.Windows.Markup/NullExtension.xml
index 0d22d689d91..929e0fa25ef 100644
--- a/xml/System.Windows.Markup/NullExtension.xml
+++ b/xml/System.Windows.Markup/NullExtension.xml
@@ -47,7 +47,7 @@
   
  This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for how XAML processors interpret a particular extension. The members that markup extension implementation classes expose are not typically intended to be called from your code. This markup extension class supports the [x:Null Markup Extension](/dotnet/framework/xaml-services/x-null-markup-extension) usage for .NET XAML Services.  
   
- In previous versions of the .NET Framework, this class (and the `x:Null` markup extension XAML behavior support as well as the relevant xmlns mapping) existed in the WPF-specific assembly PresentationFramework. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.NullExtension> is in the System.Xaml assembly. This makes the `x:Null` usage available to applications using frameworks that reference .NET XAML Services. You do not need PresentationFramework as a referenced assembly so long as you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class (and the `x:Null` markup extension XAML behavior support as well as the relevant xmlns mapping) existed in the WPF-specific assembly PresentationFramework. In .NET Framework 4, <xref:System.Windows.Markup.NullExtension> is in the System.Xaml assembly. This makes the `x:Null` usage available to applications using frameworks that reference .NET XAML Services. You do not need PresentationFramework as a referenced assembly so long as you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  The System.Xaml assembly uses <xref:System.Windows.Markup.XmlnsDefinitionAttribute> to map all types in the assembly to the XAML namespace for the XAML language ([!INCLUDE[TLA#tla_xamlxmlnsv1](~/includes/tlasharptla-xamlxmlnsv1-md.md)]). Typically you declare a prefix for [!INCLUDE[TLA#tla_xamlxmlnsv1](~/includes/tlasharptla-xamlxmlnsv1-md.md)] in a root element mapping and use the prefix `x`.  
   
diff --git a/xml/System.Windows.Markup/RootNamespaceAttribute.xml b/xml/System.Windows.Markup/RootNamespaceAttribute.xml
index 9addfa7b94d..8b730d70a8f 100644
--- a/xml/System.Windows.Markup/RootNamespaceAttribute.xml
+++ b/xml/System.Windows.Markup/RootNamespaceAttribute.xml
@@ -40,7 +40,7 @@
 ## Remarks  
  This attribute is mainly relevant for type resolutions of partial classes by markup compilers.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.RootNamespaceAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.RootNamespaceAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml b/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
index 61dcedb81f9..3721b5f3d57 100644
--- a/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
+++ b/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
@@ -44,7 +44,7 @@
   
  A XAML name value must use the [XamlName Grammar](/dotnet/framework/xaml-services/xamlname-grammar).  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  An example of an existing class in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] where the <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is applied is <xref:System.Windows.FrameworkElement>.  The <xref:System.Windows.FrameworkElement.Name%2A> property on <xref:System.Windows.FrameworkElement> is attributed with <xref:System.Windows.Markup.RuntimeNamePropertyAttribute>, which results in any <xref:System.Windows.FrameworkElement> derived class also using <xref:System.Windows.FrameworkElement.Name%2A> as its run-time name property.  
diff --git a/xml/System.Windows.Markup/TrimSurroundingWhitespaceAttribute.xml b/xml/System.Windows.Markup/TrimSurroundingWhitespaceAttribute.xml
index a9dc6cb8304..146ba5508c3 100644
--- a/xml/System.Windows.Markup/TrimSurroundingWhitespaceAttribute.xml
+++ b/xml/System.Windows.Markup/TrimSurroundingWhitespaceAttribute.xml
@@ -40,7 +40,7 @@
 ## Remarks  
  This attribute is applied to specific types that might appear as child elements within whitespace significant content. For more information, see [Whitespace Processing in XAML](/dotnet/framework/xaml-services/whitespace-processing-in-xaml).  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.TrimSurroundingWhitespaceAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.TrimSurroundingWhitespaceAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
index b39152b9f33..19135a004c9 100644
--- a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
+++ b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
@@ -36,7 +36,7 @@
 ## Remarks  
  Top-down is a metaphor that approximates XAML processor behavior when creating the object graph. When built top-down, a class is instantiated, attached to the parent, and then has its properties set. Top-down construction avoids invoking property-changed handlers multiple times. Such handling will ripple up the object graph and therefore eliminating the multiple handler calls provides a performance optimization for startup of the object graph.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.UsableDuringInitializationAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.UsableDuringInitializationAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  In WPF XAML for .NET Framework 3.0 and .NET Framework 3.5, top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
diff --git a/xml/System.Windows.Markup/ValueSerializer.xml b/xml/System.Windows.Markup/ValueSerializer.xml
index e2a78205248..294a947b2eb 100644
--- a/xml/System.Windows.Markup/ValueSerializer.xml
+++ b/xml/System.Windows.Markup/ValueSerializer.xml
@@ -44,7 +44,7 @@
   
  <xref:System.Windows.Markup.IValueSerializerContext> for a <xref:System.Windows.Markup.ValueSerializer> and its APIs is analogous to <xref:System.ComponentModel.ITypeDescriptorContext> for a <xref:System.ComponentModel.TypeConverter>. In fact, <xref:System.Windows.Markup.IValueSerializerContext> inherits <xref:System.ComponentModel.ITypeDescriptorContext>. When a <xref:System.Windows.Markup.ValueSerializer> derived class API is called, the caller (typically a serializer process) passes a context that may provide certain services. Because of the general guidance that a <xref:System.Windows.Markup.ValueSerializer> must not throw exceptions. Failure to return a particular service from the context must also not throw any exceptions.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.ValueSerializer> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.ValueSerializer> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/ValueSerializerAttribute.xml b/xml/System.Windows.Markup/ValueSerializerAttribute.xml
index b254d87dbee..10672ee1d8a 100644
--- a/xml/System.Windows.Markup/ValueSerializerAttribute.xml
+++ b/xml/System.Windows.Markup/ValueSerializerAttribute.xml
@@ -60,7 +60,7 @@
   
  Value serialization is also applicable for enumerations, interfaces and structures, but not for delegates.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.ValueSerializerAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.ValueSerializerAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml b/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
index fc3fcb3ccd3..d11937fff34 100644
--- a/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
+++ b/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
@@ -40,7 +40,7 @@
 ## Remarks  
  `xml:space` is a related concept that influences XAML processing of white space but is orthogonal to the purpose of <xref:System.Windows.Markup.WhitespaceSignificantCollectionAttribute>. For more information, see [Whitespace Processing in XAML](/dotnet/framework/xaml-services/whitespace-processing-in-xaml).  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.WhitespaceSignificantCollectionAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.WhitespaceSignificantCollectionAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
  <xref:System.Windows.Documents.InlineCollection> is an example [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] class where this attribute is applied.  
diff --git a/xml/System.Windows.Markup/XmlLangPropertyAttribute.xml b/xml/System.Windows.Markup/XmlLangPropertyAttribute.xml
index b66b78d86d2..5464fa1dbc2 100644
--- a/xml/System.Windows.Markup/XmlLangPropertyAttribute.xml
+++ b/xml/System.Windows.Markup/XmlLangPropertyAttribute.xml
@@ -38,7 +38,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.XmlLangPropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.XmlLangPropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XmlnsCompatibleWithAttribute.xml b/xml/System.Windows.Markup/XmlnsCompatibleWithAttribute.xml
index 0852b2f8f05..76af6f0335a 100644
--- a/xml/System.Windows.Markup/XmlnsCompatibleWithAttribute.xml
+++ b/xml/System.Windows.Markup/XmlnsCompatibleWithAttribute.xml
@@ -45,7 +45,7 @@
 [assembly: System.Windows.Markup.XmlnsCompatibleWith("http://www.adatum.com/2003/controls", "http://www.adatum.com/2005/controls")]  
 ```  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.XmlnsCompatibleWithAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.XmlnsCompatibleWithAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml b/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
index d8e46fcbea8..041c197b3e8 100644
--- a/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
+++ b/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
@@ -44,7 +44,7 @@
   
  In a XAML file, if the `xmlns` attribute for an object element or property element matches the <xref:System.Windows.Markup.XmlnsDefinitionAttribute.XmlNamespace%2A> in the <xref:System.Windows.Markup.XmlnsDefinitionAttribute>, the XAML processor uses the <xref:System.Windows.Markup.XmlnsDefinitionAttribute.ClrNamespace%2A> and <xref:System.Windows.Markup.XmlnsDefinitionAttribute.AssemblyName%2A> stored in the <xref:System.Windows.Markup.XmlnsDefinitionAttribute> for type resolution against types in the assembly.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.XmlnsDefinitionAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.XmlnsDefinitionAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XmlnsPrefixAttribute.xml b/xml/System.Windows.Markup/XmlnsPrefixAttribute.xml
index d1a710c670d..8a28b486cac 100644
--- a/xml/System.Windows.Markup/XmlnsPrefixAttribute.xml
+++ b/xml/System.Windows.Markup/XmlnsPrefixAttribute.xml
@@ -46,7 +46,7 @@
   
  In most cases, you apply <xref:System.Windows.Markup.XmlnsPrefixAttribute> only if you have also applied at least one <xref:System.Windows.Markup.XmlnsDefinitionAttribute> in the assembly for that same XAML namespace.  
   
- In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], <xref:System.Windows.Markup.XmlnsPrefixAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.XmlnsPrefixAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## Best Practice for XAML Designer Support or General Serialization  
  Even if you intend the associated XAML namespace to be the default XAML namespace in most usage cases for your framework or library, you should still specify a non-empty string as the recommended prefix for a XAML namespace. Default XAML namespace information is carried in individual XAML files and XAML node streams. The default XAML namespace and how it is defined in a given XAML source can easily be perpetuated for per-case serialization without using <xref:System.Windows.Markup.XmlnsPrefixAttribute>. However, the <xref:System.Windows.Markup.XmlnsPrefixAttribute> is useful for cases where the XAML author has chosen to map the default XAML namespace to something else. In this scenario a XAML text editor embedded in a design environment can use <xref:System.Windows.Markup.XmlnsPrefixAttribute> as a hint for an initial XAML namespace `xmlns` mapping. Or a design environment can add just-in-time mappings to the backing XAML for design metaphors such as dragging objects out of a toolbox and into a visual design surface. Also, it is conceivable that a designer could simultaneously support multiple XAML-enabling frameworks, and has a common XAML serializer that relies on .NET Framework XAML Services rather than framework-specific serialization. Specifying a <xref:System.Windows.Markup.XmlnsPrefixAttribute> for these scenarios helps make the XAML usage for your types more portable and robust if the XAML is exchanged between design tools, or undergoes a round trip between XAML editors and other consumers such as markup compilers or other serialization.  
diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index 062b1c28c77..c0bd640afb7 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -494,7 +494,7 @@
   
  For guidance on the use of this event, see [Resolving Assembly Loads](/dotnet/standard/assembly/resolve-loads).  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property returns the assembly that requested the assembly load that could not be resolved. For example, the loader might be unable to load a dependency of the requesting assembly because the requesting assembly and its dependency are not in the probing path. Knowing the identity of the requesting assembly might be useful in locating the dependency or in identifying the correct version, if more than one version of the dependency is available. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
+ Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property returns the assembly that requested the assembly load that could not be resolved. For example, the loader might be unable to load a dependency of the requesting assembly because the requesting assembly and its dependency are not in the probing path. Knowing the identity of the requesting assembly might be useful in locating the dependency or in identifying the correct version, if more than one version of the dependency is available. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
   
 > [!IMPORTANT]
 >  Beginning with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.ResolveEventHandler> event is raised for all assemblies, including resource assemblies. In earlier versions, the event was not raised for resource assemblies. If the operating system is localized, the handler might be called multiple times: once for each culture in the fallback chain.  
@@ -1056,7 +1056,7 @@
  If `securityInfo` is not supplied, the evidence from the current application domain is used.  
   
 > [!IMPORTANT]
->  Do not use this method overload to create sandboxed application domains. Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
+>  Do not use this method overload to create sandboxed application domains. Beginning with the .NET Framework 4, the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
   
    
   
@@ -1126,7 +1126,7 @@
  If `securityInfo` is not supplied, the evidence from the current application domain is used.  
   
 > [!IMPORTANT]
->  Do not use this method overload to create sandboxed application domains. Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
+>  Do not use this method overload to create sandboxed application domains. Beginning with the .NET Framework 4, the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
   
    
   
@@ -1273,7 +1273,7 @@
  For more information about shadow copying, see <xref:System.AppDomain.ShadowCopyFiles%2A> and [Shadow Copying Assemblies](/dotnet/framework/app-domains/shadow-copy-assemblies).  
   
 > [!IMPORTANT]
->  Do not use this method overload to create sandboxed application domains. Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
+>  Do not use this method overload to create sandboxed application domains. Beginning with the .NET Framework 4, the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
   
    
   
@@ -1353,7 +1353,7 @@
  For more information about shadow copying, see <xref:System.AppDomain.ShadowCopyFiles%2A> and [Shadow Copying Assemblies](/dotnet/framework/app-domains/shadow-copy-assemblies).  
   
 > [!IMPORTANT]
->  Do not use this method overload to create sandboxed application domains. Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
+>  Do not use this method overload to create sandboxed application domains. Beginning with the .NET Framework 4, the evidence that is supplied for `securityInfo` no longer affects the grant set of the application domain. Use the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29> method overload to create sandboxed application domains.  
   
  ]]></format>
         </remarks>
@@ -6477,7 +6477,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
+ Beginning with the .NET Framework 4, the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
   
  This method should be used only to load an assembly into the current application domain. This method is provided as a convenience for interoperability callers who cannot call the static <xref:System.Reflection.Assembly.Load%2A?displayProperty=nameWithType> method. To load assemblies into other application domains, use a method such as <xref:System.AppDomain.CreateInstanceAndUnwrap%2A>.  
   
@@ -6736,7 +6736,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
+ Beginning with the .NET Framework 4, the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
   
  This method should be used only to load an assembly into the current application domain. This method is provided as a convenience for interoperability callers who cannot call the static <xref:System.Reflection.Assembly.Load%2A?displayProperty=nameWithType> method. To load assemblies into other application domains, use a method such as <xref:System.AppDomain.CreateInstanceAndUnwrap%2A>.  
   
@@ -6989,7 +6989,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
+ Beginning with the .NET Framework 4, the trust level of an assembly that is loaded by using this method is the same as the trust level of the application domain.  
   
  This method should be used only to load an assembly into the current application domain. This method is provided as a convenience for interoperability callers who cannot call the static <xref:System.Reflection.Assembly.Load%2A?displayProperty=nameWithType> method. To load assemblies into other application domains, use a method such as <xref:System.AppDomain.CreateInstanceAndUnwrap%2A>.  
   
@@ -7467,7 +7467,7 @@
 > [!IMPORTANT]
 >  This event is raised only for missing dependencies of the assembly that you are loading into the reflection-only context (for example, by using the <xref:System.Reflection.Assembly.ReflectionOnlyLoad%2A?displayProperty=nameWithType> method). It is not raised if the assembly that you are loading cannot be found.  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property returns the assembly that requested the assembly load that could not be resolved. Knowing the identity of the requesting assembly might be useful in identifying the correct version of the dependency, if more than one version is available. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
+ Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property returns the assembly that requested the assembly load that could not be resolved. Knowing the identity of the requesting assembly might be useful in identifying the correct version of the dependency, if more than one version is available. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
   
  For this event, the <xref:System.ResolveEventArgs.Name%2A?displayProperty=nameWithType> property returns the assembly name before policy is applied.  
   
@@ -7654,7 +7654,7 @@
 > [!IMPORTANT]
 >  This event is not raised if resolution fails because no file can be found for a valid linked resource. It is raised if a manifest resource stream cannot be found, but it is not raised if an individual resource key cannot be found.  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property contains the assembly that requested the resource. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
+ Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property contains the assembly that requested the resource. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
   
  To register an event handler for this event, you must have the required permissions, or a <xref:System.Security.SecurityException> is thrown.  
   
@@ -8775,7 +8775,7 @@
   
  However, the <xref:System.AppDomain.TypeResolve> event does not occur if the runtime knows it is not possible to find a type in certain assemblies. For example, this event does not occur if the type is not found in a static assembly because the runtime knows types cannot be added dynamically to static assemblies.  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property contains the assembly that requested the type. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
+ Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property contains the assembly that requested the type. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
   
  To register an event handler for this event, you must have the required permissions, or a <xref:System.Security.SecurityException> is thrown.  
   
@@ -8870,7 +8870,7 @@
   
  If the event handler has a <xref:System.Runtime.ConstrainedExecution.ReliabilityContractAttribute> attribute with the appropriate flags, the event handler is treated as a constrained execution region.  
   
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], this event is not raised for exceptions that corrupt the state of the process, such as stack overflows or access violations, unless the event handler is security-critical and has the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute.  
+ Starting with the .NET Framework 4, this event is not raised for exceptions that corrupt the state of the process, such as stack overflows or access violations, unless the event handler is security-critical and has the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute.  
   
  In the .NET Framework versions 1.0 and 1.1, an unhandled exception that occurs in a thread other than the main application thread is caught by the runtime and therefore does not cause the application to terminate. Thus, it is possible for the <xref:System.AppDomain.UnhandledException> event to be raised without the application terminating. Starting with the .NET Framework version 2.0, this backstop for unhandled exceptions in child threads was removed, because the cumulative effect of such silent failures included performance degradation, corrupted data, and lockups, all of which were difficult to debug. For more information, including a list of cases in which the runtime does not terminate, see [Exceptions in Managed Threads](/dotnet/standard/threading/exceptions-in-managed-threads).  
   
diff --git a/xml/System/AppDomainManager.xml b/xml/System/AppDomainManager.xml
index 10248b7ad65..0088019961a 100644
--- a/xml/System/AppDomainManager.xml
+++ b/xml/System/AppDomainManager.xml
@@ -425,7 +425,7 @@
   
  Also, for add-in activations, a custom implementation could identify the current <xref:System.AppDomain> as the target application domain.  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], you can use this method to sandbox the default application domain at application startup, or to modify the sandbox of a new application domain. To do this, adjust the <xref:System.Security.Policy.ApplicationTrust.DefaultGrantSet%2A> and <xref:System.Security.Policy.ApplicationTrust.FullTrustAssemblies%2A> properties on the <xref:System.Security.Policy.ApplicationTrust> object that is assigned to the <xref:System.AppDomainSetup.ApplicationTrust%2A?displayProperty=nameWithType> property of `appDomainInfo`, before you initialize the application domain.  
+ Beginning with the .NET Framework 4, you can use this method to sandbox the default application domain at application startup, or to modify the sandbox of a new application domain. To do this, adjust the <xref:System.Security.Policy.ApplicationTrust.DefaultGrantSet%2A> and <xref:System.Security.Policy.ApplicationTrust.FullTrustAssemblies%2A> properties on the <xref:System.Security.Policy.ApplicationTrust> object that is assigned to the <xref:System.AppDomainSetup.ApplicationTrust%2A?displayProperty=nameWithType> property of `appDomainInfo`, before you initialize the application domain.  
   
 > [!NOTE]
 >  Only assemblies granted `FullTrust`, such as assemblies in the global assembly cache or identified as `fullTrustAssemblies` in the <xref:System.AppDomain.CreateDomain%28System.String%2CSystem.Security.Policy.Evidence%2CSystem.AppDomainSetup%2CSystem.Security.PermissionSet%2CSystem.Security.Policy.StrongName%5B%5D%29?displayProperty=nameWithType> method can be loaded in the  <xref:System.AppDomainManager.%23ctor%2A> constructor and the <xref:System.AppDomainManager.InitializeNewDomain%2A> method.  
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index aa59f72490a..a149d5467c8 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1089,7 +1089,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> (APTCA) attribute can be made conditional by setting its <xref:System.Security.AllowPartiallyTrustedCallersAttribute.PartialTrustVisibilityLevel%2A> property to <xref:System.Security.PartialTrustVisibilityLevel.NotVisibleByDefault>. An APTCA assembly that is marked with <xref:System.Security.PartialTrustVisibilityLevel.NotVisibleByDefault> cannot be used by partially trusted code unless the host application allows it.  
+ Beginning with the .NET Framework 4, the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> (APTCA) attribute can be made conditional by setting its <xref:System.Security.AllowPartiallyTrustedCallersAttribute.PartialTrustVisibilityLevel%2A> property to <xref:System.Security.PartialTrustVisibilityLevel.NotVisibleByDefault>. An APTCA assembly that is marked with <xref:System.Security.PartialTrustVisibilityLevel.NotVisibleByDefault> cannot be used by partially trusted code unless the host application allows it.  
   
  The host of a sandboxed application domain allows code in the application domain to use assemblies with conditional APTCA attributes by creating an array that contains the simple name and public key of each assembly, and assigning the array to this property. For example, an element of the array might look like the following: "MyAssembly, PublicKey=0024000004800000940000000602000000240000525341310004000001000100db2ad5e5fedc67ea526ff72ad426ef68e08e241d296c499eedfec6648dcc62b1a12f72be5833a45bbec481b68415b08a5fbc9f9ef247b523dd72bbea65bb532784ddc5c704544bd2f1c2d46fdbe41e4f949e76f9947357b2d5cf8ca9f970701bbd6e8ab64ad31b20ad0be9b56dae4f6b83332b92a2a3b8ea2804c40efbc0b6b9".  
   
@@ -1262,7 +1262,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Major versions of the .NET Framework sometimes introduce breaking changes from the previous version. For example, the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] introduces a small number of breaking changes from the .NET Framework 3.5. Use the <xref:System.AppDomainSetup.SetCompatibilitySwitches%2A> method to specify that one or more of these breaking changes should be rolled back for the application domain, to make the behavior compatible with the previous version of the .NET Framework.  
+ Major versions of the .NET Framework sometimes introduce breaking changes from the previous version. For example, the .NET Framework 4 introduces a small number of breaking changes from the .NET Framework 3.5. Use the <xref:System.AppDomainSetup.SetCompatibilitySwitches%2A> method to specify that one or more of these breaking changes should be rolled back for the application domain, to make the behavior compatible with the previous version of the .NET Framework.  
   
  Each time you call this method, it replaces the existing switch settings. To erase the settings, specify `null` for the `switches` parameter.  
   
diff --git a/xml/System/Char.xml b/xml/System/Char.xml
index d1847a30cb8..7911312a31c 100644
--- a/xml/System/Char.xml
+++ b/xml/System/Char.xml
@@ -116,7 +116,7 @@ To determine the Unicode category of a character, call the <xref:System.Char.Get
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.char.class/cs/GetUnicodeCategory3.cs" interactive="try-dotnet" id="Snippet6":::
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.char.class/vb/GetUnicodeCategory3.vb" id="Snippet6":::
 
- Internally, for characters outside the ASCII range (U+0000 through U+00FF), the <xref:System.Char.GetUnicodeCategory%2A> method depends on Unicode categories reported by the <xref:System.Globalization.CharUnicodeInfo> class. Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] to [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Internally, for characters outside the ASCII range (U+0000 through U+00FF), the <xref:System.Char.GetUnicodeCategory%2A> method depends on Unicode categories reported by the <xref:System.Globalization.CharUnicodeInfo> class. Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from .NET Framework 4 to [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
 <a name="Elements"></a>
 ## Characters and text elements
@@ -1033,7 +1033,7 @@ When a managed <xref:System.Char> type, which is represented as a Unicode UTF-16
 ## Remarks
  The <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method does not always return the same <xref:System.Globalization.UnicodeCategory> value as the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method when it is passed a particular character as a parameter. The <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method is designed to reflect the current version of the Unicode standard. In contrast, although the <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method usually reflects the current version of the Unicode standard, it may return a character's category based on a previous version of the standard or it may return a category that differs from the current standard in order to preserve backward compatibility. As a result, we recommend that you use the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method instead of <xref:System.Char.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType>.
 
- Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
  ]]></format>
         </remarks>
@@ -1094,7 +1094,7 @@ When a managed <xref:System.Char> type, which is represented as a Unicode UTF-16
 
  The <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method does not always return the same <xref:System.Globalization.UnicodeCategory> value as the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType> method when it is passed a particular character as a parameter. The <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType> method is designed to reflect the current version of the Unicode standard. In contrast, although the <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method usually reflects the current version of the Unicode standard, it may return a character's category based on a previous version of the standard or it may return a category that differs from the current standard in order to preserve backward compatibility. As a result, we recommend that you use the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method instead of <xref:System.Char.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType>.
 
- Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)] to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
  ]]></format>
         </remarks>
diff --git a/xml/System/Console.xml b/xml/System/Console.xml
index 3efbd211a15..6b5c3be11de 100644
--- a/xml/System/Console.xml
+++ b/xml/System/Console.xml
@@ -1384,7 +1384,7 @@ Columns are numbered from left to right starting at 0. Rows are numbered from to
 ## Remarks
  The console uses the input encoding to translate keyboard input into a corresponding character. The input encoding incorporates a code page that maps 256 keyboard character codes to individual characters. Different code pages include different special characters, typically customized for a language or a group of languages.
 
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], a property get operation may return a cached value instead of the console's current input encoding. This can occur if the value of the <xref:System.Console.InputEncoding%2A> property is modified by some means other than an assignment to the <xref:System.Console.InputEncoding%2A> property, such as calling the Windows `SetConsoleCP` function or using the `chcp` command from a PowerShell script.
+ Starting with the .NET Framework 4, a property get operation may return a cached value instead of the console's current input encoding. This can occur if the value of the <xref:System.Console.InputEncoding%2A> property is modified by some means other than an assignment to the <xref:System.Console.InputEncoding%2A> property, such as calling the Windows `SetConsoleCP` function or using the `chcp` command from a PowerShell script.
 
  ]]></format>
         </remarks>
@@ -2427,7 +2427,7 @@ This method can be used to reacquire the standard output stream after it has bee
 ## Remarks
  The console uses the output encoding to translate characters written by an application into corresponding console display characters. The default code page that the console uses is determined by the system locale.
 
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], a property get operation may return a cached value instead of the console's current output encoding. This can occur if the value of the <xref:System.Console.OutputEncoding%2A> property is modified by some means other than an assignment to the <xref:System.Console.OutputEncoding%2A> property, such as calling the Windows `SetConsoleOutputCP` function.
+ Starting with the .NET Framework 4, a property get operation may return a cached value instead of the console's current output encoding. This can occur if the value of the <xref:System.Console.OutputEncoding%2A> property is modified by some means other than an assignment to the <xref:System.Console.OutputEncoding%2A> property, such as calling the Windows `SetConsoleOutputCP` function.
 
  ]]></format>
         </remarks>
diff --git a/xml/System/Delegate.xml b/xml/System/Delegate.xml
index 643e3ce3890..e172823e34b 100644
--- a/xml/System/Delegate.xml
+++ b/xml/System/Delegate.xml
@@ -107,7 +107,7 @@
 > [!NOTE]
 >  Managed languages use the <xref:System.Delegate.Combine%2A> and <xref:System.Delegate.Remove%2A> methods to implement delegate operations. Examples include the `AddHandler` and `RemoveHandler` statements in Visual Basic and the += and -= operators on delegate types in C#.  
   
- Starting with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], generic delegate types can have variant type parameters. Contravariant type parameters can be used as parameter types of the delegate, and a covariant type parameter can be used as the return type. This feature allows generic delegate types that are constructed from the same generic type definition to be assignment-compatible if their type arguments are reference types with an inheritance relationship, as explained in [Covariance and Contravariance](/dotnet/standard/generics/covariance-and-contravariance).  
+ Starting with the .NET Framework 4, generic delegate types can have variant type parameters. Contravariant type parameters can be used as parameter types of the delegate, and a covariant type parameter can be used as the return type. This feature allows generic delegate types that are constructed from the same generic type definition to be assignment-compatible if their type arguments are reference types with an inheritance relationship, as explained in [Covariance and Contravariance](/dotnet/standard/generics/covariance-and-contravariance).  
   
 > [!NOTE]
 >  Generic delegates that are assignment-compatible because of variance are not necessarily combinable. To be combinable, the types must match exactly. For example, suppose that a class named `Derived` is derived from a class named `Base`. A delegate of type `Action<Base>` (`Action(Of Base)` in Visual Basic) can be assigned to a variable of type `Action<Derived>`, but the two delegates cannot be combined because the types do not match exactly.  
diff --git a/xml/System/MethodAccessException.xml b/xml/System/MethodAccessException.xml
index 4390b344f64..44ed20eee33 100644
--- a/xml/System/MethodAccessException.xml
+++ b/xml/System/MethodAccessException.xml
@@ -64,7 +64,7 @@
 -   The access level of a method in a class library has changed, and one or more assemblies that reference the library have not been recompiled.  
   
 > [!NOTE]
->  Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the common language runtime treats application code as transparent when it is run with partial trust. See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).  
+>  Beginning with the .NET Framework 4, the common language runtime treats application code as transparent when it is run with partial trust. See [Security Considerations for Reflection](/dotnet/framework/reflection-and-codedom/security-considerations-for-reflection).  
   
  <xref:System.MethodAccessException> uses the HRESULT COR_E_METHODACCESS, that has the value 0x80131510.  
   
diff --git a/xml/System/ResolveEventArgs.xml b/xml/System/ResolveEventArgs.xml
index 3dc10fa4394..ec4be667cee 100644
--- a/xml/System/ResolveEventArgs.xml
+++ b/xml/System/ResolveEventArgs.xml
@@ -48,7 +48,7 @@
   
 -   The <xref:System.ResolveEventArgs.Name%2A> property contains the name of the item to be resolved.  
   
--   Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventArgs.RequestingAssembly%2A> property contains the assembly that requested an assembly that can provide the named item. For more information, see the <xref:System.ResolveEventArgs.RequestingAssembly%2A> property.  
+-   Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A> property contains the assembly that requested an assembly that can provide the named item. For more information, see the <xref:System.ResolveEventArgs.RequestingAssembly%2A> property.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System/ResolveEventHandler.xml b/xml/System/ResolveEventHandler.xml
index a8e9ff6df0f..989707bce46 100644
--- a/xml/System/ResolveEventHandler.xml
+++ b/xml/System/ResolveEventHandler.xml
@@ -66,7 +66,7 @@
  If the runtime class loader cannot resolve a reference to an assembly, type, or resource, the corresponding events are raised to give the callback a chance to tell the runtime which assembly the referenced assembly, type, or resource is in. It is the responsibility of the <xref:System.ResolveEventHandler> to return the assembly that resolves the type, assembly, or resource, or to return null if the assembly is not recognized. For more information, see [Resolving Assembly Loads](/dotnet/standard/assembly/resolve-loads) and the <xref:System.AppDomain.ResourceResolve?displayProperty=nameWithType>, <xref:System.AppDomain.AssemblyResolve?displayProperty=nameWithType>, and <xref:System.AppDomain.ReflectionOnlyAssemblyResolve?displayProperty=nameWithType> events.  
   
 > [!IMPORTANT]
->  Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.ResolveEventHandler?displayProperty=nameWithType> event is raised for all assemblies, including resource assemblies. In earlier versions, the event was not raised for resource assemblies. If the operating system is localized, the handler might be called multiple times: once for each culture in the fallback chain.  
+>  Beginning with the .NET Framework 4, the <xref:System.ResolveEventHandler?displayProperty=nameWithType> event is raised for all assemblies, including resource assemblies. In earlier versions, the event was not raised for resource assemblies. If the operating system is localized, the handler might be called multiple times: once for each culture in the fallback chain.  
   
  Every derived class of <xref:System.Delegate> and <xref:System.MulticastDelegate> has a constructor and an `Invoke` method. See the C++ code example in the description for the <xref:System.Delegate> class.  
   
diff --git a/xml/System/String.xml b/xml/System/String.xml
index 8210ae23429..d03717156db 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -186,7 +186,7 @@ For more information about Unicode, UTF-16, code units, code points, and the <xr
 |.NET Framework 1.1|[The Unicode Standard, Version 4.0.0](https://www.unicode.org/versions/Unicode4.0.0/)|
 |.NET Framework 2.0|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |.NET Framework 3.5|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
-|[!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
+|.NET Framework 4|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 7|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 8 and later Windows operating systems|[The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/)|
 |.NET Core and .NET 5+|Depends on the version of the Unicode Standard supported by the underlying operating system.|
diff --git a/xml/System/TimeSpan.xml b/xml/System/TimeSpan.xml
index 29488d9cdef..4e7bd4c7a20 100644
--- a/xml/System/TimeSpan.xml
+++ b/xml/System/TimeSpan.xml
@@ -128,7 +128,7 @@
 ## Formatting a TimeSpan Value  
  A <xref:System.TimeSpan> value can be represented as [*-*]*d*.*hh*:*mm*:*ss*.*ff*, where the optional minus sign indicates a negative time interval, the *d* component is days, *hh* is hours as measured on a 24-hour clock, *mm* is minutes, *ss* is seconds, and *ff* is fractions of a second. That is, a time interval consists of a positive or negative number of days without a time of day, or a number of days with a time of day, or only a time of day.  
   
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the <xref:System.TimeSpan> structure supports culture-sensitive formatting through the overloads of its <xref:System.TimeSpan.ToString%2A> method, which converts a <xref:System.TimeSpan> value to its string representation. The default <xref:System.TimeSpan.ToString?displayProperty=nameWithType> method returns a time interval by using an invariant format that is identical to its return value in previous versions of the .NET Framework. The <xref:System.TimeSpan.ToString%28System.String%29?displayProperty=nameWithType> overload lets you specify a format string that defines the string representation of the time interval. The <xref:System.TimeSpan.ToString%28System.String%2CSystem.IFormatProvider%29?displayProperty=nameWithType> overload lets you specify a format string and the culture whose formatting conventions are used to create the string representation of the time interval. <xref:System.TimeSpan> supports both standard and custom format strings. (For more information, see [Standard TimeSpan Format Strings](/dotnet/standard/base-types/standard-timespan-format-strings) and [Custom TimeSpan Format Strings](/dotnet/standard/base-types/custom-timespan-format-strings).) However, only standard format strings are culture-sensitive.  
+ Beginning with the .NET Framework 4, the <xref:System.TimeSpan> structure supports culture-sensitive formatting through the overloads of its <xref:System.TimeSpan.ToString%2A> method, which converts a <xref:System.TimeSpan> value to its string representation. The default <xref:System.TimeSpan.ToString?displayProperty=nameWithType> method returns a time interval by using an invariant format that is identical to its return value in previous versions of the .NET Framework. The <xref:System.TimeSpan.ToString%28System.String%29?displayProperty=nameWithType> overload lets you specify a format string that defines the string representation of the time interval. The <xref:System.TimeSpan.ToString%28System.String%2CSystem.IFormatProvider%29?displayProperty=nameWithType> overload lets you specify a format string and the culture whose formatting conventions are used to create the string representation of the time interval. <xref:System.TimeSpan> supports both standard and custom format strings. (For more information, see [Standard TimeSpan Format Strings](/dotnet/standard/base-types/standard-timespan-format-strings) and [Custom TimeSpan Format Strings](/dotnet/standard/base-types/custom-timespan-format-strings).) However, only standard format strings are culture-sensitive.  
   
 ## Restoring Legacy TimeSpan Formatting  
  In some cases, code that successfully formats <xref:System.TimeSpan> values in .NET Framework 3.5 and earlier versions fails in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. This is most common in code that calls a [<TimeSpan_LegacyFormatMode> element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) method to format a <xref:System.TimeSpan> value with a format string. The following example successfully formats a <xref:System.TimeSpan> value in .NET Framework 3.5 and earlier versions, but throws an exception in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions. Note that it attempts to format a <xref:System.TimeSpan> value by using an unsupported format specifier, which is ignored in .NET Framework 3.5 and earlier versions.  
@@ -4199,7 +4199,7 @@ This member is an explicit interface member implementation. It can be used only
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>Support for formatting <see cref="T:System.TimeSpan" /> values was added in the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)]. However, the <see cref="M:System.TimeSpan.ToString" /> method overload remains culture-insensitive. Its behavior remains unchanged from previous versions of the .NET Framework. To control the formatting of a <see cref="T:System.TimeSpan" /> value, call the <see cref="M:System.TimeSpan.ToString(System.String)" /> or <see cref="M:System.TimeSpan.ToString(System.String,System.IFormatProvider)" /> overload.</para>
+          <para>Support for formatting <see cref="T:System.TimeSpan" /> values was added in the .NET Framework 4. However, the <see cref="M:System.TimeSpan.ToString" /> method overload remains culture-insensitive. Its behavior remains unchanged from previous versions of the .NET Framework. To control the formatting of a <see cref="T:System.TimeSpan" /> value, call the <see cref="M:System.TimeSpan.ToString(System.String)" /> or <see cref="M:System.TimeSpan.ToString(System.String,System.IFormatProvider)" /> overload.</para>
         </block>
         <altmember cref="T:System.String" />
         <altmember cref="M:System.TimeSpan.Parse(System.String)" />
diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 41fc556ed37..91434971bd6 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -12060,7 +12060,7 @@ Byref-like structures are declared using `ref struct` keyword in C#. An instance
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Beginning with the [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)], the common language runtime supports the embedding of type information for COM types directly into managed assemblies, instead of requiring the managed assemblies to obtain type information for COM types from interop assemblies. Because the embedded type information includes only the types and members that are actually used by a managed assembly, two managed assemblies might have very different views of the same COM type. Each managed assembly has a different <xref:System.Type> object to represent its view of the COM type. The common language runtime supports type equivalence between these different views for interfaces, structures, enumerations, and delegates.  
+ Beginning with the .NET Framework 4, the common language runtime supports the embedding of type information for COM types directly into managed assemblies, instead of requiring the managed assemblies to obtain type information for COM types from interop assemblies. Because the embedded type information includes only the types and members that are actually used by a managed assembly, two managed assemblies might have very different views of the same COM type. Each managed assembly has a different <xref:System.Type> object to represent its view of the COM type. The common language runtime supports type equivalence between these different views for interfaces, structures, enumerations, and delegates.  
   
  Type equivalence means that a COM object that is passed from one managed assembly to another can be cast to the appropriate managed type in the receiving assembly. The <xref:System.Type.IsEquivalentTo%2A> method enables an assembly to determine that a COM object obtained from another assembly has the same COM identity as one of the first assembly's own embedded interop types, and thus can be cast to that type.  
   
diff --git a/xml/ns-System.Runtime.Caching.xml b/xml/ns-System.Runtime.Caching.xml
index 0585e14d347..d0f320c17e1 100644
--- a/xml/ns-System.Runtime.Caching.xml
+++ b/xml/ns-System.Runtime.Caching.xml
@@ -8,7 +8,7 @@
  The classes in this namespace provide a way to use caching facilities like those in ASP.NET, but without a dependency on the `System.Web` assembly.
 
 > [!NOTE]
->  The output caching functionality and types in the <xref:System.Runtime.Caching> namespace were introduced in [!INCLUDE[net_v40_long](~/includes/net-v40-long-md.md)].
+>  The output caching functionality and types in the <xref:System.Runtime.Caching> namespace were introduced in .NET Framework 4.
 
  The caching types that are provided in this namespace offer the following features:
 

From a6405ddad0add7a1972f01b1289df7f63ddfe0b0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:20:54 -0800
Subject: [PATCH 036/236] net-v40-short

---
 xml/System.Globalization/CompareInfo.xml         |  2 +-
 xml/System.Globalization/CultureInfo.xml         |  4 ++--
 xml/System.Globalization/SortVersion.xml         |  4 ++--
 xml/System.Reflection/Assembly.xml               |  2 +-
 xml/System.Runtime.Caching/ObjectCache.xml       | 10 +++++-----
 ...eProcessCorruptedStateExceptionsAttribute.xml |  2 +-
 .../SecurityAction.xml                           | 16 ++++++++--------
 xml/System.Security.Policy/EvidenceBase.xml      |  4 ++--
 xml/System.Security.Policy/PolicyLevel.xml       |  2 +-
 .../AllowPartiallyTrustedCallersAttribute.xml    |  4 ++--
 xml/System.Security/SecurityRulesAttribute.xml   |  2 +-
 xml/System.Text.RegularExpressions/Regex.xml     | 12 ++++++------
 xml/System.Threading.Tasks/Task.xml              |  2 +-
 xml/System.Threading.Tasks/Task`1.xml            |  2 +-
 xml/System.Threading/ThreadPool.xml              |  6 +++---
 xml/System.Web.Compilation/BuildManager.xml      |  4 ++--
 xml/System.Web.Configuration/TrustSection.xml    |  2 +-
 .../HostSecurityPolicyResolver.xml               |  2 +-
 xml/System.Web.RegularExpressions/TagRegex35.xml |  2 +-
 xml/System.Windows.Controls/SpellCheck.xml       |  2 +-
 xml/System.Windows.Documents/Run.xml             |  4 ++--
 .../IComponentConnector.xml                      |  2 +-
 .../IReceiveMarkupExtension.xml                  |  4 ++--
 xml/System.Windows.Markup/MarkupExtension.xml    |  2 +-
 xml/System.Windows.Markup/NullExtension.xml      |  2 +-
 xml/System.Windows.Markup/ParserContext.xml      |  2 +-
 xml/System.Windows.Markup/StaticExtension.xml    |  4 ++--
 .../UsableDuringInitializationAttribute.xml      |  2 +-
 xml/System.Windows.Markup/XamlParseException.xml |  2 +-
 xml/System.Windows.Markup/XamlReader.xml         |  2 +-
 xml/System.Windows.Markup/XamlTypeMapper.xml     |  2 +-
 xml/System.Windows.Media/Visual.xml              |  2 +-
 xml/System.Windows/NameScope.xml                 |  2 +-
 xml/System.Windows/StaticResourceExtension.xml   |  2 +-
 .../ReceiveActivity.xml                          |  2 +-
 xml/System.Workflow.Activities/SendActivity.xml  |  2 +-
 xml/System/AppDomain.xml                         |  4 ++--
 xml/System/AppDomainSetup.xml                    |  2 +-
 xml/System/BadImageFormatException.xml           |  2 +-
 xml/System/ConsoleCancelEventArgs.xml            |  2 +-
 xml/System/DateTime.xml                          | 10 +++++-----
 xml/System/DateTimeOffset.xml                    | 10 +++++-----
 xml/System/String.xml                            |  8 ++++----
 xml/System/TimeSpan.xml                          |  2 +-
 xml/ns-System.Runtime.Caching.Hosting.xml        |  2 +-
 45 files changed, 83 insertions(+), 83 deletions(-)

diff --git a/xml/System.Globalization/CompareInfo.xml b/xml/System.Globalization/CompareInfo.xml
index a6a8d1cfbbd..03667531e26 100644
--- a/xml/System.Globalization/CompareInfo.xml
+++ b/xml/System.Globalization/CompareInfo.xml
@@ -5159,7 +5159,7 @@ This method has greater overhead than other <xref:System.Globalization.CompareIn
 
 |.NET Framework version|Operating system|Unicode version|
 |----------------------------|----------------------|---------------------|
-|[!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]|All operating systems|Unicode 5.0|
+|.NET Framework 4|All operating systems|Unicode 5.0|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.3|
 
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index ef671980ea8..865c62ea41c 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -94,7 +94,7 @@
 
 <a name="CultureNames"></a>   
 ## Culture names and identifiers  
- The <xref:System.Globalization.CultureInfo> class specifies a unique name for each culture, based on RFC 4646. The name is a combination of an ISO 639 two-letter lowercase culture code associated with a language and an ISO 3166 two-letter uppercase subculture code associated with a country or region. In addition, for apps that target [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later and are running under Windows 10 or later, culture names that correspond to valid BCP-47 language tags are supported.  
+ The <xref:System.Globalization.CultureInfo> class specifies a unique name for each culture, based on RFC 4646. The name is a combination of an ISO 639 two-letter lowercase culture code associated with a language and an ISO 3166 two-letter uppercase subculture code associated with a country or region. In addition, for apps that target .NET Framework 4 or later and are running under Windows 10 or later, culture names that correspond to valid BCP-47 language tags are supported.  
   
 > [!NOTE]
 >  When a culture name is passed to a class constructor or a method such as <xref:System.Globalization.CultureInfo.CreateSpecificCulture%2A> or <xref:System.Globalization.CultureInfo>, its case is not significant.  
@@ -1234,7 +1234,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
 > [!NOTE]
 >  Changing the culture by using the <xref:System.Globalization.CultureInfo.CurrentCulture%2A?displayProperty=nameWithType> property requires a <xref:System.Security.Permissions.SecurityPermission> permission with the <xref:System.Security.Permissions.SecurityPermissionFlag.ControlThread> value set. Manipulating threads is dangerous because of the security state associated with threads. Therefore, this permission should be given only to trustworthy code, and then only as necessary. You cannot change thread culture in semi-trusted code.  
   
- Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], you can explicitly change the current thread culture to either a specific culture (such as French (Canada)) or a neutral culture (such as French). When a <xref:System.Globalization.CultureInfo> object represents a neutral culture, the values of <xref:System.Globalization.CultureInfo> properties such as <xref:System.Globalization.CultureInfo.Calendar%2A>, <xref:System.Globalization.CultureInfo.CompareInfo%2A>, <xref:System.Globalization.CultureInfo.DateTimeFormat%2A>, <xref:System.Globalization.CultureInfo.NumberFormat%2A>, and <xref:System.Globalization.CultureInfo.TextInfo%2A> reflect the specific culture that is associated with the neutral culture. For example, the dominant culture for the English neutral culture is English (United States); the dominant culture for the German culture is German (Germany). The following example illustrates the difference in formatting when the current culture is set to a specific culture, French (Canada), and a neutral culture, French.  
+ Starting with the .NET Framework 4, you can explicitly change the current thread culture to either a specific culture (such as French (Canada)) or a neutral culture (such as French). When a <xref:System.Globalization.CultureInfo> object represents a neutral culture, the values of <xref:System.Globalization.CultureInfo> properties such as <xref:System.Globalization.CultureInfo.Calendar%2A>, <xref:System.Globalization.CultureInfo.CompareInfo%2A>, <xref:System.Globalization.CultureInfo.DateTimeFormat%2A>, <xref:System.Globalization.CultureInfo.NumberFormat%2A>, and <xref:System.Globalization.CultureInfo.TextInfo%2A> reflect the specific culture that is associated with the neutral culture. For example, the dominant culture for the English neutral culture is English (United States); the dominant culture for the German culture is German (Germany). The following example illustrates the difference in formatting when the current culture is set to a specific culture, French (Canada), and a neutral culture, French.  
   
  [!code-csharp[System.Globalization.CultureInfo.CurrentCulture#12](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/cs/specific12.cs#12)]
  [!code-vb[System.Globalization.CultureInfo.CurrentCulture#12](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/vb/specific12.vb#12)]  
diff --git a/xml/System.Globalization/SortVersion.xml b/xml/System.Globalization/SortVersion.xml
index efc793fd3f6..75eff611aee 100644
--- a/xml/System.Globalization/SortVersion.xml
+++ b/xml/System.Globalization/SortVersion.xml
@@ -50,7 +50,7 @@
 
 ### Sorting and string comparison in the .NET Framework
 
- From the .NET Framework 2.0 Service Pack 1 through the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the presence of these tables depends on the operating system:  
+ From the .NET Framework 2.0 Service Pack 1 through the .NET Framework 4, each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the presence of these tables depends on the operating system:  
   
 -   On [!INCLUDE[win7](~/includes/win7-md.md)] and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
   
@@ -60,7 +60,7 @@
   
 |.NET Framework version|Operating system|Unicode version|  
 |----------------------------|----------------------|---------------------|  
-|[!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]|All operating systems|Unicode 5.0|  
+|.NET Framework 4|All operating systems|Unicode 5.0|  
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions of the .NET Framework|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|  
 |[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions of the .NET Framework|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.0|  
   
diff --git a/xml/System.Reflection/Assembly.xml b/xml/System.Reflection/Assembly.xml
index 53483024d8e..3eb2eb625db 100644
--- a/xml/System.Reflection/Assembly.xml
+++ b/xml/System.Reflection/Assembly.xml
@@ -6242,7 +6242,7 @@ In .NET 5.0 and later versions, for bundled assemblies, the value returned is an
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- Use this method to load a local assembly that the operating system has flagged as having been loaded from the Web (for example, a temporary file that was downloaded from the Internet or intranet). Before the .NET Framework 4, such assemblies were automatically loaded into a sandboxed application domain. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], they are loaded with full trust.
+ Use this method to load a local assembly that the operating system has flagged as having been loaded from the Web (for example, a temporary file that was downloaded from the Internet or intranet). Before the .NET Framework 4, such assemblies were automatically loaded into a sandboxed application domain. Starting with the .NET Framework 4, they are loaded with full trust.
 
  As an alternative to using this method, you can apply the [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element) in your application configuration file. This causes the common language runtime to revert to the security policy of the .NET Framework 3.5.
 
diff --git a/xml/System.Runtime.Caching/ObjectCache.xml b/xml/System.Runtime.Caching/ObjectCache.xml
index 2f1c140cf4e..057f264c72d 100644
--- a/xml/System.Runtime.Caching/ObjectCache.xml
+++ b/xml/System.Runtime.Caching/ObjectCache.xml
@@ -29,9 +29,9 @@
  The <xref:System.Runtime.Caching.ObjectCache> type is the primary type for the in-memory object cache. To develop a custom cache implementation, you derive from the <xref:System.Runtime.Caching.ObjectCache> class.  
   
 > [!NOTE]
->  The <xref:System.Runtime.Caching.ObjectCache> class is new as of the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
+>  The <xref:System.Runtime.Caching.ObjectCache> class is new as of the .NET Framework 4.  
   
- The built-in <xref:System.Runtime.Caching.MemoryCache> class derives from the <xref:System.Runtime.Caching.ObjectCache> class. The <xref:System.Runtime.Caching.MemoryCache> class is the only concrete object cache implementation in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] that derives from the <xref:System.Runtime.Caching.ObjectCache> class.  
+ The built-in <xref:System.Runtime.Caching.MemoryCache> class derives from the <xref:System.Runtime.Caching.ObjectCache> class. The <xref:System.Runtime.Caching.MemoryCache> class is the only concrete object cache implementation in the .NET Framework 4 that derives from the <xref:System.Runtime.Caching.ObjectCache> class.  
   
  ]]></format>
     </remarks>
@@ -148,7 +148,7 @@
         <param name="key">A unique identifier for the cache entry.</param>
         <param name="value">The object to insert.</param>
         <param name="absoluteExpiration">The fixed date and time at which the cache entry will expire. This parameter is required when the <see cref="Overload:System.Runtime.Caching.ObjectCache.Add" /> method is called.</param>
-        <param name="regionName">Optional. A named region in the cache to which the cache entry can be added, if regions are implemented. Because regions are not implemented in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the default value is <see langword="null" />.</param>
+        <param name="regionName">Optional. A named region in the cache to which the cache entry can be added, if regions are implemented. Because regions are not implemented in .NET Framework 4, the default value is <see langword="null" />.</param>
         <summary>When overridden in a derived class, inserts a cache entry into the cache without overwriting any existing cache entry.</summary>
         <returns>
           <see langword="true" /> if insertion succeeded, or <see langword="false" /> if there is an already an entry in the cache that has the same key as <paramref name="key" />.</returns>
@@ -452,7 +452,7 @@
       </Parameters>
       <Docs>
         <param name="key">A unique identifier for the cache entry to get.</param>
-        <param name="regionName">Optional. A named region in the cache to which the cache was added, if regions are implemented. Because regions are not implemented in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the default is <see langword="null" />.</param>
+        <param name="regionName">Optional. A named region in the cache to which the cache was added, if regions are implemented. Because regions are not implemented in .NET Framework 4, the default is <see langword="null" />.</param>
         <summary>When overridden in a derived class, gets the specified cache entry from the cache as a <see cref="T:System.Runtime.Caching.CacheItem" /> instance.</summary>
         <returns>The cache entry that is identified by <paramref name="key" />.</returns>
         <remarks>
@@ -605,7 +605,7 @@
         </Parameter>
       </Parameters>
       <Docs>
-        <param name="regionName">Optional. A named region in the cache to which the cache entry or entries were added, if regions are implemented. Because regions are not implemented in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the default is <see langword="null" />.</param>
+        <param name="regionName">Optional. A named region in the cache to which the cache entry or entries were added, if regions are implemented. Because regions are not implemented in .NET Framework 4, the default is <see langword="null" />.</param>
         <param name="keys">A collection of unique identifiers for the cache entries to get.</param>
         <summary>Gets a set of cache entries that correspond to the specified keys.</summary>
         <returns>A dictionary of key/value pairs that represent cache entries.</returns>
diff --git a/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml b/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
index 9df2c29c6ee..fd34bca4468 100644
--- a/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
+++ b/xml/System.Runtime.ExceptionServices/HandleProcessCorruptedStateExceptionsAttribute.xml
@@ -46,7 +46,7 @@
   
  By default, the common language runtime (CLR) does not deliver these exceptions to managed code, and the `try`/`catch` blocks (and other exception-handling clauses) are not invoked for them. If you are absolutely sure that you want to maintain your handling of these exceptions, you must apply the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute to the method whose exception-handling clauses you want to execute. The CLR delivers the corrupted process state exception to applicable exception clauses only in methods that have both the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> and <xref:System.Security.SecurityCriticalAttribute> attributes.  
   
- You can also add the [\<legacyCorruptedStateExceptionsPolicy>](/dotnet/framework/configure-apps/file-schema/runtime/legacycorruptedstateexceptionspolicy-element) element to your application's configuration file. This will ensure that corrupted state exceptions are delivered to your exception handlers without the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> or <xref:System.Security.SecurityCriticalAttribute> attribute. This configuration element has no effect on applications that were compiled in versions previous to the .NET Framework 4 but are running in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later; corrupted state exceptions will continue to be delivered for those applications. The <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute is ignored when it is encountered in partially trusted or transparent code, because a trusted host should not allow an untrusted add-in to catch and ignore these serious exceptions.  
+ You can also add the [\<legacyCorruptedStateExceptionsPolicy>](/dotnet/framework/configure-apps/file-schema/runtime/legacycorruptedstateexceptionspolicy-element) element to your application's configuration file. This will ensure that corrupted state exceptions are delivered to your exception handlers without the <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> or <xref:System.Security.SecurityCriticalAttribute> attribute. This configuration element has no effect on applications that were compiled in versions previous to the .NET Framework 4 but are running in the .NET Framework 4 or later; corrupted state exceptions will continue to be delivered for those applications. The <xref:System.Runtime.ExceptionServices.HandleProcessCorruptedStateExceptionsAttribute> attribute is ignored when it is encountered in partially trusted or transparent code, because a trusted host should not allow an untrusted add-in to catch and ignore these serious exceptions.  
   
  For more information about corrupted process state exceptions, see the entry [Handling Corrupted State Exceptions](https://go.microsoft.com/fwlink/?LinkID=179681) in the CLR Inside Out blog.  
  
diff --git a/xml/System.Security.Permissions/SecurityAction.xml b/xml/System.Security.Permissions/SecurityAction.xml
index 6f5402d29dd..84625935641 100644
--- a/xml/System.Security.Permissions/SecurityAction.xml
+++ b/xml/System.Security.Permissions/SecurityAction.xml
@@ -71,21 +71,21 @@
  The following table describes the time that each security action takes place and the targets that it supports.  
   
 > [!IMPORTANT]
->  In the .NET Framework 4, runtime support has been removed for enforcing the Deny, RequestMinimum, RequestOptional, and RequestRefuse permission requests. These requests should not be used in code that is based on [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  In the .NET Framework 4, runtime support has been removed for enforcing the Deny, RequestMinimum, RequestOptional, and RequestRefuse permission requests. These requests should not be used in code that is based on .NET Framework 4 or later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
 
- You should not use `LinkDemand` in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. Instead, use the <xref:System.Security.SecurityCriticalAttribute> to restrict usage to fully trusted applications, or use `Demand` to restrict partially trusted callers.  
+ You should not use `LinkDemand` in the .NET Framework 4. Instead, use the <xref:System.Security.SecurityCriticalAttribute> to restrict usage to fully trusted applications, or use `Demand` to restrict partially trusted callers.  
   
 |Declaration of security action|Time of action|Targets supported|  
 |------------------------------------|--------------------|-----------------------|  
-|`LinkDemand` (do not use in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)])|Just-in-time compilation|Class, method|  
+|`LinkDemand` (do not use in the .NET Framework 4)|Just-in-time compilation|Class, method|  
 |`InheritanceDemand`|Load time|Class, method|  
 |`Demand`|Run time|Class, method|  
 |`Assert`|Run time|Class, method|  
-|`Deny` (obsolete in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)])|Run time|Class, method|  
+|`Deny` (obsolete in the .NET Framework 4)|Run time|Class, method|  
 |`PermitOnly`|Run time|Class, method|  
-|`RequestMinimum` (obsolete in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)])|Grant time|Assembly|  
-|`RequestOptional` (obsolete in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)])|Grant time|Assembly|  
-|`RequestRefuse` (obsolete in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)])|Grant time|Assembly|  
+|`RequestMinimum` (obsolete in the .NET Framework 4)|Grant time|Assembly|  
+|`RequestOptional` (obsolete in the .NET Framework 4)|Grant time|Assembly|  
+|`RequestRefuse` (obsolete in the .NET Framework 4)|Grant time|Assembly|  
   
  For additional information about attribute targets, see <xref:System.Attribute>.  
   
@@ -318,7 +318,7 @@
       </ReturnValue>
       <MemberValue>6</MemberValue>
       <Docs>
-        <summary>The immediate caller is required to have been granted the specified permission. Do not use in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For full trust, use <see cref="T:System.Security.SecurityCriticalAttribute" /> instead; for partial trust, use <see cref="F:System.Security.Permissions.SecurityAction.Demand" />.</summary>
+        <summary>The immediate caller is required to have been granted the specified permission. Do not use in the .NET Framework 4. For full trust, use <see cref="T:System.Security.SecurityCriticalAttribute" /> instead; for partial trust, use <see cref="F:System.Security.Permissions.SecurityAction.Demand" />.</summary>
       </Docs>
     </Member>
     <Member MemberName="PermitOnly">
diff --git a/xml/System.Security.Policy/EvidenceBase.xml b/xml/System.Security.Policy/EvidenceBase.xml
index d9d3db2b732..437bb97a1f8 100644
--- a/xml/System.Security.Policy/EvidenceBase.xml
+++ b/xml/System.Security.Policy/EvidenceBase.xml
@@ -46,9 +46,9 @@
   
  This presented a problem because there were implicit restrictions on which types could be used as evidence objects. Specifically, any object used as evidence had to be serializable and could not be `null`. If these requirements were not met, the CLR threw an exception whenever an operation that required one of these assumptions was performed.  
   
- The <xref:System.Security.Policy.EvidenceBase> class, which all evidence objects must derive from, was introduced in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] to enable constraints on the types of objects that can be used as evidence and to provide the ability to add new features and requirements to all evidence objects. The <xref:System.Security.Policy.EvidenceBase> class ensures, upon instantiation, that the evidence object is serializable. In addition, it enables new evidence requirements to be created by adding new default implementations to the base class.  
+ The <xref:System.Security.Policy.EvidenceBase> class, which all evidence objects must derive from, was introduced in the .NET Framework 4 to enable constraints on the types of objects that can be used as evidence and to provide the ability to add new features and requirements to all evidence objects. The <xref:System.Security.Policy.EvidenceBase> class ensures, upon instantiation, that the evidence object is serializable. In addition, it enables new evidence requirements to be created by adding new default implementations to the base class.  
   
- All the types used by the CLR as evidence objects have been updated in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] to derive from <xref:System.Security.Policy.EvidenceBase>.  
+ All the types used by the CLR as evidence objects have been updated in the .NET Framework 4 to derive from <xref:System.Security.Policy.EvidenceBase>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Policy/PolicyLevel.xml b/xml/System.Security.Policy/PolicyLevel.xml
index 61fa5ad97dd..4fad25c2c38 100644
--- a/xml/System.Security.Policy/PolicyLevel.xml
+++ b/xml/System.Security.Policy/PolicyLevel.xml
@@ -47,7 +47,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Starting with the .NET Framework 4, the common language runtime (CLR) is moving away from providing security policy for computers. We recommend that you use [Windows Software Restriction Policies (SRP)](https://go.microsoft.com/fwlink/?LinkId=178101) or [AppLocker](https://go.microsoft.com/fwlink/?LinkId=178102) as a replacement for CLR security policy. The information in this topic applies to the .NET Framework version 3.5 and earlier; it does not apply to the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  Starting with the .NET Framework 4, the common language runtime (CLR) is moving away from providing security policy for computers. We recommend that you use [Windows Software Restriction Policies (SRP)](https://go.microsoft.com/fwlink/?LinkId=178101) or [AppLocker](https://go.microsoft.com/fwlink/?LinkId=178102) as a replacement for CLR security policy. The information in this topic applies to the .NET Framework version 3.5 and earlier; it does not apply to the .NET Framework 4 and later. For more information about this and other changes, see [Security Changes](/dotnet/framework/security/security-changes).  
   
  The highest level of security policy is enterprise-wide. Successive lower levels of hierarchy represent further policy restrictions, but can never grant more permissions than allowed by higher levels. The following policy levels are implemented:  
   
diff --git a/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml b/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
index 177e9332062..baea8ab9f01 100644
--- a/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
+++ b/xml/System.Security/AllowPartiallyTrustedCallersAttribute.xml
@@ -56,9 +56,9 @@
 > Partially trusted code is no longer supported. This attribute has no effect in .NET Core.
   
 > [!NOTE]
->  The .NET Framework 4 introduces new security rules that affect the behavior of the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> attribute (see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2)). In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], all code defaults to security-transparent, that is, partially trusted. However, you can annotate individual types and members to assign them other transparency attributes. For this and other security changes, see [Security Changes](/dotnet/framework/security/security-changes).  
+>  The .NET Framework 4 introduces new security rules that affect the behavior of the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> attribute (see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2)). In the .NET Framework 4, all code defaults to security-transparent, that is, partially trusted. However, you can annotate individual types and members to assign them other transparency attributes. For this and other security changes, see [Security Changes](/dotnet/framework/security/security-changes).  
   
- .NET Framework version 2.0 () assemblies must be strong-named to effectively use the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> (APTCA) attribute. [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] () assemblies do not have to be strong-named for the APTCA attribute to be effective, and they can contain transparent, security-critical and security-safe-critical code. For more information about applying attributes at the assembly level, see [Applying Attributes](/dotnet/standard/attributes/applying-attributes).  
+ .NET Framework version 2.0 () assemblies must be strong-named to effectively use the <xref:System.Security.AllowPartiallyTrustedCallersAttribute> (APTCA) attribute. .NET Framework 4 () assemblies do not have to be strong-named for the APTCA attribute to be effective, and they can contain transparent, security-critical and security-safe-critical code. For more information about applying attributes at the assembly level, see [Applying Attributes](/dotnet/standard/attributes/applying-attributes).  
   
  By default, if a strong-named,  assembly does not explicitly apply this attribute at the assembly level, it can be called only by other assemblies that are granted full trust. This restriction is enforced by placing a <xref:System.Security.Permissions.SecurityAction.LinkDemand> for `FullTrust` on every public or protected method on every publicly accessible class in the assembly. Assemblies that are intended to be called by partially trusted code can declare their intent through the use of <xref:System.Security.AllowPartiallyTrustedCallersAttribute>. An example of the declaration in C# is `[assembly:AllowPartiallyTrustedCallers]`; an example in Visual Basic is `<assembly:AllowPartiallyTrustedCallers>`.  
   
diff --git a/xml/System.Security/SecurityRulesAttribute.xml b/xml/System.Security/SecurityRulesAttribute.xml
index f76629bbd44..cbc4def1f73 100644
--- a/xml/System.Security/SecurityRulesAttribute.xml
+++ b/xml/System.Security/SecurityRulesAttribute.xml
@@ -87,7 +87,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you specify the `ruleSet` parameter, use <xref:System.Security.SecurityRuleSet.Level1> for .NET Framework version 2.0 rules or <xref:System.Security.SecurityRuleSet.Level2> for [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] rules. For more information about <xref:System.Security.SecurityRuleSet.Level1> behavior, see [Security-Transparent Code, Level 1](/dotnet/framework/misc/security-transparent-code-level-1). For information about <xref:System.Security.SecurityRuleSet.Level2> behavior, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
+ When you specify the `ruleSet` parameter, use <xref:System.Security.SecurityRuleSet.Level1> for .NET Framework version 2.0 rules or <xref:System.Security.SecurityRuleSet.Level2> for .NET Framework 4 rules. For more information about <xref:System.Security.SecurityRuleSet.Level1> behavior, see [Security-Transparent Code, Level 1](/dotnet/framework/misc/security-transparent-code-level-1). For information about <xref:System.Security.SecurityRuleSet.Level2> behavior, see [Security-Transparent Code, Level 2](/dotnet/framework/misc/security-transparent-code-level-2).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Text.RegularExpressions/Regex.xml b/xml/System.Text.RegularExpressions/Regex.xml
index 39bd35385e3..4f4522c1e21 100644
--- a/xml/System.Text.RegularExpressions/Regex.xml
+++ b/xml/System.Text.RegularExpressions/Regex.xml
@@ -986,9 +986,9 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
           <paramref name="assemblyname" /> or <paramref name="regexinfos" /> is <see langword="null" />.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
--   Build the assembly that contains the compiled regular expressions on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] instead of later versions installed.  
+-   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
 -   Instead of calling <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> and retrieving the compiled regular expression from an assembly, use either static or instance <see cref="T:System.Text.RegularExpressions.Regex" /> methods with the <see cref="F:System.Text.RegularExpressions.RegexOptions.Compiled" /> option when you instantiate a <see cref="T:System.Text.RegularExpressions.Regex" /> object or call a regular expression pattern matching method.</para>
         </block>
@@ -1095,9 +1095,9 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
           <paramref name="assemblyname" /> or <paramref name="regexinfos" /> is <see langword="null" />.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
--   Build the assembly that contains the compiled regular expressions on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] instead of later versions installed.  
+-   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
 -   Instead of calling <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> and retrieving the compiled regular expression from an assembly, use either static or instance <see cref="T:System.Text.RegularExpressions.Regex" /> methods with the <see cref="F:System.Text.RegularExpressions.RegexOptions.Compiled" /> option when you instantiate a <see cref="T:System.Text.RegularExpressions.Regex" /> object or call a regular expression pattern matching method.</para>
         </block>
@@ -1191,9 +1191,9 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
         <exception cref="T:System.IO.FileNotFoundException">The file designated by the <paramref name="resourceFile" /> parameter cannot be found.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
--   Build the assembly that contains the compiled regular expressions on a system that has [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] instead of later versions installed.  
+-   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
 -   Instead of calling <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> and retrieving the compiled regular expression from an assembly, use either static or instance <see cref="T:System.Text.RegularExpressions.Regex" /> methods with the <see cref="F:System.Text.RegularExpressions.RegexOptions.Compiled" /> option when you instantiate a <see cref="T:System.Text.RegularExpressions.Regex" /> object or call a regular expression pattern matching method.</para>
         </block>
diff --git a/xml/System.Threading.Tasks/Task.xml b/xml/System.Threading.Tasks/Task.xml
index e98e554ad0f..7b5a331a0ab 100644
--- a/xml/System.Threading.Tasks/Task.xml
+++ b/xml/System.Threading.Tasks/Task.xml
@@ -106,7 +106,7 @@
  [!code-csharp[System.Threading.Tasks.Task#6](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task/cs/run1.cs#6)]
  [!code-vb[System.Threading.Tasks.Task#6](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task/vb/run1.vb#6)]  
   
- An alternative, and the most common method to start a task in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], is the static <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method. The <xref:System.Threading.Tasks.Task.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory> object. Overloads of the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method let you specify parameters to pass to the task creation options and a task scheduler. The following example uses the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method to start a task. It is functionally equivalent to the code in the previous example.  
+ An alternative, and the most common method to start a task in .NET Framework 4, is the static <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method. The <xref:System.Threading.Tasks.Task.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory> object. Overloads of the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method let you specify parameters to pass to the task creation options and a task scheduler. The following example uses the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method to start a task. It is functionally equivalent to the code in the previous example.  
   
  [!code-csharp[System.Threading.Tasks.Task#7](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task/cs/startnew1.cs#7)]
  [!code-vb[System.Threading.Tasks.Task#7](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task/vb/startnew1.vb#7)]  
diff --git a/xml/System.Threading.Tasks/Task`1.xml b/xml/System.Threading.Tasks/Task`1.xml
index d651f941923..c64773af307 100644
--- a/xml/System.Threading.Tasks/Task`1.xml
+++ b/xml/System.Threading.Tasks/Task`1.xml
@@ -67,7 +67,7 @@
  [!code-csharp[System.Threading.Tasks.Task\`1#6](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task`1/cs/run1.cs#6)]
  [!code-vb[System.Threading.Tasks.Task\`1#6](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task`1/vb/run1.vb#6)]  
   
- An alternative, and the most common way to start a task in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], is to call the static <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> or <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A?displayProperty=nameWithType> method. The <xref:System.Threading.Tasks.Task.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory> object, and the <xref:System.Threading.Tasks.Task%601.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory%601> object. Overloads of their `StartNew` method let you pass arguments, define task creation options, and specify a task scheduler. The following example uses the <xref:System.Threading.Tasks.TaskFactory%601.StartNew%28System.Func%7B%600%7D%29?displayProperty=nameWithType> method to start a task. It is functionally equivalent to the code in the previous example.  
+ An alternative, and the most common way to start a task in the .NET Framework 4, is to call the static <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> or <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A?displayProperty=nameWithType> method. The <xref:System.Threading.Tasks.Task.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory> object, and the <xref:System.Threading.Tasks.Task%601.Factory%2A?displayProperty=nameWithType> property returns a <xref:System.Threading.Tasks.TaskFactory%601> object. Overloads of their `StartNew` method let you pass arguments, define task creation options, and specify a task scheduler. The following example uses the <xref:System.Threading.Tasks.TaskFactory%601.StartNew%28System.Func%7B%600%7D%29?displayProperty=nameWithType> method to start a task. It is functionally equivalent to the code in the previous example.  
   
  [!code-csharp[System.Threading.Tasks.Task\`1#7](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task`1/cs/startnew1.cs#7)]
  [!code-vb[System.Threading.Tasks.Task\`1#7](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task`1/vb/startnew1.vb#7)]  
diff --git a/xml/System.Threading/ThreadPool.xml b/xml/System.Threading/ThreadPool.xml
index d49638c5061..4d4b8afe632 100644
--- a/xml/System.Threading/ThreadPool.xml
+++ b/xml/System.Threading/ThreadPool.xml
@@ -78,7 +78,7 @@
 > [!NOTE]
 >  Unmanaged code that hosts the .NET Framework can change the size of the thread pool by using the `CorSetMaxThreads` function, defined in the mscoree.h file.  
   
- The thread pool provides new worker threads or I/O completion threads on demand until it reaches the maximum for each category. When a maximum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the thread pool creates and destroys worker threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
+ The thread pool provides new worker threads or I/O completion threads on demand until it reaches the maximum for each category. When a maximum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the .NET Framework 4, the thread pool creates and destroys worker threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
   
 > [!NOTE]
 >  When demand is low, the actual number of thread pool threads can fall below the minimum values.  
@@ -456,7 +456,7 @@ If a thread pool implementation may have different types of work items, the coun
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The thread pool provides new worker threads or I/O completion threads on demand until it reaches the minimum for each category. By default, the minimum number of threads is set to the number of processors on a system. When the minimum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the thread pool creates and destroys threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
+ The thread pool provides new worker threads or I/O completion threads on demand until it reaches the minimum for each category. By default, the minimum number of threads is set to the number of processors on a system. When the minimum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the .NET Framework 4, the thread pool creates and destroys threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
   
 > [!NOTE]
 >  When demand is low, the actual number of thread pool threads can fall below the minimum values.  
@@ -1225,7 +1225,7 @@ If a thread pool implementation may have different types of work items, the coun
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The thread pool provides new worker threads or I/O completion threads on demand until it reaches the minimum for each category. When the minimum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the thread pool creates and destroys threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
+ The thread pool provides new worker threads or I/O completion threads on demand until it reaches the minimum for each category. When the minimum is reached, the thread pool can create additional threads in that category or wait until some tasks complete. Beginning with the .NET Framework 4, the thread pool creates and destroys threads in order to optimize throughput, which is defined as the number of tasks that complete per unit of time. Too few threads might not make optimal use of available resources, whereas too many threads could increase resource contention.  
   
  When demand is low, the actual number of thread pool threads can fall below the minimum values.  
   
diff --git a/xml/System.Web.Compilation/BuildManager.xml b/xml/System.Web.Compilation/BuildManager.xml
index 678c9089669..0b9e1ed9b09 100644
--- a/xml/System.Web.Compilation/BuildManager.xml
+++ b/xml/System.Web.Compilation/BuildManager.xml
@@ -753,14 +753,14 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property supports the ASP.NET multi-targeting feature, which enables you to use the latest version of Visual Studio to develop applications that will run with earlier versions of the .NET Framework. A build provider can use this property to make sure that the provider generates code that is appropriate for the targeted version of the .NET Framework. For example, you might want to generate different code depending on whether a Web site targets the .NET Framework 3.5 or the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information about multi-targeting, see [.NET Framework Multi-Targeting for ASP.NET Web Projects](https://docs.microsoft.com/previous-versions/aspnet/bb398791(v=vs.100)).  
+ This property supports the ASP.NET multi-targeting feature, which enables you to use the latest version of Visual Studio to develop applications that will run with earlier versions of the .NET Framework. A build provider can use this property to make sure that the provider generates code that is appropriate for the targeted version of the .NET Framework. For example, you might want to generate different code depending on whether a Web site targets the .NET Framework 3.5 or the .NET Framework 4. For more information about multi-targeting, see [.NET Framework Multi-Targeting for ASP.NET Web Projects](https://docs.microsoft.com/previous-versions/aspnet/bb398791(v=vs.100)).  
   
  If the Web site does not have a Web.config file, ASP.NET assumes that the target framework version is the version that is associated with the IIS application pool that the site is running under. For a file-system Web site that is running in Visual Studio, the default framework version is the current version of the .NET Framework.  
   
  If the Web site does have a Web.config file, ASP.NET determines the target framework by examining the Web.config file.  
   
 ## Web Sites that Target the .NET Framework 2.0  
- Web applications that target the .NET Framework 2.0 are compiled as if the target were the .NET Framework 3.0. The build process does not differentiate between the .NET Framework 2.0 and the .NET Framework 3.0 because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the .NET Framework 3.5, the Web.config file specifies the compiler version, and for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the .NET Framework 3.0.  
+ Web applications that target the .NET Framework 2.0 are compiled as if the target were the .NET Framework 3.0. The build process does not differentiate between the .NET Framework 2.0 and the .NET Framework 3.0 because the Web.config file does not indicate compiler version or target framework when one of those versions is targeted. (For the .NET Framework 3.5, the Web.config file specifies the compiler version, and for the .NET Framework 4, the Web.config file specifies the target framework.) Therefore, for Web applications that target the .NET Framework 2.0, this property returns a target framework moniker that indicates the .NET Framework 3.0.  
   
  This normally will not cause any problems. Visual Studio prevents you from creating references to .NET Framework 3.0 features in a project that is targeted for the .NET Framework 2.0. For example, Visual Studio does not provide item templates for WCF services in a project that is targeted for .NET Framework 2.0, because WCF was introduced with the .NET Framework 3.0 and is not compatible with the .NET Framework 2.0.  
   
diff --git a/xml/System.Web.Configuration/TrustSection.xml b/xml/System.Web.Configuration/TrustSection.xml
index 7db432e80e3..e9fb26f5c58 100644
--- a/xml/System.Web.Configuration/TrustSection.xml
+++ b/xml/System.Web.Configuration/TrustSection.xml
@@ -157,7 +157,7 @@
   
 -   The legacy partial trust files located in the CONFIG directory in the .NET Framework install directory are used instead of the new partial trust configuration files that are located in the same directory. The legacy files include the membership conditions that were found in the .NET Framework 1.1 or .NET Framework 2.0 SP1 versions of the .NET Framework.  
   
--   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the .NET Framework 2.0 SP1 sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
+-   Additional membership conditions to evaluate permissions are applied, as defined in ASP.NET partial trust files. The CONFIG directory that ships with the .NET Framework 4 release contains legacy partial-trust policy files. The names of these files include the string "legacy" and contain the .NET Framework 2.0 SP1 sections. These sections contain non-empty membership conditions that are needed to evaluating CAS policy against assemblies.  
   
 -   If the ASP.NET application is running in partial trust and the security policy file for the trust level maps to one of the default partial trust configuration files, ASP.NET automatically chooses the corresponding legacy configuration file. For example, if the security policy would ordinarily be loaded from Web_mediumtrust.config, then in legacy mode ASP.NET will instead load security policy from Legacy.web_mediumtrust.config.  
   
diff --git a/xml/System.Web.Hosting/HostSecurityPolicyResolver.xml b/xml/System.Web.Hosting/HostSecurityPolicyResolver.xml
index 7575f386897..340b18495f9 100644
--- a/xml/System.Web.Hosting/HostSecurityPolicyResolver.xml
+++ b/xml/System.Web.Hosting/HostSecurityPolicyResolver.xml
@@ -22,7 +22,7 @@
  In complex Web hosting environments such as SharePoint and Web farms, you might have to extend the ASP.NET code access security policy. By extending the <xref:System.Web.Hosting.HostSecurityPolicyResolver> type, you can implement custom security policy behavior that overrides the ASP.NET code access security policy.  
   
 ## Configuring a HostSecurityPolicyResolver Class  
- In the configuration files, you can configure a custom <xref:System.Web.Hosting.HostSecurityPolicyResolver> instance by adding the <xref:System.Web.Configuration.TrustSection.HostSecurityPolicyResolverType%2A> attribute to the  element. The <xref:System.Web.Configuration.TrustSection.HostSecurityPolicyResolverType%2A> attribute can be set to the name of the custom <xref:System.Web.Hosting.HostSecurityPolicyResolver> type that will be loaded by ASP.NET. The attribute value contains the fully qualified name of the derived type. By default, [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] does not set this attribute.  
+ In the configuration files, you can configure a custom <xref:System.Web.Hosting.HostSecurityPolicyResolver> instance by adding the <xref:System.Web.Configuration.TrustSection.HostSecurityPolicyResolverType%2A> attribute to the  element. The <xref:System.Web.Configuration.TrustSection.HostSecurityPolicyResolverType%2A> attribute can be set to the name of the custom <xref:System.Web.Hosting.HostSecurityPolicyResolver> type that will be loaded by ASP.NET. The attribute value contains the fully qualified name of the derived type. By default, .NET Framework 4 does not set this attribute.  
   
  The following syntax shows how to configure the attribute:  
   
diff --git a/xml/System.Web.RegularExpressions/TagRegex35.xml b/xml/System.Web.RegularExpressions/TagRegex35.xml
index dec22b982b5..adc018bee94 100644
--- a/xml/System.Web.RegularExpressions/TagRegex35.xml
+++ b/xml/System.Web.RegularExpressions/TagRegex35.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.RegularExpressions.TagRegex35> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the .NET Framework 3.5 SP1 and earlier versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex?displayProperty=nameWithType> class for applications that target the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions.  
+ The <xref:System.Web.RegularExpressions.TagRegex35> class provides a regular expression that ASP.NET uses internally to parse the opening tag of an HTML element, an XML element, or an ASP.NET Web server control tag, for applications that target the .NET Framework 3.5 SP1 and earlier versions. ASP.NET uses the <xref:System.Web.RegularExpressions.TagRegex?displayProperty=nameWithType> class for applications that target the .NET Framework 4 and later versions.  
   
 > [!NOTE]
 >  The <xref:System.Web.RegularExpressions> classes are used internally by the .NET Framework to parse ASP.NET pages.  
diff --git a/xml/System.Windows.Controls/SpellCheck.xml b/xml/System.Windows.Controls/SpellCheck.xml
index 8e9ea9648fd..0536d6fb898 100644
--- a/xml/System.Windows.Controls/SpellCheck.xml
+++ b/xml/System.Windows.Controls/SpellCheck.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- To enable the spelling checker, set the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A?displayProperty=nameWithType> property to `true` on a text-editing control. When this spelling checker is enabled, misspelled words are underlined by using a red wavy line, as shown in the following illustration. Spelling checker is supported only when WPF provides a default dictionary. In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], WPF provides dictionaries for English, French, German, and Spanish.  
+ To enable the spelling checker, set the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A?displayProperty=nameWithType> property to `true` on a text-editing control. When this spelling checker is enabled, misspelled words are underlined by using a red wavy line, as shown in the following illustration. Spelling checker is supported only when WPF provides a default dictionary. In .NET Framework 4, WPF provides dictionaries for English, French, German, and Spanish.  
   
  ![Textbox with spell&#45;checking](~/add/media/editing-textbox-with-spellchecking.png "Textbox with spell-checking")  
   
diff --git a/xml/System.Windows.Documents/Run.xml b/xml/System.Windows.Documents/Run.xml
index a2fb9b0eb40..49fa87feed8 100644
--- a/xml/System.Windows.Documents/Run.xml
+++ b/xml/System.Windows.Documents/Run.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Windows.Documents.Run.Text%2A> property of the <xref:System.Windows.Documents.Run> object is a dependency property, which means that you can bind the <xref:System.Windows.Documents.Run.Text%2A> property to a data source. The <xref:System.Windows.Documents.Run.Text%2A> property fully supports one-way binding in <xref:System.Windows.Controls.FlowDocumentReader> and other controls that display read-only text. For more information about data binding, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
+ Starting in the .NET Framework 4, the <xref:System.Windows.Documents.Run.Text%2A> property of the <xref:System.Windows.Documents.Run> object is a dependency property, which means that you can bind the <xref:System.Windows.Documents.Run.Text%2A> property to a data source. The <xref:System.Windows.Documents.Run.Text%2A> property fully supports one-way binding in <xref:System.Windows.Controls.FlowDocumentReader> and other controls that display read-only text. For more information about data binding, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
 > [!NOTE]
 >  Binding text to a <xref:System.Windows.Documents.Run> object contained within <xref:System.Windows.Controls.RichTextBox> is not supported. Editing operations within the <xref:System.Windows.Controls.RichTextBox> may cause the binding to be cleared.  
@@ -211,7 +211,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Windows.Documents.Run.Text%2A> property of the <xref:System.Windows.Documents.Run> object is a dependency property, which means that you can bind the <xref:System.Windows.Documents.Run.Text%2A> property to a data source. The <xref:System.Windows.Documents.Run.Text%2A> property fully supports one-way binding in <xref:System.Windows.Controls.FlowDocumentReader> and other controls that display read-only text. For more information about data binding, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
+ Starting in the .NET Framework 4, the <xref:System.Windows.Documents.Run.Text%2A> property of the <xref:System.Windows.Documents.Run> object is a dependency property, which means that you can bind the <xref:System.Windows.Documents.Run.Text%2A> property to a data source. The <xref:System.Windows.Documents.Run.Text%2A> property fully supports one-way binding in <xref:System.Windows.Controls.FlowDocumentReader> and other controls that display read-only text. For more information about data binding, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
 > [!NOTE]
 >  Binding text to a <xref:System.Windows.Documents.Run> object contained within <xref:System.Windows.Controls.RichTextBox> is not supported. Editing operations within the <xref:System.Windows.Controls.RichTextBox> may cause the binding to be cleared.  
diff --git a/xml/System.Windows.Markup/IComponentConnector.xml b/xml/System.Windows.Markup/IComponentConnector.xml
index c87eac58d20..f18d50136d7 100644
--- a/xml/System.Windows.Markup/IComponentConnector.xml
+++ b/xml/System.Windows.Markup/IComponentConnector.xml
@@ -38,7 +38,7 @@
  In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.IComponentConnector> is in the System.Xaml assembly. . For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 > [!TIP]
->  A failure to resolve <xref:System.Windows.Markup.IComponentConnector> during an attempted build is often an indicator that you have not updated your WPF project correctly. In particular, the project is not referencing the System.Xaml assembly for a project that targets [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. Try running the `devenv /upgrade` option for the project, or otherwise adjust the project assembly references so that System.Xaml is in the reference list.  
+>  A failure to resolve <xref:System.Windows.Markup.IComponentConnector> during an attempted build is often an indicator that you have not updated your WPF project correctly. In particular, the project is not referencing the System.Xaml assembly for a project that targets .NET Framework 4. Try running the `devenv /upgrade` option for the project, or otherwise adjust the project assembly references so that System.Xaml is in the reference list.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
index 5185aa019ae..5e40db128d8 100644
--- a/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
+++ b/xml/System.Windows.Markup/IReceiveMarkupExtension.xml
@@ -24,7 +24,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In .NET Framework 3.0, <xref:System.Windows.Markup.IReceiveMarkupExtension> was a WPF-specific technique for permitting types to enter a different codepath whenever any of its XAML-accessible members where set as markup extensions during XAML parsing. In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], this interface is obsolete, and is replaced with a .NET Framework XAML Services implementation for how markup extensions can receive services or types can invoke markup-extension specific setter logic.  
+ In .NET Framework 3.0, <xref:System.Windows.Markup.IReceiveMarkupExtension> was a WPF-specific technique for permitting types to enter a different codepath whenever any of its XAML-accessible members where set as markup extensions during XAML parsing. In .NET Framework 4, this interface is obsolete, and is replaced with a .NET Framework XAML Services implementation for how markup extensions can receive services or types can invoke markup-extension specific setter logic.  
   
  For .NET Framework 4 implementations, if types want to perform special processing when setting properties by markup extension rather than by other means, types should be defined with <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute> attributes applied. The attribute specifies a callback, which is typically defined as a private member of the type.  
   
@@ -63,7 +63,7 @@
         <param name="property">The name of the target property.</param>
         <param name="markupExtension">The markup extension instance of the incoming data.</param>
         <param name="serviceProvider">Can provide additional services that should be performed when processing the markup extension data for a property value.</param>
-        <summary>Provides the handling for markup extensions that provide property values. Do not use for [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] implementations; see <see cref="T:System.Windows.Markup.IReceiveMarkupExtension" />.</summary>
+        <summary>Provides the handling for markup extensions that provide property values. Do not use for .NET Framework 4 implementations; see <see cref="T:System.Windows.Markup.IReceiveMarkupExtension" />.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Markup/MarkupExtension.xml b/xml/System.Windows.Markup/MarkupExtension.xml
index e75beb018b5..33c85765443 100644
--- a/xml/System.Windows.Markup/MarkupExtension.xml
+++ b/xml/System.Windows.Markup/MarkupExtension.xml
@@ -124,7 +124,7 @@
 ## WPF Usage Notes  
   
 > [!IMPORTANT]
->  WPF classes that have specific interactions with markup set operations should not rely on <xref:System.Windows.Markup.IReceiveMarkupExtension> for a [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] implementation. Use <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute>-attributed callbacks instead.  
+>  WPF classes that have specific interactions with markup set operations should not rely on <xref:System.Windows.Markup.IReceiveMarkupExtension> for a .NET Framework 4 implementation. Use <xref:System.Windows.Markup.XamlSetMarkupExtensionAttribute>-attributed callbacks instead.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/NullExtension.xml b/xml/System.Windows.Markup/NullExtension.xml
index 929e0fa25ef..85f2758c600 100644
--- a/xml/System.Windows.Markup/NullExtension.xml
+++ b/xml/System.Windows.Markup/NullExtension.xml
@@ -47,7 +47,7 @@
   
  This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for how XAML processors interpret a particular extension. The members that markup extension implementation classes expose are not typically intended to be called from your code. This markup extension class supports the [x:Null Markup Extension](/dotnet/framework/xaml-services/x-null-markup-extension) usage for .NET XAML Services.  
   
- In previous versions of the .NET Framework, this class (and the `x:Null` markup extension XAML behavior support as well as the relevant xmlns mapping) existed in the WPF-specific assembly PresentationFramework. In .NET Framework 4, <xref:System.Windows.Markup.NullExtension> is in the System.Xaml assembly. This makes the `x:Null` usage available to applications using frameworks that reference .NET XAML Services. You do not need PresentationFramework as a referenced assembly so long as you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
+ In previous versions of the .NET Framework, this class (and the `x:Null` markup extension XAML behavior support as well as the relevant xmlns mapping) existed in the WPF-specific assembly PresentationFramework. In .NET Framework 4, <xref:System.Windows.Markup.NullExtension> is in the System.Xaml assembly. This makes the `x:Null` usage available to applications using frameworks that reference .NET XAML Services. You do not need PresentationFramework as a referenced assembly so long as you are targeting .NET Framework 4. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
  The System.Xaml assembly uses <xref:System.Windows.Markup.XmlnsDefinitionAttribute> to map all types in the assembly to the XAML namespace for the XAML language ([!INCLUDE[TLA#tla_xamlxmlnsv1](~/includes/tlasharptla-xamlxmlnsv1-md.md)]). Typically you declare a prefix for [!INCLUDE[TLA#tla_xamlxmlnsv1](~/includes/tlasharptla-xamlxmlnsv1-md.md)] in a root element mapping and use the prefix `x`.  
   
diff --git a/xml/System.Windows.Markup/ParserContext.xml b/xml/System.Windows.Markup/ParserContext.xml
index ed0336a3611..26f5725406f 100644
--- a/xml/System.Windows.Markup/ParserContext.xml
+++ b/xml/System.Windows.Markup/ParserContext.xml
@@ -27,7 +27,7 @@
 ## Remarks  
  The XAML parser that this context refers to is the .NET Framework 3.5 era XAML parser API that is specific to the WPF implementation, as exposed in <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType>.  
   
- The XAML system in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] uses a more sophisticated XAML type system and thus also uses a different type of context for XAML processing operations. For more information, see <xref:System.Xaml.XamlSchemaContext>.  
+ The XAML system in .NET Framework 4 uses a more sophisticated XAML type system and thus also uses a different type of context for XAML processing operations. For more information, see <xref:System.Xaml.XamlSchemaContext>.  
   
  A <xref:System.Windows.Markup.ParserContext> is typically used as an input for a call to a <xref:System.Windows.Markup.XamlReader> operation. In these cases, you are using overloads of <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType> or <xref:System.Windows.Markup.XamlReader.LoadAsync%2A?displayProperty=nameWithType> where supplying the  <xref:System.Windows.Markup.ParserContext> provides greater control over factors such as the type mapping to XAML, or altering XML processing defaults. Using a <xref:System.Windows.Markup.ParserContext> as opposed to using <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> default behavior is an advanced scenario.  
   
diff --git a/xml/System.Windows.Markup/StaticExtension.xml b/xml/System.Windows.Markup/StaticExtension.xml
index f6bbc093a9e..9267c4cbd4e 100644
--- a/xml/System.Windows.Markup/StaticExtension.xml
+++ b/xml/System.Windows.Markup/StaticExtension.xml
@@ -227,7 +227,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], <xref:System.Windows.Markup.StaticExtension> supports an alternate mode whereby it can return a static member based on <xref:System.Windows.Markup.StaticExtension.Member%2A> being the simple member name and its owning type supplied as <xref:System.Windows.Markup.StaticExtension.MemberType%2A>, rather than <xref:System.Windows.Markup.StaticExtension.Member%2A> providing a full name in the form *type*`.`*member*. The type resolver still acts, but in this case the <xref:System.Windows.Markup.StaticExtension.Member%2A> and <xref:System.Windows.Markup.StaticExtension.MemberType%2A> are basically combined: `memberFullName = MemberType.FullName + "." + Member`. Note that this technique will not support XAML namespaces and prefixes; it is working against the backing type system, not the XAML type system.  
+ In .NET Framework 4, <xref:System.Windows.Markup.StaticExtension> supports an alternate mode whereby it can return a static member based on <xref:System.Windows.Markup.StaticExtension.Member%2A> being the simple member name and its owning type supplied as <xref:System.Windows.Markup.StaticExtension.MemberType%2A>, rather than <xref:System.Windows.Markup.StaticExtension.Member%2A> providing a full name in the form *type*`.`*member*. The type resolver still acts, but in this case the <xref:System.Windows.Markup.StaticExtension.Member%2A> and <xref:System.Windows.Markup.StaticExtension.MemberType%2A> are basically combined: `memberFullName = MemberType.FullName + "." + Member`. Note that this technique will not support XAML namespaces and prefixes; it is working against the backing type system, not the XAML type system.  
   
  The string for <xref:System.Windows.Markup.StaticExtension.Member%2A> typically uses the format *prefix*`:`*typeName*`.`*fieldOrPropertyName*. (*prefix* is the mapping prefix for an XML namespace, and is only required to reference static values that are not mapped to the default XML namespace).  
   
@@ -276,7 +276,7 @@
   
  This implementation relies on services that are based on the passed `serviceProvider`. `serviceProvider` must not be `null`. The `serviceProvider` object is expected to return a service for <xref:System.Windows.Markup.IXamlTypeResolver>. Under the normal scenario of use by the default XAML readers and XAML writers, a suitable service provider is available. An invalid XAML schema context might have the side effect of breaking type mapping and thus the <xref:System.Windows.Markup.IXamlTypeResolver> service.  
   
- In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], <xref:System.Windows.Markup.StaticExtension> supports an alternate mode whereby it can return a static member based on <xref:System.Windows.Markup.StaticExtension.Member%2A> being the simple member name and its owning type supplied as <xref:System.Windows.Markup.StaticExtension.MemberType%2A>, rather than <xref:System.Windows.Markup.StaticExtension.Member%2A> providing a full name in the form *type*`.`*member*. The type resolver still acts, but in this case the <xref:System.Windows.Markup.StaticExtension.Member%2A> and <xref:System.Windows.Markup.StaticExtension.MemberType%2A> are basically combined: `memberFullName = MemberType.FullName + "." + Member`.  
+ In .NET Framework 4, <xref:System.Windows.Markup.StaticExtension> supports an alternate mode whereby it can return a static member based on <xref:System.Windows.Markup.StaticExtension.Member%2A> being the simple member name and its owning type supplied as <xref:System.Windows.Markup.StaticExtension.MemberType%2A>, rather than <xref:System.Windows.Markup.StaticExtension.Member%2A> providing a full name in the form *type*`.`*member*. The type resolver still acts, but in this case the <xref:System.Windows.Markup.StaticExtension.Member%2A> and <xref:System.Windows.Markup.StaticExtension.MemberType%2A> are basically combined: `memberFullName = MemberType.FullName + "." + Member`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
index 19135a004c9..88ac63e5ced 100644
--- a/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
+++ b/xml/System.Windows.Markup/UsableDuringInitializationAttribute.xml
@@ -39,7 +39,7 @@
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.UsableDuringInitializationAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- In WPF XAML for .NET Framework 3.0 and .NET Framework 3.5, top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)].  
+ In WPF XAML for .NET Framework 3.0 and .NET Framework 3.5, top-down construction was built in to the XAML processing for certain classes. The <xref:System.Windows.Markup.UsableDuringInitializationAttribute> attribute formalizes the reporting of the top-down behavior in .NET Framework 4.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XamlParseException.xml b/xml/System.Windows.Markup/XamlParseException.xml
index ff6f5d45309..558fd39eeeb 100644
--- a/xml/System.Windows.Markup/XamlParseException.xml
+++ b/xml/System.Windows.Markup/XamlParseException.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Markup.XamlParseException> is used only for the WPF-implemented XAML parser that performs the XAML parsing and loading for WPF applications. Specifically, the exception is only relevant when an application targets .NET Framework 3.0 and .NET Framework 3.5. The exception can also originate from user code in run-time calls to APIs that hook up the WPF-implemented XAML parser to load XAML from within a running WPF application (for example, calls to <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>).  
   
- For [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Xaml.XamlParseException> exception that typically reports XAML processing exceptions is defined in a different namespace (<xref:System.Xaml>) and a different assembly (System.Xaml).  
+ For .NET Framework 4, the <xref:System.Xaml.XamlParseException> exception that typically reports XAML processing exceptions is defined in a different namespace (<xref:System.Xaml>) and a different assembly (System.Xaml).  
   
  Unless you are writing an equivalent to the WPF XAML parser or working with .NET Framework 3.0 and .NET Framework 3.5 targeting, you generally will not throw <xref:System.Windows.Markup.XamlParseException> from your own code. However, handling for the exception is sometimes necessary. For application scenarios, where you may want to suppress XAML parse errors, a <xref:System.Windows.Threading.Dispatcher> <xref:System.Windows.Threading.Dispatcher.UnhandledException> event handler at the application level is one way to handle a run-time <xref:System.Windows.Markup.XamlParseException>. Whether to suppress exceptions or let them surface to user code depends on how you design your application for purposes of loading XAML, and the trust level that you assign to the XAML your application loads. For more information, see [XAML Security Considerations](/dotnet/framework/xaml-services/xaml-security-considerations) or "XAML Security" section of [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index a650481c95e..b3131455e3c 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -59,7 +59,7 @@
 ## System.Xaml Backing Implementation in .NET 4  
  <xref:System.Windows.Markup.XamlReader> is the callable API surface for the WPF framework-level XAML parser. The same underlying XAML parser also performs the run-time XAML loading and parsing for WPF applications that target .NET Framework 3.0 and .NET Framework 3.5.  
   
- If you are targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the external API is the same, but parts of the implementation are built on the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] general XAML implementation in the System.Xaml assembly, which improves many of the technical and reporting aspects of parsing XAML. Targeting [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] necessarily entails including System.Xaml as a reference, and details of implementation such as the exceptions reported may come from System.Xaml defined types.  
+ If you are targeting .NET Framework 4, the external API is the same, but parts of the implementation are built on the .NET Framework 4 general XAML implementation in the System.Xaml assembly, which improves many of the technical and reporting aspects of parsing XAML. Targeting .NET Framework 4 necessarily entails including System.Xaml as a reference, and details of implementation such as the exceptions reported may come from System.Xaml defined types.  
   
 ## Examples  
  The following example converts a <xref:System.Windows.Controls.Button> into a string using the <xref:System.Windows.Markup.XamlWriter> class.  The string is then loaded back into a <xref:System.Windows.Controls.Button> using the static <xref:System.Windows.Markup.XamlReader.Load%2A> method on the <xref:System.Windows.Markup.XamlReader> class.  
diff --git a/xml/System.Windows.Markup/XamlTypeMapper.xml b/xml/System.Windows.Markup/XamlTypeMapper.xml
index 964a29ef0a5..2fde0fe374f 100644
--- a/xml/System.Windows.Markup/XamlTypeMapper.xml
+++ b/xml/System.Windows.Markup/XamlTypeMapper.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Markup.XamlTypeMapper> is part of an advanced WPF scenario that supplies alternate context for <xref:System.Windows.Markup.XamlReader> and <xref:System.Windows.Markup.XamlWriter>. For [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] WPF applications, you should consider overriding <xref:System.Xaml.XamlSchemaContext> for this scenario, rather than attempting to use <xref:System.Windows.Markup.XamlTypeMapper>.  
+ <xref:System.Windows.Markup.XamlTypeMapper> is part of an advanced WPF scenario that supplies alternate context for <xref:System.Windows.Markup.XamlReader> and <xref:System.Windows.Markup.XamlWriter>. For .NET Framework 4 WPF applications, you should consider overriding <xref:System.Xaml.XamlSchemaContext> for this scenario, rather than attempting to use <xref:System.Windows.Markup.XamlTypeMapper>.  
   
  <xref:System.Windows.Markup.XamlTypeMapper> can be used to provide the XAML parser with custom mapping information through a more direct technique than the application of <xref:System.Windows.Markup.XmlnsDefinitionAttribute> values on the assembly code. This might be useful for consolidation of all CLR namespaces in an assembly, or for referencing types that are XAML-ready in an existing assembly without having to recompile it just to add <xref:System.Windows.Markup.XmlnsDefinitionAttribute> attributing.  
   
diff --git a/xml/System.Windows.Media/Visual.xml b/xml/System.Windows.Media/Visual.xml
index 37a95c0da4e..4ce629a2df9 100644
--- a/xml/System.Windows.Media/Visual.xml
+++ b/xml/System.Windows.Media/Visual.xml
@@ -59,7 +59,7 @@ Visual class hierarchy
   
  A <xref:System.Windows.Media.Visual> has a limited number of levels. In previous versions of the .NET Framework, this maximum depth was 255. This limit is inadequate for some layouts that have many levels in the visual tree.  
   
- In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the maximum depth of a <xref:System.Windows.Media.Visual> is 2047, which enables much deeper visual trees. In most applications, there is not enough stack space to traverse so many levels, and the result is a <xref:System.StackOverflowException> during layout. For the default stack size, this exception is usually thrown when the tree depth is approximately 800, which corresponds to about 190 nested <xref:System.Windows.Controls.TreeViewItem> objects.  
+ In .NET Framework 4, the maximum depth of a <xref:System.Windows.Media.Visual> is 2047, which enables much deeper visual trees. In most applications, there is not enough stack space to traverse so many levels, and the result is a <xref:System.StackOverflowException> during layout. For the default stack size, this exception is usually thrown when the tree depth is approximately 800, which corresponds to about 190 nested <xref:System.Windows.Controls.TreeViewItem> objects.  
   
  If this exception is thrown by your application and you need to have a deeper visual tree, you can increase the application's stack size. You can increase the size of the stack by using the /STACK option at compile time or by using the EDITBIN utility. Increasing the stack size may affect your application's performance. For more information, see [Stack Allocations](https://go.microsoft.com/fwlink/?LinkId=165510) and [EDITBIN Options](https://go.microsoft.com/fwlink/?LinkId=165511).  
   
diff --git a/xml/System.Windows/NameScope.xml b/xml/System.Windows/NameScope.xml
index ecdcc150f79..5b1fcdba6d2 100644
--- a/xml/System.Windows/NameScope.xml
+++ b/xml/System.Windows/NameScope.xml
@@ -74,7 +74,7 @@
   
  The various methods of <xref:System.Windows.NameScope> are used by base elements and other classes that maintain XAML namescopes in order to support <xref:System.Windows.Markup.INameScope.RegisterName%2A> and <xref:System.Windows.Markup.INameScope.FindName%2A>. You generally use the API in the <xref:System.Windows.NameScope> class only if you are replacing or augmenting the base element behavior for how they process XAML namescopes for root elements of a XAML page, and as part of templates (which use a separate XAML namescope from the rest of the page).  
   
- In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], <xref:System.Windows.NameScope> provides collection interface implementations such that you can access the collections of names that are held by a XAML namescope, including adding to it through calls to an <xref:System.Windows.NameScope.Add%2A> method.  
+ In .NET Framework 4, <xref:System.Windows.NameScope> provides collection interface implementations such that you can access the collections of names that are held by a XAML namescope, including adding to it through calls to an <xref:System.Windows.NameScope.Add%2A> method.  
   
  For more information on XAML namescope concepts, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
   
diff --git a/xml/System.Windows/StaticResourceExtension.xml b/xml/System.Windows/StaticResourceExtension.xml
index d4cf22e55d3..5bb93000a8e 100644
--- a/xml/System.Windows/StaticResourceExtension.xml
+++ b/xml/System.Windows/StaticResourceExtension.xml
@@ -132,7 +132,7 @@
   
  The property to be set can be identified by a <xref:System.Reflection.PropertyInfo> (standard property) or <xref:System.Windows.DependencyProperty> (dependency property).  
   
- This implementation relies on XAML-related services based on the passed `serviceProvider`. It must not be `null`. In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] implementation, the following are required services from service context:  
+ This implementation relies on XAML-related services based on the passed `serviceProvider`. It must not be `null`. In the .NET Framework 4 implementation, the following are required services from service context:  
   
 -   <xref:System.Xaml.IXamlSchemaContextProvider>  
   
diff --git a/xml/System.Workflow.Activities/ReceiveActivity.xml b/xml/System.Workflow.Activities/ReceiveActivity.xml
index 2a0f3093dc0..a11b29503d1 100644
--- a/xml/System.Workflow.Activities/ReceiveActivity.xml
+++ b/xml/System.Workflow.Activities/ReceiveActivity.xml
@@ -73,7 +73,7 @@
 >  To ensure that persistence performs properly and does not persist transient messages, make sure that child activities of the <xref:System.Workflow.Activities.ReceiveActivity> do not persist by themselves. This can occur if the child activities go idle when a persistence provider was created with `UnloadOnIdle` set to `true`, for instance.  
   
 > [!NOTE]
->  This activity is part of .NET Framework 3.5. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Receive>.  
+>  This activity is part of .NET Framework 3.5. For the equivalent activity in .NET Framework 4, see <xref:System.ServiceModel.Activities.Receive>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Workflow.Activities/SendActivity.xml b/xml/System.Workflow.Activities/SendActivity.xml
index df20d376f4e..6089b21cdbe 100644
--- a/xml/System.Workflow.Activities/SendActivity.xml
+++ b/xml/System.Workflow.Activities/SendActivity.xml
@@ -62,7 +62,7 @@
      The <xref:System.Workflow.Activities.SendActivity> activity sends a message and waits until a response or a fault is received from the service. During execution, the send activity throws all of the faults that were received from the server. <xref:System.Workflow.ComponentModel.FaultHandlerActivity> activities can be used to handle the faults in the client workflow.  
   
 > [!NOTE]
->  This activity is part of .NET Framework 3.5. For the equivalent activity in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], see <xref:System.ServiceModel.Activities.Send>.  
+>  This activity is part of .NET Framework 3.5. For the equivalent activity in .NET Framework 4, see <xref:System.ServiceModel.Activities.Send>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System/AppDomain.xml b/xml/System/AppDomain.xml
index c0bd640afb7..d6ae502cc1f 100644
--- a/xml/System/AppDomain.xml
+++ b/xml/System/AppDomain.xml
@@ -497,7 +497,7 @@
  Beginning with the .NET Framework 4, the <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType> property returns the assembly that requested the assembly load that could not be resolved. For example, the loader might be unable to load a dependency of the requesting assembly because the requesting assembly and its dependency are not in the probing path. Knowing the identity of the requesting assembly might be useful in locating the dependency or in identifying the correct version, if more than one version of the dependency is available. For more information, see <xref:System.ResolveEventArgs.RequestingAssembly%2A?displayProperty=nameWithType>.  
   
 > [!IMPORTANT]
->  Beginning with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.ResolveEventHandler> event is raised for all assemblies, including resource assemblies. In earlier versions, the event was not raised for resource assemblies. If the operating system is localized, the handler might be called multiple times: once for each culture in the fallback chain.  
+>  Beginning with the .NET Framework 4, the <xref:System.ResolveEventHandler> event is raised for all assemblies, including resource assemblies. In earlier versions, the event was not raised for resource assemblies. If the operating system is localized, the handler might be called multiple times: once for each culture in the fallback chain.  
   
  For this event, the <xref:System.ResolveEventArgs.Name%2A?displayProperty=nameWithType> property returns the assembly name before policy is applied.  
   
@@ -6162,7 +6162,7 @@
 |------------|-------------|  
 |"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the .NET Framework 3.5 is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
 |"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the .NET Framework 3.5 are enabled in this application domain. Its success requires sort00001000.dll to be installed. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
-|"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and Unicode 5.0 are enabled in this application domain. Its success requires sort00060101.dll to be installed.|  
+|"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the .NET Framework 4and Unicode 5.0 are enabled in this application domain. Its success requires sort00060101.dll to be installed.|  
 |"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the .NET Framework 3.5 is enabled in this application domain.  See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
 |"UseRandomizedStringHashAlgorithm"|The runtime calculates hash codes for strings on a per application domain basis instead of using a single hashing algorithm that produces a consistent hash code across application domains. See [&lt;UseRandomizedStringHashAlgorithm&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/userandomizedstringhashalgorithm-element).|  
   
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index a149d5467c8..6ef9d106ca7 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1274,7 +1274,7 @@
 |------------|-------------|  
 |"NetFx40_LegacySecurityPolicy"|Code access security (CAS) for the .NET Framework 3.5 is enabled in this application domain. See [&lt;NetFx40_LegacySecurityPolicy&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/netfx40-legacysecuritypolicy-element).|  
 |"NetFx40_Legacy20SortingBehavior"|String sorting defaults for the .NET Framework 3.5 are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00001000.dll dynamic link library to be available on the local system. See [&lt;CompatSortNLSVersion&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/compatsortnlsversion-element).|  
-|"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and Unicode 5.0 are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00060101.dll dynamic link library to be available on the local system.|  
+|"NetFx40_Legacy40SortingBehavior"|String sorting defaults for the .NET Framework 4 and Unicode 5.0 are enabled in this application domain. Successfully restoring legacy sorting behavior also requires the sort00060101.dll dynamic link library to be available on the local system.|  
 |"NetFx40_TimeSpanLegacyFormatMode"|<xref:System.TimeSpan> formatting behavior for the .NET Framework 3.5 is enabled in this application domain. See [&lt;TimeSpan_LegacyFormatMode&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) and the "Restoring Legacy TimeSpan Formatting" section of the <xref:System.TimeSpan> topic.|  
 |"UseRandomizedStringHashAlgorithm"|The runtime calculates hash codes for strings on a per application domain basis instead of using a single hashing algorithm that produces a consistent hash code across application domains. See [&lt;UseRandomizedStringHashAlgorithm&gt; Element](/dotnet/framework/configure-apps/file-schema/runtime/userandomizedstringhashalgorithm-element).|  
   
diff --git a/xml/System/BadImageFormatException.xml b/xml/System/BadImageFormatException.xml
index 6464b7917ba..beba1417cf8 100644
--- a/xml/System/BadImageFormatException.xml
+++ b/xml/System/BadImageFormatException.xml
@@ -81,7 +81,7 @@
 
      To address this exception, set the project's **Platform target** property to x86 (instead of x64 or AnyCPU) and recompile.
 
--   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the .NET Framework 2.0 SP1 or later, or when an application that was developed using the .NET Framework 2.0 SP1 or .NET Framework 3.5 tries to load an assembly that was developed using the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
+-   Your application's components were created using different versions of .NET. Typically, this exception occurs when an application or component that was developed using the .NET Framework 1.0 or the .NET Framework 1.1 tries to load an assembly that was developed using the .NET Framework 2.0 SP1 or later, or when an application that was developed using the .NET Framework 2.0 SP1 or .NET Framework 3.5 tries to load an assembly that was developed using the .NET Framework 4 or later. The <xref:System.BadImageFormatException> may be reported as a compile-time error, or the exception may be thrown at run time. The following example defines a `StringLib` class that has a single member, `ToProperCase`, and that resides in an assembly named StringLib.dll.
 
      [!code-csharp[System.BadImageFormatException.Class#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.badimageformatexception.class/cs/stringlib.cs#2)]
      [!code-vb[System.BadImageFormatException.Class#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.badimageformatexception.class/vb/stringlib.vb#2)]
diff --git a/xml/System/ConsoleCancelEventArgs.xml b/xml/System/ConsoleCancelEventArgs.xml
index 8b464f099cf..d248941cbb9 100644
--- a/xml/System/ConsoleCancelEventArgs.xml
+++ b/xml/System/ConsoleCancelEventArgs.xml
@@ -114,7 +114,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 and [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
+          <para>In the .NET Framework 3.5 and .NET Framework 4, attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
         </block>
         <altmember cref="T:System.ConsoleCancelEventHandler" />
         <altmember cref="T:System.ConsoleKey" />
diff --git a/xml/System/DateTime.xml b/xml/System/DateTime.xml
index b0db6e776ec..7add75976c0 100644
--- a/xml/System/DateTime.xml
+++ b/xml/System/DateTime.xml
@@ -5560,7 +5560,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
   
  The hour component and the AM/PM designator in <paramref name="s" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -5765,7 +5765,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
         <exception cref="T:System.ArgumentException">
           <paramref name="style" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values. For example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -5891,7 +5891,7 @@ The following example demonstrates the <xref:System.DateTime.Parse%28System.Stri
         <exception cref="T:System.ArgumentException">
           <paramref name="style" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values. For example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTime.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.TryParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -8949,7 +8949,7 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
   
  <paramref name="styles" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values (for example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />).</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.ParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
@@ -9065,7 +9065,7 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
   
  <paramref name="styles" /> contains an invalid combination of <see cref="T:System.Globalization.DateTimeStyles" /> values (for example, both <see cref="F:System.Globalization.DateTimeStyles.AssumeLocal" /> and <see cref="F:System.Globalization.DateTimeStyles.AssumeUniversal" />).</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTime.TryParseExact" /> method returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTime.ParseExact" />
         <altmember cref="T:System.Globalization.CultureInfo" />
diff --git a/xml/System/DateTimeOffset.xml b/xml/System/DateTimeOffset.xml
index 981d8e7e11b..36e1a4e213b 100644
--- a/xml/System/DateTimeOffset.xml
+++ b/xml/System/DateTimeOffset.xml
@@ -3891,7 +3891,7 @@ The following example parses an array of strings that are expected to conform to
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -4192,7 +4192,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -4317,7 +4317,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  The hour component and the AM/PM designator in <paramref name="input" /> do not agree.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTimeOffset.ParseExact" /> method throws a <see cref="T:System.FormatException" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.TryParseExact" />
         <related type="Article" href="/dotnet/standard/base-types/standard-date-and-time-format-strings">Standard Date and Time Format Strings</related>
@@ -6160,7 +6160,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  <paramref name="styles" /> includes mutually exclusive <see cref="T:System.Globalization.DateTimeStyles" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
         <altmember cref="Overload:System.DateTimeOffset.ParseExact" />
       </Docs>
@@ -6271,7 +6271,7 @@ Strings that do not specify a UTC offset are assumed to have the offset of the l
   
  <paramref name="styles" /> includes mutually exclusive <see cref="T:System.Globalization.DateTimeStyles" /> values.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
+          <para>In the .NET Framework 4, the <see cref="Overload:System.DateTimeOffset.TryParseExact" /> returns <see langword="false" /> if the string to be parsed contains an hour component and an AM/PM designator that are not in agreement. In the .NET Framework 3.5 and earlier versions, the AM/PM designator is ignored.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System/String.xml b/xml/System/String.xml
index d03717156db..a263b19861c 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -14477,7 +14477,7 @@ The following example uses the <xref:System.String.Trim?displayProperty=nameWith
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 SP1 and earlier versions maintain an internal list of white-space characters that this method trims. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintain an internal list of white-space characters that this method trims. Starting with the .NET Framework 4, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the .NET Framework 4and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="M:System.String.TrimEnd(System.Char[])" />
         <altmember cref="M:System.String.TrimStart(System.Char[])" />
@@ -14612,7 +14612,7 @@ The following example uses the `Trim(System.Char[])` method to remove space, ast
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the .NET Framework 4, if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the .NET Framework 4and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.TrimEnd(System.Char[])" />
@@ -14784,7 +14784,7 @@ The following example demonstrates how you can use the `TrimEnd(System.Char[])`
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the .NET Framework 4, if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the .NET Framework 4 and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.Trim(System.Char[])" />
@@ -14966,7 +14966,7 @@ The following example then illustrates a call to the `StripComments` method.
           ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
+          <para>The .NET Framework 3.5 SP1 and earlier versions maintains an internal list of white-space characters that this method trims if <paramref name="trimChars" /> is <see langword="null" /> or an empty array. Starting with the .NET Framework 4, if <paramref name="trimChars" /> is <see langword="null" /> or an empty array, the method trims all Unicode white-space characters (that is, characters that produce a <see langword="true" /> return value when they are passed to the <see cref="M:System.Char.IsWhiteSpace(System.Char)" /> method). Because of this change, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions removes two characters, ZERO WIDTH SPACE (U+200B) and ZERO WIDTH NO-BREAK SPACE (U+FEFF), that the <see cref="M:System.String.Trim" /> method in the .NET Framework 4 and later versions does not remove. In addition, the <see cref="M:System.String.Trim" /> method in the .NET Framework 3.5 SP1 and earlier versions does not trim three Unicode white-space characters: MONGOLIAN VOWEL SEPARATOR (U+180E), NARROW NO-BREAK SPACE (U+202F), and MEDIUM MATHEMATICAL SPACE (U+205F).</para>
         </block>
         <altmember cref="T:System.Char" />
         <altmember cref="M:System.String.Trim(System.Char[])" />
diff --git a/xml/System/TimeSpan.xml b/xml/System/TimeSpan.xml
index 4e7bd4c7a20..5ce6069b036 100644
--- a/xml/System/TimeSpan.xml
+++ b/xml/System/TimeSpan.xml
@@ -131,7 +131,7 @@
  Beginning with the .NET Framework 4, the <xref:System.TimeSpan> structure supports culture-sensitive formatting through the overloads of its <xref:System.TimeSpan.ToString%2A> method, which converts a <xref:System.TimeSpan> value to its string representation. The default <xref:System.TimeSpan.ToString?displayProperty=nameWithType> method returns a time interval by using an invariant format that is identical to its return value in previous versions of the .NET Framework. The <xref:System.TimeSpan.ToString%28System.String%29?displayProperty=nameWithType> overload lets you specify a format string that defines the string representation of the time interval. The <xref:System.TimeSpan.ToString%28System.String%2CSystem.IFormatProvider%29?displayProperty=nameWithType> overload lets you specify a format string and the culture whose formatting conventions are used to create the string representation of the time interval. <xref:System.TimeSpan> supports both standard and custom format strings. (For more information, see [Standard TimeSpan Format Strings](/dotnet/standard/base-types/standard-timespan-format-strings) and [Custom TimeSpan Format Strings](/dotnet/standard/base-types/custom-timespan-format-strings).) However, only standard format strings are culture-sensitive.  
   
 ## Restoring Legacy TimeSpan Formatting  
- In some cases, code that successfully formats <xref:System.TimeSpan> values in .NET Framework 3.5 and earlier versions fails in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)]. This is most common in code that calls a [<TimeSpan_LegacyFormatMode> element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) method to format a <xref:System.TimeSpan> value with a format string. The following example successfully formats a <xref:System.TimeSpan> value in .NET Framework 3.5 and earlier versions, but throws an exception in [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)] and later versions. Note that it attempts to format a <xref:System.TimeSpan> value by using an unsupported format specifier, which is ignored in .NET Framework 3.5 and earlier versions.  
+ In some cases, code that successfully formats <xref:System.TimeSpan> values in .NET Framework 3.5 and earlier versions fails in .NET Framework 4. This is most common in code that calls a [<TimeSpan_LegacyFormatMode> element](/dotnet/framework/configure-apps/file-schema/runtime/timespan-legacyformatmode-element) method to format a <xref:System.TimeSpan> value with a format string. The following example successfully formats a <xref:System.TimeSpan> value in .NET Framework 3.5 and earlier versions, but throws an exception in .NET Framework 4 and later versions. Note that it attempts to format a <xref:System.TimeSpan> value by using an unsupported format specifier, which is ignored in .NET Framework 3.5 and earlier versions.  
   
  [!code-csharp-interactive[System.TimeSpan.Class.Legacy#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.timespan.class.legacy/cs/legacycode1.cs#1)]
  [!code-vb[System.TimeSpan.Class.Legacy#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.timespan.class.legacy/vb/legacycode1.vb#1)]  
diff --git a/xml/ns-System.Runtime.Caching.Hosting.xml b/xml/ns-System.Runtime.Caching.Hosting.xml
index bde2c35e985..f4d4aff0119 100644
--- a/xml/ns-System.Runtime.Caching.Hosting.xml
+++ b/xml/ns-System.Runtime.Caching.Hosting.xml
@@ -7,7 +7,7 @@
 ## Remarks
  The base <xref:System.Runtime.Caching.ObjectCache> class exposes a static <xref:System.Runtime.Caching.ObjectCache.Host%2A> property. When a .NET Framework hosting environment starts individual application domains, it can set a reference to the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property. This enables the hosting environment to provide better integration with the cache.
 
- In [!INCLUDE[net_v40_short](~/includes/net-v40-short-md.md)], the <xref:System.Runtime.Caching.Hosting> namespace provides interfaces that a hosting environment can use to set a <xref:System.IServiceProvider> reference on the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property.
+ In .NET Framework 4, the <xref:System.Runtime.Caching.Hosting> namespace provides interfaces that a hosting environment can use to set a <xref:System.IServiceProvider> reference on the <xref:System.Runtime.Caching.ObjectCache.Host%2A> property.
 
  ]]></format>
     </remarks>

From 8dae23d101636fec8fb29e94da434aef6c2c1ec5 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:21:47 -0800
Subject: [PATCH 037/236] net-v45

---
 .../CompatibleFramework.xml                   |  2 +-
 .../ActivityBlockingUpdate.xml                |  2 +-
 .../DynamicUpdateInfo.xml                     |  2 +-
 .../DynamicUpdateMap.xml                      |  2 +-
 .../DynamicUpdateMapBuilder.xml               |  2 +-
 .../DynamicUpdateMapItem.xml                  |  2 +-
 .../DynamicUpdateMapQuery.xml                 |  2 +-
 .../DynamicUpdateServices.xml                 | 26 ++++++-------
 .../InstanceUpdateException.xml               |  2 +-
 .../NativeActivityUpdateContext.xml           |  2 +-
 .../NativeActivityUpdateMapMetadata.xml       |  2 +-
 .../UpdateMapMetadata.xml                     |  2 +-
 .../VersionMismatchException.xml              |  2 +-
 .../WorkflowApplicationInstance.xml           |  2 +-
 xml/System.Activities/WorkflowIdentity.xml    |  2 +-
 .../WorkflowIdentityFilter.xml                |  2 +-
 xml/System.Data.SqlClient/SqlConnection.xml   |  6 +--
 xml/System.Globalization/CharUnicodeInfo.xml  |  2 +-
 xml/System.Globalization/CompareInfo.xml      |  6 +--
 xml/System.Globalization/CultureInfo.xml      | 10 ++---
 xml/System.Globalization/IdnMapping.xml       |  8 ++--
 xml/System.Globalization/SortVersion.xml      |  6 +--
 xml/System.Globalization/UmAlQuraCalendar.xml |  2 +-
 xml/System.IO.Compression/DeflateStream.xml   | 10 ++---
 xml/System.IO.Compression/GZipStream.xml      | 10 ++---
 xml/System.IO/BufferedStream.xml              |  8 ++--
 xml/System.IO/FileStream.xml                  |  4 +-
 xml/System.IO/Stream.xml                      | 10 ++---
 .../UnicodeDecodingConformance.xml            |  2 +-
 .../UnicodeEncodingConformance.xml            |  2 +-
 xml/System.Net.Sockets/SocketFlags.xml        |  2 +-
 xml/System.Net.WebSockets/WebSocket.xml       |  4 +-
 xml/System.Net/FileWebResponse.xml            |  2 +-
 xml/System.Net/FtpWebResponse.xml             |  2 +-
 xml/System.Net/WebResponse.xml                |  2 +-
 .../AssemblySignatureKeyAttribute.xml         |  2 +-
 xml/System.Reflection/TypeInfo.xml            |  2 +-
 xml/System.Text.RegularExpressions/Regex.xml  |  8 ++--
 xml/System.Threading.Tasks/Task.xml           |  8 ++--
 xml/System.Threading.Tasks/TaskFactory.xml    | 38 +++++++++----------
 xml/System.Threading.Tasks/TaskFactory`1.xml  |  2 +-
 xml/System.Threading.Tasks/TaskScheduler.xml  |  2 +-
 xml/System.Threading.Tasks/Task`1.xml         |  4 +-
 xml/System.Threading/Interlocked.xml          |  2 +-
 xml/System.Threading/Thread.xml               |  2 +-
 xml/System/AppDomainSetup.xml                 |  2 +-
 xml/System/Console.xml                        |  2 +-
 xml/System/ConsoleCancelEventArgs.xml         |  2 +-
 xml/System/Environment.xml                    |  2 +-
 xml/System/Exception.xml                      |  2 +-
 xml/System/IAsyncResult.xml                   |  2 +-
 xml/System/String.xml                         |  4 +-
 52 files changed, 120 insertions(+), 120 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
index 56f7e5e49ff..1e474115e8b 100644
--- a/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
+++ b/xml/Microsoft.Build.Tasks.Deployment.ManifestUtilities/CompatibleFramework.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the .NET Framework 3.5 Service Pack 1, and the .NET Framework 4 Client Profile is a subset of the [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
+ A profile is a subset of the full .NET Framework. For example, the .NET Framework Client Profile is a subset of the .NET Framework 3.5 Service Pack 1, and the .NET Framework 4 Client Profile is a subset of the .NET Framework 4.5. For more information, see [.NET Framework Client Profile](/dotnet/framework/deployment/client-profile).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Activities.DynamicUpdate/ActivityBlockingUpdate.xml b/xml/System.Activities.DynamicUpdate/ActivityBlockingUpdate.xml
index 19df59dd0ad..ba8607aba60 100644
--- a/xml/System.Activities.DynamicUpdate/ActivityBlockingUpdate.xml
+++ b/xml/System.Activities.DynamicUpdate/ActivityBlockingUpdate.xml
@@ -32,7 +32,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
  - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-   Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+   Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
    Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateInfo.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateInfo.xml
index c245872ca26..f8ae0a3b332 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateInfo.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateInfo.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
  - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-   Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+   Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
    Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateMap.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateMap.xml
index 587b094be57..102a0b898da 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateMap.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateMap.xml
@@ -32,7 +32,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
    
  - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-   Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+   Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
    Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapBuilder.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapBuilder.xml
index 5ef270840d1..8136a63b696 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapBuilder.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapBuilder.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapItem.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapItem.xml
index 72d41e8ef04..6a6526b85b7 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapItem.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapItem.xml
@@ -32,7 +32,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapQuery.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapQuery.xml
index 39835ae76f4..ace9f39dfaf 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateMapQuery.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateMapQuery.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/DynamicUpdateServices.xml b/xml/System.Activities.DynamicUpdate/DynamicUpdateServices.xml
index d57a0e92d95..e1c91cb788a 100644
--- a/xml/System.Activities.DynamicUpdate/DynamicUpdateServices.xml
+++ b/xml/System.Activities.DynamicUpdate/DynamicUpdateServices.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -57,7 +57,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -107,7 +107,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -157,7 +157,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -209,7 +209,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -261,7 +261,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -315,7 +315,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -369,7 +369,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -419,7 +419,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -454,7 +454,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -503,7 +503,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -552,7 +552,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
@@ -603,7 +603,7 @@
  This method supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/InstanceUpdateException.xml b/xml/System.Activities.DynamicUpdate/InstanceUpdateException.xml
index 5ea38426ea3..09b3e45e759 100644
--- a/xml/System.Activities.DynamicUpdate/InstanceUpdateException.xml
+++ b/xml/System.Activities.DynamicUpdate/InstanceUpdateException.xml
@@ -28,7 +28,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/NativeActivityUpdateContext.xml b/xml/System.Activities.DynamicUpdate/NativeActivityUpdateContext.xml
index f6be194ad5a..2e15058ee8a 100644
--- a/xml/System.Activities.DynamicUpdate/NativeActivityUpdateContext.xml
+++ b/xml/System.Activities.DynamicUpdate/NativeActivityUpdateContext.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/NativeActivityUpdateMapMetadata.xml b/xml/System.Activities.DynamicUpdate/NativeActivityUpdateMapMetadata.xml
index 84933d2da8f..8e5a54e2225 100644
--- a/xml/System.Activities.DynamicUpdate/NativeActivityUpdateMapMetadata.xml
+++ b/xml/System.Activities.DynamicUpdate/NativeActivityUpdateMapMetadata.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities.DynamicUpdate/UpdateMapMetadata.xml b/xml/System.Activities.DynamicUpdate/UpdateMapMetadata.xml
index a85031ae5db..6b341cfa438 100644
--- a/xml/System.Activities.DynamicUpdate/UpdateMapMetadata.xml
+++ b/xml/System.Activities.DynamicUpdate/UpdateMapMetadata.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics.  
   
  [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
- Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
  Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities/VersionMismatchException.xml b/xml/System.Activities/VersionMismatchException.xml
index ad6acd55a68..7f367044d30 100644
--- a/xml/System.Activities/VersionMismatchException.xml
+++ b/xml/System.Activities/VersionMismatchException.xml
@@ -28,7 +28,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
 - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-    Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+    Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
 - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
     Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities/WorkflowApplicationInstance.xml b/xml/System.Activities/WorkflowApplicationInstance.xml
index 336e7387156..c98f6186ceb 100644
--- a/xml/System.Activities/WorkflowApplicationInstance.xml
+++ b/xml/System.Activities/WorkflowApplicationInstance.xml
@@ -22,7 +22,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
  - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-    Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+    Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
     Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities/WorkflowIdentity.xml b/xml/System.Activities/WorkflowIdentity.xml
index c378f004a1c..d5e1ed16a60 100644
--- a/xml/System.Activities/WorkflowIdentity.xml
+++ b/xml/System.Activities/WorkflowIdentity.xml
@@ -40,7 +40,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
  - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-   Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+   Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
  - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
     Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Activities/WorkflowIdentityFilter.xml b/xml/System.Activities/WorkflowIdentityFilter.xml
index 4bb8e190b53..f6e3b45b583 100644
--- a/xml/System.Activities/WorkflowIdentityFilter.xml
+++ b/xml/System.Activities/WorkflowIdentityFilter.xml
@@ -21,7 +21,7 @@
  This class supports the versioning and dynamic update functionality of Windows Workflow Foundation. For more information about workflow versioning, workflow identity, and dynamic update, see the following topics:  
   
 - [Workflow Versioning](/dotnet/framework/windows-workflow-foundation/whats-new-in-wf-in-dotnet)  
-    Describes the workflow versioning functionality introduced in [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+    Describes the workflow versioning functionality introduced in .NET Framework 4.5.  
   
 - [Dynamic Update](/dotnet/framework/windows-workflow-foundation/dynamic-update)  
     Describes how to update the workflow definition of a persisted workflow instance by using dynamic update.  
diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
index 38198f15279..c8efd11dcd2 100644
--- a/xml/System.Data.SqlClient/SqlConnection.xml
+++ b/xml/System.Data.SqlClient/SqlConnection.xml
@@ -1372,7 +1372,7 @@ The connection string contains <see langword="Context Connection=true" />.
 |App|N/A|Synonym of **Application Name**.|
 |Application Name|N/A|The name of the application, or '.NET SQLClient Data Provider' if no application name is provided.<br /><br /> An application name can be 128 characters or less.|
 |`ApplicationIntent`|`ReadWrite`|Declares the application workload type when connecting to a server. Possible values are `ReadOnly` and `ReadWrite`. For example:<br /><br /> `ApplicationIntent=ReadOnly`<br /><br /> For more information about SqlClient support for Always On Availability Groups, see [SqlClient Support for High Availability, Disaster Recovery](/dotnet/framework/data/adonet/sql/sqlclient-support-for-high-availability-disaster-recovery).|
-|Asynchronous Processing<br /><br /> -or-<br /><br /> Async|'false'|When `true`, enables asynchronous operation support. Recognized values are `true`, `false`, `yes`, and `no`.<br /><br /> This property is ignored beginning in [!INCLUDE[net_v45](~/includes/net-v45-md.md)]. For more information about SqlClient support for asynchronous programming, see [Asynchronous Programming](/dotnet/framework/data/adonet/asynchronous-programming).|
+|Asynchronous Processing<br /><br /> -or-<br /><br /> Async|'false'|When `true`, enables asynchronous operation support. Recognized values are `true`, `false`, `yes`, and `no`.<br /><br /> This property is ignored beginning in .NET Framework 4.5. For more information about SqlClient support for asynchronous programming, see [Asynchronous Programming](/dotnet/framework/data/adonet/asynchronous-programming).|
 |AttachDBFilename<br /><br /> -or-<br /><br /> Extended Properties<br /><br /> -or-<br /><br /> Initial File Name|N/A|The name of the primary database file, including the full path name of an attachable database. AttachDBFilename is only supported for primary data files with an .mdf extension.<br /><br /> If the value of the AttachDBFileName key is specified in the connection string, the database is attached and becomes the default database for the connection.<br /><br /> If this key is not specified and if the database was previously attached, the database will not be reattached. The previously attached database will be used as the default database for the connection.<br /><br /> If this key is specified together with the AttachDBFileName key, the value of this key will be used as the alias. However, if the name is already used in another attached database, the connection will fail.<br /><br /> The path may be absolute or relative by using the DataDirectory substitution string. If DataDirectory is used, the database file must exist within a subdirectory of the directory pointed to by the substitution string. **Note:**  Remote server, HTTP, and UNC path names are not supported. <br /><br /> The database name must be specified with the keyword 'database' (or one of its aliases) as in the following:<br /><br /> <code>"AttachDbFileName=&#124;DataDirectory&#124;\data\YourDB.mdf;integrated security=true;database=YourDatabase"</code><br /><br /> An error will be generated if a log file exists in the same directory as the data file and the 'database' keyword is used when attaching the primary data file. In this case, remove the log file. Once the database is attached, a new log file will be automatically generated based on the physical path.|
 |Authentication|N/A|The authentication method used for [Connecting to SQL Database By Using Azure Active Directory Authentication](https://azure.microsoft.com/documentation/articles/sql-database-aad-authentication/#7-connect-to-your-database-by-using-azure-active-directory-identities).<br /><br /> Valid values are:<br /><br /> Active Directory Integrated, Active Directory Password, Sql Password.|
 |Column Encryption Setting|N/A|Enables or disables [Always Encrypted](/sql/relational-databases/security/encryption/always-encrypted-database-engine?view=sql-server-2017) functionality for the connection.|
@@ -1382,8 +1382,8 @@ The connection string contains <see langword="Context Connection=true" />.
 |ConnectRetryInterval|10|Specifies the time between each connection retry attempt (ConnectRetryCount). Valid values are 1 to 60 seconds (default=10), applied after the first reconnection attempt. When a broken connection is detected, the client immediately attempts to reconnect; this is the first reconnection attempt and only occurs if ConnectRetryCount is greater than 0. If the first reconnection attempt fails and ConnectRetryCount is greater than 1, the client waits ConnectRetryInterval to try the second and subsequent reconnection attempts.<br /><br /> For additional information about idle connection resiliency, see [Technical Article - Idle Connection Resiliency](https://download.microsoft.com/download/D/2/0/D20E1C5F-72EA-4505-9F26-FEF9550EFD44/Idle%20Connection%20Resiliency.docx).|
 |Context Connection|'false'|`true` if an in-process connection to SQL Server should be made.|
 |Current Language<br /><br /> -or-<br /><br /> Language|N/A|Sets the language used for database server warning or error messages.<br /><br /> The language name can be 128 characters or less.|
-|Data Source<br /><br /> -or-<br /><br /> Server<br /><br /> -or-<br /><br /> Address<br /><br /> -or-<br /><br /> Addr<br /><br /> -or-<br /><br /> Network Address|N/A|The name or network address of the instance of SQL Server to which to connect. The port number can be specified after the server name:<br /><br /> `server=tcp:servername, portnumber`<br /><br /> When specifying a local instance, always use (local). To force a protocol, add one of the following prefixes:<br /><br /> `np:(local),  tcp:(local), lpc:(local)`<br /><br /> Beginning in [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can also connect to a LocalDB database as follows:<br /><br /> `server=(localdb)\\myInstance`<br /><br /> For more information about LocalDB, see [SqlClient Support for LocalDB](/dotnet/framework/data/adonet/sql/sqlclient-support-for-localdb).<br /><br /> **Data Source** must use the TCP format or the Named Pipes format.<br /><br /> TCP format is as follows:<br /><br /> -   tcp:\<host name>\\<instance name\><br />-   tcp:\<host name>,\<TCP/IP port number><br /><br /> The TCP format must start with the prefix "tcp:" and is followed by the database instance, as specified by a host name and an instance name. This format is not applicable when connecting to Azure SQL Database. TCP is automatically selected for connections to Azure SQL Database when no protocol is specified.<br /><br /> The host name MUST be specified in one of the following ways:<br /><br /> -   NetBIOSName<br />-   IPv4Address<br />-   IPv6Address<br /><br /> The instance name is used to resolve to a particular TCP/IP port number on which a database instance is hosted. Alternatively, specifying a TCP/IP port number directly is also allowed. If both instance name and port number are not present, the default database instance is used.<br /><br /> The Named Pipes format is as follows:<br /><br /> -   np:\\\\<host name\>\pipe\\<pipe name\><br /><br /> The Named Pipes format MUST start with the prefix "np:" and is followed by a named pipe name.<br /><br /> The host name MUST be specified in one of the following ways:<br /><br /> -   NetBIOSName<br />-   IPv4Address<br />-   IPv6Address<br /><br /> The pipe name is used to identify the database instance to which the .NET Framework application will be connected.<br /><br /> If the value of the **Network** key is specified, the prefixes "tcp:" and "np:" should not be specified. **Note:**  You can force the use of TCP instead of shared memory, either by prefixing **tcp:** to the server name in the connection string, or by using **localhost**.|
-|Encrypt|'false'|When `true`, SQL Server uses SSL encryption for all data sent between the client and server if the server has a certificate installed. Recognized values are `true`, `false`, `yes`, and `no`. For more information, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax).<br /><br /> Beginning in [!INCLUDE[net_v45](~/includes/net-v45-md.md)], when `TrustServerCertificate` is false and `Encrypt` is true, the server name (or IP address) in a SQL Server SSL certificate must exactly match the server name (or IP address) specified in the connection string. Otherwise, the connection attempt will fail.|
+|Data Source<br /><br /> -or-<br /><br /> Server<br /><br /> -or-<br /><br /> Address<br /><br /> -or-<br /><br /> Addr<br /><br /> -or-<br /><br /> Network Address|N/A|The name or network address of the instance of SQL Server to which to connect. The port number can be specified after the server name:<br /><br /> `server=tcp:servername, portnumber`<br /><br /> When specifying a local instance, always use (local). To force a protocol, add one of the following prefixes:<br /><br /> `np:(local),  tcp:(local), lpc:(local)`<br /><br /> Beginning in .NET Framework 4.5, you can also connect to a LocalDB database as follows:<br /><br /> `server=(localdb)\\myInstance`<br /><br /> For more information about LocalDB, see [SqlClient Support for LocalDB](/dotnet/framework/data/adonet/sql/sqlclient-support-for-localdb).<br /><br /> **Data Source** must use the TCP format or the Named Pipes format.<br /><br /> TCP format is as follows:<br /><br /> -   tcp:\<host name>\\<instance name\><br />-   tcp:\<host name>,\<TCP/IP port number><br /><br /> The TCP format must start with the prefix "tcp:" and is followed by the database instance, as specified by a host name and an instance name. This format is not applicable when connecting to Azure SQL Database. TCP is automatically selected for connections to Azure SQL Database when no protocol is specified.<br /><br /> The host name MUST be specified in one of the following ways:<br /><br /> -   NetBIOSName<br />-   IPv4Address<br />-   IPv6Address<br /><br /> The instance name is used to resolve to a particular TCP/IP port number on which a database instance is hosted. Alternatively, specifying a TCP/IP port number directly is also allowed. If both instance name and port number are not present, the default database instance is used.<br /><br /> The Named Pipes format is as follows:<br /><br /> -   np:\\\\<host name\>\pipe\\<pipe name\><br /><br /> The Named Pipes format MUST start with the prefix "np:" and is followed by a named pipe name.<br /><br /> The host name MUST be specified in one of the following ways:<br /><br /> -   NetBIOSName<br />-   IPv4Address<br />-   IPv6Address<br /><br /> The pipe name is used to identify the database instance to which the .NET Framework application will be connected.<br /><br /> If the value of the **Network** key is specified, the prefixes "tcp:" and "np:" should not be specified. **Note:**  You can force the use of TCP instead of shared memory, either by prefixing **tcp:** to the server name in the connection string, or by using **localhost**.|
+|Encrypt|'false'|When `true`, SQL Server uses SSL encryption for all data sent between the client and server if the server has a certificate installed. Recognized values are `true`, `false`, `yes`, and `no`. For more information, see [Connection String Syntax](/dotnet/framework/data/adonet/connection-string-syntax).<br /><br /> Beginning in .NET Framework 4.5, when `TrustServerCertificate` is false and `Encrypt` is true, the server name (or IP address) in a SQL Server SSL certificate must exactly match the server name (or IP address) specified in the connection string. Otherwise, the connection attempt will fail.|
 |Enlist|'true'|`true` indicates that the SQL Server connection pooler automatically enlists the connection in the creation thread's current transaction context.|
 |Failover Partner|N/A|The name of the failover partner server where database mirroring is configured.<br /><br /> If the value of this key is "", then **Initial Catalog** must be present, and its value must not be "".<br /><br /> The server name can be 128 characters or less.<br /><br /> If you specify a failover partner but the failover partner server is not configured for database mirroring and the primary server (specified with the Server keyword) is not available, then the connection will fail.<br /><br /> If you specify a failover partner and the primary server is not configured for database mirroring, the connection to the primary server (specified with the Server keyword) will succeed if the primary server is available.|
 |Initial Catalog<br /><br /> -or-<br /><br /> Database|N/A|The name of the database.<br /><br /> The database name can be 128 characters or less.|
diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 95efbc09271..6524a75fef0 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -94,7 +94,7 @@ When using this class in your applications, keep in mind the following programmi
 | .NET Framework version | Unicode Standard version |
 | - | - |
 | .NET Framework 4 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
-| [!INCLUDE[net_v45](~/includes/net-v45-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
+| .NET Framework 4.5 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v451](~/includes/net-v451-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v452](~/includes/net-v452-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v46](~/includes/net-v46-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
diff --git a/xml/System.Globalization/CompareInfo.xml b/xml/System.Globalization/CompareInfo.xml
index 03667531e26..a0f79571f75 100644
--- a/xml/System.Globalization/CompareInfo.xml
+++ b/xml/System.Globalization/CompareInfo.xml
@@ -5155,13 +5155,13 @@ This method has greater overhead than other <xref:System.Globalization.CompareIn
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The weight of individual characters, and therefore the way in which particular strings are compared or ordered, depends on the version of the Unicode specification that a particular version of the .NET Framework implements. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], this also depends on the host operating system, as the following table shows. Note that this list of supported Unicode versions applies to character comparison and sorting only; it does not apply to classification of Unicode characters by category.
+ The weight of individual characters, and therefore the way in which particular strings are compared or ordered, depends on the version of the Unicode specification that a particular version of the .NET Framework implements. In the .NET Framework 4.5, this also depends on the host operating system, as the following table shows. Note that this list of supported Unicode versions applies to character comparison and sorting only; it does not apply to classification of Unicode characters by category.
 
 |.NET Framework version|Operating system|Unicode version|
 |----------------------------|----------------------|---------------------|
 |.NET Framework 4|All operating systems|Unicode 5.0|
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.3|
+|.NET Framework 4.5 and later versions|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|
+|.NET Framework 4.5 and later versions|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.3|
 
  The <xref:System.Globalization.SortVersion> object returned by the <xref:System.Globalization.CompareInfo.Version%2A> property doesn't identify the precise Unicode version used to compare strings. It is useful only when comparing two <xref:System.Globalization.SortVersion> objects to determine whether they use the same Unicode version and culture to compare strings. For more information and an example, see the <xref:System.Globalization.SortVersion> reference page.
 
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index 865c62ea41c..ec0a541f371 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -257,14 +257,14 @@ Some `CultureInfo` objects differ depending on the underlying platform. In parti
  [!code-csharp[System.Globalization.CultureInfo.Class.Thread#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/cs/defaultthread1.cs#1)]
  [!code-vb[System.Globalization.CultureInfo.Class.Thread#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/vb/defaultthread1.vb#1)]  
   
- In versions of the .NET Framework before the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the most common way to ensure that the main application thread shares the same culture with all other worker threads is to pass either the name of the application-wide culture or a <xref:System.Globalization.CultureInfo> object that represents the application-wide culture to a <xref:System.Threading.ParameterizedThreadStart?displayProperty=nameWithType> delegate. The following example uses this approach to ensure that the currency values displayed by two threads reflect the formatting conventions of the same culture.  
+ In versions of the .NET Framework before the .NET Framework 4.5, the most common way to ensure that the main application thread shares the same culture with all other worker threads is to pass either the name of the application-wide culture or a <xref:System.Globalization.CultureInfo> object that represents the application-wide culture to a <xref:System.Threading.ParameterizedThreadStart?displayProperty=nameWithType> delegate. The following example uses this approach to ensure that the currency values displayed by two threads reflect the formatting conventions of the same culture.  
   
  [!code-csharp[System.Globalization.CultureInfo.Class.Thread#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/cs/perthread1.cs#2)]
  [!code-vb[System.Globalization.CultureInfo.Class.Thread#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/vb/perthread1.vb#2)]  
   
  You can set the culture and UI culture of thread pool threads in a similar manner by calling the <xref:System.Threading.ThreadPool.QueueUserWorkItem%28System.Threading.WaitCallback%2CSystem.Object%29?displayProperty=nameWithType> method.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the culture and UI culture of all threads in an application domain more directly by assigning a <xref:System.Globalization.CultureInfo> object that represents that culture to the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties. The following example uses these properties to ensure that all threads in the default application domain share the same culture.  
+ Starting with the .NET Framework 4.5, you can set the culture and UI culture of all threads in an application domain more directly by assigning a <xref:System.Globalization.CultureInfo> object that represents that culture to the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties. The following example uses these properties to ensure that all threads in the default application domain share the same culture.  
   
  [!code-csharp[System.Globalization.CultureInfo.Class.Thread#3](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/cs/setthreads1.cs#3)]
  [!code-vb[System.Globalization.CultureInfo.Class.Thread#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.thread/vb/setthreads1.vb#3)]  
@@ -307,7 +307,7 @@ Some `CultureInfo` objects differ depending on the underlying platform. In parti
  [!code-csharp[System.Globalization.CultureInfo.Class.Async#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/cs/asyncculture2.cs#2)]
  [!code-vb[System.Globalization.CultureInfo.Class.Async#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/vb/asyncculture2.vb#2)]  
   
- For apps that target versions of the .NET Framework from the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later but prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], you can use the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties to ensure that the culture of the calling thread is used in asynchronous tasks that execute on thread pool threads. The following example is identical to the previous example, except that it uses the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to ensure that thread pool threads have the same culture as the main app thread.  
+ For apps that target versions of the .NET Framework from the .NET Framework 4.5 and later but prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], you can use the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties to ensure that the culture of the calling thread is used in asynchronous tasks that execute on thread pool threads. The following example is identical to the previous example, except that it uses the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to ensure that thread pool threads have the same culture as the main app thread.  
   
  [!code-csharp[System.Globalization.CultureInfo.Class.Async#3](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/cs/asyncculture3.cs#3)]
  [!code-vb[System.Globalization.CultureInfo.Class.Async#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/vb/asyncculture3.vb#3)]  
@@ -1555,7 +1555,7 @@ In .NET Framework and .NET Core apps, the current UI culture is a per-thread set
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and previous versions, by default, the culture of all threads is set to the Windows system culture. For applications whose current culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property enables an application to define the default culture of all threads in an application domain.  
+ In the .NET Framework 4 and previous versions, by default, the culture of all threads is set to the Windows system culture. For applications whose current culture differs from the default system culture, this behavior is often undesirable. In the .NET Framework 4.5, the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property enables an application to define the default culture of all threads in an application domain.  
   
 > [!IMPORTANT]
 >  If you have not explicitly set the culture of any existing threads executing in an application domain, setting the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property in that application domain or, if no default value is defined, by the default system culture. Because of this, we recommend that you always explicitly set the culture of your main application thread, and not rely on the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to define the culture of the main application thread.  
@@ -1634,7 +1634,7 @@ In .NET Framework and .NET Core apps, the current UI culture is a per-thread set
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and previous versions, by default, the UI culture of all threads is set to the Windows system culture. For applications whose current UI culture differs from the default system culture, this behavior is often undesirable. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property lets you define the default UI culture of all threads in an application domain.  
+ In the .NET Framework 4 and previous versions, by default, the UI culture of all threads is set to the Windows system culture. For applications whose current UI culture differs from the default system culture, this behavior is often undesirable. In the .NET Framework 4.5, the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property lets you define the default UI culture of all threads in an application domain.  
   
 > [!IMPORTANT]
 >  If you have not explicitly set the UI culture of any existing threads executing in an application domain, setting the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property also changes the culture of these threads. However, if these threads execute in another application domain, their culture is defined by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property in that application domain or, if no default value is defined, by the default system culture. Because of this, we recommend that you always explicitly set the culture of your main application thread and do not rely on the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property to define the culture of the main application thread.  
diff --git a/xml/System.Globalization/IdnMapping.xml b/xml/System.Globalization/IdnMapping.xml
index 80a328ae1e7..7aa2045e751 100644
--- a/xml/System.Globalization/IdnMapping.xml
+++ b/xml/System.Globalization/IdnMapping.xml
@@ -51,7 +51,7 @@
  The IDNA mechanism uses Punycode to map an internationalized domain name that contains Unicode characters outside the US-ASCII character range to the US-ASCII character range supported by the domain name system. The IDNA mechanism is used to convert only domain names, not data transmitted over the Internet.  
   
 > [!IMPORTANT]
->  In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Globalization.IdnMapping> class supports different versions of the IDNA standard, depending on the operating system in use:  
+>  In the .NET Framework 4.5, the <xref:System.Globalization.IdnMapping> class supports different versions of the IDNA standard, depending on the operating system in use:  
 >   
 > - When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).
 > - When run on earlier versions of the Windows operating system, it supports the 2003 version of the standard outlined by [RFC 3490: Internationalizing Domain Names in Applications (IDNA)](https://go.microsoft.com/fwlink/?LinkId=158110).
@@ -301,7 +301,7 @@
         <exception cref="T:System.ArgumentException">
           <paramref name="unicode" /> is invalid based on the <see cref="P:System.Globalization.IdnMapping.AllowUnassigned" /> and <see cref="P:System.Globalization.IdnMapping.UseStd3AsciiRules" /> properties, and the IDNA standard.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
+          <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
 -   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
@@ -395,7 +395,7 @@
         <exception cref="T:System.ArgumentException">
           <paramref name="unicode" /> is invalid based on the <see cref="P:System.Globalization.IdnMapping.AllowUnassigned" /> and <see cref="P:System.Globalization.IdnMapping.UseStd3AsciiRules" /> properties, and the IDNA standard.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
+          <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
 -   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
@@ -493,7 +493,7 @@
         <exception cref="T:System.ArgumentException">
           <paramref name="unicode" /> is invalid based on the <see cref="P:System.Globalization.IdnMapping.AllowUnassigned" /> and <see cref="P:System.Globalization.IdnMapping.UseStd3AsciiRules" /> properties, and the IDNA standard.</exception>
         <block subset="none" type="usage">
-          <para>In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
+          <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
 -   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
diff --git a/xml/System.Globalization/SortVersion.xml b/xml/System.Globalization/SortVersion.xml
index 75eff611aee..9df4d5c8d6c 100644
--- a/xml/System.Globalization/SortVersion.xml
+++ b/xml/System.Globalization/SortVersion.xml
@@ -50,7 +50,7 @@
 
 ### Sorting and string comparison in the .NET Framework
 
- From the .NET Framework 2.0 Service Pack 1 through the .NET Framework 4, each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the presence of these tables depends on the operating system:  
+ From the .NET Framework 2.0 Service Pack 1 through the .NET Framework 4, each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the .NET Framework 4.5, the presence of these tables depends on the operating system:  
   
 -   On [!INCLUDE[win7](~/includes/win7-md.md)] and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
   
@@ -61,8 +61,8 @@
 |.NET Framework version|Operating system|Unicode version|  
 |----------------------------|----------------------|---------------------|  
 |.NET Framework 4|All operating systems|Unicode 5.0|  
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions of the .NET Framework|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|  
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions of the .NET Framework|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.0|  
+|.NET Framework 4.5 and later versions of the .NET Framework|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|  
+|.NET Framework 4.5 and later versions of the .NET Framework|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.0|  
   
  On [!INCLUDE[win8](~/includes/win8-md.md)], because the version of Unicode used in string comparison and ordering depends on the version of the operating system, the results of string comparison may differ even for applications that run on a specific version of the .NET Framework.  
 
diff --git a/xml/System.Globalization/UmAlQuraCalendar.xml b/xml/System.Globalization/UmAlQuraCalendar.xml
index d7145253434..81621a13dc6 100644
--- a/xml/System.Globalization/UmAlQuraCalendar.xml
+++ b/xml/System.Globalization/UmAlQuraCalendar.xml
@@ -1245,7 +1245,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the value of the <xref:System.Globalization.UmAlQuraCalendar.MaxSupportedDateTime%2A> property is 11/16/2077. In previous versions of the .NET Framework, its value is the last moment of May 13, 2029 C.E. in the Gregorian calendar.  
+>  Starting with the .NET Framework 4.5, the value of the <xref:System.Globalization.UmAlQuraCalendar.MaxSupportedDateTime%2A> property is 11/16/2077. In previous versions of the .NET Framework, its value is the last moment of May 13, 2029 C.E. in the Gregorian calendar.  
   
    
   
diff --git a/xml/System.IO.Compression/DeflateStream.xml b/xml/System.IO.Compression/DeflateStream.xml
index c817a0cf780..6d42b858f3b 100644
--- a/xml/System.IO.Compression/DeflateStream.xml
+++ b/xml/System.IO.Compression/DeflateStream.xml
@@ -42,7 +42,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class represents the Deflate algorithm, which is an industry-standard algorithm for lossless file compression and decompression. Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.IO.Compression.DeflateStream> class uses the zlib library. As a result, it provides a better compression algorithm and, in most cases, a smaller compressed file than it provides in earlier versions of the .NET Framework.  
+ This class represents the Deflate algorithm, which is an industry-standard algorithm for lossless file compression and decompression. Starting with the .NET Framework 4.5, the <xref:System.IO.Compression.DeflateStream> class uses the zlib library. As a result, it provides a better compression algorithm and, in most cases, a smaller compressed file than it provides in earlier versions of the .NET Framework.  
   
  This class does not inherently provide functionality for adding files to or extracting files from zip archives. To work with zip archives, use the <xref:System.IO.Compression.ZipArchive> and the <xref:System.IO.Compression.ZipArchiveEntry> classes.  
   
@@ -461,7 +461,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.BeginRead%2A> method is still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.BeginRead%2A> method is still available in the .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  Pass the <xref:System.IAsyncResult> return value to the <xref:System.IO.Compression.DeflateStream.EndRead%2A> method of the stream to determine how many bytes were read and to release operating system resources used for reading. You can do this either by using the same code that called <xref:System.IO.Compression.DeflateStream.BeginRead%2A> or in a callback passed to <xref:System.IO.Compression.DeflateStream.BeginRead%2A>.  
   
@@ -542,7 +542,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.BeginWrite%2A> method is still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.BeginWrite%2A> method is still available in the .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  Pass the <xref:System.IAsyncResult> object returned by the current method to <xref:System.IO.Compression.DeflateStream.EndWrite%2A> to ensure that the write completes and frees resources appropriately. You can do this either by using the same code that called <xref:System.IO.Compression.DeflateStream.BeginWrite%2A> or in a callback passed to <xref:System.IO.Compression.DeflateStream.BeginWrite%2A>. If an error occurs during an asynchronous write operation, an exception will not be thrown until <xref:System.IO.Compression.DeflateStream.EndWrite%2A> is called with the <xref:System.IAsyncResult> returned by this method.  
   
@@ -916,7 +916,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.Compress
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.EndRead%2A> method is still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.EndRead%2A> method is still available in the .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  Call this method to determine how many bytes were read from the stream. This method can be called once to return the amount of bytes read between calls to <xref:System.IO.Compression.DeflateStream.BeginRead%2A> and <xref:System.IO.Compression.DeflateStream.EndRead%2A>.  
   
@@ -982,7 +982,7 @@ The stream is <see langword="null" />.</exception>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.EndWrite%2A> method is still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A> method. The <xref:System.IO.Compression.DeflateStream.EndWrite%2A> method is still available in the .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  <xref:System.IO.Compression.DeflateStream.EndWrite%2A> must be called only once for every call to the <xref:System.IO.Compression.DeflateStream.BeginWrite%2A> method.  
   
diff --git a/xml/System.IO.Compression/GZipStream.xml b/xml/System.IO.Compression/GZipStream.xml
index dd8e7087b49..4b2c3637ac3 100644
--- a/xml/System.IO.Compression/GZipStream.xml
+++ b/xml/System.IO.Compression/GZipStream.xml
@@ -44,7 +44,7 @@
 ## Remarks  
  This class represents the gzip data format, which uses an industry-standard algorithm for lossless file compression and decompression. The format includes a cyclic redundancy check value for detecting data corruption. The gzip data format uses the same algorithm as the <xref:System.IO.Compression.DeflateStream> class, but can be extended to use other compression formats. The format can be readily implemented in a manner not covered by patents.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.IO.Compression.DeflateStream> class uses the zlib library for compression. As a result, it provides a better compression algorithm and, in most cases, a smaller compressed file than it provides in earlier versions of the .NET Framework.  
+ Starting with the .NET Framework 4.5, the <xref:System.IO.Compression.DeflateStream> class uses the zlib library for compression. As a result, it provides a better compression algorithm and, in most cases, a smaller compressed file than it provides in earlier versions of the .NET Framework.  
   
  Compressed <xref:System.IO.Compression.GZipStream> objects written to a file with an extension of .gz can be decompressed using many common compression tools; however, this class does not inherently provide functionality for adding files to or extracting files from zip archives.  
   
@@ -434,7 +434,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.BeginRead%2A> method is still available in [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.BeginRead%2A> method is still available in .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  Pass the <xref:System.IAsyncResult> return value to the <xref:System.IO.Compression.GZipStream.EndRead%2A> method of the stream to determine how many bytes were read and to release operating system resources used for reading. You can do this either by using the same code that called <xref:System.IO.Compression.GZipStream.BeginRead%2A> or in a callback passed to <xref:System.IO.Compression.GZipStream.BeginRead%2A>.  
   
@@ -523,7 +523,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.BeginWrite%2A> method is still available in [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.BeginWrite%2A> method is still available in .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  The <xref:System.IO.Compression.GZipStream.BeginWrite%2A> method starts an asynchronous write operation to a <xref:System.IO.Compression.GZipStream> stream object.  
   
@@ -900,7 +900,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.Compress
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.EndRead%2A> method is still available in [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous read operations by using the <xref:System.IO.Stream.ReadAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.EndRead%2A> method is still available in .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  Call this method to determine how many bytes were read from the stream. This method can be called once to return the amount of bytes read between calls to <xref:System.IO.Compression.GZipStream.BeginRead%2A> and <xref:System.IO.Compression.GZipStream.EndRead%2A>.  
   
@@ -969,7 +969,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.Compress
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.EndWrite%2A> method is still available in [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
+ Starting with the .NET Framework 4.5, you can perform asynchronous write operations by using the <xref:System.IO.Stream.WriteAsync%2A?displayProperty=nameWithType> method. The <xref:System.IO.Compression.GZipStream.EndWrite%2A> method is still available in .NET Framework 4.5 to support legacy code; however, you can implement asynchronous I/O operations more easily by using the new async methods. For more information, see [Asynchronous File I/O](/dotnet/standard/io/asynchronous-file-i-o).
   
  The <xref:System.IO.Compression.GZipStream.EndWrite%2A> method completes the asynchronous write operation started in the <xref:System.IO.Compression.GZipStream.BeginWrite%2A> method.  
   
diff --git a/xml/System.IO/BufferedStream.xml b/xml/System.IO/BufferedStream.xml
index 6fa50c76ca6..c5d7344ed9d 100644
--- a/xml/System.IO/BufferedStream.xml
+++ b/xml/System.IO/BufferedStream.xml
@@ -279,7 +279,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  <xref:System.IO.BufferedStream.EndWrite%2A> must be called exactly once for every call to <xref:System.IO.BufferedStream.BeginRead%2A>. Failing to end a read process before beginning another read can cause undesirable behavior such as deadlock.  
   
@@ -354,7 +354,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  <xref:System.IO.BufferedStream.EndWrite%2A> must be called exactly once on every <xref:System.IAsyncResult> from <xref:System.IO.BufferedStream.BeginWrite%2A>. <xref:System.IO.BufferedStream.EndWrite%2A> will block until the I/O operation has completed.  
   
@@ -940,7 +940,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.Buffered
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  <xref:System.IO.BufferedStream.EndRead%2A> must be called with this <xref:System.IAsyncResult> to find out how many bytes were read.  
   
@@ -995,7 +995,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.Buffered
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.BufferedStream.ReadAsync%2A>, <xref:System.IO.BufferedStream.WriteAsync%2A>, and <xref:System.IO.BufferedStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  <xref:System.IO.BufferedStream.EndWrite%2A> must be called exactly once for every call to <xref:System.IO.BufferedStream.BeginRead%2A>. Failing to end a read process before beginning another read operation can cause deadlock or other undesirable behavior.  
   
diff --git a/xml/System.IO/FileStream.xml b/xml/System.IO/FileStream.xml
index 1f2683083d1..a3053cfa6cf 100644
--- a/xml/System.IO/FileStream.xml
+++ b/xml/System.IO/FileStream.xml
@@ -2241,7 +2241,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.FileStre
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.FileStream.BeginRead%2A> and <xref:System.IO.FileStream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.FileStream.BeginRead%2A> and <xref:System.IO.FileStream.EndRead%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  <xref:System.IO.FileStream.EndRead%2A> must be called exactly for every call to <xref:System.IO.FileStream.BeginRead%2A>. Failing to end a read process before beginning another read can cause undesirable behavior such as deadlock.  
   
@@ -2321,7 +2321,7 @@ Calling `DisposeAsync` allows the resources used by the <xref:System.IO.FileStre
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.FileStream.BeginWrite%2A> and <xref:System.IO.FileStream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.FileStream.BeginWrite%2A> and <xref:System.IO.FileStream.EndWrite%2A> to implement asynchronous file operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A>, help you implement asynchronous file operations more easily.  
   
  This method overrides <xref:System.IO.Stream.EndWrite%2A>.  
   
diff --git a/xml/System.IO/Stream.xml b/xml/System.IO/Stream.xml
index 4b2c9a47926..840c8330ae2 100644
--- a/xml/System.IO/Stream.xml
+++ b/xml/System.IO/Stream.xml
@@ -98,7 +98,7 @@
   
  Disposing a <xref:System.IO.Stream> object flushes any buffered data, and essentially calls the <xref:System.IO.Stream.Flush%2A> method for you. <xref:System.IO.Stream.Dispose%2A> also releases operating system resources such as file handles, network connections, or memory used for any internal buffering. The <xref:System.IO.BufferedStream> class provides the capability of wrapping a buffered stream around another stream in order to improve read and write performance.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ Starting with the .NET Framework 4.5, the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  When used in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)]. You can also convert a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)] to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
   
@@ -229,7 +229,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous I/O operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous I/O operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
   
  The default implementation of `BeginRead` on a stream calls the <xref:System.IO.Stream.Read%2A> method synchronously, which means that `Read` might block on some streams. However, instances of classes such as `FileStream` and `NetworkStream` fully support asynchronous operations if the instances have been opened asynchronously. Therefore, calls to `BeginRead` will not block on those streams. You can override `BeginRead` (by using async delegates, for example) to provide asynchronous behavior.  
   
@@ -309,7 +309,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous I/O operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous I/O operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
   
  The default implementation of `BeginWrite` on a stream calls the <xref:System.IO.Stream.Write%2A> method synchronously, which means that `Write` might block on some streams. However, instances of classes such as `FileStream` and `NetworkStream` fully support asynchronous operations if the instances have been opened asynchronously. Therefore, calls to `BeginWrite` will not block on those streams. You can override `BeginWrite` (by using async delegates, for example) to provide asynchronous behavior.  
   
@@ -1330,7 +1330,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous I/O operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginRead%2A> and <xref:System.IO.Stream.EndRead%2A> to implement asynchronous I/O operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
   
  Call `EndRead` to determine how many bytes were read from the stream.  
   
@@ -1399,7 +1399,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous I/O operations. These methods are still available in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
+ In the .NET Framework 4 and earlier versions, you have to use methods such as <xref:System.IO.Stream.BeginWrite%2A> and <xref:System.IO.Stream.EndWrite%2A> to implement asynchronous I/O operations. These methods are still available in the .NET Framework 4.5 to support legacy code; however, the new async methods, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>, help you implement asynchronous I/O operations more easily.  
   
  `EndWrite` must be called exactly once on every <xref:System.IAsyncResult> from <xref:System.IO.Stream.BeginWrite%2A>.  
   
diff --git a/xml/System.Net.Configuration/UnicodeDecodingConformance.xml b/xml/System.Net.Configuration/UnicodeDecodingConformance.xml
index 73b15d40865..0282ef99de9 100644
--- a/xml/System.Net.Configuration/UnicodeDecodingConformance.xml
+++ b/xml/System.Net.Configuration/UnicodeDecodingConformance.xml
@@ -42,7 +42,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Use automatic behavior. The decoding behavior is determined by current application's target Framework. For [!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later, the Unicode encoding decoding is strict.</summary>
+        <summary>Use automatic behavior. The decoding behavior is determined by current application's target Framework. For .NET Framework 4.5 and later, the Unicode encoding decoding is strict.</summary>
       </Docs>
     </Member>
     <Member MemberName="Compat">
diff --git a/xml/System.Net.Configuration/UnicodeEncodingConformance.xml b/xml/System.Net.Configuration/UnicodeEncodingConformance.xml
index 8d43ae2ff13..55f93287387 100644
--- a/xml/System.Net.Configuration/UnicodeEncodingConformance.xml
+++ b/xml/System.Net.Configuration/UnicodeEncodingConformance.xml
@@ -42,7 +42,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Use automatic behavior. The Unicode encoding behavior is determined by current application's target Framework. For [!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later, the Unicode encoding behavior is strict.</summary>
+        <summary>Use automatic behavior. The Unicode encoding behavior is determined by current application's target Framework. For .NET Framework 4.5 and later, the Unicode encoding behavior is strict.</summary>
       </Docs>
     </Member>
     <Member MemberName="Compat">
diff --git a/xml/System.Net.Sockets/SocketFlags.xml b/xml/System.Net.Sockets/SocketFlags.xml
index e9537025b10..9364fd4c772 100644
--- a/xml/System.Net.Sockets/SocketFlags.xml
+++ b/xml/System.Net.Sockets/SocketFlags.xml
@@ -185,7 +185,7 @@
       </ReturnValue>
       <MemberValue>16</MemberValue>
       <Docs>
-        <summary>Provides a standard value for the number of WSABUF structures that are used to send and receive data. This value is not used or supported on [!INCLUDE[net_v45](~/includes/net-v45-md.md)].</summary>
+        <summary>Provides a standard value for the number of WSABUF structures that are used to send and receive data. This value is not used or supported on .NET Framework 4.5.</summary>
       </Docs>
     </Member>
     <Member MemberName="Multicast">
diff --git a/xml/System.Net.WebSockets/WebSocket.xml b/xml/System.Net.WebSockets/WebSocket.xml
index 8693eb424cc..c5273398d94 100644
--- a/xml/System.Net.WebSockets/WebSocket.xml
+++ b/xml/System.Net.WebSockets/WebSocket.xml
@@ -613,9 +613,9 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a value that indicates if the WebSocket instance is targeting [!INCLUDE[net_v45](~/includes/net-v45-md.md)].</summary>
+        <summary>Returns a value that indicates if the WebSocket instance is targeting .NET Framework 4.5.</summary>
         <returns>
-          <see langword="true" /> if the <see cref="T:System.Net.WebSockets.WebSocket" /> is targeting [!INCLUDE[net_v45](~/includes/net-v45-md.md)]; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the <see cref="T:System.Net.WebSockets.WebSocket" /> is targeting .NET Framework 4.5; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Net/FileWebResponse.xml b/xml/System.Net/FileWebResponse.xml
index 152ade68ad1..9c66b9b9202 100644
--- a/xml/System.Net/FileWebResponse.xml
+++ b/xml/System.Net/FileWebResponse.xml
@@ -560,7 +560,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is always true for [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ This property is always true for .NET Framework 4.5.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Net/FtpWebResponse.xml b/xml/System.Net/FtpWebResponse.xml
index 9f3894b9520..5977e08046d 100644
--- a/xml/System.Net/FtpWebResponse.xml
+++ b/xml/System.Net/FtpWebResponse.xml
@@ -722,7 +722,7 @@ This property is provided only for compatibility with other implementations of t
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is always true for [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ This property is always true for .NET Framework 4.5.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Net/WebResponse.xml b/xml/System.Net/WebResponse.xml
index a0d6f300f97..a4176be66df 100644
--- a/xml/System.Net/WebResponse.xml
+++ b/xml/System.Net/WebResponse.xml
@@ -893,7 +893,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is always true for [!INCLUDE[net_v45](~/includes/net-v45-md.md)].  
+ This property is always true for .NET Framework 4.5.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/AssemblySignatureKeyAttribute.xml b/xml/System.Reflection/AssemblySignatureKeyAttribute.xml
index 94245da42d4..654691c855e 100644
--- a/xml/System.Reflection/AssemblySignatureKeyAttribute.xml
+++ b/xml/System.Reflection/AssemblySignatureKeyAttribute.xml
@@ -46,7 +46,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The new larger key is the signature key. In versions before the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the signature key was identical to the identity key. Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Reflection.AssemblySignatureKeyAttribute> attribute allows the assembly metadata to continue to have the old public key token and binary large object (BLOB) so that existing assembly references continue to work. It also ensures that the mapping comes from an owner of the identity key.  
+ The new larger key is the signature key. In versions before the .NET Framework 4.5, the signature key was identical to the identity key. Starting with the .NET Framework 4.5, the <xref:System.Reflection.AssemblySignatureKeyAttribute> attribute allows the assembly metadata to continue to have the old public key token and binary large object (BLOB) so that existing assembly references continue to work. It also ensures that the mapping comes from an owner of the identity key.  
   
  The presence of the attribute does not necessarily mean that strong name validation takes place. In common full-trust scenarios, the attribute is never considered, because strong name signatures are never validated. However, when the strong name signature does have to be validated, both the strong name signature and the countersignature must be validated. The assembly's identity key does not have to be identical to the signature key (the key used to do the actual signing and validation). The identity key can be mapped to a different (more robust) signing key. This lets you set the identity of an assembly, and update the signing keys and algorithms to more secure versions.  
   
diff --git a/xml/System.Reflection/TypeInfo.xml b/xml/System.Reflection/TypeInfo.xml
index d63bd46c319..b7f67d8a7f5 100644
--- a/xml/System.Reflection/TypeInfo.xml
+++ b/xml/System.Reflection/TypeInfo.xml
@@ -68,7 +68,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Reflection.TypeInfo> class is included in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset for use in creating Windows Store apps. <xref:System.Reflection.TypeInfo> is available in the full .NET Framework as well. For more information about reflection for Windows Store apps, see [System.Reflection namespaces](/dotnet/api/?term=system.reflection) and [Reflection in the .NET Framework for Windows Store Apps](/dotnet/framework/reflection-and-codedom/reflection-for-windows-store-apps).  
+ Starting with .NET Framework 4.5, the <xref:System.Reflection.TypeInfo> class is included in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset for use in creating Windows Store apps. <xref:System.Reflection.TypeInfo> is available in the full .NET Framework as well. For more information about reflection for Windows Store apps, see [System.Reflection namespaces](/dotnet/api/?term=system.reflection) and [Reflection in the .NET Framework for Windows Store Apps](/dotnet/framework/reflection-and-codedom/reflection-for-windows-store-apps).  
   
  <xref:System.Reflection.TypeInfo> contains many of the members available in the <xref:System.Type> class, and many of the reflection properties in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] return collections of <xref:System.Reflection.TypeInfo> objects. To get a <xref:System.Reflection.TypeInfo> object from a <xref:System.Type> object, use the <xref:System.Reflection.IntrospectionExtensions.GetTypeInfo%28System.Type%29?displayProperty=nameWithType> extension method.  
   
diff --git a/xml/System.Text.RegularExpressions/Regex.xml b/xml/System.Text.RegularExpressions/Regex.xml
index 4f4522c1e21..2c78527e8c7 100644
--- a/xml/System.Text.RegularExpressions/Regex.xml
+++ b/xml/System.Text.RegularExpressions/Regex.xml
@@ -148,7 +148,7 @@
 ## Defining a Time-Out Value  
  The .NET Framework supports a full-featured regular expression language that provides substantial power and flexibility in pattern matching. However, the power and flexibility come at a cost: the risk of poor performance. Regular expressions that perform poorly are surprisingly easy to create. In some cases, regular expression operations that rely on excessive backtracking can appear to stop responding when they process text that nearly matches the regular expression pattern. For more information about the .NET Framework regular expression engine, see [Details of Regular Expression Behavior](/dotnet/standard/base-types/details-of-regular-expression-behavior). For more information about excessive backtracking, see [Backtracking](/dotnet/standard/base-types/backtracking-in-regular-expressions).  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can define a time-out interval for regular expression matches. If the regular expression engine cannot identify a match within this time interval, the matching operation throws a <xref:System.Text.RegularExpressions.RegexMatchTimeoutException> exception. In most cases, this prevents the regular expression engine from wasting processing power by trying to match text that nearly matches the regular expression pattern. It also could indicate, however, that the timeout interval has been set too low, or that the current machine load has caused an overall degradation in performance.  
+ Starting with the .NET Framework 4.5, you can define a time-out interval for regular expression matches. If the regular expression engine cannot identify a match within this time interval, the matching operation throws a <xref:System.Text.RegularExpressions.RegexMatchTimeoutException> exception. In most cases, this prevents the regular expression engine from wasting processing power by trying to match text that nearly matches the regular expression pattern. It also could indicate, however, that the timeout interval has been set too low, or that the current machine load has caused an overall degradation in performance.  
   
  How you handle the exception depends on the cause of the exception. If the exception occurs because the time-out interval is set too low or because of excessive machine load, you can increase the time-out interval and retry the matching operation. If the exception occurs because the regular expression relies on excessive backtracking, you can assume that a match does not exist, and, optionally, you can log information that will help you modify the regular expression pattern.  
   
@@ -986,7 +986,7 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
           <paramref name="assemblyname" /> or <paramref name="regexinfos" /> is <see langword="null" />.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has .NET Framework 4.5 or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
 -   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
@@ -1095,7 +1095,7 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
           <paramref name="assemblyname" /> or <paramref name="regexinfos" /> is <see langword="null" />.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has .NET Framework 4.5 or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
 -   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
@@ -1191,7 +1191,7 @@ On .NET Core, calls to the `Regex.CompileToAssembly` method throw a <xref:System
         <exception cref="T:System.IO.FileNotFoundException">The file designated by the <paramref name="resourceFile" /> parameter cannot be found.</exception>
         <exception cref="T:System.PlatformNotSupportedException">.NET 5+ and .NET Core only: Creating an assembly of compiled regular expressions is not supported. </exception>
         <block subset="none" type="usage">
-          <para>If you are developing on a system that has [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
+          <para>If you are developing on a system that has .NET Framework 4.5 or its point releases installed, you target .NET Framework 4, and you use the <see cref="M:System.Text.RegularExpressions.Regex.CompileToAssembly(System.Text.RegularExpressions.RegexCompilationInfo[],System.Reflection.AssemblyName)" /> method to create an assembly that contains compiled regular expressions. Trying to use one of the regular expressions in that assembly on a system that has .NET Framework 4 throws an exception. To work around this problem, you can do either of the following:  
   
 -   Build the assembly that contains the compiled regular expressions on a system that has .NET Framework 4 instead of later versions installed.  
   
diff --git a/xml/System.Threading.Tasks/Task.xml b/xml/System.Threading.Tasks/Task.xml
index 7b5a331a0ab..300c7ab28bc 100644
--- a/xml/System.Threading.Tasks/Task.xml
+++ b/xml/System.Threading.Tasks/Task.xml
@@ -101,7 +101,7 @@
     
 <a name="Creating"></a>   
 ## Creating and executing a task  
- <xref:System.Threading.Tasks.Task> instances may be created in a variety of ways. The most common approach, which is available starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], is to call the static <xref:System.Threading.Tasks.Task.Run%2A> method. The <xref:System.Threading.Tasks.Task.Run%2A> method provides a simple way to start a task using default values and without requiring additional parameters. The following example uses the <xref:System.Threading.Tasks.Task.Run%28System.Action%29> method to start a task that loops and then displays the number of loop iterations:  
+ <xref:System.Threading.Tasks.Task> instances may be created in a variety of ways. The most common approach, which is available starting with the .NET Framework 4.5, is to call the static <xref:System.Threading.Tasks.Task.Run%2A> method. The <xref:System.Threading.Tasks.Task.Run%2A> method provides a simple way to start a task using default values and without requiring additional parameters. The following example uses the <xref:System.Threading.Tasks.Task.Run%28System.Action%29> method to start a task that loops and then displays the number of loop iterations:  
   
  [!code-csharp[System.Threading.Tasks.Task#6](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task/cs/run1.cs#6)]
  [!code-vb[System.Threading.Tasks.Task#6](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task/vb/run1.vb#6)]  
@@ -2523,7 +2523,7 @@ Task t Status: RanToCompletion, Result: 42
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.  
+ The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -2571,7 +2571,7 @@ Task t Status: RanToCompletion, Result: 42
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.  
+ The <xref:System.Threading.Tasks.Task> class implements the <xref:System.IDisposable> interface because internally it uses resources that also implement <xref:System.IDisposable>. However, particularly if your app targets the .NET Framework 4.5 or later, there is no need to call <xref:System.Threading.Tasks.Task.Dispose%2A> unless performance or scalability testing indicates that, based on your usage patterns, your app's performance would be improved by disposing of tasks. For more information, see [Do I need to dispose of Tasks?](https://devblogs.microsoft.com/pfxteam/do-i-need-to-dispose-of-tasks/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -2678,7 +2678,7 @@ Task t Status: RanToCompletion, Result: 42
  The most common use of this property is to create and start a new task in a single call to the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task> object with default configuration values.  
+>  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task> object with default configuration values.  
   
  The following example uses the static <xref:System.Threading.Tasks.Task.Factory%2A> property to make two calls to the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A?displayProperty=nameWithType> method. The first populates an array with the names of files in the user's MyDocuments directory, while the second populates an array with the names of subdirectories of the user's MyDocuments directory. It then calls the <xref:System.Threading.Tasks.TaskFactory.ContinueWhenAll%28System.Threading.Tasks.Task%5B%5D%2CSystem.Action%7BSystem.Threading.Tasks.Task%5B%5D%7D%29?displayProperty=nameWithType> method, which displays information about the number of files and directories in the two arrays after the first two tasks have completed execution.  
   
diff --git a/xml/System.Threading.Tasks/TaskFactory.xml b/xml/System.Threading.Tasks/TaskFactory.xml
index ed4b05dbc25..e58de739658 100644
--- a/xml/System.Threading.Tasks/TaskFactory.xml
+++ b/xml/System.Threading.Tasks/TaskFactory.xml
@@ -51,7 +51,7 @@
 -   The <xref:System.Threading.Tasks.TaskFactory> class, which creates <xref:System.Threading.Tasks.Task> and <xref:System.Threading.Tasks.Task%601> objects. You can call the overloads of this method to create and execute a task that requires non-default arguments.  
   
     > [!WARNING]
-    >  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
+    >  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
   
 -   The <xref:System.Threading.Tasks.TaskFactory%601> class, which creates <xref:System.Threading.Tasks.Task%601> objects.  
   
@@ -60,7 +60,7 @@
 -   Create a task and start it immediately by calling the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> method.  
   
     > [!WARNING]
-    >  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
+    >  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
   
 -   Create a task that starts when any one of the tasks in an array has completed by calling the <xref:System.Threading.Tasks.TaskFactory.ContinueWhenAny%2A> method.  
   
@@ -4469,7 +4469,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method is the recommended way to launch a compute-bound task. Use the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> method only when you require fine-grained control for a long-running, compute-bound task. This includes scenarios in which you want to control the following:  
+ Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method is the recommended way to launch a compute-bound task. Use the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> method only when you require fine-grained control for a long-running, compute-bound task. This includes scenarios in which you want to control the following:  
   
 -   Task creation options. Tasks created by the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method by default are created with the <xref:System.Threading.Tasks.TaskCreationOptions.DenyChildAttach?displayProperty=nameWithType> option. To override this behavior, or to provide other <xref:System.Threading.Tasks.TaskCreationOptions> options, call a <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> overload.  
   
@@ -4528,7 +4528,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> is functionally equivalent to creating a task by using one of its constructors, and then calling the <xref:System.Threading.Tasks.Task.Start%2A?displayProperty=nameWithType> method to schedule the task for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%28System.Action%29?displayProperty=nameWithType> method as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%28System.Action%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%29> does. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%28System.Action%29?displayProperty=nameWithType> method as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%28System.Action%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%29> does. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -4594,7 +4594,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling `StartNew` is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%28System.Action%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%2CSystem.Threading.CancellationToken%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%28System.Action%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%2CSystem.Threading.CancellationToken%29> does. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%28System.Action%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%2CSystem.Threading.CancellationToken%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%28System.Action%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%28System.Action%2CSystem.Threading.CancellationToken%29> does. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -4662,7 +4662,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -4724,7 +4724,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> is functionally equivalent to creating a <xref:System.Threading.Tasks.Task> using one of its constructors and then calling the <xref:System.Threading.Tasks.Task.Start%2A> method to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -4795,7 +4795,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -4868,7 +4868,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -4933,7 +4933,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5006,7 +5006,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a Task using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as  a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see [Task.Run vs Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5074,7 +5074,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can call the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> method as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task%601> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%29> does. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can call the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> method as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task%601> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%29> does. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -5145,7 +5145,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5208,7 +5208,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task%601> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29> does. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29> with default parameters. Note, however, that there is a difference in behavior between the two methods regarding : <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> by default does not allow child tasks started with the <xref:System.Threading.Tasks.TaskCreationOptions.AttachedToParent?displayProperty=nameWithType> option to attach to the current <xref:System.Threading.Tasks.Task%601> instance, whereas <xref:System.Threading.Tasks.TaskFactory.StartNew%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29> does. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
    
   
@@ -5280,7 +5280,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5348,7 +5348,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5415,7 +5415,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5484,7 +5484,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
@@ -5561,7 +5561,7 @@ The NotOn\* and OnlyOn\* <xref:System.Threading.Tasks.TaskContinuationOptions>,
 ## Remarks  
  Calling StartNew is functionally equivalent to creating a <xref:System.Threading.Tasks.Task%601> using one of its constructors and then calling <xref:System.Threading.Tasks.Task.Start%2A> to schedule it for execution.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
+ Starting with the .NET Framework 4.5, you can use the <xref:System.Threading.Tasks.Task.Run%2A> method with an <xref:System.Action> object as a quick way to call <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> with default parameters. For more information and code examples, see the entry [Task.Run vs. Task.Factory.StartNew](https://devblogs.microsoft.com/pfxteam/task-run-vs-task-factory-startnew/) in the Parallel Programming with .NET blog.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Threading.Tasks/TaskFactory`1.xml b/xml/System.Threading.Tasks/TaskFactory`1.xml
index 6f96857252a..bc8fdb99b2a 100644
--- a/xml/System.Threading.Tasks/TaskFactory`1.xml
+++ b/xml/System.Threading.Tasks/TaskFactory`1.xml
@@ -61,7 +61,7 @@
 -   Create a task and start it immediately by calling the <xref:System.Threading.Tasks.TaskFactory.StartNew%2A> method. You can call the overloads of this method to create and execute a task that requires non-default arguments.  
   
     > [!WARNING]
-    >  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
+    >  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a task with default configuration values and start it immediately.  
   
 -   Create a task that starts when any one of the tasks in an array has completed by calling the <xref:System.Threading.Tasks.TaskFactory.ContinueWhenAny%2A> or   <xref:System.Threading.Tasks.TaskFactory.ContinueWhenAny%2A> method.  
   
diff --git a/xml/System.Threading.Tasks/TaskScheduler.xml b/xml/System.Threading.Tasks/TaskScheduler.xml
index aa6125a2d9f..927e046fe1b 100644
--- a/xml/System.Threading.Tasks/TaskScheduler.xml
+++ b/xml/System.Threading.Tasks/TaskScheduler.xml
@@ -832,7 +832,7 @@ protected override IEnumerable<Task> GetScheduledTasks()
 ## Remarks  
  This application domain-wide event provides a mechanism to prevent exception escalation policy (which, by default, terminates the process) from triggering.  
   
- To make it easier for developers to write asynchronous code based on tasks, the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] changes the default exception behavior for unobserved exceptions. Although unobserved exceptions still raise the <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException> exception, the process does not terminate by default. Instead, the exception is handled by the runtime after the event is raised, regardless of whether an event handler observes the exception. This behavior can be configured. Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can use the [`<ThrowUnobservedTaskExceptions>`](/dotnet/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element) configuration element to revert to the behavior of the .NET Framework 4 and terminate the process:  
+ To make it easier for developers to write asynchronous code based on tasks, the .NET Framework 4.5 changes the default exception behavior for unobserved exceptions. Although unobserved exceptions still raise the <xref:System.Threading.Tasks.TaskScheduler.UnobservedTaskException> exception, the process does not terminate by default. Instead, the exception is handled by the runtime after the event is raised, regardless of whether an event handler observes the exception. This behavior can be configured. Starting with the .NET Framework 4.5, you can use the [`<ThrowUnobservedTaskExceptions>`](/dotnet/framework/configure-apps/file-schema/runtime/throwunobservedtaskexceptions-element) configuration element to revert to the behavior of the .NET Framework 4 and terminate the process:  
   
 ```xml  
 <configuration>   
diff --git a/xml/System.Threading.Tasks/Task`1.xml b/xml/System.Threading.Tasks/Task`1.xml
index c64773af307..f9232d97694 100644
--- a/xml/System.Threading.Tasks/Task`1.xml
+++ b/xml/System.Threading.Tasks/Task`1.xml
@@ -62,7 +62,7 @@
 ## Remarks  
  The <xref:System.Threading.Tasks.Task%601> class represents a single operation that returns a value and that usually executes asynchronously. <xref:System.Threading.Tasks.Task%601> objects are one of the central components of the [task-based asynchronous pattern](/dotnet/standard/asynchronous-programming-patterns/task-based-asynchronous-pattern-tap) first introduced in the .NET Framework 4. Because the work performed by a <xref:System.Threading.Tasks.Task%601> object typically executes asynchronously on a thread pool thread rather than synchronously on the main application thread, you can use the <xref:System.Threading.Tasks.Task.Status%2A> property, as well as the <xref:System.Threading.Tasks.Task.IsCanceled%2A>, <xref:System.Threading.Tasks.Task.IsCompleted%2A>, and <xref:System.Threading.Tasks.Task.IsFaulted%2A> properties, to determine the   state of a task. Most commonly, a lambda expression is used to specify the work that the task is to perform.  
   
- <xref:System.Threading.Tasks.Task%601> instances may be created in a variety of ways. The most common approach, which is available starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], is to call the static <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> or <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method. These methods provide a simple way to start a task by using default values and without acquiring additional parameters. The following example uses the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> method to start a task that loops and then displays the number of loop iterations:  
+ <xref:System.Threading.Tasks.Task%601> instances may be created in a variety of ways. The most common approach, which is available starting with the .NET Framework 4.5, is to call the static <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> or <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%2CSystem.Threading.CancellationToken%29?displayProperty=nameWithType> method. These methods provide a simple way to start a task by using default values and without acquiring additional parameters. The following example uses the <xref:System.Threading.Tasks.Task.Run%60%601%28System.Func%7B%60%600%7D%29?displayProperty=nameWithType> method to start a task that loops and then displays the number of loop iterations:  
   
  [!code-csharp[System.Threading.Tasks.Task\`1#6](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.threading.tasks.task`1/cs/run1.cs#6)]
  [!code-vb[System.Threading.Tasks.Task\`1#6](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.threading.tasks.task`1/vb/run1.vb#6)]  
@@ -1948,7 +1948,7 @@ For operations that do not return a value, you use the <xref:System.Threading.Ta
  The most common use of this property is to create and start a new task in a single call to the <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A?displayProperty=nameWithType> method.  
   
 > [!NOTE]
->  Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task%601> object with default configuration values.  
+>  Starting with the .NET Framework 4.5, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> method provides the easiest way to create a <xref:System.Threading.Tasks.Task%601> object with default configuration values.  
   
  The following example uses the static <xref:System.Threading.Tasks.Task%601.Factory%2A> property to make three calls to the <xref:System.Threading.Tasks.TaskFactory%601.StartNew%2A?displayProperty=nameWithType> method. The first starts a `Task<Int32>` object, which executes a lambda expression that returns 1. The second starts a `Task<Test>` object, which executes a lambda expression that instantiates a new `Test` instance. The third starts a `Task<String[]>` object, which enumerates the files in the C:\Users\Public\Pictures\Sample Pictures\ directory. (Note that successful execution of the example requires that the directory exist and that it contain files.  
   
diff --git a/xml/System.Threading/Interlocked.xml b/xml/System.Threading/Interlocked.xml
index 5ede2efac52..c1eb5e1ff82 100644
--- a/xml/System.Threading/Interlocked.xml
+++ b/xml/System.Threading/Interlocked.xml
@@ -2062,7 +2062,7 @@ If `comparand` and the object in `location1` are equal by reference, then `value
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method was added to the <xref:System.Threading.Interlocked> class in the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] as a convenience; it's a wrapper for the <xref:System.Threading.Thread.MemoryBarrier%2A?displayProperty=nameWithType> method.  
+ This method was added to the <xref:System.Threading.Interlocked> class in the .NET Framework 4.5 as a convenience; it's a wrapper for the <xref:System.Threading.Thread.MemoryBarrier%2A?displayProperty=nameWithType> method.  
   
  For most purposes, the C# `lock` statement, the Visual Basic `SyncLock` statement, or the <xref:System.Threading.Monitor> class provide easier ways to synchronize data.  
   
diff --git a/xml/System.Threading/Thread.xml b/xml/System.Threading/Thread.xml
index 2dea87dce89..222f249143d 100644
--- a/xml/System.Threading/Thread.xml
+++ b/xml/System.Threading/Thread.xml
@@ -175,7 +175,7 @@
   
 -   You can pass a <xref:System.Globalization.CultureInfo> object that represents that culture to the <xref:System.Threading.ParameterizedThreadStart> delegate or the <xref:System.Threading.ThreadPool.QueueUserWorkItem%28System.Threading.WaitCallback%2CSystem.Object%29?displayProperty=nameWithType> method.  
   
--   For apps running on the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later versions, you can define the culture and UI culture that is to be assigned to all threads created in an application domain by setting the value of the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A?displayProperty=nameWithType> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A?displayProperty=nameWithType> properties. Note that this is a per-application domain setting.  
+-   For apps running on the .NET Framework 4.5 and later versions, you can define the culture and UI culture that is to be assigned to all threads created in an application domain by setting the value of the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A?displayProperty=nameWithType> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A?displayProperty=nameWithType> properties. Note that this is a per-application domain setting.  
 
  For more information and examples, see the "Culture and threads" section of the <xref:System.Globalization.CultureInfo> class topic.
 
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index 6ef9d106ca7..9f614425ad2 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1366,7 +1366,7 @@
       </Parameters>
       <Docs>
         <param name="functionName">The name of the string comparison function to override.</param>
-        <param name="functionVersion">The function version. For [!INCLUDE[net_v45](~/includes/net-v45-md.md)], its value must be 1 or greater.</param>
+        <param name="functionVersion">The function version. For .NET Framework 4.5, its value must be 1 or greater.</param>
         <param name="functionPointer">A pointer to the function that overrides <paramref name="functionName" />.</param>
         <summary>Provides the common language runtime with an alternate implementation of a string comparison function.</summary>
         <remarks>
diff --git a/xml/System/Console.xml b/xml/System/Console.xml
index 6b5c3be11de..6ce93bfeaa2 100644
--- a/xml/System/Console.xml
+++ b/xml/System/Console.xml
@@ -2435,7 +2435,7 @@ This method can be used to reacquire the standard output stream after it has bee
         <exception cref="T:System.IO.IOException">An error occurred during the execution of this operation.</exception>
         <exception cref="T:System.Security.SecurityException">Your application does not have permission to perform this operation.</exception>
         <block subset="none" type="usage">
-          <para>Of the Unicode encodings, the <see cref="T:System.Console" /> class supports UTF-8 encoding with the <see cref="T:System.Text.UTF8Encoding" /> class and, starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], it supports UTF-16 encoding with the <see cref="T:System.Text.UnicodeEncoding" /> class. UTF-32 encoding with the <see cref="T:System.Text.UTF32Encoding" /> class is not supported. Attempting to set the output encoding to UTF-32 throws an <see cref="T:System.IO.IOException" />.
+          <para>Of the Unicode encodings, the <see cref="T:System.Console" /> class supports UTF-8 encoding with the <see cref="T:System.Text.UTF8Encoding" /> class and, starting with the .NET Framework 4.5, it supports UTF-16 encoding with the <see cref="T:System.Text.UnicodeEncoding" /> class. UTF-32 encoding with the <see cref="T:System.Text.UTF32Encoding" /> class is not supported. Attempting to set the output encoding to UTF-32 throws an <see cref="T:System.IO.IOException" />.
 
  Note that successfully displaying Unicode characters to the console requires the following:
 
diff --git a/xml/System/ConsoleCancelEventArgs.xml b/xml/System/ConsoleCancelEventArgs.xml
index d248941cbb9..49501f71e2f 100644
--- a/xml/System/ConsoleCancelEventArgs.xml
+++ b/xml/System/ConsoleCancelEventArgs.xml
@@ -114,7 +114,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>In the .NET Framework 3.5 and .NET Framework 4, attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
+          <para>In the .NET Framework 3.5 and .NET Framework 4, attempting to set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> if the <see cref="E:System.Console.CancelKeyPress" /> event was invoked by the user pressing Ctrl+Break threw an <see cref="T:System.InvalidOperationException" /> exception. In the .NET Framework 4.5, you can set the <see cref="P:System.ConsoleCancelEventArgs.Cancel" /> property to <see langword="true" /> after the user presses Ctrl+Break and cancel the termination of the application.</para>
         </block>
         <altmember cref="T:System.ConsoleCancelEventHandler" />
         <altmember cref="T:System.ConsoleKey" />
diff --git a/xml/System/Environment.xml b/xml/System/Environment.xml
index 6dadb41a85d..ec2cee9e389 100644
--- a/xml/System/Environment.xml
+++ b/xml/System/Environment.xml
@@ -2491,7 +2491,7 @@ The following example creates environment variables for the <xref:System.Environ
  For the .NET Framework Versions 4, 4.5, 4.5.1, and 4.5.2, the <xref:System.Environment.Version%2A?displayProperty=nameWithType> property returns a <xref:System.Version> object whose string representation has the form `4.0.30319.xxxxx`. For the .NET Framework 4.6 and later versions, it has the form `4.0.30319.42000`.
 
 > [!WARNING]
-> For the [!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later, we do not recommend using the <xref:System.Environment.Version%2A> property to detect the version of the runtime; instead, you can determine the version of the common language runtime by querying the registry. For more information, see [How to: Determine Which .NET Framework Versions Are Installed](/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed).
+> For the .NET Framework 4.5 and later, we do not recommend using the <xref:System.Environment.Version%2A> property to detect the version of the runtime; instead, you can determine the version of the common language runtime by querying the registry. For more information, see [How to: Determine Which .NET Framework Versions Are Installed](/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed).
 
  For more information about the version of the common language runtime that is installed with each version of the .NET Framework, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).
 
diff --git a/xml/System/Exception.xml b/xml/System/Exception.xml
index f0e75bcbc76..d6a9864c626 100644
--- a/xml/System/Exception.xml
+++ b/xml/System/Exception.xml
@@ -954,7 +954,7 @@ Stack Trace:
 ## Remarks  
  HRESULT is a 32-bit value, divided into three different fields: a severity code, a facility code, and an error code. The severity code indicates whether the return value represents information, warning, or error. The facility code identifies the area of the system responsible for the error. The error code is a unique number that is assigned to represent the exception. Each exception is mapped to a distinct HRESULT. When managed code throws an exception, the runtime passes the HRESULT to the COM client. When unmanaged code returns an error, the HRESULT is converted to an exception, which is then thrown by the runtime. For information about HRESULT values and their corresponding .NET Framework exceptions, see [How to: Map HRESULTs and Exceptions](/dotnet/framework/interop/how-to-map-hresults-and-exceptions). See [Common HRESULT Values](/windows/win32/seccrypto/common-hresult-values) in the Windows documentation for a list of the values you are most likely to encounter.  
   
- Starting with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], the <xref:System.Exception.HResult%2A> property's setter is protected, whereas its getter is public.  In previous versions of the .NET Framework, both getter and setter are protected.  
+ Starting with the .NET Framework 4.5, the <xref:System.Exception.HResult%2A> property's setter is protected, whereas its getter is public.  In previous versions of the .NET Framework, both getter and setter are protected.  
   
    
   
diff --git a/xml/System/IAsyncResult.xml b/xml/System/IAsyncResult.xml
index 0d696060e13..076fe3cd05b 100644
--- a/xml/System/IAsyncResult.xml
+++ b/xml/System/IAsyncResult.xml
@@ -268,7 +268,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>Most implementers of the <see cref="T:System.IAsyncResult" /> interface will not use this property and should return <see langword="false" />. Beginning with the [!INCLUDE[net_v45](~/includes/net-v45-md.md)], a task that is created with the <see cref="M:System.Threading.Tasks.TaskFactory.FromAsync(System.IAsyncResult,System.Action{System.IAsyncResult},System.Threading.Tasks.TaskCreationOptions)" /> method will not complete if this property is not implemented correctly. See [Application Compatibility in 4.5](/dotnet/framework/migration-guide/application-compatibility-in-the-net-framework-4-5).</para>
+          <para>Most implementers of the <see cref="T:System.IAsyncResult" /> interface will not use this property and should return <see langword="false" />. Beginning with the .NET Framework 4.5, a task that is created with the <see cref="M:System.Threading.Tasks.TaskFactory.FromAsync(System.IAsyncResult,System.Action{System.IAsyncResult},System.Threading.Tasks.TaskCreationOptions)" /> method will not complete if this property is not implemented correctly. See [Application Compatibility in 4.5](/dotnet/framework/migration-guide/application-compatibility-in-the-net-framework-4-5).</para>
         </block>
         <block subset="none" type="usage">
           <para>Use this property to determine if the asynchronous operation completed synchronously. For example, this property can return <see langword="true" /> for an asynchronous I/O operation if the I/O request was small.</para>
diff --git a/xml/System/String.xml b/xml/System/String.xml
index a263b19861c..fde79e46d70 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -187,8 +187,8 @@ For more information about Unicode, UTF-16, code units, code points, and the <xr
 |.NET Framework 2.0|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |.NET Framework 3.5|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
 |.NET Framework 4|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 7|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
-|[!INCLUDE[net_v45](~/includes/net-v45-md.md)] and later on Windows 8 and later Windows operating systems|[The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/)|
+|.NET Framework 4.5 and later on Windows 7|[The Unicode Standard, Version 5.0.0](https://www.unicode.org/versions/Unicode5.0.0)|
+|.NET Framework 4.5 and later on Windows 8 and later Windows operating systems|[The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/)|
 |.NET Core and .NET 5+|Depends on the version of the Unicode Standard supported by the underlying operating system.|
 
 <a name="EmbeddedNulls"></a>

From debd2ad243e01656448dec61af0de697b95c4981 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:22:06 -0800
Subject: [PATCH 038/236] net-v451

---
 xml/System.Diagnostics.Tracing/EventSource.xml | 2 +-
 xml/System.Globalization/CharUnicodeInfo.xml   | 2 +-
 xml/System/Exception.xml                       | 8 ++++----
 xml/System/GC.xml                              | 2 +-
 xml/System/Nullable`1.xml                      | 4 ++--
 xml/System/Object.xml                          | 2 +-
 6 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/xml/System.Diagnostics.Tracing/EventSource.xml b/xml/System.Diagnostics.Tracing/EventSource.xml
index 8e874124e51..46f6e3f87de 100644
--- a/xml/System.Diagnostics.Tracing/EventSource.xml
+++ b/xml/System.Diagnostics.Tracing/EventSource.xml
@@ -59,7 +59,7 @@
   
 -   The concept of a utility event source type has been introduced. This feature enables sharing code across multiple event source types in a project to enable scenarios such as optimized <xref:System.Diagnostics.Tracing.EventSource.WriteEvent%2A> overloads.  
   
- For a version of the <xref:System.Diagnostics.Tracing.EventSource> class that provides features such as channel support you are targeting [!INCLUDE[net_v451](~/includes/net-v451-md.md)] or earlier, see [Microsoft EventSource Library 1.0.16](https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.EventSource).  
+ For a version of the <xref:System.Diagnostics.Tracing.EventSource> class that provides features such as channel support you are targeting .NET Framework 4.5.1 or earlier, see [Microsoft EventSource Library 1.0.16](https://www.nuget.org/packages/Microsoft.Diagnostics.Tracing.EventSource).  
   
    
   
diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 6524a75fef0..2ed61297ade 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -95,7 +95,7 @@ When using this class in your applications, keep in mind the following programmi
 | - | - |
 | .NET Framework 4 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
-| [!INCLUDE[net_v451](~/includes/net-v451-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
+| .NET Framework 4.5.1 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v452](~/includes/net-v452-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v46](~/includes/net-v46-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v461](~/includes/net-v461-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
diff --git a/xml/System/Exception.xml b/xml/System/Exception.xml
index d6a9864c626..7bf777be3a5 100644
--- a/xml/System/Exception.xml
+++ b/xml/System/Exception.xml
@@ -290,8 +290,8 @@ Stack Trace:
  [!code-csharp[System.Exception.Class#3](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.exception.class/cs/example.cs#3)]
  [!code-vb[System.Exception.Class#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.exception.class/vb/example.vb#3)]  
   
-## Windows Runtime and [!INCLUDE[net_v451](~/includes/net-v451-md.md)]  
- In [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] for [!INCLUDE[win8](~/includes/win8-md.md)], some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the [!INCLUDE[net_v451](~/includes/net-v451-md.md)] and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
+## Windows Runtime and .NET Framework 4.5.1  
+ In [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] for [!INCLUDE[win8](~/includes/win8-md.md)], some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
   
    
   
@@ -1096,8 +1096,8 @@ Stack Trace:
   
  The value of the <xref:System.Exception.Message%2A> property is included in the information returned by <xref:System.Exception.ToString%2A>. The <xref:System.Exception.Message%2A> property is set only when creating an <xref:System.Exception>. If no message was supplied to the constructor for the current instance, the system supplies a default message that is formatted using the current system culture.  
   
-## Windows Runtime and [!INCLUDE[net_v451](~/includes/net-v451-md.md)]  
- Starting with the [!INCLUDE[net_v451](~/includes/net-v451-md.md)] and [!INCLUDE[win81](~/includes/win81-md.md)], the fidelity of error messages from exceptions that are propagated from Windows Runtime types and members that are not part of the .NET Framework is improved. In particular, exception messages from Visual C++ component extensions (C++/CX) are now propagated back into .NET Framework <xref:System.Exception> objects.  
+## Windows Runtime and .NET Framework 4.5.1  
+ Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the fidelity of error messages from exceptions that are propagated from Windows Runtime types and members that are not part of the .NET Framework is improved. In particular, exception messages from Visual C++ component extensions (C++/CX) are now propagated back into .NET Framework <xref:System.Exception> objects.  
   
    
   
diff --git a/xml/System/GC.xml b/xml/System/GC.xml
index 3589fbb36e2..d1102995e26 100644
--- a/xml/System/GC.xml
+++ b/xml/System/GC.xml
@@ -387,7 +387,7 @@ If pinned is set to `true`, `T` must not be a reference type or a type that cont
   
  All objects, regardless of how long they have been in memory, are considered for collection; however, objects that are referenced in managed code are not collected. Use this method to force the system to try to reclaim the maximum amount of available memory.  
   
- Starting with the [!INCLUDE[net_v451](~/includes/net-v451-md.md)], you can compact the large object heap (LOH) by setting the <xref:System.Runtime.GCSettings.LargeObjectHeapCompactionMode%2A?displayProperty=nameWithType> property to <xref:System.Runtime.GCLargeObjectHeapCompactionMode.CompactOnce?displayProperty=nameWithType> before calling the <xref:System.GC.Collect%2A> method, as the following example illustrates.  
+ Starting with the .NET Framework 4.5.1, you can compact the large object heap (LOH) by setting the <xref:System.Runtime.GCSettings.LargeObjectHeapCompactionMode%2A?displayProperty=nameWithType> property to <xref:System.Runtime.GCLargeObjectHeapCompactionMode.CompactOnce?displayProperty=nameWithType> before calling the <xref:System.GC.Collect%2A> method, as the following example illustrates.  
   
  [!code-csharp[System.Runtime.GCSettings#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.runtime.gcsettings/cs/lohcompactionmode1.cs#1)]
  [!code-vb[System.Runtime.GCSettings#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.runtime.gcsettings/vb/lohcompactionmode1.vb#1)]  
diff --git a/xml/System/Nullable`1.xml b/xml/System/Nullable`1.xml
index 323a53a40ea..48bcebdddb2 100644
--- a/xml/System/Nullable`1.xml
+++ b/xml/System/Nullable`1.xml
@@ -78,8 +78,8 @@
   
  If the `HasValue` property of a nullable type is `false`, the result of a boxing operation is `null`. Consequently, if a boxed nullable type is passed to a method that expects an object argument, that method must be prepared to handle the case where the argument is `null`. When `null` is unboxed into a nullable type, the common language runtime creates a new <xref:System.Nullable%601> structure and initializes its `HasValue` property to `false`.  
   
-## [!INCLUDE[net_v451](~/includes/net-v451-md.md)] and Windows Runtime Components  
- Starting with the [!INCLUDE[net_v451](~/includes/net-v451-md.md)], you can include a <xref:System.Nullable%601> type as a member of a structure exported in a WinMD library. Previously, this was not supported.  
+## .NET Framework 4.5.1 and Windows Runtime Components  
+ Starting with the .NET Framework 4.5.1, you can include a <xref:System.Nullable%601> type as a member of a structure exported in a WinMD library. Previously, this was not supported.  
   
    
   
diff --git a/xml/System/Object.xml b/xml/System/Object.xml
index 4f262b49ec3..20121edd976 100644
--- a/xml/System/Object.xml
+++ b/xml/System/Object.xml
@@ -1130,7 +1130,7 @@ and the <xref:System.IDisposable> interface. The <xref:System.IDisposable.Dispos
 ## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
  When you call the <xref:System.Object.ToString%2A> method on a class in the [!INCLUDE[wrt](~/includes/wrt-md.md)], it provides the default behavior for classes that don't override <xref:System.Object.ToString%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the [!INCLUDE[wrt](~/includes/wrt-md.md)] don't inherit <xref:System.Object>, and don't always implement a <xref:System.Object.ToString%2A>. However, they always appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides a default behavior for these methods.  
   
- Starting with [!INCLUDE[net_v451](~/includes/net-v451-md.md)], the common language runtime uses [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) on a [!INCLUDE[wrt](~/includes/wrt-md.md)] object before falling back to the default implementation of <xref:System.Object.ToString%2A?displayProperty=nameWithType>.  
+ Starting with .NET Framework 4.5.1, the common language runtime uses [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) on a [!INCLUDE[wrt](~/includes/wrt-md.md)] object before falling back to the default implementation of <xref:System.Object.ToString%2A?displayProperty=nameWithType>.  
   
 > [!NOTE]
 > [!INCLUDE[wrt](~/includes/wrt-md.md)] classes that are written in C# or Visual Basic can override the <xref:System.Object.ToString%2A> method.  

From d9a6e277b3a011a485d446e31b33bd699edd9735 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:26:16 -0800
Subject: [PATCH 039/236] net-v452

---
 xml/System.Globalization/CharUnicodeInfo.xml                  | 2 +-
 .../X509Certificate.xml                                       | 2 +-
 .../X509Certificate2.xml                                      | 2 +-
 .../X509Chain.xml                                             | 2 +-
 .../X509Store.xml                                             | 2 +-
 xml/System.Security.Cryptography/RSA.xml                      | 4 ++--
 6 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 2ed61297ade..967e5ad1cbd 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -96,7 +96,7 @@ When using this class in your applications, keep in mind the following programmi
 | .NET Framework 4 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5.1 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
-| [!INCLUDE[net_v452](~/includes/net-v452-md.md)] | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
+| .NET Framework 4.5.2 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | [!INCLUDE[net_v46](~/includes/net-v46-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v461](~/includes/net-v461-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v462](~/includes/net-v462-md.md)] | [8.0.0](https://www.unicode.org/versions/Unicode8.0.0/) |
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml b/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
index 45ff53c75c3..085ab16f2b1 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
@@ -85,7 +85,7 @@
 > [!IMPORTANT]
 >  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
->  For apps that target the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
+>  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
    
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml b/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
index d6d028ef71a..f7c37d91307 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
@@ -50,7 +50,7 @@
 > [!IMPORTANT]
 >  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
->  For apps that target the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
+>  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
    
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml b/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
index 97ad496359f..029bb5a41c1 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
@@ -52,7 +52,7 @@
 > [!IMPORTANT]
 >  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
->  For apps that target the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
+>  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
    
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Store.xml b/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
index 255acc5d3c7..3a3535eb150 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
@@ -52,7 +52,7 @@
 > [!IMPORTANT]
 >  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
->  For apps that target the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Store> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
+>  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Store> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
    
   
diff --git a/xml/System.Security.Cryptography/RSA.xml b/xml/System.Security.Cryptography/RSA.xml
index 0a793acc0a1..fbed092cffb 100644
--- a/xml/System.Security.Cryptography/RSA.xml
+++ b/xml/System.Security.Cryptography/RSA.xml
@@ -400,7 +400,7 @@ The decryption operation failed.</exception>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions of the .NET Framework, this method was `abstract`. However, the only implementation by a derived class, <xref:System.Security.Cryptography.RSACryptoServiceProvider.DecryptValue%2A?displayProperty=nameWithType>, also threw a <xref:System.NotSupportedException> exception.  
+ In the .NET Framework 4.5.2 and earlier versions of the .NET Framework, this method was `abstract`. However, the only implementation by a derived class, <xref:System.Security.Cryptography.RSACryptoServiceProvider.DecryptValue%2A?displayProperty=nameWithType>, also threw a <xref:System.NotSupportedException> exception.  
   
  ]]></format>
         </remarks>
@@ -515,7 +515,7 @@ The encryption operation failed.</exception>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the [!INCLUDE[net_v452](~/includes/net-v452-md.md)] and earlier versions of the .NET Framework, this method was `abstract`. However, the only implementation by a derived class, <xref:System.Security.Cryptography.RSACryptoServiceProvider.DecryptValue%2A?displayProperty=nameWithType>, also threw a <xref:System.NotSupportedException> exception.  
+ In the .NET Framework 4.5.2 and earlier versions of the .NET Framework, this method was `abstract`. However, the only implementation by a derived class, <xref:System.Security.Cryptography.RSACryptoServiceProvider.DecryptValue%2A?displayProperty=nameWithType>, also threw a <xref:System.NotSupportedException> exception.  
   
  ]]></format>
         </remarks>

From d88b17e1bbe7ea5dfdcd307ff5ed6bb02b96d8d7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:26:54 -0800
Subject: [PATCH 040/236] net-v46

---
 .../ConcurrentDictionary`2.xml                |  2 +-
 .../ConcurrentQueue`1.xml                     |  2 +-
 .../ConcurrentStack`1.xml                     |  2 +-
 xml/System.Collections.Generic/HashSet`1.xml  |  2 +-
 .../EventSource.xml                           |  2 +-
 xml/System.Drawing.Design/UITypeEditor.xml    |  4 +--
 xml/System.Globalization/CharUnicodeInfo.xml  |  2 +-
 xml/System.Globalization/CultureInfo.xml      | 26 +++++++++----------
 xml/System.Globalization/PersianCalendar.xml  |  8 +++---
 .../X509Certificate.xml                       |  8 +++---
 .../X509Certificate2.xml                      |  2 +-
 .../X509Chain.xml                             |  8 +++---
 .../X509Store.xml                             |  4 +--
 xml/System.Security.Cryptography/RSA.xml      |  4 +--
 xml/System.Security.Cryptography/RSACng.xml   |  2 +-
 xml/System.Threading.Tasks/Task.xml           |  2 +-
 .../TaskCreationOptions.xml                   |  2 +-
 xml/System.Threading.Tasks/Task`1.xml         |  2 +-
 xml/System.Threading/Thread.xml               |  2 +-
 xml/System/ArraySegment`1.xml                 |  2 +-
 xml/System/GC.xml                             |  2 +-
 21 files changed, 45 insertions(+), 45 deletions(-)

diff --git a/xml/System.Collections.Concurrent/ConcurrentDictionary`2.xml b/xml/System.Collections.Concurrent/ConcurrentDictionary`2.xml
index 89792b01e06..acbef8ee3b1 100644
--- a/xml/System.Collections.Concurrent/ConcurrentDictionary`2.xml
+++ b/xml/System.Collections.Concurrent/ConcurrentDictionary`2.xml
@@ -101,7 +101,7 @@
  For very large <xref:System.Collections.Concurrent.ConcurrentDictionary%602> objects, you can increase the maximum array size to 2 gigabytes (GB) on a 64-bit system by setting the [`<gcAllowVeryLargeObjects>`](/dotnet/framework/configure-apps/file-schema/runtime/gcallowverylargeobjects-element) configuration element to `true` in the run-time environment.  
   
 > [!NOTE]
->  <xref:System.Collections.Concurrent.ConcurrentDictionary%602> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> and <xref:System.Collections.Generic.IReadOnlyDictionary%602> interfaces starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentDictionary%602> class did not implement these interfaces.  
+>  <xref:System.Collections.Concurrent.ConcurrentDictionary%602> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> and <xref:System.Collections.Generic.IReadOnlyDictionary%602> interfaces starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentDictionary%602> class did not implement these interfaces.  
   
  Like the <xref:System.Collections.Generic.Dictionary%602?displayProperty=nameWithType> class, <xref:System.Collections.Concurrent.ConcurrentDictionary%602> implements the <xref:System.Collections.Generic.IDictionary%602> interface. In addition, <xref:System.Collections.Concurrent.ConcurrentDictionary%602> provides several methods for adding or updating key/value pairs in the dictionary, as described in the following table.  
   
diff --git a/xml/System.Collections.Concurrent/ConcurrentQueue`1.xml b/xml/System.Collections.Concurrent/ConcurrentQueue`1.xml
index fe58399bbb4..8b5f35a6ea1 100644
--- a/xml/System.Collections.Concurrent/ConcurrentQueue`1.xml
+++ b/xml/System.Collections.Concurrent/ConcurrentQueue`1.xml
@@ -91,7 +91,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Collections.Concurrent.ConcurrentQueue%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentQueue%601> class did not implement this interface.  
+>  <xref:System.Collections.Concurrent.ConcurrentQueue%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentQueue%601> class did not implement this interface.  
   
    
   
diff --git a/xml/System.Collections.Concurrent/ConcurrentStack`1.xml b/xml/System.Collections.Concurrent/ConcurrentStack`1.xml
index 334479e4f24..42631fd6ce4 100644
--- a/xml/System.Collections.Concurrent/ConcurrentStack`1.xml
+++ b/xml/System.Collections.Concurrent/ConcurrentStack`1.xml
@@ -87,7 +87,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Collections.Concurrent.ConcurrentStack%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentStack%601> class did not implement this interface.  
+>  <xref:System.Collections.Concurrent.ConcurrentStack%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Collections.Concurrent.ConcurrentStack%601> class did not implement this interface.  
   
  <xref:System.Collections.Concurrent.ConcurrentStack%601> provides a few main operations:  
   
diff --git a/xml/System.Collections.Generic/HashSet`1.xml b/xml/System.Collections.Generic/HashSet`1.xml
index 40f0c2146e0..5384571fa3e 100644
--- a/xml/System.Collections.Generic/HashSet`1.xml
+++ b/xml/System.Collections.Generic/HashSet`1.xml
@@ -113,7 +113,7 @@
  The <xref:System.Collections.Generic.HashSet%601> class provides high-performance set operations. A set is a collection that contains no duplicate elements, and whose elements are in no particular order.  
   
 > [!NOTE]
->  <xref:System.Collections.Generic.HashSet%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Collections.Generic.HashSet%601> class did not implement this interface.  
+>  <xref:System.Collections.Generic.HashSet%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Collections.Generic.HashSet%601> class did not implement this interface.  
   
  The capacity of a <xref:System.Collections.Generic.HashSet%601> object is the number of elements that the object can hold. A <xref:System.Collections.Generic.HashSet%601> object's capacity automatically increases as elements are added to the object.  
   
diff --git a/xml/System.Diagnostics.Tracing/EventSource.xml b/xml/System.Diagnostics.Tracing/EventSource.xml
index 46f6e3f87de..76bdc8aae9c 100644
--- a/xml/System.Diagnostics.Tracing/EventSource.xml
+++ b/xml/System.Diagnostics.Tracing/EventSource.xml
@@ -53,7 +53,7 @@
   
  The basic functionality of <xref:System.Diagnostics.Tracing.EventSource> is sufficient for most applications.  If you want more control over the ETW manifest that is created, you can apply the <xref:System.Diagnostics.Tracing.EventAttribute> attribute to the methods. For advanced event source applications, it is possible to intercept the commands being sent to the derived event source and change the filtering, or to cause actions (such as dumping a data structure) to be performed by the inheritor.  An event source can be activated with Windows ETW controllers, such as the Logman tool, immediately.  It is also possible to programmatically control and intercept the data dispatcher.  The <xref:System.Diagnostics.Tracing.EventListener> class provides additional functionality.  
   
- Starting with [!INCLUDE[net_v46](~/includes/net-v46-md.md)], <xref:System.Diagnostics.Tracing.EventSource> provides channel support and some of the event source validation rules have been relaxed. This means:  
+ Starting with .NET Framework 4.6, <xref:System.Diagnostics.Tracing.EventSource> provides channel support and some of the event source validation rules have been relaxed. This means:  
   
 -   <xref:System.Diagnostics.Tracing.EventSource> types may now implement interfaces. This enables the use of event source types in advanced logging systems that use interfaces to define a common logging target.  
   
diff --git a/xml/System.Drawing.Design/UITypeEditor.xml b/xml/System.Drawing.Design/UITypeEditor.xml
index 85594e0bd15..f930ef680e1 100644
--- a/xml/System.Drawing.Design/UITypeEditor.xml
+++ b/xml/System.Drawing.Design/UITypeEditor.xml
@@ -439,7 +439,7 @@
 ## Remarks  
  Editors should paint within the boundaries of the specified rectangle. This rectangle indicates the area of the Properties window to draw a representation of the value within.  
   
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the rectangle specified by <xref:System.Drawing.Design.PaintValueEventArgs.Bounds%2A> will be resized based on the system DPI setting when the app.config file contains the following entry:  
+ Starting with the .NET Framework 4.6, the rectangle specified by <xref:System.Drawing.Design.PaintValueEventArgs.Bounds%2A> will be resized based on the system DPI setting when the app.config file contains the following entry:  
   
 ```  
 <appSettings>  
@@ -491,7 +491,7 @@
 ## Remarks  
  Editors should paint within the boundaries of the specified rectangle. This rectangle indicates the area of the Properties window to draw a representation of the value within.  
   
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the rectangle specified by <xref:System.Drawing.Design.PaintValueEventArgs.Bounds%2A> will be resized based on the system DPI setting when the app.config file contains the following entry:  
+ Starting with the .NET Framework 4.6, the rectangle specified by <xref:System.Drawing.Design.PaintValueEventArgs.Bounds%2A> will be resized based on the system DPI setting when the app.config file contains the following entry:  
   
 ```  
 <appSettings>  
diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 967e5ad1cbd..7b90ac96137 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -97,7 +97,7 @@ When using this class in your applications, keep in mind the following programmi
 | .NET Framework 4.5 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5.1 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5.2 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
-| [!INCLUDE[net_v46](~/includes/net-v46-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
+| .NET Framework 4.6 | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v461](~/includes/net-v461-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v462](~/includes/net-v462-md.md)] | [8.0.0](https://www.unicode.org/versions/Unicode8.0.0/) |
 
diff --git a/xml/System.Globalization/CultureInfo.xml b/xml/System.Globalization/CultureInfo.xml
index ec0a541f371..c400014208a 100644
--- a/xml/System.Globalization/CultureInfo.xml
+++ b/xml/System.Globalization/CultureInfo.xml
@@ -287,9 +287,9 @@ Some `CultureInfo` objects differ depending on the underlying platform. In parti
 ## Culture and task-based asynchronous operations  
  The [task-based asynchronous programming pattern](/dotnet/standard/parallel-programming/task-based-asynchronous-programming) uses <xref:System.Threading.Tasks.Task> and <xref:System.Threading.Tasks.Task%601> objects to asynchronously execute delegates on thread pool threads. The specific thread on which a particular task runs is not known in advance, but is determined only at runtime.  
   
- For apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] or later versions, culture is part of an asynchronous operation's context. In other words, starting with apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], asynchronous operations by default inherit the values of the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> and <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> properties of the thread from which they are launched. If the current culture or current UI culture differs from the system culture, the current culture crosses thread boundaries and becomes the current culture of the thread pool thread that is executing an asynchronous operation.  
+ For apps that target the .NET Framework 4.6 or later versions, culture is part of an asynchronous operation's context. In other words, starting with apps that target the .NET Framework 4.6, asynchronous operations by default inherit the values of the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> and <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> properties of the thread from which they are launched. If the current culture or current UI culture differs from the system culture, the current culture crosses thread boundaries and becomes the current culture of the thread pool thread that is executing an asynchronous operation.  
   
- The following example provides a simple illustration. It uses the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute to target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]. The example defines a <xref:System.Func%601> delegate, `formatDelegate`, that returns some numbers formatted as currency values. The example changes the current system culture to either French (France) or, if French (France) is already the current culture, English (United States). It then:  
+ The following example provides a simple illustration. It uses the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute to target the .NET Framework 4.6. The example defines a <xref:System.Func%601> delegate, `formatDelegate`, that returns some numbers formatted as currency values. The example changes the current system culture to either French (France) or, if French (France) is already the current culture, English (United States). It then:  
   
 -   Invokes the delegate directly so that it runs synchronously on the main app thread.  
   
@@ -302,17 +302,17 @@ Some `CultureInfo` objects differ depending on the underlying platform. In parti
  [!code-csharp[System.Globalization.CultureInfo.Class.Async#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/cs/asyncculture1.cs#1)]
  [!code-vb[System.Globalization.CultureInfo.Class.Async#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/vb/asyncculture1.vb#1)]  
   
- For apps that target versions of the .NET Framework prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], or for apps that do not target a particular version of the .NET Framework, the culture of the calling thread is not part of a task's context. Instead, unless one is explicitly defined, the culture of new threads by default is the system culture. The following example, which is identical to the previous example except that it lacks the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute, illustrates this. Because the system culture of the system on which the example executed was English (United States), the culture of the task that executes asynchronously on a thread pool thread is en-US rather than fr-FR.  
+ For apps that target versions of the .NET Framework prior to the .NET Framework 4.6, or for apps that do not target a particular version of the .NET Framework, the culture of the calling thread is not part of a task's context. Instead, unless one is explicitly defined, the culture of new threads by default is the system culture. The following example, which is identical to the previous example except that it lacks the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute, illustrates this. Because the system culture of the system on which the example executed was English (United States), the culture of the task that executes asynchronously on a thread pool thread is en-US rather than fr-FR.  
   
  [!code-csharp[System.Globalization.CultureInfo.Class.Async#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/cs/asyncculture2.cs#2)]
  [!code-vb[System.Globalization.CultureInfo.Class.Async#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/vb/asyncculture2.vb#2)]  
   
- For apps that target versions of the .NET Framework from the .NET Framework 4.5 and later but prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], you can use the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties to ensure that the culture of the calling thread is used in asynchronous tasks that execute on thread pool threads. The following example is identical to the previous example, except that it uses the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to ensure that thread pool threads have the same culture as the main app thread.  
+ For apps that target versions of the .NET Framework from the .NET Framework 4.5 and later but prior to the .NET Framework 4.6, you can use the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> properties to ensure that the culture of the calling thread is used in asynchronous tasks that execute on thread pool threads. The following example is identical to the previous example, except that it uses the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property to ensure that thread pool threads have the same culture as the main app thread.  
   
  [!code-csharp[System.Globalization.CultureInfo.Class.Async#3](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/cs/asyncculture3.cs#3)]
  [!code-vb[System.Globalization.CultureInfo.Class.Async#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.class.async/vb/asyncculture3.vb#3)]  
   
- <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> are per-app domain properties; that is, they establish a default culture for all threads not explicitly assigned a culture in a specific application domain. However, for apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] or later, the culture of the calling thread remains part of an asynchronous task's context even if the task crosses app domain boundaries.  
+ <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> and <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> are per-app domain properties; that is, they establish a default culture for all threads not explicitly assigned a culture in a specific application domain. However, for apps that target the .NET Framework 4.6 or later, the culture of the calling thread remains part of an asynchronous task's context even if the task crosses app domain boundaries.  
   
  The following example shows that the calling thread's culture remains the current culture of a task-based asynchronous operation even if the method that the task is executing crosses application domain boundaries. It defines a class, `DataRetriever`, with a single method, `GetFormattedNumber`, that returns a random double-precision floating-point number between 1 and 1,000 formatted as a currency value. A first task is run that simply instantiates a `DataRetriever` instance and calls its `GetFormattedNumber` method. A second task reports its current application domain, creates a new application domain, instantiates a `DataRetriever` instance in the new application domain, and calls its `GetFormattedNumber` method. As the output from the example shows, the current culture has remained the same in the calling thread, the first task, and the second task both when it was executing in the main application domain and the second application domain.  
   
@@ -1186,7 +1186,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
  The current culture is a property of the executing thread. Retrieving the value of the <xref:System.Globalization.CultureInfo.CurrentCulture%2A?displayProperty=nameWithType> property is a more performant equivalent of retrieving the <xref:System.Globalization.CultureInfo> object returned by the `Thread.CurrentThread.CurrentCulture` property.
   
 > [!NOTE]
->  In the .NET Framework 4.5.2 and earlier versions, the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> property is read-only;  that is, you can retrieve the property value, but you cannot set it. To change the current culture, you assign the <xref:System.Globalization.CultureInfo> object that represents the new culture to the `Thread.CurrentThread.CurrentCulture` property. Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> property is read-write; you can both set and retrieve the property's value. If you do set the property value to a <xref:System.Globalization.CultureInfo> object that represents a new culture, the value of the `Thread.CurrentThread.CurrentCulture` property also changes.  
+>  In the .NET Framework 4.5.2 and earlier versions, the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> property is read-only;  that is, you can retrieve the property value, but you cannot set it. To change the current culture, you assign the <xref:System.Globalization.CultureInfo> object that represents the new culture to the `Thread.CurrentThread.CurrentCulture` property. Starting with the .NET Framework 4.6, the <xref:System.Globalization.CultureInfo.CurrentCulture%2A> property is read-write; you can both set and retrieve the property's value. If you do set the property value to a <xref:System.Globalization.CultureInfo> object that represents a new culture, the value of the `Thread.CurrentThread.CurrentCulture` property also changes.  
   
  In this section:  
   
@@ -1202,7 +1202,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
   
 -   By retrieving the culture that is specified by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentCulture%2A> property in the application domain in which the thread is executing, if the property value is not `null`.  
   
--   If the thread is a thread pool thread that is executing a task-based asynchronous operation and the app targets the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] or a later version of the .NET Framework, its culture is determined by the culture of the calling thread.  The following example changes the current culture to Portuguese (Brazil) and launches six tasks, each of which displays its thread ID, its task ID, and its current culture. Each of the tasks (and the threads) has inherited the culture of the calling thread.  
+-   If the thread is a thread pool thread that is executing a task-based asynchronous operation and the app targets the .NET Framework 4.6 or a later version of the .NET Framework, its culture is determined by the culture of the calling thread.  The following example changes the current culture to Portuguese (Brazil) and launches six tasks, each of which displays its thread ID, its task ID, and its current culture. Each of the tasks (and the threads) has inherited the culture of the calling thread.  
   
      [!code-csharp[System.Globalization.CultureInfo.CurrentCulture#14](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/cs/Async1.cs#14)]
      [!code-vb[System.Globalization.CultureInfo.CurrentCulture#14](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/vb/Async1.vb#14)]  
@@ -1226,7 +1226,7 @@ If `name` is <xref:System.String.Empty?displayProperty=nameWithType>, the constr
   
 <a name="ExplicitSetting"></a>   
 ## Explicitly Setting the CurrentCulture Property  
- Staring with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], to change the culture that is used by an existing thread, you set the <xref:System.Globalization.CultureInfo.CurrentCulture%2A?displayProperty=nameWithType> property to the new culture. If you explicitly change a thread's culture in this way, that change persists if the thread crosses application domain boundaries. The following example changes the current thread culture to Dutch (Netherlands). It also shows that, when the current thread crosses application domain boundaries, its current culture remains changed.  
+ Staring with the .NET Framework 4.6, to change the culture that is used by an existing thread, you set the <xref:System.Globalization.CultureInfo.CurrentCulture%2A?displayProperty=nameWithType> property to the new culture. If you explicitly change a thread's culture in this way, that change persists if the thread crosses application domain boundaries. The following example changes the current thread culture to Dutch (Netherlands). It also shows that, when the current thread crosses application domain boundaries, its current culture remains changed.  
   
  [!code-csharp[System.Globalization.CultureInfo.CurrentCulture#11](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/cs/changeculture11.cs#11)]
  [!code-vb[System.Globalization.CultureInfo.CurrentCulture#11](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentculture/vb/changeculture11.vb#11)]  
@@ -1340,11 +1340,11 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The current UI culture is a per-thread property. That is, each thread has its own current UI culture. This property is equivalent to retrieving or, starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], setting the <xref:System.Globalization.CultureInfo> object assigned to the  `System.Threading.Thread.CurrentThread.CurrentUICulture` property. When a thread is started, its UI culture is initially determined as follows:  
+ The current UI culture is a per-thread property. That is, each thread has its own current UI culture. This property is equivalent to retrieving or, starting with the .NET Framework 4.6, setting the <xref:System.Globalization.CultureInfo> object assigned to the  `System.Threading.Thread.CurrentThread.CurrentUICulture` property. When a thread is started, its UI culture is initially determined as follows:  
   
 -   By retrieving the culture that is specified by the <xref:System.Globalization.CultureInfo.DefaultThreadCurrentUICulture%2A> property in the application domain in which the thread is executing, if the property value is not `null`.  
   
--   If the thread is a thread pool thread that is executing a task-based asynchronous operation and the app targets the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] or a later version of the .NET Framework, its UI culture is determined by the UI culture of the calling thread.  The following example changes the current UI culture to Portuguese (Brazil) and launches six tasks, each of which displays its thread ID, its task ID, and its current UI culture. Each of the tasks (and the threads) has inherited the UI culture of the calling thread.  
+-   If the thread is a thread pool thread that is executing a task-based asynchronous operation and the app targets the .NET Framework 4.6 or a later version of the .NET Framework, its UI culture is determined by the UI culture of the calling thread.  The following example changes the current UI culture to Portuguese (Brazil) and launches six tasks, each of which displays its thread ID, its task ID, and its current UI culture. Each of the tasks (and the threads) has inherited the UI culture of the calling thread.  
   
      [!code-csharp[System.Globalization.CultureInfo.CurrentUICulture#14](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentuiculture/cs/Async1.cs#14)]
      [!code-vb[System.Globalization.CultureInfo.CurrentUICulture#14](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentuiculture/vb/Async1.vb#14)]  
@@ -1356,10 +1356,10 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
 > [!NOTE]
 >  In the .NET Compact Framework, the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property is read-only. The current UI culture is determined by the system's regional settings and cannot be changed programmatically.  
   
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], to change the user interface culture used by a thread, set the <xref:System.Threading.Thread.CurrentUICulture%2A?displayProperty=nameWithType> property to the new culture. If you explicitly change a thread's UI culture in this way, that change persists if the thread crosses application domain boundaries.  
+ Starting with the .NET Framework 4.6, to change the user interface culture used by a thread, set the <xref:System.Threading.Thread.CurrentUICulture%2A?displayProperty=nameWithType> property to the new culture. If you explicitly change a thread's UI culture in this way, that change persists if the thread crosses application domain boundaries.  
   
 > [!NOTE]
->  In the .NET Framework 4.5.2 and earlier versions, the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property is read-only;  that is, you can retrieve the property value, but you cannot set it. To change the current UI culture, you assign the <xref:System.Globalization.CultureInfo> object that represents the new UI culture to the `Thread.CurrentThread.CurrentUICulture` property. Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A?displayProperty=nameWithType> property is read-write; you can both set and retrieve the property's value. If you do set the property value to a <xref:System.Globalization.CultureInfo> object that represents a new culture, the value of the `Thread.CurrentThread.CurrentCulture` property also changes.  
+>  In the .NET Framework 4.5.2 and earlier versions, the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property is read-only;  that is, you can retrieve the property value, but you cannot set it. To change the current UI culture, you assign the <xref:System.Globalization.CultureInfo> object that represents the new UI culture to the `Thread.CurrentThread.CurrentUICulture` property. Starting with the .NET Framework 4.6, the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A?displayProperty=nameWithType> property is read-write; you can both set and retrieve the property's value. If you do set the property value to a <xref:System.Globalization.CultureInfo> object that represents a new culture, the value of the `Thread.CurrentThread.CurrentCulture` property also changes.  
   
  In this section:  
   
@@ -1380,7 +1380,7 @@ In .NET Framework and .NET Core apps, the current culture is a per-thread settin
   
 <a name="Explicit"></a>   
 ## Explicitly Setting the Current UI Culture  
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], you can change the current UI culture by assigning a <xref:System.Globalization.CultureInfo> object that represents the new culture to the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A?displayProperty=nameWithType> property. The current UI culture can be set to either a specific culture (such as en-US or de-DE) or to a neutral culture (such as en or de). The following example sets the current UI culture to fr-FR or French (France).  
+ Starting with the .NET Framework 4.6, you can change the current UI culture by assigning a <xref:System.Globalization.CultureInfo> object that represents the new culture to the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A?displayProperty=nameWithType> property. The current UI culture can be set to either a specific culture (such as en-US or de-DE) or to a neutral culture (such as en or de). The following example sets the current UI culture to fr-FR or French (France).  
   
  [!code-csharp[System.Globalization.CultureInfo.CurrentUICulture#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentuiculture/cs/currentuiculture1.cs#1)]
  [!code-vb[System.Globalization.CultureInfo.CurrentUICulture#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.globalization.cultureinfo.currentuiculture/vb/currentuiculture1.vb#1)]  
diff --git a/xml/System.Globalization/PersianCalendar.xml b/xml/System.Globalization/PersianCalendar.xml
index 30b08003f51..aa989362dbc 100644
--- a/xml/System.Globalization/PersianCalendar.xml
+++ b/xml/System.Globalization/PersianCalendar.xml
@@ -65,7 +65,7 @@
  Each of the first six months in the Persian calendar has 31 days, each of the next five months has 30 days, and the last month has 29 days in a common year and 30 days in a leap year. A leap year is a year that, when divided by 33, has a remainder of 1, 5, 9, 13, 17, 22, 26, or 30. For example, the year 1370 is a leap year because dividing it by 33 yields a remainder of 17. There are approximately eight leap years in every 33-year cycle.  
   
 ## The PersianCalendar class and .NET Framework versions  
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the <xref:System.Globalization.PersianCalendar> class uses the Hijri solar astronomical algorithm rather than an observational algorithm to calculate dates. This makes the <xref:System.Globalization.PersianCalendar> implementation consistent with the Persian calendar in use in Iran and Afghanistan, the two countries in which the Persian calendar is in most widespread use. The change affects all apps running on the .NET Framework 4 or later if the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] is installed.  
+ Starting with the .NET Framework 4.6, the <xref:System.Globalization.PersianCalendar> class uses the Hijri solar astronomical algorithm rather than an observational algorithm to calculate dates. This makes the <xref:System.Globalization.PersianCalendar> implementation consistent with the Persian calendar in use in Iran and Afghanistan, the two countries in which the Persian calendar is in most widespread use. The change affects all apps running on the .NET Framework 4 or later if the .NET Framework 4.6 is installed.  
   
  As a result of the changed algorithm:  
   
@@ -1166,7 +1166,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the implementation of the <xref:System.Globalization.PersianCalendar> class has changed from an observational algorithm to the Hijri solar algorithm. As a result, the <xref:System.Globalization.PersianCalendar.IsLeapYear%2A> method may return different values when run on [!INCLUDE[net_v46](~/includes/net-v46-md.md)] than when run on previous versions of the .NET Framework.  
+ Starting with the .NET Framework 4.6, the implementation of the <xref:System.Globalization.PersianCalendar> class has changed from an observational algorithm to the Hijri solar algorithm. As a result, the <xref:System.Globalization.PersianCalendar.IsLeapYear%2A> method may return different values when run on .NET Framework 4.6 than when run on previous versions of the .NET Framework.  
   
    
   
@@ -1227,7 +1227,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value of the <xref:System.Globalization.PersianCalendar.MaxSupportedDateTime%2A> property is the last moment of December 31, 9999 C.E. in the Gregorian calendar. In the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this value is equivalent to the 13th day of the 10th month of the year 9378 in the Persian calendar. In previous versions of the .NET Framework, it is equivalent to the 10th day of the 10th month of the year 9378 in the Persian calendar. For more information, see "The PersianCalendar class and .NET Framework versions" in the <xref:System.Globalization.PersianCalendar> topic.  
+ The value of the <xref:System.Globalization.PersianCalendar.MaxSupportedDateTime%2A> property is the last moment of December 31, 9999 C.E. in the Gregorian calendar. In the .NET Framework 4.6, this value is equivalent to the 13th day of the 10th month of the year 9378 in the Persian calendar. In previous versions of the .NET Framework, it is equivalent to the 10th day of the 10th month of the year 9378 in the Persian calendar. For more information, see "The PersianCalendar class and .NET Framework versions" in the <xref:System.Globalization.PersianCalendar> topic.  
   
  9999 C.E. is equivalent to the year 9378 in the Persian calendar.  
   
@@ -1285,7 +1285,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the value of the <xref:System.Globalization.PersianCalendar.MinSupportedDateTime%2A> property is equivalent to the first moment of March 22, 622 C.E. in the Gregorian calendar. In previous versions of the .NET Framework, it is equivalent to the first moment of March 21, 622 C.E. in the Gregorian calendar. For more information, see "The PersianCalendar class and .NET Framework versions" in the <xref:System.Globalization.PersianCalendar> topic.  
+ Starting with the .NET Framework 4.6, the value of the <xref:System.Globalization.PersianCalendar.MinSupportedDateTime%2A> property is equivalent to the first moment of March 22, 622 C.E. in the Gregorian calendar. In previous versions of the .NET Framework, it is equivalent to the first moment of March 21, 622 C.E. in the Gregorian calendar. For more information, see "The PersianCalendar class and .NET Framework versions" in the <xref:System.Globalization.PersianCalendar> topic.  
   
  622 C.E. is equivalent to the year 0001 in the Persian calendar.  
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml b/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
index 085ab16f2b1..b7cc0f241c3 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Certificate.xml
@@ -83,7 +83,7 @@
  For most scenarios, you should use the <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> class instead.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
+>  Starting with the .NET Framework 4.6, this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
 >  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
@@ -1117,7 +1117,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
@@ -1165,7 +1165,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
@@ -1220,7 +1220,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Certificate> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml b/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
index f7c37d91307..69088567d47 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml
@@ -48,7 +48,7 @@
  The X.509 structure originated in the International Organization for Standardization (ISO) working groups. This structure can be used to represent various types of information including identity, entitlement, and holder attributes (permissions, age, sex, location, affiliation, and so forth). Although the ISO specifications are most informative on the structure itself, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> class is designed to model the usage scenarios defined in specifications issued by the Internet Engineering Task Force (IETF) Public Key Infrastructure, X.509 (PKIX) working group. The most informative of these specifications is RFC 3280, "[Certificate and Certificate Revocation List (CRL) Profile](https://go.microsoft.com/fwlink/?LinkId=45286)."  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
+>  Starting with the .NET Framework 4.6, this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
 >  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Certificate2> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml b/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
index 029bb5a41c1..e73f09f594f 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Chain.xml
@@ -50,7 +50,7 @@
  The <xref:System.Security.Cryptography.X509Certificates.X509Chain> object has a global error status called <xref:System.Security.Cryptography.X509Certificates.X509Chain.ChainStatus%2A> that should be used for certificate validation. The rules governing certificate validation are complex, and it is easy to oversimplify the validation logic by ignoring the error status of one or more of the elements involved. The global error status takes into consideration the status of each element in the chain.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
+>  Starting with the .NET Framework 4.6, this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
 >  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
@@ -574,7 +574,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
@@ -628,7 +628,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
@@ -683,7 +683,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Chain> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Chain> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509Store.xml b/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
index 3a3535eb150..b5ecd910731 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509Store.xml
@@ -50,7 +50,7 @@
  Use this class to work with an X.509 store.  
   
 > [!IMPORTANT]
->  Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
+>  Starting with the .NET Framework 4.6, this type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
 >   
 >  For apps that target the .NET Framework 4.5.2 and earlier versions, the <xref:System.Security.Cryptography.X509Certificates.X509Store> class does not implement the <xref:System.IDisposable> interface and therefore does not have a `Dispose` method.  
   
@@ -837,7 +837,7 @@
 ## Remarks  
   
 > [!NOTE]
->  <xref:System.Security.Cryptography.X509Certificates.X509Store> implements the <xref:System.IDisposable> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Store> class does not implement this interface, and therefore the `Dispose` method does not exist.  
+>  <xref:System.Security.Cryptography.X509Certificates.X509Store> implements the <xref:System.IDisposable> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.Security.Cryptography.X509Certificates.X509Store> class does not implement this interface, and therefore the `Dispose` method does not exist.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Security.Cryptography/RSA.xml b/xml/System.Security.Cryptography/RSA.xml
index fbed092cffb..16240e55408 100644
--- a/xml/System.Security.Cryptography/RSA.xml
+++ b/xml/System.Security.Cryptography/RSA.xml
@@ -404,7 +404,7 @@ The decryption operation failed.</exception>
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method call is not supported. This exception is thrown starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)].</exception>
+        <exception cref="T:System.NotSupportedException">This method call is not supported. This exception is thrown starting with the .NET Framework 4.6.</exception>
         <altmember cref="M:System.Security.Cryptography.RSA.Decrypt(System.Byte[],System.Security.Cryptography.RSAEncryptionPadding)" />
         <related type="Article" href="/dotnet/standard/security/cryptographic-services">Cryptographic Services</related>
       </Docs>
@@ -519,7 +519,7 @@ The encryption operation failed.</exception>
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.NotSupportedException">This method call is not supported. This exception is thrown starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)].</exception>
+        <exception cref="T:System.NotSupportedException">This method call is not supported. This exception is thrown starting with the .NET Framework 4.6.</exception>
         <altmember cref="M:System.Security.Cryptography.RSA.Encrypt(System.Byte[],System.Security.Cryptography.RSAEncryptionPadding)" />
         <related type="Article" href="/dotnet/standard/security/cryptographic-services">Cryptographic Services</related>
       </Docs>
diff --git a/xml/System.Security.Cryptography/RSACng.xml b/xml/System.Security.Cryptography/RSACng.xml
index 85fe4061371..20c8b273c3b 100644
--- a/xml/System.Security.Cryptography/RSACng.xml
+++ b/xml/System.Security.Cryptography/RSACng.xml
@@ -843,7 +843,7 @@ any already open key is unaffected by this method.
   
  -or-  
   
- The signature is badly formatted. (In the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] and 4.6.1 only; starting with the [!INCLUDE[net_v462](~/includes/net-v462-md.md)], the method returns <see langword="false" /> if a signature is badly formatted.</exception>
+ The signature is badly formatted. (In the .NET Framework 4.6 and 4.6.1 only; starting with the [!INCLUDE[net_v462](~/includes/net-v462-md.md)], the method returns <see langword="false" /> if a signature is badly formatted.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Threading.Tasks/Task.xml b/xml/System.Threading.Tasks/Task.xml
index 300c7ab28bc..8e3b19fe2f2 100644
--- a/xml/System.Threading.Tasks/Task.xml
+++ b/xml/System.Threading.Tasks/Task.xml
@@ -154,7 +154,7 @@
   
 <a name="Culture"></a>   
 ## Tasks and culture  
- Starting with desktop apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the culture of the thread that creates and invokes a task becomes part of the thread's context. That is, regardless of the current culture of the thread on which the task executes, the current culture of the task is the culture of the calling thread. For apps that target versions of the .NET Framework prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the culture of the task is the culture of the thread on which the task executes. For more information, see the "Culture and task-based asynchronous operations" section in the <xref:System.Globalization.CultureInfo> topic.  
+ Starting with desktop apps that target the .NET Framework 4.6, the culture of the thread that creates and invokes a task becomes part of the thread's context. That is, regardless of the current culture of the thread on which the task executes, the current culture of the task is the culture of the calling thread. For apps that target versions of the .NET Framework prior to the .NET Framework 4.6, the culture of the task is the culture of the thread on which the task executes. For more information, see the "Culture and task-based asynchronous operations" section in the <xref:System.Globalization.CultureInfo> topic.  
   
 > [!NOTE]
 >  Store apps follow the Windows Runtime in setting and getting the default culture.  
diff --git a/xml/System.Threading.Tasks/TaskCreationOptions.xml b/xml/System.Threading.Tasks/TaskCreationOptions.xml
index e925d79a8be..7d0ca12fd33 100644
--- a/xml/System.Threading.Tasks/TaskCreationOptions.xml
+++ b/xml/System.Threading.Tasks/TaskCreationOptions.xml
@@ -341,7 +341,7 @@
       <Docs>
         <summary>Forces continuations added to the current task to be executed asynchronously.  
   
- Note that the <see cref="F:System.Threading.Tasks.TaskCreationOptions.RunContinuationsAsynchronously" /> member is available in the <see cref="T:System.Threading.Tasks.TaskCreationOptions" /> enumeration starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)].</summary>
+ Note that the <see cref="F:System.Threading.Tasks.TaskCreationOptions.RunContinuationsAsynchronously" /> member is available in the <see cref="T:System.Threading.Tasks.TaskCreationOptions" /> enumeration starting with the .NET Framework 4.6.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Threading.Tasks/Task`1.xml b/xml/System.Threading.Tasks/Task`1.xml
index f9232d97694..09f9bed2c15 100644
--- a/xml/System.Threading.Tasks/Task`1.xml
+++ b/xml/System.Threading.Tasks/Task`1.xml
@@ -76,7 +76,7 @@
   
  The <xref:System.Threading.Tasks.Task%601> class also provides constructors that initialize the task but that do not schedule it for execution. For performance reasons, the <xref:System.Threading.Tasks.Task.Run%2A?displayProperty=nameWithType> and `Task.Factory.StartNew` methods are the preferred mechanisms for creating and scheduling computational tasks, but for scenarios where task creation and scheduling must be separated, the constructors may be used, and the task's <xref:System.Threading.Tasks.Task.Start%2A> method may then be used to schedule the task for execution at a later time.  
   
- Starting with desktop apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the culture of the thread that creates and invokes a task becomes part of the thread's context. That is, regardless of the current culture of the thread on which the task executes, the current culture of the task is the culture of the calling thread. For apps that target versions of the .NET Framework prior to the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the culture of the task is the culture of the thread on which the task executes. For more information, see the "Culture and task-based asynchronous operations" section in the <xref:System.Globalization.CultureInfo> topic. Note that Store apps follow the Windows Runtime in setting and getting the default culture.  
+ Starting with desktop apps that target the .NET Framework 4.6, the culture of the thread that creates and invokes a task becomes part of the thread's context. That is, regardless of the current culture of the thread on which the task executes, the current culture of the task is the culture of the calling thread. For apps that target versions of the .NET Framework prior to the .NET Framework 4.6, the culture of the task is the culture of the thread on which the task executes. For more information, see the "Culture and task-based asynchronous operations" section in the <xref:System.Globalization.CultureInfo> topic. Note that Store apps follow the Windows Runtime in setting and getting the default culture.  
   
 For operations that do not return a value, you use the <xref:System.Threading.Tasks.Task> class. Starting with C# 7.0, for a more lightweight task that is a value type rather than a reference type, use the <xref:System.Threading.Tasks.ValueTask%601?displayProperty=nameWithType> structure. 
   
diff --git a/xml/System.Threading/Thread.xml b/xml/System.Threading/Thread.xml
index 222f249143d..ab32c6e4237 100644
--- a/xml/System.Threading/Thread.xml
+++ b/xml/System.Threading/Thread.xml
@@ -169,7 +169,7 @@
  When a new thread is instantiated, its culture and UI culture are defined by the current system culture and UI culture, and not by the culture and UI culture of the thread from which the new thread is created. This means, for example, that if the current system culture is English (United States) and the current culture of the primary application thread is French (France), the culture of a new thread created by calling the   <xref:System.Threading.Thread.%23ctor%28System.Threading.ParameterizedThreadStart%29> constructor from the primary thread is English (United States), and not French (France). For more information, see the "Culture and threads" section of the <xref:System.Globalization.CultureInfo> class topic.  
   
 > [!IMPORTANT]
-> This is not true of threads that execute asynchronous operations for apps that target the [!INCLUDE[net_v46](~/includes/net-v46-md.md)] and later versions, In this case, the culture and UI culture is part of an asynchronous operations' context; the thread on which an asynchronous operation executes by default inherits the culture and UI culture of the thread from which the asynchronous operation was launched. For more information, see the "Culture and task-based asynchronous operations" section of the <xref:System.Globalization.CultureInfo> class topic.  
+> This is not true of threads that execute asynchronous operations for apps that target the .NET Framework 4.6 and later versions, In this case, the culture and UI culture is part of an asynchronous operations' context; the thread on which an asynchronous operation executes by default inherits the culture and UI culture of the thread from which the asynchronous operation was launched. For more information, see the "Culture and task-based asynchronous operations" section of the <xref:System.Globalization.CultureInfo> class topic.  
   
  You can do either of the following to ensure that all of the threads executing in an application share the same culture and UI culture:  
   
diff --git a/xml/System/ArraySegment`1.xml b/xml/System/ArraySegment`1.xml
index f7976f0d29e..5a1f72bef04 100644
--- a/xml/System/ArraySegment`1.xml
+++ b/xml/System/ArraySegment`1.xml
@@ -86,7 +86,7 @@
  <xref:System.ArraySegment%601> is a wrapper around an array that delimits a range of elements in that array. Multiple <xref:System.ArraySegment%601> instances can refer to the same original array and can overlap. The original array must be one-dimensional and must have zero-based indexing.  
   
 > [!NOTE]
->  <xref:System.ArraySegment%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)]; in previous versions of the .NET Framework, the <xref:System.ArraySegment%601> structure did not implement this interface.  
+>  <xref:System.ArraySegment%601> implements the <xref:System.Collections.Generic.IReadOnlyCollection%601> interface starting with the .NET Framework 4.6; in previous versions of the .NET Framework, the <xref:System.ArraySegment%601> structure did not implement this interface.  
   
  The <xref:System.ArraySegment%601> structure is useful whenever the elements of an array will be manipulated in distinct segments. For example:  
   
diff --git a/xml/System/GC.xml b/xml/System/GC.xml
index d1102995e26..e02b745b440 100644
--- a/xml/System/GC.xml
+++ b/xml/System/GC.xml
@@ -84,7 +84,7 @@
   
 <a name="NoGCRegion"></a>   
 ## Disallowing garbage collection  
- Starting with the [!INCLUDE[net_v46](~/includes/net-v46-md.md)], the garbage collector supports a no GC region latency mode that can be used during the execution of critical paths in which garbage collection can adversely affect an app's performance. The no GC region latency mode requires that you specify an amount of memory that can be allocated without interference from the garbage collector. If the runtime can allocate that memory, the runtime will not perform a garbage collection while code in the critical path is executing.  
+ Starting with the .NET Framework 4.6, the garbage collector supports a no GC region latency mode that can be used during the execution of critical paths in which garbage collection can adversely affect an app's performance. The no GC region latency mode requires that you specify an amount of memory that can be allocated without interference from the garbage collector. If the runtime can allocate that memory, the runtime will not perform a garbage collection while code in the critical path is executing.  
   
  You define the beginning of the critical path of the no GC region by calling one of the overloads of the <xref:System.GC.TryStartNoGCRegion%2A>. You specify the end of its critical path by calling the <xref:System.GC.EndNoGCRegion%2A> method.  
   

From cc97abb04c0cdf3af3ff0753a4b5f4a6a9d1be7c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:27:16 -0800
Subject: [PATCH 041/236] net-v461

---
 xml/System.Globalization/CharUnicodeInfo.xml                | 2 +-
 xml/System.IO/PathTooLongException.xml                      | 4 ++--
 xml/System.Printing/OutputQuality.xml                       | 2 +-
 .../X509ChainStatusFlags.xml                                | 2 +-
 xml/System/Char.xml                                         | 6 +++---
 5 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 7b90ac96137..3af3c3dfd9b 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -98,7 +98,7 @@ When using this class in your applications, keep in mind the following programmi
 | .NET Framework 4.5.1 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.5.2 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.6 | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
-| [!INCLUDE[net_v461](~/includes/net-v461-md.md)] | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
+| .NET Framework 4.6.1 | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | [!INCLUDE[net_v462](~/includes/net-v462-md.md)] | [8.0.0](https://www.unicode.org/versions/Unicode8.0.0/) |
 
 Each version of the Unicode standard includes information on changes to the Unicode character database since the previous version. The Unicode character database is used by the <see cref="T:System.Globalization.CharUnicodeInfo" /> class for categorizing characters.</para>
diff --git a/xml/System.IO/PathTooLongException.xml b/xml/System.IO/PathTooLongException.xml
index ca8dee655bc..bc368897db9 100644
--- a/xml/System.IO/PathTooLongException.xml
+++ b/xml/System.IO/PathTooLongException.xml
@@ -67,10 +67,10 @@
   
 -   The length of the path exceeds <xref:System.Int16.MaxValue?displayProperty=nameWithType> (32,767) characters.  
   
- **Apps that target the [!INCLUDE[net_v461](~/includes/net-v461-md.md)] and earlier versions**  
+ **Apps that target the .NET Framework 4.6.1 and earlier versions**  
  Long paths are disabled by default, and the legacy behavior is maintained. The runtime throws a <xref:System.IO.PathTooLongException> whenever a path exceeds 260 characters.  
   
- If this is undesirable, apps that target the [!INCLUDE[net_v461](~/includes/net-v461-md.md)] and earlier but run under the [!INCLUDE[net_v462](~/includes/net-v462-md.md)] can enable long path support by including the following setting in the [\<runtime>](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) element of the application configuration file:  
+ If this is undesirable, apps that target the .NET Framework 4.6.1 and earlier but run under the [!INCLUDE[net_v462](~/includes/net-v462-md.md)] can enable long path support by including the following setting in the [\<runtime>](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) element of the application configuration file:  
   
 ```xml  
   
diff --git a/xml/System.Printing/OutputQuality.xml b/xml/System.Printing/OutputQuality.xml
index 5b4794a2b8d..bfb641cf2d3 100644
--- a/xml/System.Printing/OutputQuality.xml
+++ b/xml/System.Printing/OutputQuality.xml
@@ -34,7 +34,7 @@
   
 <a name="Photographic"></a>   
 ## Notes on OutputQuality.Photographic  
- Starting with the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], the output quality obtained with the Photographic value is improved (compared to previous versions of the .NET Framework) when printing to a GDI-based printer and when running on Windows 7 and earlier versions of the Windows operating system.  
+ Starting with the .NET Framework 4.6.1, the output quality obtained with the Photographic value is improved (compared to previous versions of the .NET Framework) when printing to a GDI-based printer and when running on Windows 7 and earlier versions of the Windows operating system.  
   
  Producing documents with better output quality requires larger print spooler files and longer wait times. If these side effects are undesirable, you can instead use the  High value.  
   
diff --git a/xml/System.Security.Cryptography.X509Certificates/X509ChainStatusFlags.xml b/xml/System.Security.Cryptography.X509Certificates/X509ChainStatusFlags.xml
index f8efdb0b8ba..d10b6dff670 100644
--- a/xml/System.Security.Cryptography.X509Certificates/X509ChainStatusFlags.xml
+++ b/xml/System.Security.Cryptography.X509Certificates/X509ChainStatusFlags.xml
@@ -45,7 +45,7 @@
 ## Remarks  
  This enumeration is used in conjunction with the <xref:System.Security.Cryptography.X509Certificates.X509ChainStatus> structure and the <xref:System.Security.Cryptography.X509Certificates.X509Chain.ChainStatus%2A> property.  
   
- The flags ExplicitDistrust, HasNotSupportedCriticalExtension and  HasWeakSignature were introduced with the [!INCLUDE[net_v461](~/includes/net-v461-md.md)].  
+ The flags ExplicitDistrust, HasNotSupportedCriticalExtension and  HasWeakSignature were introduced with the .NET Framework 4.6.1.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System/Char.xml b/xml/System/Char.xml
index 7911312a31c..320dc0c9377 100644
--- a/xml/System/Char.xml
+++ b/xml/System/Char.xml
@@ -116,7 +116,7 @@ To determine the Unicode category of a character, call the <xref:System.Char.Get
  :::code language="csharp" source="~/samples/snippets/csharp/VS_Snippets_CLR_System/system.char.class/cs/GetUnicodeCategory3.cs" interactive="try-dotnet" id="Snippet6":::
  :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.char.class/vb/GetUnicodeCategory3.vb" id="Snippet6":::
 
- Internally, for characters outside the ASCII range (U+0000 through U+00FF), the <xref:System.Char.GetUnicodeCategory%2A> method depends on Unicode categories reported by the <xref:System.Globalization.CharUnicodeInfo> class. Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from .NET Framework 4 to [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Internally, for characters outside the ASCII range (U+0000 through U+00FF), the <xref:System.Char.GetUnicodeCategory%2A> method depends on Unicode categories reported by the <xref:System.Globalization.CharUnicodeInfo> class. Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from .NET Framework 4 to .NET Framework 4.6.1, they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
 <a name="Elements"></a>
 ## Characters and text elements
@@ -1033,7 +1033,7 @@ When a managed <xref:System.Char> type, which is represented as a Unicode UTF-16
 ## Remarks
  The <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method does not always return the same <xref:System.Globalization.UnicodeCategory> value as the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method when it is passed a particular character as a parameter. The <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method is designed to reflect the current version of the Unicode standard. In contrast, although the <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method usually reflects the current version of the Unicode standard, it may return a character's category based on a previous version of the standard or it may return a category that differs from the current standard in order to preserve backward compatibility. As a result, we recommend that you use the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method instead of <xref:System.Char.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType>.
 
- Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the .NET Framework 4.6.1, they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
  ]]></format>
         </remarks>
@@ -1094,7 +1094,7 @@ When a managed <xref:System.Char> type, which is represented as a Unicode UTF-16
 
  The <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method does not always return the same <xref:System.Globalization.UnicodeCategory> value as the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType> method when it is passed a particular character as a parameter. The <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType> method is designed to reflect the current version of the Unicode standard. In contrast, although the <xref:System.Char.GetUnicodeCategory%2A?displayProperty=nameWithType> method usually reflects the current version of the Unicode standard, it may return a character's category based on a previous version of the standard or it may return a category that differs from the current standard in order to preserve backward compatibility. As a result, we recommend that you use the <xref:System.Globalization.CharUnicodeInfo.GetUnicodeCategory%28System.Char%29?displayProperty=nameWithType> method instead of <xref:System.Char.GetUnicodeCategory%28System.String%2CSystem.Int32%29?displayProperty=nameWithType>.
 
- Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the [!INCLUDE[net_v461](~/includes/net-v461-md.md)], they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
+ Starting with .NET Framework 4.6.2, Unicode characters are classified based on [The Unicode Standard, Version 8.0.0](https://www.unicode.org/versions/Unicode8.0.0/). In versions of the .NET Framework from the .NET Framework 4 to  the .NET Framework 4.6.1, they are classified based on [The Unicode Standard, Version 6.3.0](https://www.unicode.org/versions/Unicode6.3.0/).
 
  ]]></format>
         </remarks>

From 47f4d83d1764ace1aade31fcf65db74c26ed7751 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:28:29 -0800
Subject: [PATCH 042/236] net-v462

---
 xml/System.Globalization/CharUnicodeInfo.xml | 2 +-
 xml/System.IO/PathTooLongException.xml       | 8 ++++----
 xml/System.Security.Cryptography/RSACng.xml  | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Globalization/CharUnicodeInfo.xml b/xml/System.Globalization/CharUnicodeInfo.xml
index 3af3c3dfd9b..9b862bcae08 100644
--- a/xml/System.Globalization/CharUnicodeInfo.xml
+++ b/xml/System.Globalization/CharUnicodeInfo.xml
@@ -99,7 +99,7 @@ When using this class in your applications, keep in mind the following programmi
 | .NET Framework 4.5.2 | [5.0.0](https://www.unicode.org/versions/Unicode5.0.0/) |
 | .NET Framework 4.6 | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
 | .NET Framework 4.6.1 | [6.3.0](https://www.unicode.org/versions/Unicode6.3.0/) |
-| [!INCLUDE[net_v462](~/includes/net-v462-md.md)] | [8.0.0](https://www.unicode.org/versions/Unicode8.0.0/) |
+| .NET Framework 4.6.2 | [8.0.0](https://www.unicode.org/versions/Unicode8.0.0/) |
 
 Each version of the Unicode standard includes information on changes to the Unicode character database since the previous version. The Unicode character database is used by the <see cref="T:System.Globalization.CharUnicodeInfo" /> class for categorizing characters.</para>
     </block>
diff --git a/xml/System.IO/PathTooLongException.xml b/xml/System.IO/PathTooLongException.xml
index bc368897db9..3f3aceeb5a7 100644
--- a/xml/System.IO/PathTooLongException.xml
+++ b/xml/System.IO/PathTooLongException.xml
@@ -53,14 +53,14 @@
 ## Remarks  
  If your code does not have <xref:System.Security.Permissions.FileIOPermissionAttribute.PathDiscovery%2A?displayProperty=nameWithType> permission, the error message for this exception may contain only file or directory names instead of full paths.  
   
- In apps that run under versions of the .NET Framework prior to the [!INCLUDE[net_v462](~/includes/net-v462-md.md)], full paths must not exceed 260 characters to maintain compatibility with Windows operating systems. Any path in excess of 260 characters automatically throws a <xref:System.IO.PathTooLongException>. For more information about this restriction, see the entry [Long Paths in .NET](https://go.microsoft.com/fwlink/?LinkID=163666) in the BCL Team blog.  
+ In apps that run under versions of the .NET Framework prior to the .NET Framework 4.6.2, full paths must not exceed 260 characters to maintain compatibility with Windows operating systems. Any path in excess of 260 characters automatically throws a <xref:System.IO.PathTooLongException>. For more information about this restriction, see the entry [Long Paths in .NET](https://go.microsoft.com/fwlink/?LinkID=163666) in the BCL Team blog.  
   
 > [!NOTE]
 >  This exception is not included in [.NET for Windows Store apps](https://go.microsoft.com/fwlink/?LinkID=247912) or the [Portable Class Library](/dotnet/standard/cross-platform/cross-platform-development-with-the-portable-class-library), but it is thrown by some members that are. To catch the exception in that case, write a `catch` statement that handles an <xref:System.IO.IOException> instead.  
   
- Starting with apps running under the [!INCLUDE[net_v462](~/includes/net-v462-md.md)], the .NET Framework supports long paths in excess of 260 (or `MAX_PATH`) characters.  The conditions under which a <xref:System.IO.PathTooLongException> exception are thrown depend on the version of the .NET Framework that an app targets:  
+ Starting with apps running under the .NET Framework 4.6.2, the .NET Framework supports long paths in excess of 260 (or `MAX_PATH`) characters.  The conditions under which a <xref:System.IO.PathTooLongException> exception are thrown depend on the version of the .NET Framework that an app targets:  
   
- **Apps that target the [!INCLUDE[net_v462](~/includes/net-v462-md.md)] and later versions**  
+ **Apps that target the .NET Framework 4.6.2 and later versions**  
  Long paths are supported by default. The runtime throws a <xref:System.IO.PathTooLongException> under the following conditions:  
   
 -   The operating system returns `COR_E_PATHTOOLONG` or its equivalent.  
@@ -70,7 +70,7 @@
  **Apps that target the .NET Framework 4.6.1 and earlier versions**  
  Long paths are disabled by default, and the legacy behavior is maintained. The runtime throws a <xref:System.IO.PathTooLongException> whenever a path exceeds 260 characters.  
   
- If this is undesirable, apps that target the .NET Framework 4.6.1 and earlier but run under the [!INCLUDE[net_v462](~/includes/net-v462-md.md)] can enable long path support by including the following setting in the [\<runtime>](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) element of the application configuration file:  
+ If this is undesirable, apps that target the .NET Framework 4.6.1 and earlier but run under the .NET Framework 4.6.2 can enable long path support by including the following setting in the [\<runtime>](/dotnet/framework/configure-apps/file-schema/runtime/runtime-element) element of the application configuration file:  
   
 ```xml  
   
diff --git a/xml/System.Security.Cryptography/RSACng.xml b/xml/System.Security.Cryptography/RSACng.xml
index 20c8b273c3b..26bc602ae1f 100644
--- a/xml/System.Security.Cryptography/RSACng.xml
+++ b/xml/System.Security.Cryptography/RSACng.xml
@@ -843,7 +843,7 @@ any already open key is unaffected by this method.
   
  -or-  
   
- The signature is badly formatted. (In the .NET Framework 4.6 and 4.6.1 only; starting with the [!INCLUDE[net_v462](~/includes/net-v462-md.md)], the method returns <see langword="false" /> if a signature is badly formatted.</exception>
+ The signature is badly formatted. (In the .NET Framework 4.6 and 4.6.1 only; starting with the .NET Framework 4.6.2, the method returns <see langword="false" /> if a signature is badly formatted.</exception>
       </Docs>
     </Member>
   </Members>

From 73b9955dc06d44e139513c98cbfa842753a1be98 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:28:47 -0800
Subject: [PATCH 043/236] net-v463

---
 xml/System/ValueTuple.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System/ValueTuple.xml b/xml/System/ValueTuple.xml
index e42e72cad6a..65328b4f26d 100644
--- a/xml/System/ValueTuple.xml
+++ b/xml/System/ValueTuple.xml
@@ -77,7 +77,7 @@
 ## Remarks  
 A tuple is a data structure that has a specific number and sequence of elements. An example of a tuple is a data structure with three elements (known as a 3-tuple or triple) that is used to store an identifier such as a person's name in the first element, a year in the second element, and the person's income for that year in the third element.  
   
-Value tuples are tuple types introduced in the [!INCLUDE[net_v463](~/includes/net-v463-md.md)] to provide the runtime implementation of [tuples in C#](/dotnet/csharp/tuples) and struct tuples in F#. They differ from the tuple classes, such as  <xref:System.Tuple%601>, <xref:System.Tuple%602>, etc., as follows:  
+Value tuples are tuple types introduced in the .NET Framework 4.7 to provide the runtime implementation of [tuples in C#](/dotnet/csharp/tuples) and struct tuples in F#. They differ from the tuple classes, such as  <xref:System.Tuple%601>, <xref:System.Tuple%602>, etc., as follows:  
   
 -   They are structures (value types) rather than classes (reference types).  
   

From 355ac2090bcca3fad370f64e7905746da80609e6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:29:12 -0800
Subject: [PATCH 044/236] net-win8-profile

---
 xml/System.Reflection/TypeInfo.xml | 12 ++++++------
 xml/System/Exception.xml           |  2 +-
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.Reflection/TypeInfo.xml b/xml/System.Reflection/TypeInfo.xml
index b7f67d8a7f5..616451c7181 100644
--- a/xml/System.Reflection/TypeInfo.xml
+++ b/xml/System.Reflection/TypeInfo.xml
@@ -68,20 +68,20 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with .NET Framework 4.5, the <xref:System.Reflection.TypeInfo> class is included in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset for use in creating Windows Store apps. <xref:System.Reflection.TypeInfo> is available in the full .NET Framework as well. For more information about reflection for Windows Store apps, see [System.Reflection namespaces](/dotnet/api/?term=system.reflection) and [Reflection in the .NET Framework for Windows Store Apps](/dotnet/framework/reflection-and-codedom/reflection-for-windows-store-apps).  
+ Starting with .NET Framework 4.5, the <xref:System.Reflection.TypeInfo> class is included in the .NET for Windows 8.x Store apps subset for use in creating Windows Store apps. <xref:System.Reflection.TypeInfo> is available in the full .NET Framework as well. For more information about reflection for Windows Store apps, see [System.Reflection namespaces](/dotnet/api/?term=system.reflection) and [Reflection in the .NET Framework for Windows Store Apps](/dotnet/framework/reflection-and-codedom/reflection-for-windows-store-apps).  
   
- <xref:System.Reflection.TypeInfo> contains many of the members available in the <xref:System.Type> class, and many of the reflection properties in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] return collections of <xref:System.Reflection.TypeInfo> objects. To get a <xref:System.Reflection.TypeInfo> object from a <xref:System.Type> object, use the <xref:System.Reflection.IntrospectionExtensions.GetTypeInfo%28System.Type%29?displayProperty=nameWithType> extension method.  
+ <xref:System.Reflection.TypeInfo> contains many of the members available in the <xref:System.Type> class, and many of the reflection properties in the .NET for Windows 8.x Store apps return collections of <xref:System.Reflection.TypeInfo> objects. To get a <xref:System.Reflection.TypeInfo> object from a <xref:System.Type> object, use the <xref:System.Reflection.IntrospectionExtensions.GetTypeInfo%28System.Type%29?displayProperty=nameWithType> extension method.  
   
  A <xref:System.Reflection.TypeInfo> object represents the type definition itself, whereas a <xref:System.Type> object represents a reference to the type definition. Getting a <xref:System.Reflection.TypeInfo> object forces the assembly that contains that type to load. In comparison, you can manipulate <xref:System.Type> objects without necessarily requiring the runtime to load the assembly they reference.  
   
- In the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)], you use the reflection properties of <xref:System.Reflection.TypeInfo> that return <xref:System.Collections.Generic.IEnumerable%601> collections instead of methods that return arrays. For example, use the <xref:System.Reflection.TypeInfo.DeclaredMembers%2A> property to get all declared members, or the <xref:System.Reflection.TypeInfo.DeclaredProperties%2A> property to get all declared properties. Reflection contexts can implement lazy traversal of these collections for large assemblies or types. To get specific members, use methods such as <xref:System.Reflection.TypeInfo.GetDeclaredMethod%2A> and <xref:System.Reflection.TypeInfo.GetDeclaredProperty%2A>, and pass the name of the method or property you would like to retrieve.  
+ In the .NET for Windows 8.x Store apps, you use the reflection properties of <xref:System.Reflection.TypeInfo> that return <xref:System.Collections.Generic.IEnumerable%601> collections instead of methods that return arrays. For example, use the <xref:System.Reflection.TypeInfo.DeclaredMembers%2A> property to get all declared members, or the <xref:System.Reflection.TypeInfo.DeclaredProperties%2A> property to get all declared properties. Reflection contexts can implement lazy traversal of these collections for large assemblies or types. To get specific members, use methods such as <xref:System.Reflection.TypeInfo.GetDeclaredMethod%2A> and <xref:System.Reflection.TypeInfo.GetDeclaredProperty%2A>, and pass the name of the method or property you would like to retrieve.  
   
  To filter the results of <xref:System.Reflection.TypeInfo> properties, use LINQ queries. For reflection objects that originate with the runtime (for example, as the result of `typeof(Object)`), you can traverse the inheritance tree by using the methods in the <xref:System.Reflection.RuntimeReflectionExtensions> class. Consumers of objects from customized reflection contexts cannot use these methods and must traverse the inheritance tree themselves.  
   
    
   
 ## Examples  
- This example uses the reflection types and members in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
@@ -584,7 +584,7 @@
    
   
 ## Examples  
- This example uses the reflection types and members in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
@@ -701,7 +701,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- This example uses the reflection types and members in the [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
diff --git a/xml/System/Exception.xml b/xml/System/Exception.xml
index 7bf777be3a5..7543484a26f 100644
--- a/xml/System/Exception.xml
+++ b/xml/System/Exception.xml
@@ -291,7 +291,7 @@ Stack Trace:
  [!code-vb[System.Exception.Class#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.exception.class/vb/example.vb#3)]  
   
 ## Windows Runtime and .NET Framework 4.5.1  
- In [!INCLUDE[net_win8_profile](~/includes/net-win8-profile-md.md)] for [!INCLUDE[win8](~/includes/win8-md.md)], some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
+ In .NET for Windows 8.x Store apps for [!INCLUDE[win8](~/includes/win8-md.md)], some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
   
    
   

From 6e646fd6183a74d731dd4835144b4c9d85e53d14 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:29:37 -0800
Subject: [PATCH 045/236] netfx35-long

---
 xml/System.ServiceModel/WSHttpContextBinding.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.ServiceModel/WSHttpContextBinding.xml b/xml/System.ServiceModel/WSHttpContextBinding.xml
index dc9a07b1b89..3797cda55c8 100644
--- a/xml/System.ServiceModel/WSHttpContextBinding.xml
+++ b/xml/System.ServiceModel/WSHttpContextBinding.xml
@@ -35,7 +35,7 @@
  The <xref:System.ServiceModel.WSHttpContextBinding> adds a <xref:System.ServiceModel.Channels.ContextBindingElement> to the stack of <xref:System.ServiceModel.Channels.BindingElement> objects in the system-provided <xref:System.ServiceModel.WSHttpBinding>. This enables SOAP headers to be used to exchange context when HTTP cookies are not enabled.  
   
 > [!NOTE]
->  When calling a WCF service built with [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] or later from a WCF client application built with [!INCLUDE[netfx35_long](~/includes/netfx35-long-md.md)] or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
+>  When calling a WCF service built with [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] or later from a WCF client application built with .NET Framework version 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
   
  ]]></format>
     </remarks>

From 94bd608fa62fb39d48f598b335a1fb074e0d01a7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:29:55 -0800
Subject: [PATCH 046/236] netfx35-short

---
 xml/System.ServiceModel.Channels/CustomBinding.xml              | 2 +-
 .../SecurityContextSecurityToken.xml                            | 2 +-
 xml/System.ServiceModel.Syndication/SyndicationItem.xml         | 2 +-
 xml/System.ServiceModel/NetTcpContextBinding.xml                | 2 +-
 xml/System.ServiceModel/WS2007FederationHttpBinding.xml         | 2 +-
 xml/System.ServiceModel/WSFederationHttpBinding.xml             | 2 +-
 xml/System.ServiceModel/WSHttpContextBinding.xml                | 2 +-
 xml/System.Xml.Serialization/XmlSerializer.xml                  | 2 +-
 8 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.ServiceModel.Channels/CustomBinding.xml b/xml/System.ServiceModel.Channels/CustomBinding.xml
index 02261a01c61..5da5cd02102 100644
--- a/xml/System.ServiceModel.Channels/CustomBinding.xml
+++ b/xml/System.ServiceModel.Channels/CustomBinding.xml
@@ -116,7 +116,7 @@
  For a discussion on how to use a custom binding to modify a system-provided binding, see [How to: Customize a System-Provided Binding](/dotnet/framework/wcf/extending/how-to-customize-a-system-provided-binding).  
   
 > [!NOTE]
->  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the validity attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute validity". To workaround this problem, remove the validity attribute from the binding configuration.  
+>  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the validity attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute validity". To workaround this problem, remove the validity attribute from the binding configuration.  
   
    
   
diff --git a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
index 7273e63bffb..b48dbb41b76 100644
--- a/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
+++ b/xml/System.ServiceModel.Security.Tokens/SecurityContextSecurityToken.xml
@@ -624,7 +624,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting with the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)], this property is emitted on the wire as an `<sc:Instance>` element. In prior versions of the .NET Framework, it was emitted as an `<sc:Generation>` element.  
+ Starting with the .NET Framework 3.5, this property is emitted on the wire as an `<sc:Instance>` element. In prior versions of the .NET Framework, it was emitted as an `<sc:Generation>` element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel.Syndication/SyndicationItem.xml b/xml/System.ServiceModel.Syndication/SyndicationItem.xml
index d3522c4c3bb..f64f69b66bf 100644
--- a/xml/System.ServiceModel.Syndication/SyndicationItem.xml
+++ b/xml/System.ServiceModel.Syndication/SyndicationItem.xml
@@ -707,7 +707,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.ServiceModel.Syndication.SyndicationContent> is a base class for all syndication content types. The [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] defines the following syndication content types:  
+ <xref:System.ServiceModel.Syndication.SyndicationContent> is a base class for all syndication content types. The .NET Framework 3.5 defines the following syndication content types:  
   
 -   <xref:System.ServiceModel.Syndication.TextSyndicationContent>  
   
diff --git a/xml/System.ServiceModel/NetTcpContextBinding.xml b/xml/System.ServiceModel/NetTcpContextBinding.xml
index fd2392c9d8c..dfc26549ad2 100644
--- a/xml/System.ServiceModel/NetTcpContextBinding.xml
+++ b/xml/System.ServiceModel/NetTcpContextBinding.xml
@@ -34,7 +34,7 @@
 ## Remarks  
   
 > [!NOTE]
->  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the contextManagementEnabled attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the contextManagementEnabled attribute from the binding configuration.  
+>  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the contextManagementEnabled attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the contextManagementEnabled attribute from the binding configuration.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel/WS2007FederationHttpBinding.xml b/xml/System.ServiceModel/WS2007FederationHttpBinding.xml
index 396be25a2ff..c1067cd3740 100644
--- a/xml/System.ServiceModel/WS2007FederationHttpBinding.xml
+++ b/xml/System.ServiceModel/WS2007FederationHttpBinding.xml
@@ -23,7 +23,7 @@
  Federation is the ability to share identities across multiple enterprises or trust domains for authentication and authorization. It uses the WS-Trust protocol to map the identity representation from one trust domain to another. Federated HTTP binding supports SOAP security as well as mixed-mode security, but it does not support transport security. Services configured with this binding must use the HTTP transport. For more information, see <xref:System.ServiceModel.WSFederationHttpBinding>.  
   
 > [!NOTE]
->  When calling a WCF service built with.Net Framework 4.0 from a WCF client application built with [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the establishSecurityContext attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute establishSecurityContext". To workaround this problem, remove the establishSecurityContext attribute from the binding configuration.  
+>  When calling a WCF service built with.Net Framework 4.0 from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio will contain the establishSecurityContext attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application will thrown an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute establishSecurityContext". To workaround this problem, remove the establishSecurityContext attribute from the binding configuration.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel/WSFederationHttpBinding.xml b/xml/System.ServiceModel/WSFederationHttpBinding.xml
index 1bec3002bc5..bba1f28f991 100644
--- a/xml/System.ServiceModel/WSFederationHttpBinding.xml
+++ b/xml/System.ServiceModel/WSFederationHttpBinding.xml
@@ -29,7 +29,7 @@
  The <xref:System.ServiceModel.WSFederationHttpBinding> also provides a <xref:System.ServiceModel.WSFederationHttpBinding.PrivacyNoticeAt%2A> property to set and retrieve the URI at which the privacy notice is located.  
   
 > [!NOTE]
->  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `establishSecurityContext` attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application throws an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute establishSecurityContext ". To workaround this problem, remove the `establishSecurityContext` attribute from the binding configuration.  
+>  When calling a WCF service built with .NET Framework 4.0 or later from a WCF client application built with .NET Framework 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `establishSecurityContext` attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application throws an <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute establishSecurityContext ". To workaround this problem, remove the `establishSecurityContext` attribute from the binding configuration.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel/WSHttpContextBinding.xml b/xml/System.ServiceModel/WSHttpContextBinding.xml
index 3797cda55c8..78c954781dc 100644
--- a/xml/System.ServiceModel/WSHttpContextBinding.xml
+++ b/xml/System.ServiceModel/WSHttpContextBinding.xml
@@ -35,7 +35,7 @@
  The <xref:System.ServiceModel.WSHttpContextBinding> adds a <xref:System.ServiceModel.Channels.ContextBindingElement> to the stack of <xref:System.ServiceModel.Channels.BindingElement> objects in the system-provided <xref:System.ServiceModel.WSHttpBinding>. This enables SOAP headers to be used to exchange context when HTTP cookies are not enabled.  
   
 > [!NOTE]
->  When calling a WCF service built with [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] or later from a WCF client application built with .NET Framework version 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
+>  When calling a WCF service built with [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] or later from a WCF client application built with .NET Framework version 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Xml.Serialization/XmlSerializer.xml b/xml/System.Xml.Serialization/XmlSerializer.xml
index d1dd55b511f..d87ece9478e 100644
--- a/xml/System.Xml.Serialization/XmlSerializer.xml
+++ b/xml/System.Xml.Serialization/XmlSerializer.xml
@@ -229,7 +229,7 @@ xmlSerializer mySerializer=new XmlSerializer(typeof(LargeNumbers));
 ```  
   
 ## Objects marked with the Obsolete Attribute no longer serialized  
- In the [!INCLUDE[netfx35_short](~/includes/netfx35-short-md.md)] the <xref:System.Xml.Serialization.XmlSerializer> class no longer serializes objects that are marked as `[Obsolete]`.  
+ In the .NET Framework 3.5 the <xref:System.Xml.Serialization.XmlSerializer> class no longer serializes objects that are marked as `[Obsolete]`.  
   
    
   

From 0c404a0cdc81f70f88ac3d8061462e11ef9dfa64 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:30:15 -0800
Subject: [PATCH 047/236] netfx40-long

---
 .../InstanceEncodingOption.xml                                  | 2 +-
 xml/System.ServiceModel/WSHttpContextBinding.xml                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Activities.DurableInstancing/InstanceEncodingOption.xml b/xml/System.Activities.DurableInstancing/InstanceEncodingOption.xml
index b7a42727ea0..e0266990207 100644
--- a/xml/System.Activities.DurableInstancing/InstanceEncodingOption.xml
+++ b/xml/System.Activities.DurableInstancing/InstanceEncodingOption.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] ships with a SQL persistence provider as a constituent of the SQL Workflow Instance Store, which is a concrete implementation of the <xref:System.Runtime.DurableInstancing.InstanceStore> class and is used to persist state information in to the SQL Server database. When the `instanceEncodingOption` attribute is set to GZip for the <xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> service behavior associated with a service, the SQL persistence provider uses the GZip algorithm to encode instance state information for the instance of the service before saving the state information into the SQL Server persistence database.  
+ .NET Framework version 4 ships with a SQL persistence provider as a constituent of the SQL Workflow Instance Store, which is a concrete implementation of the <xref:System.Runtime.DurableInstancing.InstanceStore> class and is used to persist state information in to the SQL Server database. When the `instanceEncodingOption` attribute is set to GZip for the <xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> service behavior associated with a service, the SQL persistence provider uses the GZip algorithm to encode instance state information for the instance of the service before saving the state information into the SQL Server persistence database.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel/WSHttpContextBinding.xml b/xml/System.ServiceModel/WSHttpContextBinding.xml
index 78c954781dc..2dc6895e532 100644
--- a/xml/System.ServiceModel/WSHttpContextBinding.xml
+++ b/xml/System.ServiceModel/WSHttpContextBinding.xml
@@ -35,7 +35,7 @@
  The <xref:System.ServiceModel.WSHttpContextBinding> adds a <xref:System.ServiceModel.Channels.ContextBindingElement> to the stack of <xref:System.ServiceModel.Channels.BindingElement> objects in the system-provided <xref:System.ServiceModel.WSHttpBinding>. This enables SOAP headers to be used to exchange context when HTTP cookies are not enabled.  
   
 > [!NOTE]
->  When calling a WCF service built with [!INCLUDE[netfx40_long](~/includes/netfx40-long-md.md)] or later from a WCF client application built with .NET Framework version 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
+>  When calling a WCF service built with .NET Framework version 4 or later from a WCF client application built with .NET Framework version 3.5 or earlier, the configuration file generated by svcutil.exe or adding a service reference from Visual Studio contains the `contextManagementEnabled` attribute in the binding configuration. This attribute is not recognized by the .NET Framework 3.5 runtime and the application throws a <xref:System.Configuration.ConfigurationErrorsException> with the message "Unrecognized attribute 'contextManagementEnabled". To workaround this problem, remove the `contextManagementEnabled` attribute from the binding configuration.  
   
  ]]></format>
     </remarks>

From ea83a4299f84937272413bb22063881bd24515fe Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:30:47 -0800
Subject: [PATCH 048/236] netfx40-short

---
 .../InstanceCompletionAction.xml              |  2 +-
 xml/System/String.xml                         | 22 +++++++++----------
 2 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Activities.DurableInstancing/InstanceCompletionAction.xml b/xml/System.Activities.DurableInstancing/InstanceCompletionAction.xml
index f5043e141d6..8d9c36184a8 100644
--- a/xml/System.Activities.DurableInstancing/InstanceCompletionAction.xml
+++ b/xml/System.Activities.DurableInstancing/InstanceCompletionAction.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] ships with a SQL persistence provider as a constituent of the SQL Workflow Instance Store, which is a concrete implementation of the <xref:System.Runtime.DurableInstancing.InstanceStore> class and is used to persist state information in to the SQL Server database. When the `InstanceCompletionAction` attribute is set to DeleteNothing for the <xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> service behavior associated with a service, the SQL persistence provider keeps the instance state information for the instance in the SQL Server persistence database even after the instance completes, and when the `InstanceCompletionAction` attribute is set to DeleteAll (which is the default value), the persistence provider deletes all the instance state information when the instance completes.  
+ .NET Framework 4 ships with a SQL persistence provider as a constituent of the SQL Workflow Instance Store, which is a concrete implementation of the <xref:System.Runtime.DurableInstancing.InstanceStore> class and is used to persist state information in to the SQL Server database. When the `InstanceCompletionAction` attribute is set to DeleteNothing for the <xref:System.Activities.DurableInstancing.SqlWorkflowInstanceStore> service behavior associated with a service, the SQL persistence provider keeps the instance state information for the instance in the SQL Server persistence database even after the instance completes, and when the `InstanceCompletionAction` attribute is set to DeleteAll (which is the default value), the persistence provider deletes all the instance state information when the instance completes.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System/String.xml b/xml/System/String.xml
index fde79e46d70..6ea5fe719d7 100644
--- a/xml/System/String.xml
+++ b/xml/System/String.xml
@@ -1637,7 +1637,7 @@ The following example demonstrates how you can create an instance of the <xref:S
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, a culture-sensitive comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
+          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the .NET Framework 4 or later, a culture-sensitive comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
 
  [!code-csharp[System.String.Compare#21](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Compare/cs/compare21.cs#21)]
  [!code-vb[System.String.Compare#21](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Compare/vb/compare21.vb#21)]
@@ -1755,7 +1755,7 @@ The following example demonstrates how you can create an instance of the <xref:S
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String,System.Boolean)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, a culture-sensitive, case-insensitive comparison of "animal" with "Ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
+          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String,System.Boolean)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the .NET Framework 4 or later, a culture-sensitive, case-insensitive comparison of "animal" with "Ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
 
  [!code-csharp[System.String.Compare#22](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Compare/cs/compare22.cs#22)]
  [!code-vb[System.String.Compare#22](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Compare/vb/compare22.vb#22)]
@@ -1986,7 +1986,7 @@ The following example demonstrates how you can create an instance of the <xref:S
         <exception cref="T:System.ArgumentNullException">
           <paramref name="culture" /> is <see langword="null" />.</exception>
         <block subset="none" type="usage">
-          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String,System.Boolean,System.Globalization.CultureInfo)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, a case-insensitive comparison of "animal" with "Ani-mal" (using a soft hyphen, or U+00AD) using the invariant culture indicates that the two strings are equivalent.
+          <para>Character sets include ignorable characters. The <see cref="M:System.String.Compare(System.String,System.String,System.Boolean,System.Globalization.CultureInfo)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the .NET Framework 4 or later, a case-insensitive comparison of "animal" with "Ani-mal" (using a soft hyphen, or U+00AD) using the invariant culture indicates that the two strings are equivalent.
 
  [!code-csharp[System.String.Compare#23](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.Compare/cs/compare23.cs#23)]
  [!code-vb[System.String.Compare#23](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.Compare/vb/compare23.vb#23)]
@@ -3073,7 +3073,7 @@ The following example demonstrates how you can create an instance of the <xref:S
         <exception cref="T:System.ArgumentException">
           <paramref name="value" /> is not a <see cref="T:System.String" />.</exception>
         <block subset="none" type="usage">
-          <para>Character sets include ignorable characters. The <see cref="M:System.String.CompareTo(System.Object)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, a comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
+          <para>Character sets include ignorable characters. The <see cref="M:System.String.CompareTo(System.Object)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the .NET Framework 4 or later, a comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
 
  [!code-csharp[System.String.CompareTo#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.string.compareto/cs/compareto1.cs#1)]
  [!code-vb[System.String.CompareTo#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.string.compareto/vb/compareto1.vb#1)]
@@ -3189,7 +3189,7 @@ The following example demonstrates how you can create an instance of the <xref:S
  ]]></format>
         </remarks>
         <block subset="none" type="usage">
-          <para>Character sets include ignorable characters. The <see cref="M:System.String.CompareTo(System.String)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, a comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
+          <para>Character sets include ignorable characters. The <see cref="M:System.String.CompareTo(System.String)" /> method does not consider such characters when it performs a culture-sensitive comparison. For example, if the following code is run on the .NET Framework 4 or later, a comparison of "animal" with "ani-mal" (using a soft hyphen, or U+00AD) indicates that the two strings are equivalent.
 
  [!code-csharp[System.String.CompareTo#2](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.string.compareto/cs/compareto2.cs#2)]
  [!code-vb[System.String.CompareTo#2](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.string.compareto/vb/compareto2.vb#2)]
@@ -6784,7 +6784,7 @@ The `GetPinnableReference` method returns a character that can be used for pinni
 
  This method performs a word (case-sensitive and culture-sensitive) search using the current culture. The search begins at the first character position of this instance and continues until the last character position.
 
- Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String)> method always returns 0 (zero) to indicate that the match is found at the beginning of the current instance. In the following example, the <xref:System.String.IndexOf(System.String)> method is used to find three substrings (a soft hyphen (U+00AD), a soft hyphen followed by "n", and a soft hyphen followed by "m") in two strings. Only one of the strings contains a soft hyphen. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, in each case, because the soft hyphen is an ignorable character, the result is the same as if the soft hyphen had not been included in `value`. When searching for a soft hyphen only, the method returns 0 (zero) to indicate that it has found a match at the beginning of the string.
+ Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String)> method always returns 0 (zero) to indicate that the match is found at the beginning of the current instance. In the following example, the <xref:System.String.IndexOf(System.String)> method is used to find three substrings (a soft hyphen (U+00AD), a soft hyphen followed by "n", and a soft hyphen followed by "m") in two strings. Only one of the strings contains a soft hyphen. If the example is run on the .NET Framework 4 or later, in each case, because the soft hyphen is an ignorable character, the result is the same as if the soft hyphen had not been included in `value`. When searching for a soft hyphen only, the method returns 0 (zero) to indicate that it has found a match at the beginning of the string.
 
  [!code-csharp[System.String.IndexOf#21](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable21.cs#21)]
  [!code-vb[System.String.IndexOf#21](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable21.vb#21)]
@@ -6992,7 +6992,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
 
  This method performs a word (case-sensitive and culture-sensitive) search using the current culture. The search begins at the `startIndex` character position of this instance and continues until the last character position.
 
- Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String%2CSystem.Int32)> method always returns `startIndex`, which is the character position at which the search begins. In the following example, the <xref:System.String.IndexOf(System.String%2CSystem.Int32)> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" in two strings. Only one of the strings contains the required substring. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m".
+ Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String%2CSystem.Int32)> method always returns `startIndex`, which is the character position at which the search begins. In the following example, the <xref:System.String.IndexOf(System.String%2CSystem.Int32)> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" in two strings. Only one of the strings contains the required substring. If the example is run on the .NET Framework 4 or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m".
 
  [!code-csharp[System.String.IndexOf#22](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable22.cs#22)]
  [!code-vb[System.String.IndexOf#22](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable22.vb#22)]
@@ -7095,7 +7095,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
         <block subset="none" type="usage">
           <para>Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search (that is, if <paramref name="comparisonType" /> is not <see cref="F:System.StringComparison.Ordinal" /> or <see cref="F:System.StringComparison.OrdinalIgnoreCase" />), if <paramref name="value" /> contains an ignorable character, the result is equivalent to searching with that character removed. If <paramref name="value" /> consists only of one or more ignorable characters, the <see cref="M:System.String.IndexOf(System.String,System.StringComparison)" /> method always returns 0 (zero) to indicate that the match is found at the beginning of the current instance.
 
- In the following example, the <see cref="M:System.String.IndexOf(System.String,System.StringComparison)" /> method is used to find three substrings (a soft hyphen (U+00AD), a soft hyphen followed by "n", and a soft hyphen followed by "m") in two strings. Only one of the strings contains a soft hyphen. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, because the soft hyphen is an ignorable character, a culture-sensitive search returns the same value that it would return if the soft hyphen were not included in the search string. An ordinal search, however, successfully finds the soft hyphen in one string and reports that it is absent from the second string.
+ In the following example, the <see cref="M:System.String.IndexOf(System.String,System.StringComparison)" /> method is used to find three substrings (a soft hyphen (U+00AD), a soft hyphen followed by "n", and a soft hyphen followed by "m") in two strings. Only one of the strings contains a soft hyphen. If the example is run on the .NET Framework 4 or later, because the soft hyphen is an ignorable character, a culture-sensitive search returns the same value that it would return if the soft hyphen were not included in the search string. An ordinal search, however, successfully finds the soft hyphen in one string and reports that it is absent from the second string.
 
  [!code-csharp[System.String.IndexOf#26](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable26.cs#26)]
  [!code-vb[System.String.IndexOf#26](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable26.vb#26)]</para>
@@ -7242,7 +7242,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
 
  This method performs a word (case-sensitive and culture-sensitive) search using the current culture. The search begins at `startIndex` and continues to `startIndex` + `count` -1. The character at `startIndex` + `count` is not included in the search.
 
- Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String%2CSystem.Int32%2CSystem.Int32)> method always returns `startIndex`, which is the character position at which the search begins. In the following example, the <xref:System.String.IndexOf(System.String%2CSystem.Int32%2CSystem.Int32)> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting in the third through sixth character positions in two strings. Only one of the strings contains the required substring. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m".
+ Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search, if `value` contains an ignorable character, the result is equivalent to searching with that character removed. If `value` consists only of one or more ignorable characters, the <xref:System.String.IndexOf(System.String%2CSystem.Int32%2CSystem.Int32)> method always returns `startIndex`, which is the character position at which the search begins. In the following example, the <xref:System.String.IndexOf(System.String%2CSystem.Int32%2CSystem.Int32)> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting in the third through sixth character positions in two strings. Only one of the strings contains the required substring. If the example is run on the .NET Framework 4 or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m".
 
  [!code-csharp[System.String.IndexOf#23](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable23.cs#23)]
  [!code-vb[System.String.IndexOf#23](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable23.vb#23)]
@@ -7353,7 +7353,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
         <block subset="none" type="usage">
           <para>Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search (that is, if <paramref name="comparisonType" /> is not <see cref="F:System.StringComparison.Ordinal" /> or <see cref="F:System.StringComparison.OrdinalIgnoreCase" />), if <paramref name="value" /> contains an ignorable character, the result is equivalent to searching with that character removed. If <paramref name="value" /> consists only of one or more ignorable characters, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.StringComparison)" /> method always returns <paramref name="startIndex" />, which is the character position at which the search begins.
 
- In the following example, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.StringComparison)" /> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting with the third character position in two strings. Only one of the strings contains the required substring. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m". The method returns the index of the soft hyphen in the first string only when it performs an ordinal comparison.
+ In the following example, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.StringComparison)" /> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting with the third character position in two strings. Only one of the strings contains the required substring. If the example is run on the .NET Framework 4 or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m". The method returns the index of the soft hyphen in the first string only when it performs an ordinal comparison.
 
  [!code-csharp[System.String.IndexOf#25](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable25.cs#25)]
  [!code-vb[System.String.IndexOf#25](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable25.vb#25)]</para>
@@ -7447,7 +7447,7 @@ The `comparisonType` parameter is a <xref:System.StringComparison> enumeration m
         <block subset="none" type="usage">
           <para>Character sets include ignorable characters, which are characters that are not considered when performing a linguistic or culture-sensitive comparison. In a culture-sensitive search (that is, if <paramref name="comparisonType" /> is not <see cref="F:System.StringComparison.Ordinal" /> or <see cref="F:System.StringComparison.OrdinalIgnoreCase" />), if <paramref name="value" /> contains an ignorable character, the result is equivalent to searching with that character removed. If <paramref name="value" /> consists only of one or more ignorable characters, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.Int32,System.StringComparison)" /> method always returns <paramref name="startIndex" />, which is the character position at which the search begins.
 
- In the following example, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.Int32,System.StringComparison)" /> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting in the third through sixth character positions in two strings. Only one of the strings contains the required substring. If the example is run on the [!INCLUDE[netfx40_short](~/includes/netfx40-short-md.md)] or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. When it performs an ordinal comparison, however, it finds the substring only in the first string. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m" when it performs a culture-sensitive comparison. The method returns the index of the soft hyphen in the first string only when it performs an ordinal comparison.
+ In the following example, the <see cref="M:System.String.IndexOf(System.String,System.Int32,System.Int32,System.StringComparison)" /> method is used to find the position of a soft hyphen (U+00AD) followed by an "m" starting in the third through sixth character positions in two strings. Only one of the strings contains the required substring. If the example is run on the .NET Framework 4 or later, in both cases, because the soft hyphen is an ignorable character, the method returns the index of "m" in the string when it performs a culture-sensitive comparison. When it performs an ordinal comparison, however, it finds the substring only in the first string. Note that in the case of the first string, which includes the soft hyphen followed by an "m", the method fails to return the index of the soft hyphen but instead returns the index of the "m" when it performs a culture-sensitive comparison. The method returns the index of the soft hyphen in the first string only when it performs an ordinal comparison.
 
  [!code-csharp[System.String.IndexOf#24](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.String.IndexOf/CS/ignorable24.cs#24)]
  [!code-vb[System.String.IndexOf#24](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.String.IndexOf/VB/ignorable24.vb#24)]</para>

From 56148f1528ac6265069c48244dd56853b307cfd0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:31:08 -0800
Subject: [PATCH 049/236] ofprword

---
 xml/System.Windows.Forms/DataGridView.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Forms/DataGridView.xml b/xml/System.Windows.Forms/DataGridView.xml
index 190a0dc9fb1..ad6fd88faf7 100644
--- a/xml/System.Windows.Forms/DataGridView.xml
+++ b/xml/System.Windows.Forms/DataGridView.xml
@@ -4852,7 +4852,7 @@ The <xref:System.Windows.Forms.DataGridView> control replaces and extends the <x
 ## Remarks  
  The <xref:System.Windows.Forms.DataGridView> control copies the text representation of each selected cell to the Clipboard. This value is the cell value converted to a string or, for image cells, the value of the <xref:System.Windows.Forms.DataGridViewImageCell.Description%2A> property.  
   
- Values are copied to the Clipboard in <xref:System.Windows.Forms.DataFormats.Text>, <xref:System.Windows.Forms.DataFormats.UnicodeText>, <xref:System.Windows.Forms.DataFormats.Html>, and <xref:System.Windows.Forms.DataFormats.CommaSeparatedValue> formats. These formats are useful for pasting content into applications such as Notepad, Microsoft Excel, and [!INCLUDE[ofprword](~/includes/ofprword-md.md)].  
+ Values are copied to the Clipboard in <xref:System.Windows.Forms.DataFormats.Text>, <xref:System.Windows.Forms.DataFormats.UnicodeText>, <xref:System.Windows.Forms.DataFormats.Html>, and <xref:System.Windows.Forms.DataFormats.CommaSeparatedValue> formats. These formats are useful for pasting content into applications such as Notepad, Microsoft Excel, and Microsoft Word.  
   
  The <xref:System.Windows.Forms.DataGridView> control copies the cells contained in the smallest rectangle that includes all selected cells. Rows and columns that do not contain any selected cells are not represented in the copied data. Any unselected cells in the remaining rows and columns are represented by blank placeholders. Depending on the copy mode and the selection mode, header values for the copied rows and columns may be copied, as well.  
   

From 4202c8912b91922c1d2cab265aed97868a6172ba Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:31:51 -0800
Subject: [PATCH 050/236] sil3-first

---
 xml/System.Net/WebRequest.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Net/WebRequest.xml b/xml/System.Net/WebRequest.xml
index bdf52f38b28..32d46c83ed8 100644
--- a/xml/System.Net/WebRequest.xml
+++ b/xml/System.Net/WebRequest.xml
@@ -1162,7 +1162,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
-This property allows an application to determine which <xref:System.Net.IWebRequestCreate> derived factory object was used to create the request. This object may be [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) or [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)), but it may also be a custom instance derived from <xref:System.Net.IWebRequestCreate>. This allows an application to determine whether the browser hosting [!INCLUDE[silverlight](~/includes/silverlight-md.md)], the [!INCLUDE[silverlight](~/includes/silverlight-md.md)] client, or some custom object handles HTTP requests and responses for the <xref:System.Net.WebRequest> instance. The <xref:System.Net.WebRequest.RegisterPrefix%2A> method allows an application to configure which derived <xref:System.Net.WebRequest> type will be instantiated when making a request to a specific URI. <xref:System.Net.WebRequest> creators are typically registered to handle a specific protocol, such HTTP or HTTPS, but can be registered to handle a request to a specific server or path on a server. This is useful when more than one derived <xref:System.Net.WebRequest> type can process requests for the same protocol. The [!INCLUDE[sil3_first](~/includes/sil3-first-md.md)] and later runtime supports multiple HTTP handlers each having different capabilities. For example, a web service that uses Representational State Transfer (REST) might require the [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)) handler while a SOAP web service might be able to use the default [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) handler.
+This property allows an application to determine which <xref:System.Net.IWebRequestCreate> derived factory object was used to create the request. This object may be [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) or [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)), but it may also be a custom instance derived from <xref:System.Net.IWebRequestCreate>. This allows an application to determine whether the browser hosting [!INCLUDE[silverlight](~/includes/silverlight-md.md)], the [!INCLUDE[silverlight](~/includes/silverlight-md.md)] client, or some custom object handles HTTP requests and responses for the <xref:System.Net.WebRequest> instance. The <xref:System.Net.WebRequest.RegisterPrefix%2A> method allows an application to configure which derived <xref:System.Net.WebRequest> type will be instantiated when making a request to a specific URI. <xref:System.Net.WebRequest> creators are typically registered to handle a specific protocol, such HTTP or HTTPS, but can be registered to handle a request to a specific server or path on a server. This is useful when more than one derived <xref:System.Net.WebRequest> type can process requests for the same protocol. The Microsoft Silverlight 3 and later runtime supports multiple HTTP handlers each having different capabilities. For example, a web service that uses Representational State Transfer (REST) might require the [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)) handler while a SOAP web service might be able to use the default [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) handler.
   
  ]]></format>
         </remarks>

From 6dc9a18a4a8796c847648ce1c3e6a2fc28371b49 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:07 -0800
Subject: [PATCH 051/236] silverlight

---
 xml/System.Net/WebRequest.xml            | 2 +-
 xml/System.Windows.Controls/Calendar.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Net/WebRequest.xml b/xml/System.Net/WebRequest.xml
index 32d46c83ed8..a36d548544a 100644
--- a/xml/System.Net/WebRequest.xml
+++ b/xml/System.Net/WebRequest.xml
@@ -1162,7 +1162,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
-This property allows an application to determine which <xref:System.Net.IWebRequestCreate> derived factory object was used to create the request. This object may be [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) or [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)), but it may also be a custom instance derived from <xref:System.Net.IWebRequestCreate>. This allows an application to determine whether the browser hosting [!INCLUDE[silverlight](~/includes/silverlight-md.md)], the [!INCLUDE[silverlight](~/includes/silverlight-md.md)] client, or some custom object handles HTTP requests and responses for the <xref:System.Net.WebRequest> instance. The <xref:System.Net.WebRequest.RegisterPrefix%2A> method allows an application to configure which derived <xref:System.Net.WebRequest> type will be instantiated when making a request to a specific URI. <xref:System.Net.WebRequest> creators are typically registered to handle a specific protocol, such HTTP or HTTPS, but can be registered to handle a request to a specific server or path on a server. This is useful when more than one derived <xref:System.Net.WebRequest> type can process requests for the same protocol. The Microsoft Silverlight 3 and later runtime supports multiple HTTP handlers each having different capabilities. For example, a web service that uses Representational State Transfer (REST) might require the [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)) handler while a SOAP web service might be able to use the default [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) handler.
+This property allows an application to determine which <xref:System.Net.IWebRequestCreate> derived factory object was used to create the request. This object may be [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) or [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)), but it may also be a custom instance derived from <xref:System.Net.IWebRequestCreate>. This allows an application to determine whether the browser hosting Silverlight, the Silverlight client, or some custom object handles HTTP requests and responses for the <xref:System.Net.WebRequest> instance. The <xref:System.Net.WebRequest.RegisterPrefix%2A> method allows an application to configure which derived <xref:System.Net.WebRequest> type will be instantiated when making a request to a specific URI. <xref:System.Net.WebRequest> creators are typically registered to handle a specific protocol, such HTTP or HTTPS, but can be registered to handle a request to a specific server or path on a server. This is useful when more than one derived <xref:System.Net.WebRequest> type can process requests for the same protocol. The Microsoft Silverlight 3 and later runtime supports multiple HTTP handlers each having different capabilities. For example, a web service that uses Representational State Transfer (REST) might require the [System.Net.Browser.WebRequestCreator.ClientHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.clienthttp(v=vs.95)) handler while a SOAP web service might be able to use the default [System.Net.Browser.WebRequestCreator.BrowserHttp](https://msdn.microsoft.com/library/system.net.browser.webrequestcreator.browserhttp(v=vs.95)) handler.
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/Calendar.xml b/xml/System.Windows.Controls/Calendar.xml
index 30cf8e097b2..535e61c9f83 100644
--- a/xml/System.Windows.Controls/Calendar.xml
+++ b/xml/System.Windows.Controls/Calendar.xml
@@ -1002,7 +1002,7 @@ Calendar with dates that cannot be selected
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a <see cref="T:System.Windows.Automation.Peers.CalendarAutomationPeer" /> for use by the [!INCLUDE[silverlight](~/includes/silverlight-md.md)] automation infrastructure.</summary>
+        <summary>Returns a <see cref="T:System.Windows.Automation.Peers.CalendarAutomationPeer" /> for use by the Silverlight automation infrastructure.</summary>
         <returns>A <see cref="T:System.Windows.Automation.Peers.CalendarAutomationPeer" /> for the <see cref="T:System.Windows.Controls.Calendar" /> object.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 9d9ae29240e729ff3329777e92e6ac3e77cb5ddd Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:30 -0800
Subject: [PATCH 052/236] sqltecxlinq

---
 xml/System.Xml.Linq/Extensions.xml             |  6 +++---
 xml/System.Xml.Linq/XAttribute.xml             |  6 +++---
 xml/System.Xml.Linq/XContainer.xml             |  4 ++--
 xml/System.Xml.Linq/XDocument.xml              |  8 ++++----
 xml/System.Xml.Linq/XDocumentType.xml          |  8 ++++----
 xml/System.Xml.Linq/XNamespace.xml             |  2 +-
 xml/System.Xml.Linq/XNode.xml                  | 10 +++++-----
 xml/System.Xml.Linq/XObjectChangeEventArgs.xml | 14 +++++++-------
 xml/System.Xml.Linq/XProcessingInstruction.xml |  2 +-
 xml/System.Xml.Linq/XText.xml                  |  4 ++--
 xml/System.Xml.XPath/Extensions.xml            |  2 +-
 11 files changed, 33 insertions(+), 33 deletions(-)

diff --git a/xml/System.Xml.Linq/Extensions.xml b/xml/System.Xml.Linq/Extensions.xml
index 3681342d4b5..0f4ccfd6c9f 100644
--- a/xml/System.Xml.Linq/Extensions.xml
+++ b/xml/System.Xml.Linq/Extensions.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Most of the [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] extension methods are axis methods that are used in [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] queries. The methods in this class operate on collections and return collections. These methods enumerate the source collection, call the appropriate axis method on each item in the collection, and concatenate the results.  
+ Most of the LINQ to XML extension methods are axis methods that are used in [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] queries. The methods in this class operate on collections and return collections. These methods enumerate the source collection, call the appropriate axis method on each item in the collection, and concatenate the results.  
   
  The two <xref:System.Xml.Linq.Extensions.Remove%2A> extension methods are not axis methods, however. These methods remove attributes or nodes from the XML tree.  
   
@@ -1182,7 +1182,7 @@ Ancestors and Self
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Note that unlike some other XML programming interfaces, in [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)], namespaces are surfaced as attributes.  
+ Note that unlike some other XML programming interfaces, in LINQ to XML, namespaces are surfaced as attributes.  
   
  Although Visual Basic users can use the integrated attribute axis to retrieve attributes with a specified name from a collection of elements, there is no integrated Visual Basic axis to retrieve all attributes of all elements in a collection.  
   
@@ -1378,7 +1378,7 @@ aw:Att2="content6"
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Note that unlike some other XML programming interfaces, in [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)], namespaces are surfaced as attributes.  
+ Note that unlike some other XML programming interfaces, in LINQ to XML, namespaces are surfaced as attributes.  
   
  This method uses deferred execution.  
   
diff --git a/xml/System.Xml.Linq/XAttribute.xml b/xml/System.Xml.Linq/XAttribute.xml
index 48ed8dc9704..2633420175f 100644
--- a/xml/System.Xml.Linq/XAttribute.xml
+++ b/xml/System.Xml.Linq/XAttribute.xml
@@ -59,7 +59,7 @@
   
  Attributes are maintained in the XML tree in the order that they were added to the element. When a collection of attributes is returned by <xref:System.Xml.Linq.XElement.Attributes%2A>, they are returned in the order that they were added to the element, and are not sorted.  
   
- Technically, in XML, namespace declarations are not attributes proper. However, this distinction is not normally made by many XML programmers. Instead, because namespace declarations have exactly the same XML syntax as attributes, most XML programmers think of namespaces as attributes. To simplify the [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] programming interface, namespaces are represented in the XML tree as attributes. Such namespace attributes impact serialization of an XML tree. When serializing, [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] attempts to serialize with the namespace prefix specified in namespace attributes. You can use the <xref:System.Xml.Linq.XAttribute.IsNamespaceDeclaration%2A> to determine if an attribute is really a namespace declaration.  
+ Technically, in XML, namespace declarations are not attributes proper. However, this distinction is not normally made by many XML programmers. Instead, because namespace declarations have exactly the same XML syntax as attributes, most XML programmers think of namespaces as attributes. To simplify the LINQ to XML programming interface, namespaces are represented in the XML tree as attributes. Such namespace attributes impact serialization of an XML tree. When serializing, LINQ to XML attempts to serialize with the namespace prefix specified in namespace attributes. You can use the <xref:System.Xml.Linq.XAttribute.IsNamespaceDeclaration%2A> to determine if an attribute is really a namespace declaration.  
   
  The <xref:System.Xml.Linq.XAttribute> class derives from <xref:System.Xml.Linq.XObject>. You can add annotations to attributes, and observe events for them.  
   
@@ -388,7 +388,7 @@ Console.WriteLine(root)
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Technically, in XML, namespace declarations are not attributes proper. However, this distinction is not normally made by most XML programmers. Instead, because namespace declarations have exactly the same syntax as attributes, most XML programmers think of namespaces as attributes. To simplify the [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] programming interface, namespaces are represented in the XML tree as attributes. You can use this property to determine if a particular [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] attribute is really a namespace declaration.  
+ Technically, in XML, namespace declarations are not attributes proper. However, this distinction is not normally made by most XML programmers. Instead, because namespace declarations have exactly the same syntax as attributes, most XML programmers think of namespaces as attributes. To simplify the LINQ to XML programming interface, namespaces are represented in the XML tree as attributes. You can use this property to determine if a particular LINQ to XML attribute is really a namespace declaration.  
   
    
   
@@ -2841,7 +2841,7 @@ Att1="1"
 ## Remarks  
  You can use this method to modify an XML tree. This method will cause events to occur.  
   
- There are many scenarios in which you might want to remove a set of attributes. In [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] programming, you should not manipulate or modify a set of nodes while you are querying for nodes in that set. In practical terms, this means that you should not iterate over a set of attributes and remove them. Instead, you should materialize them into a <xref:System.Collections.Generic.List%601> using the <xref:System.Linq.Enumerable.ToList%2A> extension method. Then you can iterate over the list, removing the attributes. For more information, see [Mixed Declarative Code/Imperative Code Bugs (LINQ to XML)](/dotnet/standard/linq/mixed-declarative-imperative-code-bugs).  
+ There are many scenarios in which you might want to remove a set of attributes. In LINQ to XML programming, you should not manipulate or modify a set of nodes while you are querying for nodes in that set. In practical terms, this means that you should not iterate over a set of attributes and remove them. Instead, you should materialize them into a <xref:System.Collections.Generic.List%601> using the <xref:System.Linq.Enumerable.ToList%2A> extension method. Then you can iterate over the list, removing the attributes. For more information, see [Mixed Declarative Code/Imperative Code Bugs (LINQ to XML)](/dotnet/standard/linq/mixed-declarative-imperative-code-bugs).  
   
  Alternatively, if you want to remove a set of attributes, it is recommended that you use the <xref:System.Xml.Linq.Extensions.Remove%2A?displayProperty=nameWithType> method. This method copies the attributes to a list, then iterates over the list, removing the attributes.  
   
diff --git a/xml/System.Xml.Linq/XContainer.xml b/xml/System.Xml.Linq/XContainer.xml
index c26e2526f4f..8bc21251290 100644
--- a/xml/System.Xml.Linq/XContainer.xml
+++ b/xml/System.Xml.Linq/XContainer.xml
@@ -945,7 +945,7 @@ Console.WriteLine(newTree)
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Note that attributes are not considered to be nodes in [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)], so they will not be part of the collection that is returned by this method.  
+ Note that attributes are not considered to be nodes in LINQ to XML, so they will not be part of the collection that is returned by this method.  
   
  This method uses deferred execution.  
   
@@ -2012,7 +2012,7 @@ Console.WriteLine(lastNode)
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Note that the content does not include attributes. In [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)], attributes are not considered to be nodes of the tree. They are name/value pairs associated with an element.  
+ Note that the content does not include attributes. In LINQ to XML, attributes are not considered to be nodes of the tree. They are name/value pairs associated with an element.  
   
  This method uses deferred execution.  
   
diff --git a/xml/System.Xml.Linq/XDocument.xml b/xml/System.Xml.Linq/XDocument.xml
index 462a05da5ba..08da5542e68 100644
--- a/xml/System.Xml.Linq/XDocument.xml
+++ b/xml/System.Xml.Linq/XDocument.xml
@@ -732,13 +732,13 @@ Console.WriteLine(doc.Declaration)
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] provides limited support for DTDs.  
+ LINQ to XML provides limited support for DTDs.  
   
- You can populate an XML tree with an XML document that contains a DTD. The XML tree will then contain a <xref:System.Xml.Linq.XDocument.DocumentType%2A> node. When you serialize or save the tree, the DTD will also be serialized. [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] will expand any entities in the DTD. When you serialize or save the XML tree, the entity references are not saved; instead, the nodes are saved with the entity references replaced by the text of the entity.  
+ You can populate an XML tree with an XML document that contains a DTD. The XML tree will then contain a <xref:System.Xml.Linq.XDocument.DocumentType%2A> node. When you serialize or save the tree, the DTD will also be serialized. LINQ to XML will expand any entities in the DTD. When you serialize or save the XML tree, the entity references are not saved; instead, the nodes are saved with the entity references replaced by the text of the entity.  
   
  If the DTD contains default attributes, the attributes are created in the XML tree as ordinary attributes.  
   
- By default, [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] does not validate a document based on its DTD. To validate a document based on a DTD, create an <xref:System.Xml.XmlReader> that will validate based on a DTD, and then create an XML tree from the <xref:System.Xml.XmlReader>.  
+ By default, LINQ to XML does not validate a document based on its DTD. To validate a document based on a DTD, create an <xref:System.Xml.XmlReader> that will validate based on a DTD, and then create an XML tree from the <xref:System.Xml.XmlReader>.  
   
    
   
@@ -2199,7 +2199,7 @@ nodes when not preserving whitespace: 4
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is useful when you want to compose [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] queries in the same context as when composing them for a tree rooted in <xref:System.Xml.Linq.XElement>. See [Query an XDocument vs. query an XElement](/dotnet/standard/linq/query-xdocument-vs-query-xelement) for more details.  
+ This property is useful when you want to compose LINQ to XML queries in the same context as when composing them for a tree rooted in <xref:System.Xml.Linq.XElement>. See [Query an XDocument vs. query an XElement](/dotnet/standard/linq/query-xdocument-vs-query-xelement) for more details.  
   
    
   
diff --git a/xml/System.Xml.Linq/XDocumentType.xml b/xml/System.Xml.Linq/XDocumentType.xml
index 42fe72516c5..09dca3b325d 100644
--- a/xml/System.Xml.Linq/XDocumentType.xml
+++ b/xml/System.Xml.Linq/XDocumentType.xml
@@ -49,13 +49,13 @@
   
  This class represents the XML concept of a DTD.  
   
- DTD support in [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] is limited.  
+ DTD support in LINQ to XML is limited.  
   
- [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] will expand internal entities by default, but it will not resolve external entity references unless an <xref:System.Xml.XmlReader> with an associated <xref:System.Xml.XmlResolver> is used to load the XML tree.  
+ LINQ to XML will expand internal entities by default, but it will not resolve external entity references unless an <xref:System.Xml.XmlReader> with an associated <xref:System.Xml.XmlResolver> is used to load the XML tree.  
   
- [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] will not validate a document against a DTD, but you can use a validating <xref:System.Xml.XmlReader> to perform DTD validation if necessary.  
+ LINQ to XML will not validate a document against a DTD, but you can use a validating <xref:System.Xml.XmlReader> to perform DTD validation if necessary.  
   
- To validate an [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] tree against an XML schema, use the <xref:System.Xml.Schema.Extensions.Validate%2A> method.  
+ To validate an LINQ to XML tree against an XML schema, use the <xref:System.Xml.Schema.Extensions.Validate%2A> method.  
   
  When a document contains entity references that are defined in a DTD, the references are expanded upon creation of the XML tree. However, when you serialize or save the XML tree, the content of the expanded entities is preserved; the entity references are not.  
   
diff --git a/xml/System.Xml.Linq/XNamespace.xml b/xml/System.Xml.Linq/XNamespace.xml
index 416b811acbd..f0820c9bdf9 100644
--- a/xml/System.Xml.Linq/XNamespace.xml
+++ b/xml/System.Xml.Linq/XNamespace.xml
@@ -198,7 +198,7 @@ Console.WriteLine(e)
 <Root p1:Att="content" xmlns:p1="http://www.adventure-works.com" xmlns="http://www.adventure-works.com" />  
 ```  
   
- This approach has performance implications. Each time that you pass a string that contains an expanded name to [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)], it must parse the name, find the atomized namespace, and find the atomized name. This process takes CPU time. If performance is important, you may want to use a different approach.  
+ This approach has performance implications. Each time that you pass a string that contains an expanded name to LINQ to XML, it must parse the name, find the atomized namespace, and find the atomized name. This process takes CPU time. If performance is important, you may want to use a different approach.  
   
  With Visual Basic, the recommended approach is to use XML literals, which does not involve the use of expanded names.  
   
diff --git a/xml/System.Xml.Linq/XNode.xml b/xml/System.Xml.Linq/XNode.xml
index 56e2bc6d122..6574cad2c5c 100644
--- a/xml/System.Xml.Linq/XNode.xml
+++ b/xml/System.Xml.Linq/XNode.xml
@@ -1098,11 +1098,11 @@ el1 is before el2
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You typically use this method when you have to supply another component with an <xref:System.Xml.XmlReader>. For example, you can create an <xref:System.Xml.XmlReader> from a [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] tree, and then pass that reader to <xref:System.Xml.XmlDocument.Load%2A>.  
+ You typically use this method when you have to supply another component with an <xref:System.Xml.XmlReader>. For example, you can create an <xref:System.Xml.XmlReader> from a LINQ to XML tree, and then pass that reader to <xref:System.Xml.XmlDocument.Load%2A>.  
   
  All of the readers returned by <xref:System.Xml.XmlReader.Create%2A> are normalizing readers. They always perform line break normalization and full normalization of attributes. In contrast, the <xref:System.Xml.XmlReader> returned by <xref:System.Xml.Linq.XNode.CreateReader%2A> is not a normalizing reader. It does not transform any white space. It also returns attributes in the order that they were added, not in attribute name order.  
   
- [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] does not keep information about whether attributes are default attributes. <xref:System.Xml.XmlReader.IsDefault%2A> will always return false regardless of whether the attribute was populated from a default value or not.  
+ LINQ to XML does not keep information about whether attributes are default attributes. <xref:System.Xml.XmlReader.IsDefault%2A> will always return false regardless of whether the attribute was populated from a default value or not.  
   
  The `PUBLIC` and `SYSTEM` pseudo attributes on <xref:System.Xml.Linq.XDocumentType> are not available through the <xref:System.Xml.XmlReader.MoveToAttribute%2A?displayProperty=nameWithType> method. They are only available through the <xref:System.Xml.XmlReader.GetAttribute%2A?displayProperty=nameWithType> method that takes the qualified name of the attribute as a parameter. If you have to retrieve the `PUBLIC` or `SYSTEM` attributes, you should use the <xref:System.Xml.XmlReader.GetAttribute%2A?displayProperty=nameWithType> method.  
   
@@ -2725,7 +2725,7 @@ NodeType: Element   Child1
   
  Certain standard query operators, such as <xref:System.Linq.Enumerable.OrderBy%2A>, iterate their source, collect all of the data, sort it, and then finally yield the first item in the sequence. If you use a query operator that materializes its source before yielding the first item, you will not retain a small memory footprint.  
   
- For an example of using [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] to transform extremely large XML documents while maintaining a small memory footprint, see [How to perform streaming transform of large XML documents](/dotnet/standard/linq/perform-streaming-transform-large-xml-documents).  
+ For an example of using LINQ to XML to transform extremely large XML documents while maintaining a small memory footprint, see [How to perform streaming transform of large XML documents](/dotnet/standard/linq/perform-streaming-transform-large-xml-documents).  
   
 ## Examples
 
@@ -2828,7 +2828,7 @@ ccc
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] programming, you should not manipulate or modify a set of nodes while you are querying for nodes in that set. In practical terms, this means that you should not iterate over a set of nodes and remove them. Instead, you should materialize them into a <xref:System.Collections.Generic.List%601> by using the <xref:System.Linq.Enumerable.ToList%2A> extension method. Then, you can iterate over the list to remove the nodes. For more information, see [Mixed Declarative Code/Imperative Code Bugs (LINQ to XML)](/dotnet/standard/linq/mixed-declarative-imperative-code-bugs).  
+ In LINQ to XML programming, you should not manipulate or modify a set of nodes while you are querying for nodes in that set. In practical terms, this means that you should not iterate over a set of nodes and remove them. Instead, you should materialize them into a <xref:System.Collections.Generic.List%601> by using the <xref:System.Linq.Enumerable.ToList%2A> extension method. Then, you can iterate over the list to remove the nodes. For more information, see [Mixed Declarative Code/Imperative Code Bugs (LINQ to XML)](/dotnet/standard/linq/mixed-declarative-imperative-code-bugs).  
   
  Alternatively, if you want to remove a set of nodes, it is recommended that you use the <xref:System.Xml.Linq.Extensions.Remove%2A?displayProperty=nameWithType> method. This method copies the nodes to a list, and then iterates over the list to remove the nodes.  
   
@@ -3123,7 +3123,7 @@ Console.WriteLine(xmlTree)
    
   
 ## Examples  
- The following example shows using the results of a [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] query as the input to this method.  
+ The following example shows using the results of a LINQ to XML query as the input to this method.  
   
 ```csharp  
 XElement srcTree = new XElement("Root",  
diff --git a/xml/System.Xml.Linq/XObjectChangeEventArgs.xml b/xml/System.Xml.Linq/XObjectChangeEventArgs.xml
index 89abb444173..8e9c47a16e8 100644
--- a/xml/System.Xml.Linq/XObjectChangeEventArgs.xml
+++ b/xml/System.Xml.Linq/XObjectChangeEventArgs.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The purpose of this class is to hold the argument that is passed to an event handler when [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] raises events.  
+ The purpose of this class is to hold the argument that is passed to an event handler when LINQ to XML raises events.  
   
  ]]></format>
     </remarks>
@@ -85,13 +85,13 @@
         <Parameter Name="objectChange" Type="System.Xml.Linq.XObjectChange" />
       </Parameters>
       <Docs>
-        <param name="objectChange">An <see cref="T:System.Xml.Linq.XObjectChange" /> that contains the event arguments for [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] events.</param>
+        <param name="objectChange">An <see cref="T:System.Xml.Linq.XObjectChange" /> that contains the event arguments for LINQ to XML events.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Xml.Linq.XObjectChangeEventArgs" /> class.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The read-only fields <xref:System.Xml.Linq.XObjectChangeEventArgs.Add>, <xref:System.Xml.Linq.XObjectChangeEventArgs.Remove>, <xref:System.Xml.Linq.XObjectChangeEventArgs.Name>, and <xref:System.Xml.Linq.XObjectChangeEventArgs.Value> provide predefined instances for all the event arguments that are raised in [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)]. A typical user will not need to construct event arguments.  
+ The read-only fields <xref:System.Xml.Linq.XObjectChangeEventArgs.Add>, <xref:System.Xml.Linq.XObjectChangeEventArgs.Remove>, <xref:System.Xml.Linq.XObjectChangeEventArgs.Name>, and <xref:System.Xml.Linq.XObjectChangeEventArgs.Value> provide predefined instances for all the event arguments that are raised in LINQ to XML. A typical user will not need to construct event arguments.  
   
  ]]></format>
         </remarks>
@@ -135,7 +135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] raises an <xref:System.Xml.Linq.XObjectChange.Add> event, it passes the instance returned by this property as an argument.  
+ When LINQ to XML raises an <xref:System.Xml.Linq.XObjectChange.Add> event, it passes the instance returned by this property as an argument.  
   
  ]]></format>
         </remarks>
@@ -179,7 +179,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] raises an <xref:System.Xml.Linq.XObjectChange.Name> event, it passes the instance returned by this property as an argument.  
+ When LINQ to XML raises an <xref:System.Xml.Linq.XObjectChange.Name> event, it passes the instance returned by this property as an argument.  
   
  ]]></format>
         </remarks>
@@ -267,7 +267,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] raises an <xref:System.Xml.Linq.XObjectChange.Remove> event, it passes the instance returned by this property as an argument.  
+ When LINQ to XML raises an <xref:System.Xml.Linq.XObjectChange.Remove> event, it passes the instance returned by this property as an argument.  
   
  ]]></format>
         </remarks>
@@ -311,7 +311,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] raises an <xref:System.Xml.Linq.XObjectChange.Value> event, it passes the instance returned by this property as an argument.  
+ When LINQ to XML raises an <xref:System.Xml.Linq.XObjectChange.Value> event, it passes the instance returned by this property as an argument.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Xml.Linq/XProcessingInstruction.xml b/xml/System.Xml.Linq/XProcessingInstruction.xml
index 376aab2a2f0..15cbe5b8858 100644
--- a/xml/System.Xml.Linq/XProcessingInstruction.xml
+++ b/xml/System.Xml.Linq/XProcessingInstruction.xml
@@ -41,7 +41,7 @@
 ## Remarks  
  You can use processing instructions in XML to indicate that an XML document can be processed by some processor, such as XSLT.  
   
- Processing instructions are nodes in the XML tree. When a processing instruction is found in the XML being parsed, [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] creates an <xref:System.Xml.Linq.XProcessingInstruction> node.  
+ Processing instructions are nodes in the XML tree. When a processing instruction is found in the XML being parsed, LINQ to XML creates an <xref:System.Xml.Linq.XProcessingInstruction> node.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Xml.Linq/XText.xml b/xml/System.Xml.Linq/XText.xml
index 86e1dc03e65..a560ccc354a 100644
--- a/xml/System.Xml.Linq/XText.xml
+++ b/xml/System.Xml.Linq/XText.xml
@@ -41,9 +41,9 @@
 ## Remarks  
  XML elements can contain text content. Sometimes the content is simple (the element only contains text content), and sometimes the content is mixed (the contents of the element contains both text and other elements). In either case, each chunk of text is represented as an <xref:System.Xml.Linq.XText> node.  
   
- [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] developers will often have to write code to work with arbitrary [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] trees that they did not create. If you are writing code that has to work with [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] trees that you have no control over creating, you should be aware of certain behaviors of <xref:System.Xml.Linq.XText> nodes.  
+ LINQ to XML developers will often have to write code to work with arbitrary LINQ to XML trees that they did not create. If you are writing code that has to work with LINQ to XML trees that you have no control over creating, you should be aware of certain behaviors of <xref:System.Xml.Linq.XText> nodes.  
   
- When processing the contents of an XML tree at the node level, you should be prepared for multiple <xref:System.Xml.Linq.XText> nodes to be adjacent to each other. Further, you should be prepared for <xref:System.Xml.Linq.XText> nodes that contain no text. It is possible through [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] methods to remove the content of a text node. However, [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] does not automatically delete the node. The node has identity, and might have annotations, so [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] allows for zero-length nodes in the tree.  
+ When processing the contents of an XML tree at the node level, you should be prepared for multiple <xref:System.Xml.Linq.XText> nodes to be adjacent to each other. Further, you should be prepared for <xref:System.Xml.Linq.XText> nodes that contain no text. It is possible through LINQ to XML methods to remove the content of a text node. However, LINQ to XML does not automatically delete the node. The node has identity, and might have annotations, so LINQ to XML allows for zero-length nodes in the tree.  
   
  For more information, see [Programming with nodes](/dotnet/standard/linq/program-nodes).  
   
diff --git a/xml/System.Xml.XPath/Extensions.xml b/xml/System.Xml.XPath/Extensions.xml
index 23269784f07..dc5d1e7bef0 100644
--- a/xml/System.Xml.XPath/Extensions.xml
+++ b/xml/System.Xml.XPath/Extensions.xml
@@ -37,7 +37,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- There is some performance penalty for using these methods. Using [!INCLUDE[sqltecxlinq](~/includes/sqltecxlinq-md.md)] queries yields better performance.  
+ There is some performance penalty for using these methods. Using LINQ to XML queries yields better performance.  
   
  Although the ordering of returned collections is not specified in the XML XPath Language 1.0 Recommendation, this extension method returns nodes in document order.  
   

From 8984d16bdec360d3c25195ffbfb8fbb9b6ea5c90 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:32:56 -0800
Subject: [PATCH 053/236] sqprsqlong

---
 xml/System.Web.Caching/SqlCacheDependency.xml        | 12 ++++++------
 .../SqlCacheDependencySection.xml                    |  2 +-
 2 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.Web.Caching/SqlCacheDependency.xml b/xml/System.Web.Caching/SqlCacheDependency.xml
index e2a8eede21b..45df8b56c38 100644
--- a/xml/System.Web.Caching/SqlCacheDependency.xml
+++ b/xml/System.Web.Caching/SqlCacheDependency.xml
@@ -22,14 +22,14 @@
 ## Remarks
  On all supported versions of SQL Server (Microsoft SQL Server 7.0, Microsoft SQL Server 2000, and SQL Server 2005) the <xref:System.Web.Caching.SqlCacheDependency> class monitors a specific SQL Server database table. When the table changes, items associated with the table are removed from the <xref:System.Web.Caching.Cache>, and a new version of the item is added to the <xref:System.Web.Caching.Cache>.
 
- The <xref:System.Web.Caching.SqlCacheDependency> class also supports integration with the <xref:System.Data.SqlClient.SqlDependency?displayProperty=nameWithType> class when using a [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] database. The query notification mechanism of [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] detects changes to data that invalidate the results of an SQL query and removes any cached items associated with the SQL query from the <xref:System.Web.Caching.Cache?displayProperty=nameWithType>.
+ The <xref:System.Web.Caching.SqlCacheDependency> class also supports integration with the <xref:System.Data.SqlClient.SqlDependency?displayProperty=nameWithType> class when using a SQL Server 2005 database. The query notification mechanism of SQL Server 2005 detects changes to data that invalidate the results of an SQL query and removes any cached items associated with the SQL query from the <xref:System.Web.Caching.Cache?displayProperty=nameWithType>.
 
- You can use the <xref:System.Web.Caching.SqlCacheDependency> class to add items to your application's <xref:System.Web.Caching.Cache> that are dependent on either a SQL Server database table or on an SQL query when using [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)]. You can also use this class with the  directive to make an output-cached page or a user control dependent on a SQL Server database table. Finally, you can use the <xref:System.Web.Caching.SqlCacheDependency> class with the  page directive to make an output-cached page dependent on the results of an SQL query when using [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)]. Query notification using [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] is not supported on the  directive for user controls.
+ You can use the <xref:System.Web.Caching.SqlCacheDependency> class to add items to your application's <xref:System.Web.Caching.Cache> that are dependent on either a SQL Server database table or on an SQL query when using SQL Server 2005. You can also use this class with the  directive to make an output-cached page or a user control dependent on a SQL Server database table. Finally, you can use the <xref:System.Web.Caching.SqlCacheDependency> class with the  page directive to make an output-cached page dependent on the results of an SQL query when using SQL Server 2005. Query notification using SQL Server 2005 is not supported on the  directive for user controls.
 
 > [!NOTE]
 >  For this class to work correctly when using table-based notifications, the database and any tables that you want to make dependencies on must have notifications enabled. You can enable notifications by calling methods of the <xref:System.Web.Caching.SqlCacheDependencyAdmin> class or by using the  command-line tool. In addition, the proper configuration settings must be included in the application's Web.config file.
 >
->  Using a <xref:System.Web.Caching.SqlCacheDependency> object with [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] query notification does not require any explicit configuration. Consult the [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] Books Online for information about restrictions on the types of Transact-SQL queries that are allowed when using query notification.
+>  Using a <xref:System.Web.Caching.SqlCacheDependency> object with SQL Server 2005 query notification does not require any explicit configuration. Consult the SQL Server 2005 Books Online for information about restrictions on the types of Transact-SQL queries that are allowed when using query notification.
 
  The following example shows an ASP.NET Web.config file that enables table-based dependencies on a SQL Server database table.
 
@@ -101,7 +101,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This constructor is used to create <xref:System.Web.Caching.SqlCacheDependency> objects that use the query-notification feature of [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] products.
+ This constructor is used to create <xref:System.Web.Caching.SqlCacheDependency> objects that use the query-notification feature of SQL Server 2005 products.
 
  SQL statements that are associated with the `sqlCmd` parameter must include the following:
 
@@ -109,7 +109,7 @@
 
 -   Explicit column names in the Select statement. You cannot use the asterisk (*) wildcard character to select all columns from a table. For example, instead of `select * from dbo.customers`, you must use `select name, address, city, state from dbo.customers`.
 
- This constructor cannot be used to associate a <xref:System.Data.SqlClient.SqlCommand> instance with a <xref:System.Web.Caching.SqlCacheDependency> instance on a page using [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] query notifications with page-level output caching.
+ This constructor cannot be used to associate a <xref:System.Data.SqlClient.SqlCommand> instance with a <xref:System.Web.Caching.SqlCacheDependency> instance on a page using SQL Server 2005 query notifications with page-level output caching.
 
  ]]></format>
         </remarks>
@@ -305,7 +305,7 @@
 ## Remarks
  The <xref:System.Web.Caching.SqlCacheDependency> method returns an identifier used to uniquely track <xref:System.Web.Caching.SqlCacheDependency> objects associated with an item or application. The unique identifier generated when using table-based notifications is partially dependent on the change identifier generated by the database.
 
- When using SQL Server 2005-based query notifications, the unique identifier is `null` because [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] does not support returning unique identifiers for individual query notifications .
+ When using SQL Server 2005-based query notifications, the unique identifier is `null` because SQL Server 2005 does not support returning unique identifiers for individual query notifications .
 
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Configuration/SqlCacheDependencySection.xml b/xml/System.Web.Configuration/SqlCacheDependencySection.xml
index b3d31202288..51e8cdc71b9 100644
--- a/xml/System.Web.Configuration/SqlCacheDependencySection.xml
+++ b/xml/System.Web.Configuration/SqlCacheDependencySection.xml
@@ -24,7 +24,7 @@
   
  The SQL cache dependency allows the cached data to be synchronized with the original source. After you configure the relationship between an item stored in an ASP.NET application's cache and a specific SQL Server database table, an instance of the <xref:System.Web.Caching.SqlCacheDependency> class monitors the table so that when an item in the table changes, the item is automatically removed from the cache.  
   
- The settings in this element only affect the table-based version of the <xref:System.Web.Caching.SqlCacheDependency> object. The row-level <xref:System.Web.Caching.SqlCacheDependency> objects used with [!INCLUDE[sqprsqlong](~/includes/sqprsqlong-md.md)] and above are not affected by these settings.  
+ The settings in this element only affect the table-based version of the <xref:System.Web.Caching.SqlCacheDependency> object. The row-level <xref:System.Web.Caching.SqlCacheDependency> objects used with SQL Server 2005 and above are not affected by these settings.  
   
 > [!NOTE]
 >  The <xref:System.Web.Configuration.SqlCacheDependencySection> can write information into the related section of the configuration file according to the restrictions defined by the section property <xref:System.Configuration.SectionInformation.AllowDefinition%2A> whose value is <xref:System.Configuration.ConfigurationAllowDefinition.MachineToApplication>. Any attempt to write in a configuration file at a level not allowed in the hierarchy will result in an error message generated by the parser. However, you can use this class to read configuration information at any level in the hierarchy.  

From ed1af9f682b2d27858c19a63a884970cace1a530 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:33:36 -0800
Subject: [PATCH 054/236] ss2k

---
 xml/System.Web.UI.WebControls/LinqDataSource.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Web.UI.WebControls/LinqDataSource.xml b/xml/System.Web.UI.WebControls/LinqDataSource.xml
index ea5c60d8b42..fdf6a1b706a 100644
--- a/xml/System.Web.UI.WebControls/LinqDataSource.xml
+++ b/xml/System.Web.UI.WebControls/LinqDataSource.xml
@@ -124,7 +124,7 @@
  You use the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property to specify the names of properties from the returned data to sort by.  
   
 > [!NOTE]
->  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with [!INCLUDE[ss2k](~/includes/ss2k-md.md)] or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
+>  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
   
 <a name="grouping_data"></a>   
 ## Grouping Data  
@@ -1662,7 +1662,7 @@ The `LoadViewState` method is used to load the previously saved view state of th
  You can provide more than one property in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property by separating each property by using a comma. For example, to order by properties named `LastName` and `FirstName`, set the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property to "LastName, FirstName".  
   
 > [!NOTE]
->  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with [!INCLUDE[ss2k](~/includes/ss2k-md.md)] or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
+>  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
   
  If the <xref:System.Web.UI.WebControls.LinqDataSource.AutoSort%2A> property is set to `true`, a data-bound control can pass a sort expression to the <xref:System.Web.UI.WebControls.LinqDataSource> control at run time. The <xref:System.Web.UI.WebControls.LinqDataSource> control will apply the sort expression from the data-bound control after it applies the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. Therefore, the data is returned according to the sort expression from the data-bound control.  
   

From 178db5f0dd7fc46a6e90540d88b18d37fc544dd2 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:34:01 -0800
Subject: [PATCH 055/236] ssastoria

---
 .../DataServiceBuildProvider.xml               |  2 +-
 .../DataServiceCollection`1.xml                |  2 +-
 .../DataServiceContext.xml                     | 18 +++++++++---------
 .../DataServiceQuery`1.xml                     |  2 +-
 .../EntityPropertyMappingAttribute.xml         |  2 +-
 .../SyndicationItemProperty.xml                |  2 +-
 .../EntityClassGenerator.xml                   |  2 +-
 .../OpenTypeMethods.xml                        |  2 +-
 .../ResourceType.xml                           |  2 +-
 .../ChangeInterceptorAttribute.xml             |  2 +-
 xml/System.Data.Services/DataServiceHost.xml   | 10 +++++-----
 .../DataServiceHostFactory.xml                 |  2 +-
 xml/System.Data.Services/ETagAttribute.xml     |  2 +-
 xml/System.Data.Services/IDataServiceHost.xml  | 10 +++++-----
 .../QueryInterceptorAttribute.xml              |  2 +-
 15 files changed, 31 insertions(+), 31 deletions(-)

diff --git a/xml/System.Data.Services.BuildProvider/DataServiceBuildProvider.xml b/xml/System.Data.Services.BuildProvider/DataServiceBuildProvider.xml
index b7e1c75b097..c40ddf88c3a 100644
--- a/xml/System.Data.Services.BuildProvider/DataServiceBuildProvider.xml
+++ b/xml/System.Data.Services.BuildProvider/DataServiceBuildProvider.xml
@@ -84,7 +84,7 @@
       </Parameters>
       <Docs>
         <param name="assemblyBuilder">A container for building an assembly.</param>
-        <summary>Generates C# or Visual Basic code for a [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] client application based on the metadata returned by the data service.</summary>
+        <summary>Generates C# or Visual Basic code for a WCF Data Services client application based on the metadata returned by the data service.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Data.Services.Client/DataServiceCollection`1.xml b/xml/System.Data.Services.Client/DataServiceCollection`1.xml
index 2a7c30dbfa3..5dfd5c76bf5 100644
--- a/xml/System.Data.Services.Client/DataServiceCollection`1.xml
+++ b/xml/System.Data.Services.Client/DataServiceCollection`1.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] provides the <xref:System.Data.Services.Client.DataServiceCollection%601> class to support binding data to controls in client applications. This class inherits from the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface and is the primary data binding mechanism for Windows Presentation Foundation (WPF) and Silverlight-based applications.  
+ WCF Data Services provides the <xref:System.Data.Services.Client.DataServiceCollection%601> class to support binding data to controls in client applications. This class inherits from the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface and is the primary data binding mechanism for Windows Presentation Foundation (WPF) and Silverlight-based applications.  
   
  You can load an <xref:System.Collections.ObjectModel.ObservableCollection%601> binding collection by using any collection that implements the <xref:System.Collections.Generic.IEnumerable%601> interface. Items loaded into the binding collection must implement the <xref:System.ComponentModel.INotifyPropertyChanged> interface. For more information, see [Binding Data to Controls](/dotnet/framework/data/wcf/binding-data-to-controls-wcf-data-services).  
   
diff --git a/xml/System.Data.Services.Client/DataServiceContext.xml b/xml/System.Data.Services.Client/DataServiceContext.xml
index d7df86fd4b2..c9c94007f7d 100644
--- a/xml/System.Data.Services.Client/DataServiceContext.xml
+++ b/xml/System.Data.Services.Client/DataServiceContext.xml
@@ -21,12 +21,12 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] are stateless, but the <xref:System.Data.Services.Client.DataServiceContext> is not. State on the client is maintained between interactions in order to support features such as update management. This class, and the <xref:System.Data.Services.Client.DataServiceQuery> class that represents a particular HTTP request to a data service, are the two main classes in the client library.  
+ WCF Data Services are stateless, but the <xref:System.Data.Services.Client.DataServiceContext> is not. State on the client is maintained between interactions in order to support features such as update management. This class, and the <xref:System.Data.Services.Client.DataServiceQuery> class that represents a particular HTTP request to a data service, are the two main classes in the client library.  
   
    
   
 ## Examples  
- The following example shows how to use the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool to implicitly execute a query against the Northwind data service that returns all customers. The URI of the requested `Customers` entity set is determined automatically by the context. The query is executed implicitly when the enumeration occurs. The Northwind data service is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to use the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool to implicitly execute a query against the Northwind data service that returns all customers. The URI of the requested `Customers` entity set is determined automatically by the context. The query is executed implicitly when the enumeration occurs. The Northwind data service is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#GetAllCustomers](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#getallcustomers)]
  [!code-vb[Astoria Northwind Client#GetAllCustomers](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#getallcustomers)]  
@@ -114,7 +114,7 @@
    
   
 ## Examples  
- The following example shows how to use the <xref:System.Data.Services.Client.DataServiceContext.AddLink%2A> and <xref:System.Data.Services.Client.DataServiceContext.SetLink%2A> methods to create links that define relationships. In this example, the navigation properties on the `Order_Details` object are also explicitly set. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to use the <xref:System.Data.Services.Client.DataServiceContext.AddLink%2A> and <xref:System.Data.Services.Client.DataServiceContext.SetLink%2A> methods to create links that define relationships. In this example, the navigation properties on the `Order_Details` object are also explicitly set. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#AddOrderDetailToOrder](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#addorderdetailtoorder)]
  [!code-vb[Astoria Northwind Client#AddOrderDetailToOrder](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#addorderdetailtoorder)]  
@@ -528,7 +528,7 @@
    
   
 ## Examples  
- The following example shows how to execute an asynchronous query by calling the <xref:System.Data.Services.Client.DataServiceQuery%601.BeginExecute%2A> method to start the query. The inline delegate calls the <xref:System.Data.Services.Client.DataServiceQuery%601.EndExecute%2A> method to display the query results. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to execute an asynchronous query by calling the <xref:System.Data.Services.Client.DataServiceQuery%601.BeginExecute%2A> method to start the query. The inline delegate calls the <xref:System.Data.Services.Client.DataServiceQuery%601.EndExecute%2A> method to display the query results. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#ExecuteQueryAsync](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#executequeryasync)]
  [!code-vb[Astoria Northwind Client#ExecuteQueryAsync](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#executequeryasync)]  
@@ -1022,7 +1022,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default value of this property is the default [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] namespace: `http://schemas.microsoft.com/ado/2007/08/dataservices`.  
+ The default value of this property is the default WCF Data Services namespace: `http://schemas.microsoft.com/ado/2007/08/dataservices`.  
   
  This property affects both the namespace that is used for parsing content from the data service and the namespace used to generate content sent to the data service.  
   
@@ -1227,7 +1227,7 @@
    
   
 ## Examples  
- The following example shows how to execute an asynchronous query by calling the <xref:System.Data.Services.Client.DataServiceQuery%601.BeginExecute%2A> method to start the query. The inline delegate calls the <xref:System.Data.Services.Client.DataServiceQuery%601.EndExecute%2A> method to display the query results. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to execute an asynchronous query by calling the <xref:System.Data.Services.Client.DataServiceQuery%601.BeginExecute%2A> method to start the query. The inline delegate calls the <xref:System.Data.Services.Client.DataServiceQuery%601.EndExecute%2A> method to display the query results. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#ExecuteQueryAsync](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#executequeryasync)]
  [!code-vb[Astoria Northwind Client#ExecuteQueryAsync](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#executequeryasync)]  
@@ -1560,7 +1560,7 @@
    
   
 ## Examples  
- The following example shows how to call the <xref:System.Data.Services.Client.DataServiceContext.ExecuteBatch*> method to execute an array of <xref:System.Data.Services.Client.DataServiceRequest%601> objects that contains queries that return both `Customers` and `Products` objects from the Northwind data service. The collection of <xref:System.Data.Services.Client.QueryOperationResponse%601> objects in the returned <xref:System.Data.Services.Client.DataServiceResponse> is enumerated, and the collection of objects that is contained in each <xref:System.Data.Services.Client.QueryOperationResponse%601> is also enumerated. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to call the <xref:System.Data.Services.Client.DataServiceContext.ExecuteBatch*> method to execute an array of <xref:System.Data.Services.Client.DataServiceRequest%601> objects that contains queries that return both `Customers` and `Products` objects from the Northwind data service. The collection of <xref:System.Data.Services.Client.QueryOperationResponse%601> objects in the returned <xref:System.Data.Services.Client.DataServiceResponse> is enumerated, and the collection of objects that is contained in each <xref:System.Data.Services.Client.QueryOperationResponse%601> is also enumerated. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#BatchQuery](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#batchquery)]
  [!code-vb[Astoria Northwind Client#BatchQuery](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#batchquery)]  
@@ -2025,7 +2025,7 @@
    
   
 ## Examples  
- The following example shows how to explicitly load the `Customers` object that is related to each returned `Orders` instance. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example shows how to explicitly load the `Customers` object that is related to each returned `Orders` instance. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#LoadRelatedOrderCustomer](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#loadrelatedordercustomer)]
  [!code-vb[Astoria Northwind Client#LoadRelatedOrderCustomer](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#loadrelatedordercustomer)]  
@@ -2838,7 +2838,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example retrieves and modifies an existing object and then calls the <xref:System.Data.Services.Client.DataServiceContext.UpdateObject%2A> method on the <xref:System.Data.Services.Client.DataServiceContext> to mark the item in the context as updated. An HTTP MERGE message is sent to the data service when <xref:System.Data.Services.Client.DataServiceContext.SaveChanges%2A> is called. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] .  
+ The following example retrieves and modifies an existing object and then calls the <xref:System.Data.Services.Client.DataServiceContext.UpdateObject%2A> method on the <xref:System.Data.Services.Client.DataServiceContext> to mark the item in the context as updated. An HTTP MERGE message is sent to the data service when <xref:System.Data.Services.Client.DataServiceContext.SaveChanges%2A> is called. This example uses the <xref:System.Data.Services.Client.DataServiceContext> generated by the Add Service Reference tool based on the Northwind data service, which is created when you complete the WCF Data Services .  
   
  [!code-csharp[Astoria Northwind Client#ModifyCustomer](~/samples/snippets/csharp/VS_Snippets_Misc/astoria_northwind_client/cs/source.cs#modifycustomer)]
  [!code-vb[Astoria Northwind Client#ModifyCustomer](~/samples/snippets/visualbasic/VS_Snippets_Misc/astoria_northwind_client/vb/source.vb#modifycustomer)]  
diff --git a/xml/System.Data.Services.Client/DataServiceQuery`1.xml b/xml/System.Data.Services.Client/DataServiceQuery`1.xml
index a91a20555a3..108ebedd959 100644
--- a/xml/System.Data.Services.Client/DataServiceQuery`1.xml
+++ b/xml/System.Data.Services.Client/DataServiceQuery`1.xml
@@ -80,7 +80,7 @@
 ## Remarks  
  The query options are added to the resultant URI using `?name=value&name2=value2`… syntax where the name maps directly to the `name` parameter and the `value` is obtained by calling ToString on the `value` parameter. The `name` starts with `$`.  
   
- Non-[!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] syntax does not start with `$`. Non-[!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] query options can be added using this method. It is legal to add the same query option twice if the option is not an [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] query option. If a query option is added that is already present in the underlying URI, an exception is thrown.  
+ Non-WCF Data Services syntax does not start with `$`. Non-WCF Data Services query options can be added using this method. It is legal to add the same query option twice if the option is not an WCF Data Services query option. If a query option is added that is already present in the underlying URI, an exception is thrown.  
   
    
   
diff --git a/xml/System.Data.Services.Common/EntityPropertyMappingAttribute.xml b/xml/System.Data.Services.Common/EntityPropertyMappingAttribute.xml
index 4edfd25440f..78bea7b951a 100644
--- a/xml/System.Data.Services.Common/EntityPropertyMappingAttribute.xml
+++ b/xml/System.Data.Services.Common/EntityPropertyMappingAttribute.xml
@@ -153,7 +153,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When the value of <xref:System.Data.Services.Common.EntityPropertyMappingAttribute.KeepInContent%2A> is `true`, the feed is backward compatible with [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] client applications that use protocol version 1.0. When the value of <xref:System.Data.Services.Common.EntityPropertyMappingAttribute.KeepInContent%2A> is `false`, the protocol version used by the data service must be 2.0 or later versions. For more information, see [Data Service Versioning](/dotnet/framework/data/wcf/data-service-versioning-wcf-data-services).  
+ When the value of <xref:System.Data.Services.Common.EntityPropertyMappingAttribute.KeepInContent%2A> is `true`, the feed is backward compatible with WCF Data Services client applications that use protocol version 1.0. When the value of <xref:System.Data.Services.Common.EntityPropertyMappingAttribute.KeepInContent%2A> is `false`, the protocol version used by the data service must be 2.0 or later versions. For more information, see [Data Service Versioning](/dotnet/framework/data/wcf/data-service-versioning-wcf-data-services).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Services.Common/SyndicationItemProperty.xml b/xml/System.Data.Services.Common/SyndicationItemProperty.xml
index 1a401d17f58..1e684eda182 100644
--- a/xml/System.Data.Services.Common/SyndicationItemProperty.xml
+++ b/xml/System.Data.Services.Common/SyndicationItemProperty.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The values of this enumeration are used when defining custom feeds for [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)].  
+ The values of this enumeration are used when defining custom feeds for WCF Data Services.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Services.Design/EntityClassGenerator.xml b/xml/System.Data.Services.Design/EntityClassGenerator.xml
index ed3be34e60d..403c4fe01ae 100644
--- a/xml/System.Data.Services.Design/EntityClassGenerator.xml
+++ b/xml/System.Data.Services.Design/EntityClassGenerator.xml
@@ -302,7 +302,7 @@
         <ReturnType>System.Data.Services.Design.DataServiceCodeVersion</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the version of [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] that the generated code targets.</summary>
+        <summary>Gets or sets the version of WCF Data Services that the generated code targets.</summary>
         <value>A <see cref="T:System.Data.Services.Design.DataServiceCodeVersion" /> value that indicates the version of the generated code.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Data.Services.Providers/OpenTypeMethods.xml b/xml/System.Data.Services.Providers/OpenTypeMethods.xml
index f3c9287f971..5e52ffdda5f 100644
--- a/xml/System.Data.Services.Providers/OpenTypeMethods.xml
+++ b/xml/System.Data.Services.Providers/OpenTypeMethods.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is used when you implement a custom data service provider for [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)].  
+ This class is used when you implement a custom data service provider for WCF Data Services.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Services.Providers/ResourceType.xml b/xml/System.Data.Services.Providers/ResourceType.xml
index 22100b4298a..1ae29183d0f 100644
--- a/xml/System.Data.Services.Providers/ResourceType.xml
+++ b/xml/System.Data.Services.Providers/ResourceType.xml
@@ -54,7 +54,7 @@
         <Parameter Name="isAbstract" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="instanceType">CLR type that represents the format inside the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] runtime.</param>
+        <param name="instanceType">CLR type that represents the format inside the WCF Data Services runtime.</param>
         <param name="resourceTypeKind">
           <see cref="T:System.Data.Services.Providers.ResourceTypeKind" /> of the resource type.</param>
         <param name="baseType">Base type of the resource type as string.</param>
diff --git a/xml/System.Data.Services/ChangeInterceptorAttribute.xml b/xml/System.Data.Services/ChangeInterceptorAttribute.xml
index 51208c51f8c..dacd0e9a3ed 100644
--- a/xml/System.Data.Services/ChangeInterceptorAttribute.xml
+++ b/xml/System.Data.Services/ChangeInterceptorAttribute.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Resource-level change authorization and validation is implemented by methods annotated on the <xref:System.Data.Services.ChangeInterceptorAttribute>. [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] provides the infrastructure required for service developers to write per-entity change processing rules and validation.  
+ Resource-level change authorization and validation is implemented by methods annotated on the <xref:System.Data.Services.ChangeInterceptorAttribute>. WCF Data Services provides the infrastructure required for service developers to write per-entity change processing rules and validation.  
   
  Entity-level access control and validation can be enforced through query interceptors. For more information, see <xref:System.Data.Services.QueryInterceptorAttribute>.  
   
diff --git a/xml/System.Data.Services/DataServiceHost.xml b/xml/System.Data.Services/DataServiceHost.xml
index b864d4bfe7f..a4a145d98c7 100644
--- a/xml/System.Data.Services/DataServiceHost.xml
+++ b/xml/System.Data.Services/DataServiceHost.xml
@@ -26,9 +26,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] are not autonomous server entities. Instead, the service is a component hosted in an environment such as the Windows Communication Foundation (WCF) that provides core server networking facilities. Specifically, a service does not bind to and listen on a network socket for incoming requests to its Representational State Transfer (REST) entry points. The host handles direct interactions with the network and support caching, scalability, and authentication modules.  
+ WCF Data Services are not autonomous server entities. Instead, the service is a component hosted in an environment such as the Windows Communication Foundation (WCF) that provides core server networking facilities. Specifically, a service does not bind to and listen on a network socket for incoming requests to its Representational State Transfer (REST) entry points. The host handles direct interactions with the network and support caching, scalability, and authentication modules.  
   
- [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] defines a generic hosting interface <xref:System.Data.Services.IDataServiceHost> that abstracts its implementation from a specific host. This allows [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] to run in a range of hosting environments. For more information, see [Hosting the Data Service](/dotnet/framework/data/wcf/hosting-the-data-service-wcf-data-services).  
+ WCF Data Services defines a generic hosting interface <xref:System.Data.Services.IDataServiceHost> that abstracts its implementation from a specific host. This allows WCF Data Services to run in a range of hosting environments. For more information, see [Hosting the Data Service](/dotnet/framework/data/wcf/hosting-the-data-service-wcf-data-services).  
   
  ]]></format>
     </remarks>
@@ -58,14 +58,14 @@
         <Parameter Name="baseAddresses" Type="System.Uri[]" />
       </Parameters>
       <Docs>
-        <param name="serviceType">Identifies the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] to the host.</param>
+        <param name="serviceType">Identifies the WCF Data Services to the host.</param>
         <param name="baseAddresses">The URI of the host.</param>
-        <summary>Instantiates <see cref="T:System.Data.Services.DataServiceHost" /> for [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)].</summary>
+        <summary>Instantiates <see cref="T:System.Data.Services.DataServiceHost" /> for WCF Data Services.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] defines a generic hosting interface <xref:System.Data.Services.IDataServiceHost> that abstracts its implementation from a specific host. This allows [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] to run in a range of hosting environments. This interface should not be confused with <xref:System.Data.Services.DataServiceHost>, which instead handles registration and activation for the service. A default <xref:System.Data.Services.IDataServiceHost> is used in this case.  
+ WCF Data Services defines a generic hosting interface <xref:System.Data.Services.IDataServiceHost> that abstracts its implementation from a specific host. This allows WCF Data Services to run in a range of hosting environments. This interface should not be confused with <xref:System.Data.Services.DataServiceHost>, which instead handles registration and activation for the service. A default <xref:System.Data.Services.IDataServiceHost> is used in this case.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Services/DataServiceHostFactory.xml b/xml/System.Data.Services/DataServiceHostFactory.xml
index 1f802206af9..19dd142eea5 100644
--- a/xml/System.Data.Services/DataServiceHostFactory.xml
+++ b/xml/System.Data.Services/DataServiceHostFactory.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class enables [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] to hook up to WCF as a raw HTTP handler. Not recommended for use by third parties.  
+ This class enables WCF Data Services to hook up to WCF as a raw HTTP handler. Not recommended for use by third parties.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Services/ETagAttribute.xml b/xml/System.Data.Services/ETagAttribute.xml
index f1de8bf2917..dd375b3ea77 100644
--- a/xml/System.Data.Services/ETagAttribute.xml
+++ b/xml/System.Data.Services/ETagAttribute.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Optimistic concurrency checks are enabled on a per type basis in [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)]. For more information, see [Making Changes to Data (WCF Data Services)](https://msdn.microsoft.com/library/c83a5a41-826c-4fe5-8d43-61bc96ddaa19).  
+ Optimistic concurrency checks are enabled on a per type basis in WCF Data Services. For more information, see [Making Changes to Data (WCF Data Services)](https://msdn.microsoft.com/library/c83a5a41-826c-4fe5-8d43-61bc96ddaa19).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Services/IDataServiceHost.xml b/xml/System.Data.Services/IDataServiceHost.xml
index 02689f72fb9..eff1451b8d4 100644
--- a/xml/System.Data.Services/IDataServiceHost.xml
+++ b/xml/System.Data.Services/IDataServiceHost.xml
@@ -17,7 +17,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each component that hosts [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)], such as Windows Communication Foundation (WCF) must implement this interface. <xref:System.Data.Services.IDataServiceHost> is the contract between [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] and its hosting environment. This abstraction allows the [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] runtime to be agnostic to any particular hosting environment. The interface provides [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] with access to inbound HTTP requests. A new object implementing this interface is instantiated for each HTTP request and is then used to inspect properties of the HTTP request and configure the HTTP response.  
+ Each component that hosts WCF Data Services, such as Windows Communication Foundation (WCF) must implement this interface. <xref:System.Data.Services.IDataServiceHost> is the contract between WCF Data Services and its hosting environment. This abstraction allows the WCF Data Services runtime to be agnostic to any particular hosting environment. The interface provides WCF Data Services with access to inbound HTTP requests. A new object implementing this interface is instantiated for each HTTP request and is then used to inspect properties of the HTTP request and configure the HTTP response.  
   
  ]]></format>
     </remarks>
@@ -108,7 +108,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The query string portion of an [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] URI is made up of key/value pairs, with the key and value separated by the '=' character. `GetQueryStringItem` returns a data item for an identity key specified by the parameter of the method.  
+ The query string portion of an WCF Data Services URI is made up of key/value pairs, with the key and value separated by the '=' character. `GetQueryStringItem` returns a data item for an identity key specified by the parameter of the method.  
   
  ]]></format>
         </remarks>
@@ -163,7 +163,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Protocols currently supported by [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] include JSON and AtomPub.  
+ Protocols currently supported by WCF Data Services include JSON and AtomPub.  
   
  ]]></format>
         </remarks>
@@ -221,7 +221,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Protocols currently supported by [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] include JSON and AtomPub.  
+ Protocols currently supported by WCF Data Services include JSON and AtomPub.  
   
  ]]></format>
         </remarks>
@@ -532,7 +532,7 @@ http://myhost/myservice.svc/Customers, the response location would be http://myh
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a null stream is returned or an exception occurs when writing to the stream, [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)] aborts the request.  
+ If a null stream is returned or an exception occurs when writing to the stream, WCF Data Services aborts the request.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Services/QueryInterceptorAttribute.xml b/xml/System.Data.Services/QueryInterceptorAttribute.xml
index 62840aa7dfa..2eb30b86d00 100644
--- a/xml/System.Data.Services/QueryInterceptorAttribute.xml
+++ b/xml/System.Data.Services/QueryInterceptorAttribute.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Entity set-level authorization and validation is implemented by methods annotated with the <xref:System.Data.Services.QueryInterceptorAttribute>. [!INCLUDE[ssAstoria](~/includes/ssastoria-md.md)]s do not implement security policies but instead provide the infrastructure required for service developers to write their own security rules and business validation.  
+ Entity set-level authorization and validation is implemented by methods annotated with the <xref:System.Data.Services.QueryInterceptorAttribute>. WCF Data Servicess do not implement security policies but instead provide the infrastructure required for service developers to write their own security rules and business validation.  
   
  Entity set access control and validation is enabled through query operations by using query composition. To control entity-based access, implement a method-per-entity set according to the following rules:  
   

From 914830ccc2d189a5b4d3cb5171b74cfc80cca754 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:34:19 -0800
Subject: [PATCH 056/236] ssew

---
 xml/System.Web.UI.WebControls/LinqDataSource.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Web.UI.WebControls/LinqDataSource.xml b/xml/System.Web.UI.WebControls/LinqDataSource.xml
index fdf6a1b706a..68186c739a7 100644
--- a/xml/System.Web.UI.WebControls/LinqDataSource.xml
+++ b/xml/System.Web.UI.WebControls/LinqDataSource.xml
@@ -124,7 +124,7 @@
  You use the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property to specify the names of properties from the returned data to sort by.  
   
 > [!NOTE]
->  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
+>  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or SQL Server Compact 3.5 and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
   
 <a name="grouping_data"></a>   
 ## Grouping Data  
@@ -1662,7 +1662,7 @@ The `LoadViewState` method is used to load the previously saved view state of th
  You can provide more than one property in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property by separating each property by using a comma. For example, to order by properties named `LastName` and `FirstName`, set the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property to "LastName, FirstName".  
   
 > [!NOTE]
->  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or [!INCLUDE[ssEW](~/includes/ssew-md.md)] and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
+>  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control with SQL Server 2000 or SQL Server Compact 3.5 and the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is set to `true`, you must provide a value in the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. By default, the <xref:System.Web.UI.WebControls.LinqDataSource.AutoPage%2A> property is `true`. If you assign a value to the <xref:System.Web.UI.WebControls.LinqDataSource.Select%2A> property, you must also include all identity columns in the list of properties that is returned in the query.  
   
  If the <xref:System.Web.UI.WebControls.LinqDataSource.AutoSort%2A> property is set to `true`, a data-bound control can pass a sort expression to the <xref:System.Web.UI.WebControls.LinqDataSource> control at run time. The <xref:System.Web.UI.WebControls.LinqDataSource> control will apply the sort expression from the data-bound control after it applies the <xref:System.Web.UI.WebControls.LinqDataSource.OrderBy%2A> property. Therefore, the data is returned according to the sort expression from the data-bound control.  
   

From c765caae4d0fc3dddded4ffad21e928f048abdc7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:34:42 -0800
Subject: [PATCH 057/236] sskatmai-r2

---
 xml/System.Data.SqlClient/SqlConnection.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
index c8efd11dcd2..d36b898fa2c 100644
--- a/xml/System.Data.SqlClient/SqlConnection.xml
+++ b/xml/System.Data.SqlClient/SqlConnection.xml
@@ -1065,7 +1065,7 @@ The connection string contains <see langword="Context Connection=true" />.
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- <xref:System.Data.SqlClient.SqlConnection.ClientConnectionId%2A> works regardless of which version of the server you connect to, but extended events logs and entry on connectivity ring buffer errors will not be present in [!INCLUDE[sskatmai_r2](~/includes/sskatmai-r2-md.md)] and earlier.
+ <xref:System.Data.SqlClient.SqlConnection.ClientConnectionId%2A> works regardless of which version of the server you connect to, but extended events logs and entry on connectivity ring buffer errors will not be present in SQL Server 2008 R2 and earlier.
 
  You can locate the connection ID in the extended events log to see if the failure was on the server if the extended event for logging connection ID is enabled. You can also locate the connection ID in the connection ring buffer for certain connection errors. If the connection ID is not in the connection ring buffer, you can assume a network error.
 

From 02b9105977ef0a8b97b84a2841ccd41cd24495fc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 11:35:04 -0800
Subject: [PATCH 058/236] ssodatashort

---
 .../DataServiceProtocolVersion.xml                            | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Data.Services.Common/DataServiceProtocolVersion.xml b/xml/System.Data.Services.Common/DataServiceProtocolVersion.xml
index 4ee4ae2efda..d62ad94a497 100644
--- a/xml/System.Data.Services.Common/DataServiceProtocolVersion.xml
+++ b/xml/System.Data.Services.Common/DataServiceProtocolVersion.xml
@@ -38,7 +38,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Version 1 of the [!INCLUDE[ssODataShort](~/includes/ssodatashort-md.md)] protocol.</summary>
+        <summary>Version 1 of the OData protocol.</summary>
       </Docs>
     </Member>
     <Member MemberName="V2">
@@ -60,7 +60,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>Version 2 of the [!INCLUDE[ssODataShort](~/includes/ssodatashort-md.md)] protocol.</summary>
+        <summary>Version 2 of the OData protocol.</summary>
       </Docs>
     </Member>
   </Members>

From 23f66c1e31d0d6b694a035534b7ae3082cd86ec5 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:24:28 -0800
Subject: [PATCH 059/236] tla2sharptla-2d

---
 xml/System.Windows.Media.Media3D/SpecularMaterial.xml | 2 +-
 xml/System.Windows.Media/Matrix.xml                   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
index e48636e48ba..d9035b1d120 100644
--- a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
+++ b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
@@ -356,7 +356,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value that specifies the degree to which a material applied to a 3-D model reflects the lighting model as shine.</summary>
-        <value>Relative contribution, for a material applied as a [!INCLUDE[TLA2#tla_2d](~/includes/tla2sharptla-2d-md.md)] brush to a [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] model, of the specular component of the lighting model.</value>
+        <value>Relative contribution, for a material applied as a 2-D brush to a [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] model, of the specular component of the lighting model.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media/Matrix.xml b/xml/System.Windows.Media/Matrix.xml
index 1c7e971d7e6..df1257ff00a 100644
--- a/xml/System.Windows.Media/Matrix.xml
+++ b/xml/System.Windows.Media/Matrix.xml
@@ -40,7 +40,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A 3x3 matrix is used for transformations in a [!INCLUDE[TLA2#tla_2d](~/includes/tla2sharptla-2d-md.md)] x-y plane. Affine transformation matrices can be multiplied to form any number of linear transformations, such as rotation and skew (shear), followed by translation. An affine transformation matrix has its final column equal to (0, 0, 1), so only the members in the first two columns need to be specified.  Note that vectors are expressed as row-vectors, not column vectors.  
+ A 3x3 matrix is used for transformations in a 2-D x-y plane. Affine transformation matrices can be multiplied to form any number of linear transformations, such as rotation and skew (shear), followed by translation. An affine transformation matrix has its final column equal to (0, 0, 1), so only the members in the first two columns need to be specified.  Note that vectors are expressed as row-vectors, not column vectors.  
   
  A [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Media.Matrix> is stored using row-major order and has the following structure:  
   

From 4c1664856d0e0111c2720588cefee8d59af0328e Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:27:25 -0800
Subject: [PATCH 060/236] tla2sharptla-3d

---
 xml/System.Windows.Controls/Viewport3D.xml             | 2 +-
 xml/System.Windows.Media.Media3D/MatrixTransform3D.xml | 4 ++--
 xml/System.Windows.Media.Media3D/Model3DGroup.xml      | 2 +-
 xml/System.Windows.Media.Media3D/RotateTransform3D.xml | 4 ++--
 xml/System.Windows.Media.Media3D/SpecularMaterial.xml  | 2 +-
 xml/System.Windows.Media.Media3D/Vector3D.xml          | 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Windows.Controls/Viewport3D.xml b/xml/System.Windows.Controls/Viewport3D.xml
index deec4398a44..d4ce366724b 100644
--- a/xml/System.Windows.Controls/Viewport3D.xml
+++ b/xml/System.Windows.Controls/Viewport3D.xml
@@ -127,7 +127,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property represents the viewing projection of the [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] scene.  
+ This property represents the viewing projection of the 3-D scene.  
   
 <a name="dependencyPropertyInfo_CameraProperty"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml b/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
index 68f3738be81..ba9c6d480f5 100644
--- a/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
@@ -220,7 +220,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> that specifies a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] transformation.</summary>
-        <value>A Matrix3D that specifies a [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] transformation.</value>
+        <value>A Matrix3D that specifies a 3-D transformation.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -291,7 +291,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets a matrix representation of the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] transformation.</summary>
-        <value>A <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> representation of the [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] transformation.</value>
+        <value>A <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> representation of the 3-D transformation.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media.Media3D/Model3DGroup.xml b/xml/System.Windows.Media.Media3D/Model3DGroup.xml
index 673859a563a..7c03ec7e418 100644
--- a/xml/System.Windows.Media.Media3D/Model3DGroup.xml
+++ b/xml/System.Windows.Media.Media3D/Model3DGroup.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Media3D.Model3DGroup> allows a developer to apply transformations, animations, or other processes to a group of [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] models as though they were a single model.  
+ <xref:System.Windows.Media.Media3D.Model3DGroup> allows a developer to apply transformations, animations, or other processes to a group of 3-D models as though they were a single model.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
index 5e913b5a241..ed95522b38c 100644
--- a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
@@ -24,9 +24,9 @@
 ## Remarks  
  Rotations in [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] usually consist of two arguments: a point around which to rotate an object or set of objects, and a value in degrees or radians that determines the amount of rotation. In [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)], it is necessary to specify a <xref:System.Windows.Media.Media3D.Vector3D> rather than a point around which to rotate.  
   
- Rotations in [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] become more complicated when they are animated.  To animate a [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] rotation using <xref:System.Windows.Media.Media3D.RotateTransform3D>, you can animate the <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Angle%2A> or <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Axis%2A> properties of an <xref:System.Windows.Media.Media3D.AxisAngleRotation3D>, or specify a <xref:System.Windows.Media.Media3D.QuaternionRotation3D> for the transform. 
+ Rotations in 3-D become more complicated when they are animated.  To animate a 3-D rotation using <xref:System.Windows.Media.Media3D.RotateTransform3D>, you can animate the <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Angle%2A> or <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Axis%2A> properties of an <xref:System.Windows.Media.Media3D.AxisAngleRotation3D>, or specify a <xref:System.Windows.Media.Media3D.QuaternionRotation3D> for the transform. 
   
- Axis/angle rotations in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] are specified in degrees, not radians.  
+ Axis/angle rotations in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] 3-D are specified in degrees, not radians.  
   
    
   
diff --git a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
index d9035b1d120..27c86643f16 100644
--- a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
+++ b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
@@ -356,7 +356,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value that specifies the degree to which a material applied to a 3-D model reflects the lighting model as shine.</summary>
-        <value>Relative contribution, for a material applied as a 2-D brush to a [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] model, of the specular component of the lighting model.</value>
+        <value>Relative contribution, for a material applied as a 2-D brush to a 3-D model, of the specular component of the lighting model.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media.Media3D/Vector3D.xml b/xml/System.Windows.Media.Media3D/Vector3D.xml
index 4a7a3b886da..464901fc36c 100644
--- a/xml/System.Windows.Media.Media3D/Vector3D.xml
+++ b/xml/System.Windows.Media.Media3D/Vector3D.xml
@@ -1395,7 +1395,7 @@
         <Parameter Name="source" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="source">The <see cref="T:System.String" /> representation of the [!INCLUDE[TLA2#tla_3d](~/includes/tla2sharptla-3d-md.md)] vector.</param>
+        <param name="source">The <see cref="T:System.String" /> representation of the 3-D vector.</param>
         <summary>Converts a <see cref="T:System.String" /> representation of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] vector into the equivalent <see cref="T:System.Windows.Media.Media3D.Vector3D" /> structure.</summary>
         <returns>The equivalent <see cref="T:System.Windows.Media.Media3D.Vector3D" /> structure.</returns>
         <remarks>

From 54ccb6dab9702524179bbb5a2434a8e27257573d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:28:12 -0800
Subject: [PATCH 061/236] tla2sharptla-baml

---
 .../BamlLocalizabilityResolver.xml                 | 14 +++++++-------
 .../BamlLocalizableResource.xml                    |  2 +-
 .../BamlLocalizableResourceKey.xml                 |  6 +++---
 3 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
index e11f22887e1..637bfbe83ae 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
@@ -21,15 +21,15 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Markup.Localizer.BamlLocalizabilityResolver> is used by the <xref:System.Windows.Markup.Localizer.BamlLocalizer> in order to resolve localizability settings for classes and properties in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)]. The resolver is called both at the time of resource extraction as well as when localized [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] is updated.  
+ <xref:System.Windows.Markup.Localizer.BamlLocalizabilityResolver> is used by the <xref:System.Windows.Markup.Localizer.BamlLocalizer> in order to resolve localizability settings for classes and properties in BAML. The resolver is called both at the time of resource extraction as well as when localized BAML is updated.  
   
  At the time of resource extraction (<xref:System.Windows.Markup.Localizer.BamlLocalizer.ExtractResources%2A>), the resolver:  
   
--   Provides <xref:System.Windows.LocalizabilityAttribute> for classes and properties in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] when the <xref:System.Windows.Markup.Localizer.BamlLocalizer> is constructing localizable resources.  
+-   Provides <xref:System.Windows.LocalizabilityAttribute> for classes and properties in BAML when the <xref:System.Windows.Markup.Localizer.BamlLocalizer> is constructing localizable resources.  
   
--   Provides formatting preferences for elements in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] so elements are formatted as inline tags.  
+-   Provides formatting preferences for elements in BAML so elements are formatted as inline tags.  
   
- At the time at which localized [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] is updated (<xref:System.Windows.Markup.Localizer.BamlLocalizer.UpdateBaml%2A>), the resolver:  
+ At the time at which localized BAML is updated (<xref:System.Windows.Markup.Localizer.BamlLocalizer.UpdateBaml%2A>), the resolver:  
   
 -   Resolves formatting tags back into classes.  
   
@@ -90,7 +90,7 @@
         <Parameter Name="className" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="assembly">The full name of the assembly that contains [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] to be localized.</param>
+        <param name="assembly">The full name of the assembly that contains BAML to be localized.</param>
         <param name="className">The full class name of the element that you want to retrieve localizability information for.</param>
         <summary>Returns a value that indicates whether a specified type of element can be localized and, if so, whether it can be formatted inline.</summary>
         <returns>An object that contains the localizability information for the specified assembly and element.</returns>
@@ -120,7 +120,7 @@
         <Parameter Name="property" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="assembly">The full name of the assembly that contains [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] to be localized.</param>
+        <param name="assembly">The full name of the assembly that contains BAML to be localized.</param>
         <param name="className">The full class name of the element that you want to retrieve localizability information for.</param>
         <param name="property">The name of the property that you want to retrieve localizability information for.</param>
         <summary>Returns a value that indicates whether a specified property of a specified type of element can be localized.</summary>
@@ -177,7 +177,7 @@
       </Parameters>
       <Docs>
         <param name="formattingTag">The name of the tag.</param>
-        <summary>Returns the full class name of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] tag that has not been encountered in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)].</summary>
+        <summary>Returns the full class name of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] tag that has not been encountered in BAML.</summary>
         <returns>The full class name associated with the tag.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
index afd24b2f7f5..f96b99a60c6 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
@@ -169,7 +169,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Localization comments are authored by the developer to provide rules or hints for localizers. The comments are free-form strings that are extracted from [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] or from localization comments files. To attach comments to an element in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], use the <xref:System.Windows.Localization.Comments%2A?displayProperty=nameWithType> attached property For more information on this attached property, see [Localization Attributes and Comments](/dotnet/framework/wpf/advanced/localization-attributes-and-comments).  
+ Localization comments are authored by the developer to provide rules or hints for localizers. The comments are free-form strings that are extracted from BAML or from localization comments files. To attach comments to an element in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], use the <xref:System.Windows.Localization.Comments%2A?displayProperty=nameWithType> attached property For more information on this attached property, see [Localization Attributes and Comments](/dotnet/framework/wpf/advanced/localization-attributes-and-comments).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
index 912409f6244..3d069fae3f0 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class represents a key that can uniquely identify a localizable value inside [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)]. It represents a combination of a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A>, class name, and property name.  
   
- The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
+ The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
   
  `<TextBlock x:Uid="myBlock">Click </TextBlock>`  
     
@@ -68,7 +68,7 @@
       <Docs>
         <param name="uid">The Uid of an element that has a localizable resource.</param>
         <param name="className">The class name of a localizable resource in [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)].</param>
-        <param name="propertyName">The property name of a localizable resource in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)].</param>
+        <param name="propertyName">The property name of a localizable resource in BAML.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Markup.Localizer.BamlLocalizableResourceKey" /> class with the supplied Uid, class name, and property name.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -103,7 +103,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The assembly name is not required to uniquely identify a resource in [!INCLUDE[TLA2#tla_baml](~/includes/tla2sharptla-baml-md.md)] but is included here as a convenience.  
+ The assembly name is not required to uniquely identify a resource in BAML but is included here as a convenience.  
   
  ]]></format>
         </remarks>

From f0fa1ec06481a0a1b0838dbeabd3c5e76e080a89 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:28:58 -0800
Subject: [PATCH 062/236] tla2sharptla-bpp

---
 xml/System.Windows.Media/PixelFormats.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Media/PixelFormats.xml b/xml/System.Windows.Media/PixelFormats.xml
index 60cc81e1aaa..76f4182900e 100644
--- a/xml/System.Windows.Media/PixelFormats.xml
+++ b/xml/System.Windows.Media/PixelFormats.xml
@@ -802,7 +802,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> is a ScRGB format with 128 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is allocated 32 [!INCLUDE[tla2#tla_bpp](~/includes/tla2sharptla-bpp-md.md)]. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> is a ScRGB format with 128 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is allocated 32 BPP. This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From c52cecbd479ae669d21e5a72e710d49fd69c1244 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:29:20 -0800
Subject: [PATCH 063/236] tla2sharptla-caf

---
 xml/System.Windows.Annotations.Storage/XmlStreamStore.xml | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml b/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
index 2261ad67498..b7626a8a293 100644
--- a/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
+++ b/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
@@ -447,7 +447,7 @@
 ## Remarks  
  The `name` parameter works only for predefined [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)] namespaces.  For any other namespace given in the `name` parameter <xref:System.Windows.Annotations.Storage.XmlStreamStore.GetWellKnownCompatibleNamespaces%2A> will return `null`, even those namespaces registered through the `knownNamespaces` parameter of the <xref:System.Windows.Annotations.Storage.XmlStreamStore.%23ctor%2A> constructor.  
   
- The namespaces predefined by the [!INCLUDE[TLA2#tla_caf](~/includes/tla2sharptla-caf-md.md)] include the following:  
+ The namespaces predefined by the Annotations Framework include the following:  
   
 - `http://schemas.microsoft.com/windows/annotations/2003/11/core`
   
@@ -494,7 +494,7 @@
 ## Remarks  
  The <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> property will never return `null`, however the returned list can be empty if no namespaces are ignored.  
   
- <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> helps in XML markup compatibility when the program reads annotation content created by different versions of the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)].  When an older application is given annotation content created using a newer version of the [!INCLUDE[TLA2#tla_caf](~/includes/tla2sharptla-caf-md.md)], <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> returns a list of the XML namespaces for elements and attributes not known to the older framework.  Unknown XML elements and attributes associated with newer namespaces are ignored when the annotation content is read and deserialized by the older application.  For more information see the *XML Markup Compatibility Specification* available at [https://go.microsoft.com/fwlink/?LinkId=73824](https://go.microsoft.com/fwlink/?LinkId=73824).  
+ <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> helps in XML markup compatibility when the program reads annotation content created by different versions of the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)].  When an older application is given annotation content created using a newer version of the Annotations Framework, <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> returns a list of the XML namespaces for elements and attributes not known to the older framework.  Unknown XML elements and attributes associated with newer namespaces are ignored when the annotation content is read and deserialized by the older application.  For more information see the *XML Markup Compatibility Specification* available at [https://go.microsoft.com/fwlink/?LinkId=73824](https://go.microsoft.com/fwlink/?LinkId=73824).  
   
  ]]></format>
         </remarks>
@@ -547,13 +547,13 @@
         <ReturnType>System.Collections.Generic.IList&lt;System.Uri&gt;</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a list of all namespaces that are predefined by the [!INCLUDE[TLA2#tla_caf](~/includes/tla2sharptla-caf-md.md)].</summary>
+        <summary>Gets a list of all namespaces that are predefined by the Annotations Framework.</summary>
         <value>The list of namespaces that are predefined by the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)].</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The namespaces predefined by the [!INCLUDE[TLA2#tla_caf](~/includes/tla2sharptla-caf-md.md)] include the following:  
+ The namespaces predefined by the Annotations Framework include the following:  
   
 - `http://schemas.microsoft.com/windows/annotations/2003/11/core`
   

From 4fc3a053046571ecb38bfc12c94a727cf3e611ac Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:29:50 -0800
Subject: [PATCH 064/236] tla2sharptla-clr

---
 .../DependencyPropertyDescriptor.xml          |  4 +--
 xml/System.Windows.Controls/StyleSelector.xml |  4 +--
 xml/System.Windows.Data/Binding.xml           |  2 +-
 xml/System.Windows.Input/Mouse.xml            |  8 ++---
 .../XmlnsDefinitionAttribute.xml              |  4 +--
 xml/System.Windows/ContentElement.xml         | 24 +++++++--------
 xml/System.Windows/DependencyObject.xml       |  8 ++---
 xml/System.Windows/DependencyObjectType.xml   | 12 ++++----
 xml/System.Windows/DependencyProperty.xml     |  8 ++---
 xml/System.Windows/EventManager.xml           |  2 +-
 .../FrameworkContentElement.xml               |  2 +-
 xml/System.Windows/LocalValueEnumerator.xml   |  2 +-
 xml/System.Windows/PropertyPath.xml           |  4 +--
 xml/System.Windows/UIElement.xml              | 30 +++++++++----------
 xml/System.Windows/UIElement3D.xml            | 28 ++++++++---------
 15 files changed, 71 insertions(+), 71 deletions(-)

diff --git a/xml/System.ComponentModel/DependencyPropertyDescriptor.xml b/xml/System.ComponentModel/DependencyPropertyDescriptor.xml
index 583c818cb20..bc827de8b6f 100644
--- a/xml/System.ComponentModel/DependencyPropertyDescriptor.xml
+++ b/xml/System.ComponentModel/DependencyPropertyDescriptor.xml
@@ -811,7 +811,7 @@
 ## Remarks  
  This property relies on the underlying <xref:System.ComponentModel.PropertyDescriptor>.  
   
- Dependency properties are registered as read-only using particular method calls, and by convention the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] wrapper properties that are the properties viewed by reflection and the descriptors must also be read-only. However, since this is a convention and not a requirement to compile, you might want to double check the dependency property identifier read-only state. To do this, get the identifier (<xref:System.Windows.DependencyProperty>) value for this <xref:System.ComponentModel.DependencyPropertyDescriptor> and then check the value of <xref:System.Windows.DependencyProperty.ReadOnly%2A>. Note that the <xref:System.Windows.DependencyProperty.ReadOnly%2A> is on the identifier itself, not metadata.  
+ Dependency properties are registered as read-only using particular method calls, and by convention the CLR wrapper properties that are the properties viewed by reflection and the descriptors must also be read-only. However, since this is a convention and not a requirement to compile, you might want to double check the dependency property identifier read-only state. To do this, get the identifier (<xref:System.Windows.DependencyProperty>) value for this <xref:System.ComponentModel.DependencyPropertyDescriptor> and then check the value of <xref:System.Windows.DependencyProperty.ReadOnly%2A>. Note that the <xref:System.Windows.DependencyProperty.ReadOnly%2A> is on the identifier itself, not metadata.  
   
  ]]></format>
         </remarks>
@@ -849,7 +849,7 @@
 ## Remarks  
  The value can be `null` if there is  no metadata or if the property is not a dependency property.  
   
- Metadata that has matching concepts in [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] attributes is re-exposed as attributes in the <xref:System.ComponentModel.DependencyPropertyDescriptor.Attributes%2A> collection.  
+ Metadata that has matching concepts in CLR attributes is re-exposed as attributes in the <xref:System.ComponentModel.DependencyPropertyDescriptor.Attributes%2A> collection.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/StyleSelector.xml b/xml/System.Windows.Controls/StyleSelector.xml
index 134d3c14ea1..9be0624d5e6 100644
--- a/xml/System.Windows.Controls/StyleSelector.xml
+++ b/xml/System.Windows.Controls/StyleSelector.xml
@@ -31,7 +31,7 @@
  [!code-csharp[ListViewSnips#ItemStyleSelector](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewSnips/CSharp/Window1.xaml.cs#itemstyleselector)]
  [!code-vb[ListViewSnips#ItemStyleSelector](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ListViewSnips/visualbasic/window1.xaml.vb#itemstyleselector)]  
   
- The following example shows how to define a <xref:System.Windows.ResourceKey> for the <xref:System.Windows.Controls.StyleSelector>. The `namespc` prefix maps to a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] namespace and the corresponding assembly where the <xref:System.Windows.Controls.StyleSelector> is defined. For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
+ The following example shows how to define a <xref:System.Windows.ResourceKey> for the <xref:System.Windows.Controls.StyleSelector>. The `namespc` prefix maps to a CLR namespace and the corresponding assembly where the <xref:System.Windows.Controls.StyleSelector> is defined. For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
   
  [!code-xaml[ListViewSnips#myStyleSelectorKey](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewSnips/CSharp/Window1.xaml#mystyleselectorkey)]  
   
@@ -113,7 +113,7 @@
  [!code-csharp[ListViewSnips#ItemStyleSelector](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewSnips/CSharp/Window1.xaml.cs#itemstyleselector)]
  [!code-vb[ListViewSnips#ItemStyleSelector](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ListViewSnips/visualbasic/window1.xaml.vb#itemstyleselector)]  
   
- The following example shows how to define a <xref:System.Windows.ResourceKey> for the <xref:System.Windows.Controls.StyleSelector>. The `namespc` prefix maps to a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] namespace and the corresponding assembly where the <xref:System.Windows.Controls.StyleSelector> is defined. For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
+ The following example shows how to define a <xref:System.Windows.ResourceKey> for the <xref:System.Windows.Controls.StyleSelector>. The `namespc` prefix maps to a CLR namespace and the corresponding assembly where the <xref:System.Windows.Controls.StyleSelector> is defined. For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
   
  [!code-xaml[ListViewSnips#myStyleSelectorKey](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewSnips/CSharp/Window1.xaml#mystyleselectorkey)]  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 76cbe47cef2..cfde100fed2 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -33,7 +33,7 @@
   
 -   The target property must be a dependency property. This also means that you cannot bind a field. Most properties of <xref:System.Windows.UIElement> objects are dependency properties and most dependency properties, except read-only ones, support data binding by default. (Only <xref:System.Windows.DependencyObject> types can define dependency properties and all <xref:System.Windows.UIElement> objects derive from <xref:System.Windows.DependencyObject>.)  
   
--   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] object. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding supports data in the form of [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] objects and [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data.  
+-   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding supports data in the form of CLR objects and [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data.  
   
  Use the <xref:System.Windows.Data.Binding.Mode%2A> property to specify the direction of the data flow. To detect source changes in one-way or two-way bindings, the source must implement a suitable property change notification mechanism such as <xref:System.ComponentModel.INotifyPropertyChanged>. For an example, see [How to: Implement Property Change Notification](/dotnet/framework/wpf/data/how-to-implement-property-change-notification). The <xref:System.Windows.Data.Binding.UpdateSourceTrigger%2A> property specifies the timing of source updates. For more information, see "Basic Data Binding Concepts" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 970b9822a48..01672659041 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -970,7 +970,7 @@
   
 -   Register a handler on the control procedurally by calling <xref:System.Windows.UIElement.AddHandler%2A> and choosing the signature option that enables handlers to listen for events even if they are already marked as handled in the routed event data.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying mouse routed event be surfaced as [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] events along the route. Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by further children toward the source, and how would that affect compositing a control where the compositing pieces might have expected mouse behaviors?  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying mouse routed event be surfaced as CLR events along the route. Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by further children toward the source, and how would that affect compositing a control where the compositing pieces might have expected mouse behaviors?  
   
 <a name="routedEventInfo_MouseDown"></a>   
 ## Routed Event Information  
@@ -1238,7 +1238,7 @@
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] events all along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events all along the route.  
   
  Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by children further towards the source, and how would that affect compositing in a control where the compositing pieces might have expected mouse behaviors?  
   
@@ -1450,7 +1450,7 @@
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] events along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
 <a name="routedEventInfo_PreviewMouseDown"></a>   
 ## Routed Event Information  
@@ -1653,7 +1653,7 @@
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] events along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
 ## Routed Event Information  
   
diff --git a/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml b/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
index 041c197b3e8..5ec4fe53951 100644
--- a/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
+++ b/xml/System.Windows.Markup/XmlnsDefinitionAttribute.xml
@@ -77,7 +77,7 @@
       </Parameters>
       <Docs>
         <param name="xmlNamespace">The XAML namespace identifier.</param>
-        <param name="clrNamespace">A string that references a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] namespace name.</param>
+        <param name="clrNamespace">A string that references a CLR namespace name.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Markup.XmlnsDefinitionAttribute" /> class.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
@@ -154,7 +154,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the string name of the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] namespace specified in this attribute.</summary>
+        <summary>Gets the string name of the CLR namespace specified in this attribute.</summary>
         <value>The CLR namespace, specified as a string.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index 5ecabd44437..64af0022697 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -1304,7 +1304,7 @@ where `myElement` is the class name of the type that you are overriding the meta
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2017,7 +2017,7 @@ where `myElement` is the class name of the type that you are overriding the meta
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2249,7 +2249,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2350,7 +2350,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2455,7 +2455,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2552,7 +2552,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2655,7 +2655,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2830,7 +2830,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -2926,7 +2926,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3032,7 +3032,7 @@ The default implementation of this property caches the value and also calculates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -10463,11 +10463,11 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] level. The example that follows this remarks section illustrates this scenario.  
+ The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
   
  Calling this method has no effect if there were no handlers registered with criteria that match the input parameters for the method call.  
   
- If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] behavior of the `-=` operator.  
+ If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with CLR behavior of the `-=` operator.  
   
  Neither `routedEvent` nor `handler` may be `null`. Attempting to provide either value as `null` will raise an exception.  
   
diff --git a/xml/System.Windows/DependencyObject.xml b/xml/System.Windows/DependencyObject.xml
index ea098bafc56..370de3ee55c 100644
--- a/xml/System.Windows/DependencyObject.xml
+++ b/xml/System.Windows/DependencyObject.xml
@@ -238,13 +238,13 @@
         <ReturnType>System.Windows.DependencyObjectType</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="T:System.Windows.DependencyObjectType" /> that wraps the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] type of this instance.</summary>
-        <value>A <see cref="T:System.Windows.DependencyObjectType" /> that wraps the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] type of this instance.</value>
+        <summary>Gets the <see cref="T:System.Windows.DependencyObjectType" /> that wraps the CLR type of this instance.</summary>
+        <value>A <see cref="T:System.Windows.DependencyObjectType" /> that wraps the CLR type of this instance.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is useful if an object that is returned from a method has a return value type of <xref:System.Windows.DependencyObject> and you want to perform property system specific operations on it depending on its type. For example it is more efficient to call <xref:System.Windows.DependencyProperty.GetMetadata%28System.Windows.DependencyObjectType%29> using the <xref:System.Windows.DependencyObjectType> rather than the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] type. <xref:System.Windows.DependencyObjectType> facilitates faster lookup.  
+ This property is useful if an object that is returned from a method has a return value type of <xref:System.Windows.DependencyObject> and you want to perform property system specific operations on it depending on its type. For example it is more efficient to call <xref:System.Windows.DependencyProperty.GetMetadata%28System.Windows.DependencyObjectType%29> using the <xref:System.Windows.DependencyObjectType> rather than the CLR type. <xref:System.Windows.DependencyObjectType> facilitates faster lookup.  
   
    
   
@@ -707,7 +707,7 @@
    
   
 ## Examples  
- The following example defines a read-only dependency property, along with a `public static readonly` <xref:System.Windows.DependencyProperty> that provides necessary read-only exposure to property consumers, and the get accessor for the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] wrapper.  
+ The following example defines a read-only dependency property, along with a `public static readonly` <xref:System.Windows.DependencyProperty> that provides necessary read-only exposure to property consumers, and the get accessor for the CLR wrapper.  
   
  [!code-csharp[WPFAquariumSln#RODP](~/samples/snippets/csharp/VS_Snippets_Wpf/WPFAquariumSln/CSharp/WPFAquariumObjects/Class1.cs#rodp)]
  [!code-vb[WPFAquariumSln#RODP](~/samples/snippets/visualbasic/VS_Snippets_Wpf/WPFAquariumSln/visualbasic/wpfaquariumobjects/class1.vb#rodp)]  
diff --git a/xml/System.Windows/DependencyObjectType.xml b/xml/System.Windows/DependencyObjectType.xml
index 1329b5bb7e2..c7326c9ada2 100644
--- a/xml/System.Windows/DependencyObjectType.xml
+++ b/xml/System.Windows/DependencyObjectType.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.DependencyObjectType> represents a specific underlying system ([!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)]) <xref:System.Type> of a <xref:System.Windows.DependencyObject>. <xref:System.Windows.DependencyObjectType> is essentially a wrapper for the ([!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)]) <xref:System.Type> so that it can extend some of its capabilities.  
+ <xref:System.Windows.DependencyObjectType> represents a specific underlying system (CLR) <xref:System.Type> of a <xref:System.Windows.DependencyObject>. <xref:System.Windows.DependencyObjectType> is essentially a wrapper for the (CLR) <xref:System.Type> so that it can extend some of its capabilities.  
   
  This class has no public constructor. Instances of this class can only be obtained through properties on other objects (such as <xref:System.Windows.DependencyObject.DependencyObjectType%2A?displayProperty=nameWithType>), or through the static method <xref:System.Windows.DependencyObjectType.FromSystemType%2A>.  
   
@@ -80,9 +80,9 @@
         <Parameter Name="systemType" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="systemType">The system ([!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)]) type to convert.</param>
-        <summary>Returns a <see cref="T:System.Windows.DependencyObjectType" /> that represents a given system ([!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)]) type.</summary>
-        <returns>A <see cref="T:System.Windows.DependencyObjectType" /> that represents the system ([!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)]) type.</returns>
+        <param name="systemType">The system (CLR) type to convert.</param>
+        <summary>Returns a <see cref="T:System.Windows.DependencyObjectType" /> that represents a given system (CLR) type.</summary>
+        <returns>A <see cref="T:System.Windows.DependencyObjectType" /> that represents the system (CLR) type.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -250,7 +250,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the name of the represented [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] system type.</summary>
-        <value>The name of the represented [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] system type.</value>
+        <value>The name of the represented CLR system type.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -287,7 +287,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</summary>
-        <value>The [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</value>
+        <value>The CLR system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index e4f965b75ee..9c0b5a08ac3 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -142,7 +142,7 @@
   
  This signature does not allow for specifying metadata.  When you use this method, the metadata is automatically generated for the new <xref:System.Windows.DependencyProperty> and its owner type. The auto-generated metadata is the result of the merged metadata from all of the base types that have this property defined. If no merged metadata is available, then the default metadata for the property is used. If the property is registered by using the <xref:System.Windows.DependencyProperty.RegisterAttached%2A> method, then the default metadata is the same as the metadata that is created when <xref:System.Windows.DependencyProperty.RegisterAttached%2A> was called. Otherwise, the <xref:System.Windows.PropertyMetadata> object is created with the <xref:System.Windows.PropertyMetadata.DefaultValue%2A> property set to the property type's default and all other properties of the <xref:System.Windows.PropertyMetadata> is set to `null`. Use the <xref:System.Windows.DependencyProperty.AddOwner%28System.Type%2CSystem.Windows.PropertyMetadata%29> signature if you want to provide metadata for the version of the dependency property as added to the provided type.  
   
- The return value of this method is typically used to declare and expose the dependency property by storing a dependency property identifier. The identifier provides access to the dependency property if you want to call property system APIs against the dependency property, particularly as it exists on the adding owner class. The same property name for both original owner and added owner should be used to indicate the similar functionality. You should use the <xref:System.Windows.DependencyProperty> return value of the <xref:System.Windows.DependencyProperty.AddOwner%2A> method to define the dependency property identifier, and also to declare [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
+ The return value of this method is typically used to declare and expose the dependency property by storing a dependency property identifier. The identifier provides access to the dependency property if you want to call property system APIs against the dependency property, particularly as it exists on the adding owner class. The same property name for both original owner and added owner should be used to indicate the similar functionality. You should use the <xref:System.Windows.DependencyProperty> return value of the <xref:System.Windows.DependencyProperty.AddOwner%2A> method to define the dependency property identifier, and also to declare CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
   
  The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating the dependency properties that are declared within [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> based on the original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a new static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
   
@@ -182,11 +182,11 @@
 ## Remarks  
  This method enables the property system to recognize a dependency property on a type that did not register that particular dependency property initially.  
   
- The return value of this method is used to declare and expose the dependency property, particularly as it exists on the adding owner class. Generally, the same property name for both original owner and added owner should be used to indicate the similar functionality. It is good practice to expose the identifiers, as well as new [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
+ The return value of this method is used to declare and expose the dependency property, particularly as it exists on the adding owner class. Generally, the same property name for both original owner and added owner should be used to indicate the similar functionality. It is good practice to expose the identifiers, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
   
  The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating APIs declared within [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> on original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
   
- The added owner's dependency property identifier should be used for operations such as <xref:System.Windows.DependencyObject.GetValue%2A>. However, type-specific operations involving either types or instances of the class that was added as owner with different metadata will still return the expected results even if the original (not the added owner's) dependency property identifier is specified in calls to methods such as <xref:System.Windows.DependencyObject.GetValue%2A> or <xref:System.Windows.DependencyProperty.GetMetadata%2A>. The metadata for the added owner is perpetuated by the <xref:System.Windows.DependencyProperty.AddOwner%2A> call itself, not necessarily referenced exclusively by the adding owner class identifier field. Nevertheless, it is good practice to expose the  identifier, as well as new [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>, because failing to do so creates disparity between the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representations of your properties.  
+ The added owner's dependency property identifier should be used for operations such as <xref:System.Windows.DependencyObject.GetValue%2A>. However, type-specific operations involving either types or instances of the class that was added as owner with different metadata will still return the expected results even if the original (not the added owner's) dependency property identifier is specified in calls to methods such as <xref:System.Windows.DependencyObject.GetValue%2A> or <xref:System.Windows.DependencyProperty.GetMetadata%2A>. The metadata for the added owner is perpetuated by the <xref:System.Windows.DependencyProperty.AddOwner%2A> call itself, not necessarily referenced exclusively by the adding owner class identifier field. Nevertheless, it is good practice to expose the  identifier, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>, because failing to do so creates disparity between the CLR and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representations of your properties.  
   
  The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist. Only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics, such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A>, are replaced if they are specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
   
@@ -804,7 +804,7 @@
   
  Read-only dependency properties require a <xref:System.Windows.DependencyPropertyKey> identifier rather than a <xref:System.Windows.DependencyProperty> identifier to perform metadata operations such as overriding the metadata or setting the value. If you obtained a collection of <xref:System.Windows.DependencyProperty> identifiers through a call to <xref:System.Windows.DependencyObject.GetLocalValueEnumerator%2A> or another API that exposes identifiers, check the <xref:System.Windows.DependencyProperty.ReadOnly%2A> value before attempting to call <xref:System.Windows.DependencyObject.SetValue%2A> or <xref:System.Windows.DependencyProperty.OverrideMetadata%2A> using that dependency property identifier as an input parameter, to verify that the dependency property that the identifier represents is not read-only. If the value of <xref:System.Windows.DependencyProperty.ReadOnly%2A> is `true` on a dependency property, there is no programmatic way to obtain a reference to the <xref:System.Windows.DependencyPropertyKey> identifier of that dependency property, from the metadata or from the <xref:System.Windows.DependencyProperty> identifier; the identifier must be available as a static field in order to call <xref:System.Windows.DependencyObject.SetValue%28System.Windows.DependencyPropertyKey%2CSystem.Object%29> against a read-only dependency property.  
   
- When you create a custom dependency property, and register it as read-only, you should define only a get accessor for the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] wrapper property. Otherwise, your class will have a confusing object model for the property wrapper as compared to the access to the backing dependency property. For details, see [Custom Dependency Properties](/dotnet/framework/wpf/advanced/custom-dependency-properties) or [Read-Only Dependency Properties](/dotnet/framework/wpf/advanced/read-only-dependency-properties).  
+ When you create a custom dependency property, and register it as read-only, you should define only a get accessor for the CLR wrapper property. Otherwise, your class will have a confusing object model for the property wrapper as compared to the access to the backing dependency property. For details, see [Custom Dependency Properties](/dotnet/framework/wpf/advanced/custom-dependency-properties) or [Read-Only Dependency Properties](/dotnet/framework/wpf/advanced/read-only-dependency-properties).  
   
    
   
diff --git a/xml/System.Windows/EventManager.xml b/xml/System.Windows/EventManager.xml
index ec502d2db1e..310613770ca 100644
--- a/xml/System.Windows/EventManager.xml
+++ b/xml/System.Windows/EventManager.xml
@@ -28,7 +28,7 @@
    
   
 ## Examples  
- The following example show how to use this class to register a new routed event as a class member, along with the routed event "wrapper" technique of overriding the add and remove implementations for a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event.  
+ The following example show how to use this class to register a new routed event as a class member, along with the routed event "wrapper" technique of overriding the add and remove implementations for a CLR event.  
   
  [!code-csharp[DPCustom#EventManagerClass](~/samples/snippets/csharp/VS_Snippets_Wpf/DPCustom/CSharp/default.xaml.cs#eventmanagerclass)]
  [!code-vb[DPCustom#EventManagerClass](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DPCustom/visualbasic/default.xaml.vb#eventmanagerclass)]  
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 9467e199c38..e48fb954e98 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -798,7 +798,7 @@
 <a name="xamlValues_DataContext"></a>   
 ## XAML Values  
  *dataContextObject*  
- A directly embedded object that serves as data context for any bindings within the parent element. Typically, this object is a <xref:System.Windows.Data.Binding> or another <xref:System.Windows.Data.BindingBase> subclass. Alternatively, raw data of any [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] object type intended for binding may be placed here, with the actual bindings defined later.  
+ A directly embedded object that serves as data context for any bindings within the parent element. Typically, this object is a <xref:System.Windows.Data.Binding> or another <xref:System.Windows.Data.BindingBase> subclass. Alternatively, raw data of any CLR object type intended for binding may be placed here, with the actual bindings defined later.  
   
  *bindingUsage*  
  A binding usage that evaluates to an appropriate data context. For details, see [Binding Markup Extension](/dotnet/framework/wpf/advanced/binding-markup-extension).  
diff --git a/xml/System.Windows/LocalValueEnumerator.xml b/xml/System.Windows/LocalValueEnumerator.xml
index 68669243b9a..1cb048cedae 100644
--- a/xml/System.Windows/LocalValueEnumerator.xml
+++ b/xml/System.Windows/LocalValueEnumerator.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A *local value* is a value for a dependency property that was set directly on a dependency property, by calling <xref:System.Windows.DependencyObject.SetValue%2A>, or more typically by using the set accessor of a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] property wrapper that calls <xref:System.Windows.DependencyObject.SetValue%2A> internally. Examples of other property system determinants that are not local values are values set through styles, or dependency property default values. For details, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
+ A *local value* is a value for a dependency property that was set directly on a dependency property, by calling <xref:System.Windows.DependencyObject.SetValue%2A>, or more typically by using the set accessor of a CLR property wrapper that calls <xref:System.Windows.DependencyObject.SetValue%2A> internally. Examples of other property system determinants that are not local values are values set through styles, or dependency property default values. For details, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
   
  A <xref:System.Windows.LocalValueEnumerator> is returned by the <xref:System.Windows.DependencyObject.GetLocalValueEnumerator%2A> method and implements the <xref:System.Collections.IEnumerator> interface. A public <xref:System.Windows.LocalValueEnumerator> constructor does not exist; therefore, you must call <xref:System.Windows.DependencyObject.GetLocalValueEnumerator%2A> to obtain an instance of this class.  
   
diff --git a/xml/System.Windows/PropertyPath.xml b/xml/System.Windows/PropertyPath.xml
index 991fb8f8b6f..f9863871962 100644
--- a/xml/System.Windows/PropertyPath.xml
+++ b/xml/System.Windows/PropertyPath.xml
@@ -89,7 +89,7 @@
 ## Remarks  
  This constructor has two completely different usages depending on whether it is being used for a source-mode property path for a binding, or for a target-mode single-step property path for a storyboard target.  
   
- If using this <xref:System.Windows.PropertyPath> in source mode for a binding, `parameter` is a string representing a property name, or can be a string that describes a "step-through" path to the property in the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] object model of the object that is being used as the source for a binding. For a binding property path, the character that identifies a "step" is a dot (.). Indexer references (including multiple indexers, and type differentiation) are also supported. For more details on the syntax of the string as specifically used by the <xref:System.Windows.Data.Binding> object, see <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. A property used as a binding source need not be a dependency property. If the binding updates two-way, the property referenced must be read-write. Also note that the binding target does have to be a dependency property. For details, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
+ If using this <xref:System.Windows.PropertyPath> in source mode for a binding, `parameter` is a string representing a property name, or can be a string that describes a "step-through" path to the property in the CLR object model of the object that is being used as the source for a binding. For a binding property path, the character that identifies a "step" is a dot (.). Indexer references (including multiple indexers, and type differentiation) are also supported. For more details on the syntax of the string as specifically used by the <xref:System.Windows.Data.Binding> object, see <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. A property used as a binding source need not be a dependency property. If the binding updates two-way, the property referenced must be read-write. Also note that the binding target does have to be a dependency property. For details, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
  If using this <xref:System.Windows.PropertyPath> in target mode for a single-step path for a storyboard target, `parameter` is generally provided as type <xref:System.Windows.DependencyProperty>. You can also specify a string that is the <xref:System.Windows.DependencyProperty.Name%2A>. Either of these evaluate to the same result, because it is stored internally as a string. A provided <xref:System.Windows.DependencyProperty> is converted to a string through <xref:System.Windows.Markup.DependencyPropertyConverter>. The <xref:System.Windows.Markup.DependencyPropertyConverter> supports a qualified naming format for dependency properties, so you can specify a *typeName*.*propertyName* qualified dependency property name string to the <xref:System.Windows.PropertyPath.%23ctor%2A?displayProperty=nameWithType> constructor in code. The qualified path to the dependency property identifier is a different concept than a complex path. A complex-path <xref:System.Windows.PropertyPath> should instead be created with the <xref:System.Windows.PropertyPath.%23ctor%2A?displayProperty=nameWithType> constructor.  
   
@@ -173,7 +173,7 @@
 ## Remarks  
  The string contained in this property has three completely different meanings depending on whether a <xref:System.Windows.PropertyPath> is being used for a source-mode property path for a binding, for a target-mode single-step property path for a storyboard target, or for a complex path for a storyboard target.  
   
- If using this <xref:System.Windows.PropertyPath> in source mode for a binding, <xref:System.Windows.PropertyPath.Path%2A> is a string representing a property name, or can be a string that describes a "step-through" path to the property in the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] object model of the object that is being used as the source for a binding. For a binding property path, the character that identifies a "step" is a dot (.). Indexer references (including multiple indexers, and type differentiation) are also supported. For more details on the syntax of the string as specifically used by the <xref:System.Windows.Data.Binding> object, see <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. A property used as a binding source need not be a dependency property. If the binding updates two-way, the property source must be read-write. Also note that the binding target does have to be a dependency property. For details, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
+ If using this <xref:System.Windows.PropertyPath> in source mode for a binding, <xref:System.Windows.PropertyPath.Path%2A> is a string representing a property name, or can be a string that describes a "step-through" path to the property in the CLR object model of the object that is being used as the source for a binding. For a binding property path, the character that identifies a "step" is a dot (.). Indexer references (including multiple indexers, and type differentiation) are also supported. For more details on the syntax of the string as specifically used by the <xref:System.Windows.Data.Binding> object, see <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. A property used as a binding source need not be a dependency property. If the binding updates two-way, the property source must be read-write. Also note that the binding target does have to be a dependency property. For details, see [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
  If using this <xref:System.Windows.PropertyPath> in target mode for a single-step path for a storyboard target, <xref:System.Windows.PropertyPath> is a string that is a *typeName*.*propertyName* qualified dependency property name string.  
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 68517265c59..cbdd76753e8 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -1959,7 +1959,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3014,7 +3014,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3210,7 +3210,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3344,7 +3344,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3447,7 +3447,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3646,7 +3646,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3743,7 +3743,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -3847,7 +3847,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -4027,7 +4027,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -4125,7 +4125,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -4232,7 +4232,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -4404,7 +4404,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This event is not raised if the element is not being rendered by the layout system, for reasons other than the value of the <xref:System.Windows.UIElement.IsVisible%2A> property. For example, the element might not have an associated visual.  
   
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -4613,7 +4613,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  A layout update can occur as a result of a property change, a window resize, or an explicit user request.  
   
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  ]]></format>
         </remarks>
@@ -12858,11 +12858,11 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] level. The example that follows this remarks section illustrates this scenario.  
+ The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
   
  Calling this method has no effect if there were no handlers registered with criteria that matches the input parameters for the method call.  
   
- If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] behavior of the `-=` operator.  
+ If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with CLR behavior of the `-=` operator.  
   
  Neither `routedEvent` nor `handler` may be `null`. Attempting to provide either value as `null` will raise an exception.  
   
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index cba50ba0e7f..51dcff916ac 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -1122,7 +1122,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.FocusableChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -1846,7 +1846,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsEnabledChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2059,7 +2059,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsHitTestVisibleChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2207,7 +2207,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsKeyboardFocusedChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2322,7 +2322,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsKeyboardFocusWithinChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2431,7 +2431,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsMouseCapturedChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2539,7 +2539,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsMouseCaptureWithinChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2654,7 +2654,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsMouseDirectlyOverChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2847,7 +2847,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsStylusCapturedChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -2956,7 +2956,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsStylusCaptureWithinChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -3074,7 +3074,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsStylusDirectlyOverChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -3268,7 +3268,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This member is a [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] event, not a routed event.  
+ This member is a CLR event, not a routed event.  
   
  <xref:System.Windows.UIElement3D.IsVisibleChanged> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -11103,11 +11103,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] level.  
+ The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level.  
   
  Calling this method has no effect if there were no handlers registered with criteria that match the input parameters for the method call.  
   
- If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with [!INCLUDE[TLA2#tla_clr](~/includes/tla2sharptla-clr-md.md)] behavior of the `-=` operator.  
+ If more than one handler is attached that matched the criteria, only the first handler in the event handler store is removed. This behavior is consistent with CLR behavior of the `-=` operator.  
   
  Neither `routedEvent` nor `handler` may be `null`. Attempting to provide either value as `null` will raise an exception.  
   

From 7391f9a58f3e12bdf593c5cb47bb9f1522c56f08 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:30:15 -0800
Subject: [PATCH 065/236] tla2sharptla-com

---
 xml/System.Dynamic/IInvokeOnGetBinder.xml | 4 ++--
 xml/System.Printing/PrintQueue.xml        | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Dynamic/IInvokeOnGetBinder.xml b/xml/System.Dynamic/IInvokeOnGetBinder.xml
index 2809c594a99..dc3f487eec4 100644
--- a/xml/System.Dynamic/IInvokeOnGetBinder.xml
+++ b/xml/System.Dynamic/IInvokeOnGetBinder.xml
@@ -80,9 +80,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is used by some languages to get a better [!INCLUDE[TLA2#tla_com](~/includes/tla2sharptla-com-md.md)] interoperation experience.  
+ This property is used by some languages to get a better COM interoperation experience.  
   
- When the value is set to false, the dynamic [!INCLUDE[TLA2#tla_com](~/includes/tla2sharptla-com-md.md)] object will not invoke the object but will instead bind to the name, and return an object that can be invoked or indexed later. This is useful for indexed properties and languages that do not produce InvokeMember call sites.  
+ When the value is set to false, the dynamic COM object will not invoke the object but will instead bind to the name, and return an object that can be invoked or indexed later. This is useful for indexed properties and languages that do not produce InvokeMember call sites.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index d6f6846cd32..19c204012b5 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -584,7 +584,7 @@
 ## Remarks  
  If `fastCopy` is `true`, then the printer must be an [Printing Overview](/dotnet/framework/wpf/advanced/printing-overview). If it is not, the <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> method throws an exception.  
   
- If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to [!INCLUDE[TLA#tla_com](~/includes/tlasharptla-com-md.md)]. The call to [!INCLUDE[TLA2#tla_com](~/includes/tla2sharptla-com-md.md)] requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
+ If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to [!INCLUDE[TLA#tla_com](~/includes/tlasharptla-com-md.md)]. The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
   
 -   The simplest way is to add the <xref:System.STAThreadAttribute> (that is, "`[System.STAThreadAttribute()]`") just above the first line of the application's `Main` method (usually "`static void Main(string[] args)`").  
   

From 8789a7f4e77cc3e847604d32874c2a7f9dc5abf8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:30:51 -0800
Subject: [PATCH 066/236] tla2sharptla-dpi

---
 xml/System.Windows.Media/ContainerVisual.xml  | 8 ++++----
 xml/System.Windows.Media/Visual.xml           | 8 ++++----
 xml/System.Windows.Media/VisualTreeHelper.xml | 8 ++++----
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Windows.Media/ContainerVisual.xml b/xml/System.Windows.Media/ContainerVisual.xml
index 1a772866c58..52abafa0441 100644
--- a/xml/System.Windows.Media/ContainerVisual.xml
+++ b/xml/System.Windows.Media/ContainerVisual.xml
@@ -669,9 +669,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -708,9 +708,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/Visual.xml b/xml/System.Windows.Media/Visual.xml
index 4ce629a2df9..592b6e1f0ee 100644
--- a/xml/System.Windows.Media/Visual.xml
+++ b/xml/System.Windows.Media/Visual.xml
@@ -1312,9 +1312,9 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -1345,9 +1345,9 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/VisualTreeHelper.xml b/xml/System.Windows.Media/VisualTreeHelper.xml
index 2b4f5f3b8de..e9ee2ce9234 100644
--- a/xml/System.Windows.Media/VisualTreeHelper.xml
+++ b/xml/System.Windows.Media/VisualTreeHelper.xml
@@ -771,9 +771,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -808,9 +808,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] settings and makes the application automatically [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)]-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this [!INCLUDE[TLA2#tla_dpi](~/includes/tla2sharptla-dpi-md.md)] independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>

From d8ea129a9c6d6430d16c6f57405677a8c87a079f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:31:20 -0800
Subject: [PATCH 067/236] tla2sharptla-dx

---
 xml/System.Windows.Media/RenderCapability.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Media/RenderCapability.xml b/xml/System.Windows.Media/RenderCapability.xml
index ce12b36f890..1d1c1c8d65b 100644
--- a/xml/System.Windows.Media/RenderCapability.xml
+++ b/xml/System.Windows.Media/RenderCapability.xml
@@ -31,7 +31,7 @@
   
 -   Multitexture Support: Multitexture support refers to the ability to apply two or more distinct textures during a blending operation on a 3D graphics object. The degree of multitexture support is determined by the number of multitexture units on the graphics hardware.  
   
- The pixel shader, vertex shader, and multitexture features are used to define specific [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] version levels, which, in turn, are used to define the different rendering tiers in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For a full description of the rendering tiers, see [Graphics Rendering Tiers](/dotnet/framework/wpf/advanced/graphics-rendering-tiers).  
+ The pixel shader, vertex shader, and multitexture features are used to define specific DirectX version levels, which, in turn, are used to define the different rendering tiers in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For a full description of the rendering tiers, see [Graphics Rendering Tiers](/dotnet/framework/wpf/advanced/graphics-rendering-tiers).  
   
  ]]></format>
     </remarks>
@@ -247,21 +247,21 @@
 ## Remarks  
   
 > [!NOTE]
->  Starting in the .NET Framework 4, rendering tier 1 has been redefined to only include graphics hardware that supports [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] 9.0 or greater. Graphics hardware that supports [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] 7 or 8 is now defined as rendering tier 0.  
+>  Starting in the .NET Framework 4, rendering tier 1 has been redefined to only include graphics hardware that supports DirectX 9.0 or greater. Graphics hardware that supports DirectX 7 or 8 is now defined as rendering tier 0.  
   
  The return value is one of three possible values:  
   
 |Return value|Rendering tier|Notes|  
 |------------------|--------------------|-----------|  
-|0x00000000|0|No graphics hardware acceleration is available for the application on the device. All graphics features use software acceleration. The [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] version level is less than version 9.0.|  
-|0x00010000|1|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] version that is greater than or equal to 9.0.|  
-|0x00020000|2|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration provided the necessary system resources have not been exhausted. This corresponds to a [!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] version that is greater than or equal to 9.0.|  
+|0x00000000|0|No graphics hardware acceleration is available for the application on the device. All graphics features use software acceleration. The DirectX version level is less than version 9.0.|  
+|0x00010000|1|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
+|0x00020000|2|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration provided the necessary system resources have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
   
  The following table shows the differences in graphics hardware requirements for rendering tier 1 and rendering tier 2:  
   
 |Feature|Tier 1|Tier 2|  
 |-------------|------------|------------|  
-|[!INCLUDE[TLA2#tla_dx](~/includes/tla2sharptla-dx-md.md)] version|Must be greater than or equal to 9.0.|Must be greater than or equal to 9.0.|  
+|DirectX version|Must be greater than or equal to 9.0.|Must be greater than or equal to 9.0.|  
 |Video RAM|Must be greater than or equal to 60MB.|Must be greater than or equal to 120MB.|  
 |Pixel shader|Version level must greater than or equal to 2.0.|Version level must greater than or equal to 2.0.|  
 |Vertex shader|No requirement.|Version level must greater than or equal to 2.0.|  

From e03349cafebb82f60832b3bee4f132f52b6a7e5b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:31:41 -0800
Subject: [PATCH 068/236] tla2sharptla-exif

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index b8d1e935479..83830c62bbb 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -40,7 +40,7 @@
    
   
 ## Examples  
- The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and [!INCLUDE[TLA2#tla_exif](~/includes/tla2sharptla-exif-md.md)] schemas.  
+ The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and Exif schemas.  
   
  [!code-csharp[BitmapFrameExample#7](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#7)]
  [!code-vb[BitmapFrameExample#7](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#7)]  
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and [!INCLUDE[TLA2#tla_exif](~/includes/tla2sharptla-exif-md.md)] schemas.  
+ The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and Exif schemas.  
   
  [!code-csharp[BitmapFrameExample#7](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#7)]
  [!code-vb[BitmapFrameExample#7](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#7)]  

From 5a769c0d67805ea80066bcd278f165638b46ab2f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:31:57 -0800
Subject: [PATCH 069/236] tla2sharptla-gui

---
 xml/System.Windows.Automation.Peers/AutomationPeer.xml          | 2 +-
 .../ContentElementAutomationPeer.xml                            | 2 +-
 xml/System.Windows.Automation.Peers/DocumentAutomationPeer.xml  | 2 +-
 .../GridViewCellAutomationPeer.xml                              | 2 +-
 xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml | 2 +-
 xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml      | 2 +-
 .../ScrollViewerAutomationPeer.xml                              | 2 +-
 xml/System.Windows.Automation.Peers/TableAutomationPeer.xml     | 2 +-
 xml/System.Windows.Automation.Peers/TableCellAutomationPeer.xml | 2 +-
 xml/System.Windows.Automation.Peers/TextBlockAutomationPeer.xml | 2 +-
 .../UIElement3DAutomationPeer.xml                               | 2 +-
 xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml | 2 +-
 12 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Windows.Automation.Peers/AutomationPeer.xml b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
index a74b1f63a0f..910ea8b52b4 100644
--- a/xml/System.Windows.Automation.Peers/AutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
@@ -1469,7 +1469,7 @@ This method calls the derived implementation of <xref:System.Windows.Automation.
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets a value that indicates whether the element is understood by the user as interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)].</summary>
+        <summary>Gets a value that indicates whether the element is understood by the user as interactive or as contributing to the logical structure of the control in the GUI.</summary>
         <returns>
           <see langword="true" /> if the element is a control; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
index d76ae83ce32..64845ddaba6 100644
--- a/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
@@ -676,7 +676,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets a value that indicates whether the <see cref="T:System.Windows.ContentElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.ContentElementAutomationPeer" /> is something that the end user would understand as being interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. Called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets a value that indicates whether the <see cref="T:System.Windows.ContentElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.ContentElementAutomationPeer" /> is something that the end user would understand as being interactive or as contributing to the logical structure of the control in the GUI. Called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/DocumentAutomationPeer.xml b/xml/System.Windows.Automation.Peers/DocumentAutomationPeer.xml
index 499b804fe28..b0b58b96cbd 100644
--- a/xml/System.Windows.Automation.Peers/DocumentAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/DocumentAutomationPeer.xml
@@ -242,7 +242,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.FrameworkContentElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.DocumentAutomationPeer" /> is understood by the end user as interactive or the user might understand the <see cref="T:System.Windows.FrameworkContentElement" /> as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.FrameworkContentElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.DocumentAutomationPeer" /> is understood by the end user as interactive or the user might understand the <see cref="T:System.Windows.FrameworkContentElement" /> as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" /> in all cases.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/GridViewCellAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GridViewCellAutomationPeer.xml
index f3c1ed2f595..d629b6c6dd8 100644
--- a/xml/System.Windows.Automation.Peers/GridViewCellAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GridViewCellAutomationPeer.xml
@@ -122,7 +122,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the element that is associated with this <see cref="T:System.Windows.Automation.Peers.GridViewCellAutomationPeer" /> is understood by the end user as interactive or the user might understand the element as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the element that is associated with this <see cref="T:System.Windows.Automation.Peers.GridViewCellAutomationPeer" /> is understood by the end user as interactive or the user might understand the element as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>If this <see cref="T:System.Windows.Automation.Peers.GridViewCellAutomationPeer" /> is associated with a <see cref="T:System.Windows.Controls.TextBlock" /> element, this method returns <see langword="true" />; otherwise, this method returns a list of child elements.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
index d413a7b1aa3..36b7ba74344 100644
--- a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
@@ -180,7 +180,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.Hyperlink" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.HyperlinkAutomationPeer" /> is understood by the end user as interactive the user might understand the <see cref="T:System.Windows.Documents.Hyperlink" /> as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.Hyperlink" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.HyperlinkAutomationPeer" /> is understood by the end user as interactive the user might understand the <see cref="T:System.Windows.Documents.Hyperlink" /> as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
index 033e2bd4fb8..9531bbbce51 100644
--- a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
@@ -653,7 +653,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.UIElement> corresponds to the data item in the <xref:System.Windows.Controls.ItemsControl.Items%2A> collection. The user might understand the <xref:System.Windows.UIElement> as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <xref:System.Windows.Automation.Peers.AutomationPeer.IsControlElement%2A>.  
+ The <xref:System.Windows.UIElement> corresponds to the data item in the <xref:System.Windows.Controls.ItemsControl.Items%2A> collection. The user might understand the <xref:System.Windows.UIElement> as contributing to the logical structure of the control in the GUI. This method is called by <xref:System.Windows.Automation.Peers.AutomationPeer.IsControlElement%2A>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
index b47fd234fae..67cecb43372 100644
--- a/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
@@ -151,7 +151,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Controls.ScrollViewer" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.ScrollViewerAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Controls.ScrollViewer" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.ScrollViewerAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>If the <see cref="P:System.Windows.FrameworkElement.TemplatedParent" /> is <see langword="null" />, this method returns <see langword="true" />; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/ui-automation/ui-automation-overview">UI Automation Overview</related>
diff --git a/xml/System.Windows.Automation.Peers/TableAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TableAutomationPeer.xml
index aa944420623..361a6ae5b7d 100644
--- a/xml/System.Windows.Automation.Peers/TableAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TableAutomationPeer.xml
@@ -170,7 +170,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.Table" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TableAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.Table" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TableAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/TableCellAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TableCellAutomationPeer.xml
index 5f568e05ed5..2d04452025c 100644
--- a/xml/System.Windows.Automation.Peers/TableCellAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TableCellAutomationPeer.xml
@@ -205,7 +205,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.TableCell" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TableCellAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Documents.TableCell" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TableCellAutomationPeer" /> is understood by the end user as interactive or as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/TextBlockAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TextBlockAutomationPeer.xml
index 0b753d5de88..f46e5f2d670 100644
--- a/xml/System.Windows.Automation.Peers/TextBlockAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TextBlockAutomationPeer.xml
@@ -150,7 +150,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Controls.TextBlock" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TextBlockAutomationPeer" /> is something that the end user would understand as being interactive or as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. Called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.Controls.TextBlock" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.TextBlockAutomationPeer" /> is something that the end user would understand as being interactive or as contributing to the logical structure of the control in the GUI. Called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="false" /> if the element is part of a template; otherwise <see langword="true" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
index 88e3d0c5be1..1603634bcfe 100644
--- a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
@@ -801,7 +801,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a value that indicates whether the <see cref="T:System.Windows.UIElement3D" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.UIElement3DAutomationPeer" /> is understood by the end user as interactive. Optionally, the user might understand the <see cref="T:System.Windows.UIElement3D" /> as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Returns a value that indicates whether the <see cref="T:System.Windows.UIElement3D" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.UIElement3DAutomationPeer" /> is understood by the end user as interactive. Optionally, the user might understand the <see cref="T:System.Windows.UIElement3D" /> as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" /> in all cases.</returns>
         <remarks>
diff --git a/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml b/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
index 6d1c37936aa..3894680d1df 100644
--- a/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
@@ -663,7 +663,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.UIElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.UIElementAutomationPeer" /> is understood by the end user as interactive. Optionally, the user might understand the <see cref="T:System.Windows.UIElement" /> as contributing to the logical structure of the control in the [!INCLUDE[TLA2#tla_gui](~/includes/tla2sharptla-gui-md.md)]. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
+        <summary>Gets or sets a value that indicates whether the <see cref="T:System.Windows.UIElement" /> that is associated with this <see cref="T:System.Windows.Automation.Peers.UIElementAutomationPeer" /> is understood by the end user as interactive. Optionally, the user might understand the <see cref="T:System.Windows.UIElement" /> as contributing to the logical structure of the control in the GUI. This method is called by <see cref="M:System.Windows.Automation.Peers.AutomationPeer.IsControlElement" />.</summary>
         <returns>
           <see langword="true" />.</returns>
         <remarks>To be added.</remarks>

From ec1561aa6b7d3ac4f67f5a2603795c985c0e1475 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:32:35 -0800
Subject: [PATCH 070/236] tla2sharptla-html

---
 xml/System.Windows.Controls/WebBrowser.xml | 28 +++++++++++-----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/xml/System.Windows.Controls/WebBrowser.xml b/xml/System.Windows.Controls/WebBrowser.xml
index 78d27c31d55..d1c015e3ea0 100644
--- a/xml/System.Windows.Controls/WebBrowser.xml
+++ b/xml/System.Windows.Controls/WebBrowser.xml
@@ -43,7 +43,7 @@
   
  <xref:System.Windows.Controls.WebBrowser> is bound by the security constraints of the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application that is hosting the <xref:System.Windows.Controls.WebBrowser>:  
   
--   When <xref:System.Windows.Controls.WebBrowser> is hosted by a full-trust [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application (a stand-alone application, for example), <xref:System.Windows.Controls.WebBrowser> can host [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] documents from any location.  
+-   When <xref:System.Windows.Controls.WebBrowser> is hosted by a full-trust [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application (a stand-alone application, for example), <xref:System.Windows.Controls.WebBrowser> can host HTML documents from any location.  
   
 -   When <xref:System.Windows.Controls.WebBrowser> is hosted by a partial-trust [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application (an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], for example), <xref:System.Windows.Controls.WebBrowser> can only host documents that are **Site Of Origin** application data files. For more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files).  
   
@@ -53,7 +53,7 @@
    
   
 ## Examples  
- The following example shows how to configure <xref:System.Windows.Controls.WebBrowser> to navigate to an [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document by using markup only.  
+ The following example shows how to configure <xref:System.Windows.Controls.WebBrowser> to navigate to an HTML document by using markup only.  
   
 ```xaml  
 <!-- Web Browser Control that hosts a web page. -->  
@@ -223,7 +223,7 @@ private void backButton_Click(object sender, RoutedEventArgs e)
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to navigate forward to the next [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document by calling <xref:System.Windows.Controls.WebBrowser.GoForward%2A>. The example first checks that there are documents to navigate forward to by checking <xref:System.Windows.Controls.WebBrowser.CanGoForward%2A>.  
+ The following example shows how to navigate forward to the next HTML document by calling <xref:System.Windows.Controls.WebBrowser.GoForward%2A>. The example first checks that there are documents to navigate forward to by checking <xref:System.Windows.Controls.WebBrowser.CanGoForward%2A>.  
   
 ```csharp  
 private void forwardButton_Click(object sender, RoutedEventArgs e)  
@@ -266,7 +266,7 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the Document object that represents the hosted [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] page.</summary>
+        <summary>Gets the Document object that represents the hosted HTML page.</summary>
         <value>A Document object.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -315,7 +315,7 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
    
   
 ## Examples  
- The following example shows how to navigate back to the previous [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document by calling <xref:System.Windows.Controls.WebBrowser.GoBack%2A>. The example first checks that there are [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] documents to navigate back to by checking <xref:System.Windows.Controls.WebBrowser.CanGoBack%2A>.  
+ The following example shows how to navigate back to the previous HTML document by calling <xref:System.Windows.Controls.WebBrowser.GoBack%2A>. The example first checks that there are HTML documents to navigate back to by checking <xref:System.Windows.Controls.WebBrowser.CanGoBack%2A>.  
   
 ```csharp  
 private void backButton_Click(object sender, RoutedEventArgs e)  
@@ -362,7 +362,7 @@ private void backButton_Click(object sender, RoutedEventArgs e)
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Navigate forward to the next [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document, if there is one.</summary>
+        <summary>Navigate forward to the next HTML document, if there is one.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -444,7 +444,7 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
 ## Examples  
  The following example shows how to call a script function in a document from a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application by using <xref:System.Windows.Controls.WebBrowser.InvokeScript%28System.String%29>. In this example, the script function has no parameters.  
   
- The following is the [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document that implements the script function that will be called from [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)].  
+ The following is the HTML document that implements the script function that will be called from [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)].  
   
 ```html  
 <html>  
@@ -465,7 +465,7 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
 </html>  
 ```  
   
- The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script function in the [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document.  
+ The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script function in the HTML document.  
   
 ```csharp  
 private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArgs e)  
@@ -570,7 +570,7 @@ private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArg
 </html>  
 ```  
   
- The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script functions in the [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document.  
+ The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script functions in the HTML document.  
   
 ```csharp  
 private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArgs e)  
@@ -940,7 +940,7 @@ private void goNavigateButton_Click(object sender, RoutedEventArgs e)
 ## Remarks  
  If the `stream` parameter is `null`, <xref:System.Windows.Controls.WebBrowser> navigates to a blank document ("about:blank").  
   
- If the stream parameter is not in a valid [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] format, it will be displayed as plain text.  
+ If the stream parameter is not in a valid HTML format, it will be displayed as plain text.  
   
  After navigation, <xref:System.Windows.Controls.WebBrowser.Source%2A> will be `null`.  
   
@@ -997,7 +997,7 @@ private void goNavigateToStreamButton_Click(object sender, RoutedEventArgs e)
 ## Remarks  
  If the `text` parameter is `null`, <xref:System.Windows.Controls.WebBrowser> navigates to a blank document ("about:blank").  
   
- If the text parameter is not in valid [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] format, it will be displayed as plain text.  
+ If the text parameter is not in valid HTML format, it will be displayed as plain text.  
   
  After navigation, <xref:System.Windows.Controls.WebBrowser.Source%2A> will be `null`.  
   
@@ -1093,7 +1093,7 @@ private void goNavigateToStringButton_Click(object sender, RoutedEventArgs e)
 ## Remarks  
  This property can be set to any COM-visible object for which you want its public properties and methods available to scripting code. You can make a class COM-visible by marking it with the <xref:System.Runtime.InteropServices.ComVisibleAttribute>.  
   
- The object that is set for scripting is exposed to the current document by the [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] DOM using the `window.external` property.  
+ The object that is set for scripting is exposed to the current document by the HTML DOM using the `window.external` property.  
   
  ]]></format>
         </remarks>
@@ -1207,7 +1207,7 @@ private void goNavigateToStringButton_Click(object sender, RoutedEventArgs e)
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the <see cref="T:System.Uri" /> of the current document hosted in the <see cref="T:System.Windows.Controls.WebBrowser" />.</summary>
-        <value>The <see cref="T:System.Uri" /> for the current [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document.</value>
+        <value>The <see cref="T:System.Uri" /> for the current HTML document.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1217,7 +1217,7 @@ private void goNavigateToStringButton_Click(object sender, RoutedEventArgs e)
    
   
 ## Examples  
- The following example shows how to configure <xref:System.Windows.Controls.WebBrowser> to navigate to an [!INCLUDE[TLA2#tla_html](~/includes/tla2sharptla-html-md.md)] document by using markup only.  
+ The following example shows how to configure <xref:System.Windows.Controls.WebBrowser> to navigate to an HTML document by using markup only.  
   
 ```xaml  
 <!-- Web Browser Control that hosts a web page. -->  

From 43c5c81a789c0940e637136b9c345300913f1907 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:33:06 -0800
Subject: [PATCH 071/236] tla2sharptla-idsharpplural

---
 xml/System.Windows.Automation/Automation.xml                  | 4 ++--
 .../AutomationFocusChangedEventArgs.xml                       | 4 ++--
 xml/System.Windows.Automation/ControlType.xml                 | 2 +-
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows.Automation/Automation.xml b/xml/System.Windows.Automation/Automation.xml
index 71df47553e0..49ae6368c03 100644
--- a/xml/System.Windows.Automation/Automation.xml
+++ b/xml/System.Windows.Automation/Automation.xml
@@ -268,7 +268,7 @@
         <param name="runtimeId2">The second run-time ID to compare.</param>
         <summary>Compares two integer arrays containing run-time [!INCLUDE[TLA#tla_id#plural](~/includes/tlasharptla-idsharpplural-md.md)] to determine whether their content is the same.</summary>
         <returns>
-          <see langword="true" /> if the compared run-time [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)] refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element; otherwise <see langword="false" />.</returns>
+          <see langword="true" /> if the compared run-time IDs refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element; otherwise <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -278,7 +278,7 @@
    
   
 ## Examples  
- The following example function determines whether a run-time ID is in a list of run-time [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)].  
+ The following example function determines whether a run-time ID is in a list of run-time IDs.  
   
  [!code-csharp[UIAFocusTracker_snip#103](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAFocusTracker_snip/CSharp/FocusTracker.cs#103)]
  [!code-vb[UIAFocusTracker_snip#103](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAFocusTracker_snip/VisualBasic/FocusTracker.vb#103)]  
diff --git a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
index 126e799e4a2..0dccdf5666a 100644
--- a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
@@ -88,7 +88,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Object [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)] are 32-bit values that identify categories of accessible objects within an application. The `idObject` and `idChild` parameters contain the object [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)] that clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
+ Object IDs are 32-bit values that identify categories of accessible objects within an application. The `idObject` and `idChild` parameters contain the object IDs that clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
   
  ]]></format>
         </remarks>
@@ -124,7 +124,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Object [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)] are 32-bit values that identify categories of accessible objects within an application. The `idObject` and `idChild` parameters contain the object [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)] that clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
+ Object IDs are 32-bit values that identify categories of accessible objects within an application. The `idObject` and `idChild` parameters contain the object IDs that clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/ControlType.xml b/xml/System.Windows.Automation/ControlType.xml
index b77f8b575b7..31d51eed738 100644
--- a/xml/System.Windows.Automation/ControlType.xml
+++ b/xml/System.Windows.Automation/ControlType.xml
@@ -406,7 +406,7 @@
       <Parameters />
       <Docs>
         <summary>Retrieves an array of the required property [!INCLUDE[TLA#tla_id#plural](~/includes/tlasharptla-idsharpplural-md.md)] for this control type.</summary>
-        <returns>An array of property [!INCLUDE[TLA2#tla_id#plural](~/includes/tla2sharptla-idsharpplural-md.md)].</returns>
+        <returns>An array of property IDs.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From 6c388c5c682a42170574130cd668c2c7ea699dc4 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:33:32 -0800
Subject: [PATCH 072/236] tla2sharptla-ie6

---
 xml/System.Windows.Controls/DataGridHyperlinkColumn.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml b/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
index 8ab47f257fb..458be19a2c3 100644
--- a/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
+++ b/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
@@ -26,7 +26,7 @@
  ![DataGridHyperlinkColumn with email addresses](~/add/media/wpf-hyperlinkcolumn.png "DataGridHyperlinkColumn with email addresses")  
   
 > [!NOTE]
->  <xref:System.Windows.Documents.Hyperlink> navigation can only occur if either the direct or indirect parent of a <xref:System.Windows.Documents.Hyperlink> is a navigation host. Examples of navigation hosts include <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or any browser that can host [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)], such as [!INCLUDE[TLA2#tla_ie6](~/includes/tla2sharptla-ie6-md.md)] or later and Firefox 2.0 or later. For more information, see the "Navigation Hosts" topic in [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
+>  <xref:System.Windows.Documents.Hyperlink> navigation can only occur if either the direct or indirect parent of a <xref:System.Windows.Documents.Hyperlink> is a navigation host. Examples of navigation hosts include <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or any browser that can host [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)], such as Microsoft Internet Explorer 6 or later and Firefox 2.0 or later. For more information, see the "Navigation Hosts" topic in [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
   
  To populate the column, bind the column to the <xref:System.Uri> data by using the <xref:System.Windows.Controls.DataGridBoundColumn.Binding%2A> property. To display hyperlink text that is different than the URI string, bind the text value to the <xref:System.Windows.Controls.DataGridHyperlinkColumn.ContentBinding%2A> property. The <xref:System.Windows.Controls.DataGridBoundColumn.Binding%2A> property is applied to the <xref:System.Windows.Documents.Hyperlink> or <xref:System.Windows.Controls.TextBox> element created in the column. The <xref:System.Windows.FrameworkElement.DataContext%2A> for the element in each cell is the data item for the row the cell is in. Therefore, to set up the binding you only have to set the <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. Optionally, you can specify a <xref:System.Windows.Data.Binding.Converter%2A?displayProperty=nameWithType> if you want to convert the data. For more information about data binding, see [Data Binding (WPF)](/dotnet/framework/wpf/data/data-binding-wpf).  
   

From 3c20073d1ef9aa0612fa3d00397ed9e1668ce412 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:33:50 -0800
Subject: [PATCH 073/236] tla2sharptla-ie7

---
 xml/System.Windows.Navigation/CustomContentState.xml | 2 +-
 xml/System.Windows.Navigation/JournalEntry.xml       | 2 +-
 xml/System.Windows.Navigation/NavigationService.xml  | 6 +++---
 xml/System.Windows.Navigation/NavigationWindow.xml   | 2 +-
 xml/System.Windows/Application.xml                   | 2 +-
 5 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.Windows.Navigation/CustomContentState.xml b/xml/System.Windows.Navigation/CustomContentState.xml
index a57b759417c..e7f756a65f7 100644
--- a/xml/System.Windows.Navigation/CustomContentState.xml
+++ b/xml/System.Windows.Navigation/CustomContentState.xml
@@ -58,7 +58,7 @@
   
  When the navigation history entry is navigated to, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] checks to see if a custom <xref:System.Windows.Navigation.CustomContentState> object is associated with it. If so, it calls <xref:System.Windows.Navigation.CustomContentState.Replay%2A> to allow the custom <xref:System.Windows.Navigation.CustomContentState> object to apply the state it remembered from the previous navigation.  
   
- A custom <xref:System.Windows.Navigation.CustomContentState> class can override <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> to change the name that appears for the navigation history entry to which the <xref:System.Windows.Navigation.CustomContentState> object is associated. The value that <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> returns is visible from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the various navigators ([!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
+ A custom <xref:System.Windows.Navigation.CustomContentState> class can override <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> to change the name that appears for the navigation history entry to which the <xref:System.Windows.Navigation.CustomContentState> object is associated. The value that <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> returns is visible from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the various navigators (Internet Explorer 7, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
  A class that derives from <xref:System.Windows.Navigation.CustomContentState> must be serializable, which means it must at least be augmented with <xref:System.SerializableAttribute>, and optionally implement <xref:System.Runtime.Serialization.ISerializable>.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntry.xml b/xml/System.Windows.Navigation/JournalEntry.xml
index 1e707f3434b..762b1f1ec79 100644
--- a/xml/System.Windows.Navigation/JournalEntry.xml
+++ b/xml/System.Windows.Navigation/JournalEntry.xml
@@ -308,7 +308,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Content hosted by <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)], display navigation UI that allows users to navigate through back and forward navigation history. The text that is displayed for each entry in navigation history depends on which of the following pieces of data are used to automatically construct a navigation history entry name, in order of precedence:  
+ Content hosted by <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or Internet Explorer 7, display navigation UI that allows users to navigate through back and forward navigation history. The text that is displayed for each entry in navigation history depends on which of the following pieces of data are used to automatically construct a navigation history entry name, in order of precedence:  
   
 -   The attached <xref:System.Windows.Navigation.JournalEntry.Name%2A> attribute.  
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 8412b235cfb..60073d57a7c 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -73,11 +73,11 @@
   
  <xref:System.Windows.Navigation.NavigationService> is a `sealed` class and therefore cannot be instantiated; instead, <xref:System.Windows.Navigation.NavigationService> is used by navigators to enable navigation. In WPF, there are two navigators: <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame>.  
   
- Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] as a navigator, to provide an integrated user experience. Physically, however, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] in the following ways:  
+ Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. Physically, however, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7 in the following ways:  
   
--   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] the relevant navigation history entries are also added to [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] navigation history.  
+-   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] the relevant navigation history entries are also added to Internet Explorer 7 navigation history.  
   
--   When entries in the [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] are selected, [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
+-   When entries in the Internet Explorer 7 navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] are selected, Internet Explorer 7 causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
   
 > [!NOTE]
 >  A <xref:System.Windows.Controls.Frame> can provide its own navigation history, or use the navigation history of the navigator that hosts it. If <xref:System.Windows.Controls.Frame> provides its own navigation history, it can display its own navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to navigate through the entries in navigation history; those entries are not added to the navigation history of the host navigator (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, [!INCLUDE[TLA2#tla_iegeneric](~/includes/tla2sharptla-iegeneric-md.md)]) and, consequently, cannot be navigated to from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of each (see <xref:System.Windows.Controls.Frame.JournalOwnership%2A>).  
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index 9212e431942..69810a207c4 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -96,7 +96,7 @@
   
  Using <xref:System.Windows.Navigation.NavigationWindow.AddBackEntry%2A>, you can also remember multiple sets of state for a single page instance.  
   
- <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] as a navigator, to provide an integrated user experience. However, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)] will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)].  
+ <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. However, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7.  
   
  **Content Model:**  <xref:System.Windows.Navigation.NavigationWindow> is a <xref:System.Windows.Controls.ContentControl>, which means that <xref:System.Windows.Navigation.NavigationWindow> can contain content such as text, images, or panels. Also, <xref:System.Windows.Navigation.NavigationWindow> is a root element and, consequently, cannot be part of another element's content. For more information about the content model for <xref:System.Windows.Controls.Button>, see [WPF Content Model](/dotnet/framework/wpf/controls/wpf-content-model).  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index d1044675662..3b3b756c3a3 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -358,7 +358,7 @@
   
 -   An [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] is navigated away from.  
   
--   In [!INCLUDE[TLA2#tla_ie7](~/includes/tla2sharptla-ie7-md.md)], when the tab that is hosting the [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] is closed.  
+-   In Internet Explorer 7, when the tab that is hosting the [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] is closed.  
   
 -   When the browser is closed.  
   

From 508386127906a9f8d86e9f1143f7305551c0f2e3 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:34:10 -0800
Subject: [PATCH 074/236] tla2sharptla-iegeneric

---
 xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml | 2 +-
 xml/System.Windows.Navigation/NavigationService.xml           | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml b/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
index 4556a951738..7d0c44988e3 100644
--- a/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
+++ b/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
@@ -148,7 +148,7 @@
       </ReturnValue>
       <Docs>
         <summary>The navigator that raised the <see cref="E:System.Windows.Navigation.NavigationService.FragmentNavigation" /> event.</summary>
-        <value>A <see cref="T:System.Object" /> that refers to the navigator ([!INCLUDE[TLA2#tla_iegeneric](~/includes/tla2sharptla-iegeneric-md.md)], <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />.) that is navigating to the content fragment.</value>
+        <value>A <see cref="T:System.Object" /> that refers to the navigator (Internet Explorer, <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />.) that is navigating to the content fragment.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 60073d57a7c..3b2e38a8bd3 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -80,7 +80,7 @@
 -   When entries in the Internet Explorer 7 navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] are selected, Internet Explorer 7 causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
   
 > [!NOTE]
->  A <xref:System.Windows.Controls.Frame> can provide its own navigation history, or use the navigation history of the navigator that hosts it. If <xref:System.Windows.Controls.Frame> provides its own navigation history, it can display its own navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to navigate through the entries in navigation history; those entries are not added to the navigation history of the host navigator (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, [!INCLUDE[TLA2#tla_iegeneric](~/includes/tla2sharptla-iegeneric-md.md)]) and, consequently, cannot be navigated to from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of each (see <xref:System.Windows.Controls.Frame.JournalOwnership%2A>).  
+>  A <xref:System.Windows.Controls.Frame> can provide its own navigation history, or use the navigation history of the navigator that hosts it. If <xref:System.Windows.Controls.Frame> provides its own navigation history, it can display its own navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to navigate through the entries in navigation history; those entries are not added to the navigation history of the host navigator (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, Internet Explorer) and, consequently, cannot be navigated to from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of each (see <xref:System.Windows.Controls.Frame.JournalOwnership%2A>).  
   
  ]]></format>
     </remarks>

From 2b7664cba97b0d11147d8c49f8b90c16b6c550c6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:34:28 -0800
Subject: [PATCH 075/236] tla2sharptla-mime

---
 xml/System.IO.Packaging/PackWebResponse.xml   |  8 +++---
 xml/System.IO.Packaging/PackagePart.xml       | 26 +++++++++----------
 .../IXpsFixedPageWriter.xml                   |  4 +--
 3 files changed, 19 insertions(+), 19 deletions(-)

diff --git a/xml/System.IO.Packaging/PackWebResponse.xml b/xml/System.IO.Packaging/PackWebResponse.xml
index d298f690ef5..5f4f149e6bd 100644
--- a/xml/System.IO.Packaging/PackWebResponse.xml
+++ b/xml/System.IO.Packaging/PackWebResponse.xml
@@ -119,20 +119,20 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] content type of the response stream's content.</summary>
-        <value>The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the stream's content.</value>
+        <value>The MIME type of the stream's content.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a request does not specify a part in the package, it returns the [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the package.  
+ If a request does not specify a part in the package, it returns the MIME type of the package.  
   
  Requests that specify a part in the package return one of the following:  
   
 1.  If the requested part contains a <xref:System.IO.Packaging.PackagePart.ContentType%2A> value, the <xref:System.IO.Packaging.PackagePart.ContentType%2A> value is returned.  
   
-2.  If the requested part contains no <xref:System.IO.Packaging.PackagePart.ContentType%2A> value but the stream name contains a recognized [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] extension type, the [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type corresponding to the extension is returned.  
+2.  If the requested part contains no <xref:System.IO.Packaging.PackagePart.ContentType%2A> value but the stream name contains a recognized MIME extension type, the MIME type corresponding to the extension is returned.  
   
-3.  If the requested part does not contain a <xref:System.IO.Packaging.PackagePart.ContentType%2A> value nor a recognized [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] extension type, <xref:System.IO.Packaging.PackWebResponse.ContentType%2A> returns an empty string.  
+3.  If the requested part does not contain a <xref:System.IO.Packaging.PackagePart.ContentType%2A> value nor a recognized MIME extension type, <xref:System.IO.Packaging.PackWebResponse.ContentType%2A> returns an empty string.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.IO.Packaging/PackagePart.xml b/xml/System.IO.Packaging/PackagePart.xml
index a61e81f6701..a4d394ed158 100644
--- a/xml/System.IO.Packaging/PackagePart.xml
+++ b/xml/System.IO.Packaging/PackagePart.xml
@@ -39,7 +39,7 @@
 |Access|Description|  
 |------------|-----------------|  
 |<xref:System.IO.Packaging.PackagePart.Uri%2A>|The URI of the part.|  
-|<xref:System.IO.Packaging.PackagePart.ContentType%2A>|The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the content stream.|  
+|<xref:System.IO.Packaging.PackagePart.ContentType%2A>|The MIME type of the content stream.|  
 |<xref:System.IO.Packaging.PackagePart.GetStream%2A>|The content data stream of the part.|  
   
  ]]></format>
@@ -158,8 +158,8 @@
       <Docs>
         <param name="package">The parent <see cref="T:System.IO.Packaging.Package" /> of the part.</param>
         <param name="partUri">The URI of the part, relative to the parent <see cref="T:System.IO.Packaging.Package" /> root.</param>
-        <param name="contentType">The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] content type of the part data stream.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.IO.Packaging.PackagePart" /> class with a specified parent <see cref="P:System.IO.Packaging.PackagePart.Package" />, part URI, and [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] content type.</summary>
+        <param name="contentType">The MIME content type of the part data stream.</param>
+        <summary>Initializes a new instance of the <see cref="T:System.IO.Packaging.PackagePart" /> class with a specified parent <see cref="P:System.IO.Packaging.PackagePart.Package" />, part URI, and MIME content type.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -168,7 +168,7 @@
   
  By default, the <xref:System.IO.Packaging.PackagePart.CompressionOption%2A> property of the part is initialized to <xref:System.IO.Packaging.CompressionOption.NotCompressed>.  
   
- `contentType` must be a [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
@@ -224,16 +224,16 @@
       <Docs>
         <param name="package">The parent <see cref="T:System.IO.Packaging.Package" /> of the part.</param>
         <param name="partUri">The URI of the part, relative to the parent <see cref="T:System.IO.Packaging.Package" /> root.</param>
-        <param name="contentType">The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] content type of the part's data stream.</param>
+        <param name="contentType">The MIME content type of the part's data stream.</param>
         <param name="compressionOption">The compression option of the part data stream.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.IO.Packaging.PackagePart" /> class with a specified parent <see cref="P:System.IO.Packaging.PackagePart.Package" />, part URI, [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] content type, and <see cref="T:System.IO.Packaging.CompressionOption" />.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.IO.Packaging.PackagePart" /> class with a specified parent <see cref="P:System.IO.Packaging.PackagePart.Package" />, part URI, MIME content type, and <see cref="T:System.IO.Packaging.CompressionOption" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  `partUri` must be valid <xref:System.IO.Packaging.PackagePart> URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
   
- `contentType` must be a [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
@@ -330,8 +330,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the content stream.</summary>
-        <value>The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the content data stream for the part.</value>
+        <summary>Gets the MIME type of the content stream.</summary>
+        <value>The MIME type of the content data stream for the part.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -340,7 +340,7 @@
   
  The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is automatically set by the <xref:System.IO.Packaging.PackagePart.%23ctor%2A> constructor.  After it is set by the constructor, the <xref:System.IO.Packaging.PackagePart.ContentType%2A> cannot be changed.  
   
- The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is a [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
@@ -698,13 +698,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>When overridden in a derived class, returns the [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the part content.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the part content.</returns>
+        <summary>When overridden in a derived class, returns the MIME type of the part content.</summary>
+        <returns>The MIME type of the part content.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.IO.Packaging.PackagePart.GetContentTypeCore%2A> is a virtual method of the <xref:System.IO.Packaging.PackagePart> abstract base class. Implement this method only in derived types where the value for the content type cannot be provided at the time of construction, or if calculating the content type value is a nontrivial or costly operation. The return value must be a valid [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] content type.  
+ <xref:System.IO.Packaging.PackagePart.GetContentTypeCore%2A> is a virtual method of the <xref:System.IO.Packaging.PackagePart> abstract base class. Implement this method only in derived types where the value for the content type cannot be provided at the time of construction, or if calculating the content type value is a nontrivial or costly operation. The return value must be a valid MIME content type.  
   
  Derived classes can call <xref:System.IO.Packaging.PackagePart.GetContentTypeCore%2A> to initialize the <xref:System.IO.Packaging.PackagePart.ContentType%2A> property of the derived class to a default value.  After the <xref:System.IO.Packaging.PackagePart.ContentType%2A> property has been set it cannot be changed.  
   
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
index d91b009f1c9..b7f7a39863d 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
@@ -294,8 +294,8 @@
         <Parameter Name="mimeType" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="mimeType">The [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type of the image to add.</param>
-        <summary>Adds a new <see cref="T:System.Windows.Xps.Packaging.XpsImage" /> with a specified [!INCLUDE[TLA2#tla_mime](~/includes/tla2sharptla-mime-md.md)] type to the current page.</summary>
+        <param name="mimeType">The MIME type of the image to add.</param>
+        <summary>Adds a new <see cref="T:System.Windows.Xps.Packaging.XpsImage" /> with a specified MIME type to the current page.</summary>
         <returns>The new image resource that was added to the page</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From dd9ed5d6c2837a7f1784ddd7defc3c856a951e69 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:34:44 -0800
Subject: [PATCH 076/236] tla2sharptla-net

---
 xml/System.Windows.Data/Binding.xml          | 2 +-
 xml/System.Windows.Input/RoutedUICommand.xml | 2 +-
 xml/System.Windows.Markup/XamlReader.xml     | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index cfde100fed2..67670a6af1a 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -573,7 +573,7 @@
   
  While waiting for the value to arrive, the binding reports the <xref:System.Windows.Data.BindingBase.FallbackValue%2A>, if one is available, or the default value of the binding target property.  
   
- However, there should not be many scenarios where you need to use the <xref:System.Windows.Data.Binding.IsAsync%2A> property. The [!INCLUDE[TLA2#tla_net](~/includes/tla2sharptla-net-md.md)] guidelines recommend against defining properties that are orders of magnitude slower than a field set would be. When you are creating your class, consider handling extremely slow operations outside of the `get` accessor and caching the result.  
+ However, there should not be many scenarios where you need to use the <xref:System.Windows.Data.Binding.IsAsync%2A> property. The .NET guidelines recommend against defining properties that are orders of magnitude slower than a field set would be. When you are creating your class, consider handling extremely slow operations outside of the `get` accessor and caching the result.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/RoutedUICommand.xml b/xml/System.Windows.Input/RoutedUICommand.xml
index cd6e1185cd9..bdbb59eab24 100644
--- a/xml/System.Windows.Input/RoutedUICommand.xml
+++ b/xml/System.Windows.Input/RoutedUICommand.xml
@@ -58,7 +58,7 @@
  One of the predefined commands.  
   
  *prefix*  
- The `xlmns` prefix that maps *customClassName*.*customCommandName* to the [!INCLUDE[TLA2#tla_net](~/includes/tla2sharptla-net-md.md)] class.  For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
+ The `xlmns` prefix that maps *customClassName*.*customCommandName* to the .NET class.  For more information, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
   
  *customClassName*  
  A custom class that contains the custom command.  
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index b3131455e3c..e29a69c483e 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -41,7 +41,7 @@
 ## Code Access Security, Loose XAML, and XamlReader  
  XAML is a markup language that directly represents object instantiation and execution. Therefore, elements created in XAML have the same ability to interact with system resources (network access, file system IO, for example) as the equivalent generated code does.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] supports the [!INCLUDE[TLA2#tla_net](~/includes/tla2sharptla-net-md.md)] security framework [!INCLUDE[TLA#tla_cas](~/includes/tlasharptla-cas-md.md)]. This means that [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
+ [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] supports the .NET security framework [!INCLUDE[TLA#tla_cas](~/includes/tlasharptla-cas-md.md)]. This means that [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
   
  The implications of these statements for <xref:System.Windows.Markup.XamlReader> is that your application design must make trust decisions about the XAML you decide to load. If you are loading XAML that is not trusted, consider implementing your own sandboxing technique for how you load the resulting object graph.  
   

From 71aacaa9f33eef05129d370195e466d3109e87c7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:35:03 -0800
Subject: [PATCH 077/236] tla2sharptla-netframewkattr

---
 .../AttachedPropertyBrowsableForTypeAttribute.xml               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
index 7ca6580cc8a..2cd4c0e21eb 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
@@ -190,7 +190,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation returns a unique value for each  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], which is necessary because this  [!INCLUDE[TLA2#tla_netframewkattr](~/includes/tla2sharptla-netframewkattr-md.md)] allows multiple usages.  
+ This implementation returns a unique value for each  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], which is necessary because this  .NET Framework attribute allows multiple usages.  
   
  ]]></format>
         </remarks>

From b38569c3ad7fc9d2364335e1676ff9d10c094dbb Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:35:22 -0800
Subject: [PATCH 078/236] tla2sharptla-opentype

---
 xml/System.Windows/FontStretch.xml   | 6 +++---
 xml/System.Windows/FontStretches.xml | 2 +-
 xml/System.Windows/FontWeight.xml    | 4 ++--
 xml/System.Windows/FontWeights.xml   | 4 ++--
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Windows/FontStretch.xml b/xml/System.Windows/FontStretch.xml
index e095fa7afa9..912450bdc38 100644
--- a/xml/System.Windows/FontStretch.xml
+++ b/xml/System.Windows/FontStretch.xml
@@ -37,7 +37,7 @@
 ## Remarks  
  A font stretch describes the degree to which a font form is stretched from its normal aspect ratio, which is the original width to height ratio specified for the glyphs in the font.  
   
- The <xref:System.Windows.FontStretches> values correspond to the `usWidthClass` definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification. The `usWidthClass` represents an integer value between 1 and 9 - lower values indicate narrower widths; higher values indicate wider widths.  
+ The <xref:System.Windows.FontStretches> values correspond to the `usWidthClass` definition in the OpenType specification. The `usWidthClass` represents an integer value between 1 and 9 - lower values indicate narrower widths; higher values indicate wider widths.  
   
 |Font stretch|usWidthClass|% of normal|  
 |------------------|------------------|-----------------|  
@@ -195,7 +195,7 @@
         <Parameter Name="stretchValue" Type="System.Int32" />
       </Parameters>
       <Docs>
-        <param name="stretchValue">An integer value between one and nine that corresponds to the usStretchValue definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification.</param>
+        <param name="stretchValue">An integer value between one and nine that corresponds to the usStretchValue definition in the OpenType specification.</param>
         <summary>Creates a new instance of <see cref="T:System.Windows.FontStretch" /> that corresponds to the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] usStretchClass value.</summary>
         <returns>A new instance of <see cref="T:System.Windows.FontStretch" />.</returns>
         <remarks>To be added.</remarks>
@@ -484,7 +484,7 @@
       <Parameters />
       <Docs>
         <summary>Returns a value that represents the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usStretchClass</c> for this <see cref="T:System.Windows.FontStretch" /> object.</summary>
-        <returns>An integer value between 1 and 999 that corresponds to the <c>usStretchClass</c> definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification.</returns>
+        <returns>An integer value between 1 and 999 that corresponds to the <c>usStretchClass</c> definition in the OpenType specification.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/FontStretches.xml b/xml/System.Windows/FontStretches.xml
index 6aaf3896041..429ab5cad21 100644
--- a/xml/System.Windows/FontStretches.xml
+++ b/xml/System.Windows/FontStretches.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  A font stretch describes the degree to which a font form is stretched from its normal aspect ratio, which is the original width to height ratio specified for the glyphs in the font.  
   
- The <xref:System.Windows.FontStretches> values correspond to the `usWidthClass` definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification. The `usWidthClass` represents an integer value between 1 and 9. Lower numeric values indicate narrower widths; higher values indicate wider widths.  
+ The <xref:System.Windows.FontStretches> values correspond to the `usWidthClass` definition in the OpenType specification. The `usWidthClass` represents an integer value between 1 and 9. Lower numeric values indicate narrower widths; higher values indicate wider widths.  
   
 |Font stretch|usWidthClass|% of normal|  
 |------------------|------------------|-----------------|  
diff --git a/xml/System.Windows/FontWeight.xml b/xml/System.Windows/FontWeight.xml
index 4d749396fda..2ff617399a1 100644
--- a/xml/System.Windows/FontWeight.xml
+++ b/xml/System.Windows/FontWeight.xml
@@ -196,7 +196,7 @@
         <Parameter Name="weightValue" Type="System.Int32" />
       </Parameters>
       <Docs>
-        <param name="weightValue">An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification.</param>
+        <param name="weightValue">An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the OpenType specification.</param>
         <summary>Creates a new instance of <see cref="T:System.Windows.FontWeight" /> that corresponds to the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usWeightClass</c> value.</summary>
         <returns>A new instance of <see cref="T:System.Windows.FontWeight" />.</returns>
         <remarks>
@@ -527,7 +527,7 @@
       <Parameters />
       <Docs>
         <summary>Returns a value that represents the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usWeightClass</c> for the <see cref="T:System.Windows.FontWeight" /> object.</summary>
-        <returns>An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification.</returns>
+        <returns>An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the OpenType specification.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/FontWeights.xml b/xml/System.Windows/FontWeights.xml
index 61dce9662e3..123d1b46d26 100644
--- a/xml/System.Windows/FontWeights.xml
+++ b/xml/System.Windows/FontWeights.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  A font weight describes the relative weight of a font, in terms of the lightness or heaviness of the strokes. Weight differences are generally differentiated by an increased stroke or thickness that is associated with a given character in a font, as compared to a "normal" character from that same font.  
   
- The <xref:System.Windows.FontWeights> values correspond to the `usWeightClass` definition in the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification. The `usWeightClass` represents an integer value between 1 and 999. Lower values indicate lighter weights; higher values indicate heavier weights.  
+ The <xref:System.Windows.FontWeights> values correspond to the `usWeightClass` definition in the OpenType specification. The `usWeightClass` represents an integer value between 1 and 999. Lower values indicate lighter weights; higher values indicate heavier weights.  
   
 |Font weight|usWeightClass|  
 |-----------------|-------------------|  
@@ -38,7 +38,7 @@
 |<xref:System.Windows.FontWeights.Black%2A><br /><br /> <xref:System.Windows.FontWeights.Heavy%2A>|900|  
 |<xref:System.Windows.FontWeights.ExtraBlack%2A><br /><br /> <xref:System.Windows.FontWeights.UltraBlack%2A>|950|  
   
- For more information about the OpenType 'usWeightClass' value, see the [usWeightClass](https://docs.microsoft.com/typography/opentype/spec/os2#usweightclass) section of the [!INCLUDE[TLA2#tla_opentype](~/includes/tla2sharptla-opentype-md.md)] specification. 
+ For more information about the OpenType 'usWeightClass' value, see the [usWeightClass](https://docs.microsoft.com/typography/opentype/spec/os2#usweightclass) section of the OpenType specification. 
 
    
   

From 3030e6e5119d1d2c5717b5a39be80dcaf335935d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:35:37 -0800
Subject: [PATCH 079/236] tla2sharptla-passport

---
 xml/System.Security.RightsManagement/AuthenticationType.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Security.RightsManagement/AuthenticationType.xml b/xml/System.Security.RightsManagement/AuthenticationType.xml
index 6304cf5806f..93583cac04f 100644
--- a/xml/System.Security.RightsManagement/AuthenticationType.xml
+++ b/xml/System.Security.RightsManagement/AuthenticationType.xml
@@ -123,7 +123,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>Either Windows authentication or [!INCLUDE[TLA2#tla_passport](~/includes/tla2sharptla-passport-md.md)] authentication.</summary>
+        <summary>Either Windows authentication or Windows Live ID authentication.</summary>
       </Docs>
     </Member>
   </Members>

From 0a491be9162bdb087f638ee3b7cb8dc6ebf0a3e2 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:36:04 -0800
Subject: [PATCH 080/236] tla2sharptla-png

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml    | 10 +++++-----
 .../BitmapMetadataBlob.xml                             |  2 +-
 xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml  |  2 +-
 .../PngInterlaceOption.xml                             |  2 +-
 4 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index 83830c62bbb..5cc99965df4 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index 185d2380a70..734f2dc8755 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt ([!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
index 4aa5603106a..8caacf0d50e 100644
--- a/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
@@ -101,7 +101,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Interlacing refers to the process of displaying a [!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] frame in two fields. One field contains the even lines of the frame, and the other field contains the odd lines of the frame. When the [!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] is viewed, the lines in one field are displayed first, and then the lines in the second field are displayed.  
+ Interlacing refers to the process of displaying a PNG frame in two fields. One field contains the even lines of the frame, and the other field contains the odd lines of the frame. When the PNG is viewed, the lines in one field are displayed first, and then the lines in the second field are displayed.  
   
 ## Examples  
  The following example demonstrates how to use the <xref:System.Windows.Media.Imaging.PngBitmapEncoder.Interlace%2A> property.  
diff --git a/xml/System.Windows.Media.Imaging/PngInterlaceOption.xml b/xml/System.Windows.Media.Imaging/PngInterlaceOption.xml
index 27b45e28069..48376ba5dc2 100644
--- a/xml/System.Windows.Media.Imaging/PngInterlaceOption.xml
+++ b/xml/System.Windows.Media.Imaging/PngInterlaceOption.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Interlacing refers to the process of displaying a [!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] frame in two fields. One field contains the even lines of the frame, while the other field contains the odd lines of the frame. When the [!INCLUDE[TLA2#tla_png](~/includes/tla2sharptla-png-md.md)] is viewed, the lines in one field are displayed first, and then the lines in the second field are displayed.  
+ Interlacing refers to the process of displaying a PNG frame in two fields. One field contains the even lines of the frame, while the other field contains the odd lines of the frame. When the PNG is viewed, the lines in one field are displayed first, and then the lines in the second field are displayed.  
   
    
   

From 2529d45983049969c1b0af7b58af80a483296faf Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:36:31 -0800
Subject: [PATCH 081/236] tla2sharptla-riff

---
 xml/System.Windows/DataFormats.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 514a7dc102d..14196624a9a 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -578,7 +578,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_riff](~/includes/tla2sharptla-riff-md.md)] is a broad-based specification, designed to be used in defining standard formats for different types of multimedia files.  
+ RIFF is a broad-based specification, designed to be used in defining standard formats for different types of multimedia files.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   

From 62be6f182c40f46de025e9f1d62719cecd9be386 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:36:54 -0800
Subject: [PATCH 082/236] tla2sharptla-sdk

---
 xml/System.Windows/SourceChangedEventArgs.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/SourceChangedEventArgs.xml b/xml/System.Windows/SourceChangedEventArgs.xml
index 6d31f3e7a38..25e0b23af9e 100644
--- a/xml/System.Windows/SourceChangedEventArgs.xml
+++ b/xml/System.Windows/SourceChangedEventArgs.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The SourceChanged event is a routed event where the event identifier is not publicly exposed. This is because this event plays a potentially critical part in interoperation and should not be allowed to be raised arbitrarily by any other source than the internal implementation of a known <xref:System.Windows.PresentationSource> subclass (currently, the only such class is <xref:System.Windows.Interop.HwndSource>). When implementing an interoperation solution, you can attach or remove handlers for the event (by calling <xref:System.Windows.PresentationSource.AddSourceChangedHandler%2A> and <xref:System.Windows.PresentationSource.RemoveSourceChangedHandler%2A>, respectively) but you cannot perform other operations normally available to routed events such as class handling, adding owners, or raising the event from an arbitrary element source.  
   
- This class overrides the <xref:System.Windows.RoutedEventArgs> virtual method <xref:System.Windows.RoutedEventArgs.InvokeEventHandler%2A?displayProperty=nameWithType>, in order to return a type-specific handler when requested by the event system. This <xref:System.Windows.SourceChangedEventArgs> override does not appear in the class members table in this [!INCLUDE[TLA2#tla_sdk](~/includes/tla2sharptla-sdk-md.md)] documentation because it is a protected member implemented by a sealed class.  
+ This class overrides the <xref:System.Windows.RoutedEventArgs> virtual method <xref:System.Windows.RoutedEventArgs.InvokeEventHandler%2A?displayProperty=nameWithType>, in order to return a type-specific handler when requested by the event system. This <xref:System.Windows.SourceChangedEventArgs> override does not appear in the class members table in this SDK documentation because it is a protected member implemented by a sealed class.  
   
  ]]></format>
     </remarks>

From 597624323c4d1fb1491e7a08ef1a60cf05fa8f3f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:37:08 -0800
Subject: [PATCH 083/236] tla2sharptla-tiff

---
 xml/System.Windows/DataFormats.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 14196624a9a..8328251fa3a 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -770,7 +770,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_tiff](~/includes/tla2sharptla-tiff-md.md)] is a standard file format commonly used for scanning, storage, and interchanges of gray-scale graphic images.  
+ TIFF is a standard file format commonly used for scanning, storage, and interchanges of gray-scale graphic images.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   

From 53a814fc31e0630b7b933e49e5adfb7762de19a9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:37:24 -0800
Subject: [PATCH 084/236] tla2sharptla-titlexaml

---
 .../MarkupCompilePass1.xml                     |  2 +-
 xml/System.Windows.Controls/Frame.xml          |  2 +-
 xml/System.Windows.Controls/Page.xml           |  2 +-
 .../FragmentNavigationEventArgs.xml            |  2 +-
 .../NavigationService.xml                      |  6 +++---
 .../NavigationWindow.xml                       |  2 +-
 xml/System.Windows/Application.xml             | 18 +++++++++---------
 7 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
index 24abe7315ef..cb9407c3312 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
@@ -347,7 +347,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets a value that specifies whether the current value of **DefineConstants** is kept.</summary>
-        <value>Specifies whether the current value of **DefineConstants** is kept, which affects target assembly generation; if this parameter is changed, the public API in the target assembly may be changed and the compilation of [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] files that reference local types may be affected.</value>
+        <value>Specifies whether the current value of **DefineConstants** is kept, which affects target assembly generation; if this parameter is changed, the public API in the target assembly may be changed and the compilation of XAML files that reference local types may be affected.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Windows.Controls/Frame.xml b/xml/System.Windows.Controls/Frame.xml
index 24101c24ef6..e7c163ff798 100644
--- a/xml/System.Windows.Controls/Frame.xml
+++ b/xml/System.Windows.Controls/Frame.xml
@@ -650,7 +650,7 @@
         <ReturnType>System.Windows.Navigation.FragmentNavigationEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] content has been loaded, if the desired fragment is in different content.</summary>
+        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source XAML content has been loaded, if the desired fragment is in different content.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index e7cabb5b4c5..45bb3e05347 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -54,7 +54,7 @@
   
  A page can be hosted from <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or from a browser. To be hosted, a page can be:  
   
--   The direct child of a <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, or <xref:System.Windows.Controls.Frame> element in [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)].  
+-   The direct child of a <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, or <xref:System.Windows.Controls.Frame> element in XAML.  
   
 -   Instantiated and set as the value of the `Content` property of <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, and <xref:System.Windows.Controls.Frame>.  
   
diff --git a/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml b/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
index 7d0c44988e3..1f2d4d90b29 100644
--- a/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
+++ b/xml/System.Windows.Navigation/FragmentNavigationEventArgs.xml
@@ -37,7 +37,7 @@
 <TextBlock Name="FragmentName">...</TextBlock>  
 ```  
   
- You navigate to a [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] fragment by providing a URI with a suffix in the following format:  
+ You navigate to a XAML fragment by providing a URI with a suffix in the following format:  
   
  \#*FragmentName*  
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 3b2e38a8bd3..2a8a4139215 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -278,7 +278,7 @@
         <ReturnType>System.Windows.Navigation.FragmentNavigationEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] content has been loaded, if the desired fragment is in different content.</summary>
+        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source XAML content has been loaded, if the desired fragment is in different content.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -297,7 +297,7 @@
   
  `http://www.microsoft.com/targetpage.xaml#FragmentName`  
   
- After the source page loads (after <xref:System.Windows.Navigation.NavigationService.LoadCompleted> event is raised), fragment navigation begins and the <xref:System.Windows.Navigation.NavigationService> attempts to locate the [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] fragment. If the [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] fragment is found, <xref:System.Windows.Navigation.NavigationService> instructs the content navigator  (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>) to show the fragment. If you need to change this behavior, you can handle <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> to provide your own fragment navigation behavior. <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> is passed a <xref:System.Windows.Navigation.FragmentNavigationEventArgs> parameter which exposes properties that are useful for this purpose, including:  
+ After the source page loads (after <xref:System.Windows.Navigation.NavigationService.LoadCompleted> event is raised), fragment navigation begins and the <xref:System.Windows.Navigation.NavigationService> attempts to locate the XAML fragment. If the XAML fragment is found, <xref:System.Windows.Navigation.NavigationService> instructs the content navigator  (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>) to show the fragment. If you need to change this behavior, you can handle <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> to provide your own fragment navigation behavior. <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> is passed a <xref:System.Windows.Navigation.FragmentNavigationEventArgs> parameter which exposes properties that are useful for this purpose, including:  
   
 -   The navigator that owns this navigation service (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
@@ -322,7 +322,7 @@
    
   
 ## Examples  
- The following example shows how to handle <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> to provide custom fragment navigation behavior. In this case, the example opens an error [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] page if the fragment in the source [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] page is not found.  
+ The following example shows how to handle <xref:System.Windows.Navigation.NavigationService.FragmentNavigation> to provide custom fragment navigation behavior. In this case, the example opens an error XAML page if the fragment in the source XAML page is not found.  
   
  [!code-csharp[NavigationServiceSnippets#MainWindowFragmentNavigationCODE](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationServiceSnippets/CSharp/MainWindow.xaml.cs#mainwindowfragmentnavigationcode)]
  [!code-vb[NavigationServiceSnippets#MainWindowFragmentNavigationCODE](~/samples/snippets/visualbasic/VS_Snippets_Wpf/NavigationServiceSnippets/visualbasic/mainwindow.xaml.vb#mainwindowfragmentnavigationcode)]  
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index 69810a207c4..e82d588e084 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -531,7 +531,7 @@
         <ReturnType>System.Windows.Navigation.FragmentNavigationEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] content has been loaded, if the desired fragment is in different content.</summary>
+        <summary>Occurs when navigation to a content fragment begins, which occurs immediately, if the desired fragment is in the current content, or after the source XAML content has been loaded, if the desired fragment is in different content.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 3b3b756c3a3..04d771eed12 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -459,7 +459,7 @@
         <ReturnType>System.Windows.Navigation.FragmentNavigationEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when a navigator in the application begins navigation to a content fragment, Navigation occurs immediately if the desired fragment is in the current content, or after the source [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] content has been loaded if the desired fragment is in different content.</summary>
+        <summary>Occurs when a navigator in the application begins navigation to a content fragment, Navigation occurs immediately if the desired fragment is in the current content, or after the source XAML content has been loaded if the desired fragment is in different content.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -704,7 +704,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  
@@ -746,7 +746,7 @@
 ## Remarks  
  You must explicitly convert the return value to the same type as the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.  
   
- The [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  
@@ -756,7 +756,7 @@
         <exception cref="T:System.ArgumentNullException">
           <paramref name="resourceLocator" /> is null.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="resourceLocator" /> is an absolute URI.</exception>
-        <exception cref="T:System.Exception">The file is not a [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] file.</exception>
+        <exception cref="T:System.Exception">The file is not a XAML file.</exception>
         <altmember cref="M:System.Windows.Application.GetResourceStream(System.Uri)" />
         <altmember cref="M:System.Windows.Application.GetContentStream(System.Uri)" />
         <altmember cref="M:System.Windows.Application.GetRemoteStream(System.Uri)" />
@@ -797,7 +797,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  
@@ -844,9 +844,9 @@
   
  If the <xref:System.Windows.Application.ShutdownMode%2A> property of the <xref:System.Windows.Application> object is set to <xref:System.Windows.ShutdownMode.OnMainWindowClose>, closing the main window causes the application to shut down.  
   
- It is possible to set the <xref:System.Windows.Application.MainWindow%2A> property from [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)], if an application's main window is not the window that is produced by setting the <xref:System.Windows.Application.StartupUri%2A> property in [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)]. The two limitations of the [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)] approach are:  
+ It is possible to set the <xref:System.Windows.Application.MainWindow%2A> property from [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)], if an application's main window is not the window that is produced by setting the <xref:System.Windows.Application.StartupUri%2A> property in XAML. The two limitations of the XAML approach are:  
   
--   You can specify either a [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)]-only <xref:System.Windows.Window> or a [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)]-only <xref:System.Windows.Navigation.NavigationWindow> as the main window.  
+-   You can specify either a XAML-only <xref:System.Windows.Window> or a XAML-only <xref:System.Windows.Navigation.NavigationWindow> as the main window.  
   
 -   You must set the <xref:System.Windows.UIElement.Visibility%2A> property of the window you specify, otherwise it won't be shown.  
   
@@ -865,7 +865,7 @@
  [!code-csharp[ApplicationMainWindowSnippets#GetApplicationMainWindowCODE](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationMainWindowSnippets/CSharp/App.xaml.cs#getapplicationmainwindowcode)]
  [!code-vb[ApplicationMainWindowSnippets#GetApplicationMainWindowCODE](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationMainWindowSnippets/visualbasic/application.xaml.vb#getapplicationmainwindowcode)]  
   
- The following example shows how to set <xref:System.Windows.Application.MainWindow%2A> using [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)].  
+ The following example shows how to set <xref:System.Windows.Application.MainWindow%2A> using XAML.  
   
  [!code-xaml[ApplicationMainWindowSnippets#SetApplicationMainWindowXAML](~/samples/snippets/xaml/VS_Snippets_Wpf/ApplicationMainWindowSnippets/XAML/App.xaml#setapplicationmainwindowxaml)]  
   
@@ -2154,7 +2154,7 @@ This example illustrates how to use XAML together with application-scope resourc
 > [!NOTE]
 >  Command-line parameters can also be acquired by calling the static <xref:System.Environment.GetCommandLineArgs%2A> method of the <xref:System.Environment> object. However, <xref:System.Environment.GetCommandLineArgs%2A> requires full trust to execute.  
   
- If you set <xref:System.Windows.Application.StartupUri%2A> using [!INCLUDE[TLA2#tla_titlexaml](~/includes/tla2sharptla-titlexaml-md.md)], the main window that is created is not available from either the <xref:System.Windows.Application.MainWindow%2A> property or the <xref:System.Windows.Application.Windows%2A> property of the <xref:System.Windows.Application> object until after the <xref:System.Windows.Application.Startup> event is processed. If you need access to the main window during startup, you need to manually create a new window object from your <xref:System.Windows.Application.Startup> event handler.  
+ If you set <xref:System.Windows.Application.StartupUri%2A> using XAML, the main window that is created is not available from either the <xref:System.Windows.Application.MainWindow%2A> property or the <xref:System.Windows.Application.Windows%2A> property of the <xref:System.Windows.Application> object until after the <xref:System.Windows.Application.Startup> event is processed. If you need access to the main window during startup, you need to manually create a new window object from your <xref:System.Windows.Application.Startup> event handler.  
   
 > [!NOTE]
 >  If your application uses <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> to specify a credential policy, you need to set <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> after <xref:System.Windows.Application.Startup> is raised; otherwise, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] sets it to a default internal policy directly after the <xref:System.Windows.Application.Startup> event has been raised.  

From e3d55c0e7475d2df402875c10c48c05d9ba327d0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:37:42 -0800
Subject: [PATCH 085/236] tla2sharptla-tpc

---
 xml/System.Windows/SystemParameters.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index 22f4a1f52ee..1b03e5a696a 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -3447,7 +3447,7 @@
       <Docs>
         <summary>Gets a value that indicates whether the current operating system is Microsoft Windows XP [!INCLUDE[TLA#tla_tpc](~/includes/tlasharptla-tpc-md.md)] Edition.</summary>
         <value>
-          <see langword="true" /> if the current operating system is Windows XP [!INCLUDE[TLA2#tla_tpc](~/includes/tla2sharptla-tpc-md.md)] Edition; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the current operating system is Windows XP Tablet PC Edition; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From f2d3aa19a6eed513f36e2a6d0b2e6f356a8865c7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:38:04 -0800
Subject: [PATCH 086/236] tla2sharptla-ui

---
 .../FrameworkElementAdapters.xml              |  4 +--
 .../ObservableCollection`1.xml                |  2 +-
 .../INotifyCollectionChanged.xml              |  2 +-
 .../TabItemWrapperAutomationPeer.xml          |  2 +-
 xml/System.Windows.Automation/Automation.xml  |  4 +--
 ...onElement+AutomationElementInformation.xml |  4 +--
 .../AutomationElement.xml                     | 34 +++++++++----------
 .../AutomationElementMode.xml                 |  4 +--
 .../CacheRequest.xml                          |  2 +-
 .../IItemContainerGenerator.xml               |  2 +-
 .../FlowDocumentReader.xml                    |  4 +--
 .../FlowDocumentScrollViewer.xml              |  2 +-
 xml/System.Windows.Controls/ItemsControl.xml  |  6 ++--
 xml/System.Windows.Controls/Page.xml          | 14 ++++----
 xml/System.Windows.Controls/PasswordBox.xml   |  2 +-
 xml/System.Windows.Controls/RichTextBox.xml   |  2 +-
 xml/System.Windows.Controls/TextBlock.xml     |  2 +-
 xml/System.Windows.Controls/TextBox.xml       |  2 +-
 .../VirtualizationCacheLength.xml             |  4 +--
 .../VirtualizingStackPanel.xml                |  8 ++---
 xml/System.Windows.Data/Binding.xml           |  2 +-
 xml/System.Windows.Data/BindingMode.xml       |  2 +-
 xml/System.Windows.Data/CollectionView.xml    |  6 ++--
 .../DataSourceProvider.xml                    | 12 +++----
 .../FocusNavigationDirection.xml              |  2 +-
 xml/System.Windows.Input/InputMethod.xml      | 12 +++----
 .../NavigationCommands.xml                    | 32 ++++++++---------
 .../HwndSourceParameters.xml                  |  2 +-
 xml/System.Windows.Interop/InteropBitmap.xml  |  6 ++--
 .../CustomContentState.xml                    |  6 ++--
 .../JournalEntryUnifiedViewConverter.xml      |  2 +-
 .../NavigationService.xml                     |  6 ++--
 xml/System.Windows.Threading/Dispatcher.xml   |  2 +-
 xml/System.Windows/CoerceValueCallback.xml    |  2 +-
 xml/System.Windows/ContentElement.xml         |  2 +-
 .../FrameworkContentElement.xml               |  6 ++--
 xml/System.Windows/FrameworkElement.xml       | 10 +++---
 xml/System.Windows/Style.xml                  |  2 +-
 xml/System.Windows/SystemParameters.xml       |  2 +-
 xml/System.Windows/UIElement.xml              |  4 +--
 xml/System.Windows/Window.xml                 |  2 +-
 41 files changed, 114 insertions(+), 114 deletions(-)

diff --git a/xml/System.AddIn.Pipeline/FrameworkElementAdapters.xml b/xml/System.AddIn.Pipeline/FrameworkElementAdapters.xml
index feb1dbf63b0..5ec8d066ea7 100644
--- a/xml/System.AddIn.Pipeline/FrameworkElementAdapters.xml
+++ b/xml/System.AddIn.Pipeline/FrameworkElementAdapters.xml
@@ -67,7 +67,7 @@ Windows Presentation Foundation (WPF) extends the .NET Framework add-in model to
       <Docs>
         <param name="nativeHandleContract">The <see cref="T:System.AddIn.Contract.INativeHandleContract" /> that was passed across the isolation boundary between the host application and the add-in.</param>
         <summary>Returns a <see cref="T:System.Windows.FrameworkElement" /> that has been converted from an <see cref="T:System.AddIn.Contract.INativeHandleContract" />.</summary>
-        <returns>A <see cref="T:System.Windows.FrameworkElement" /> that will be displayed from either the host application or add-in, depending on the direction in which the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] is passed between the two.</returns>
+        <returns>A <see cref="T:System.Windows.FrameworkElement" /> that will be displayed from either the host application or add-in, depending on the direction in which the UI is passed between the two.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.AddIn.Pipeline.FrameworkElementAdapters.ViewToContractAdapter(System.Windows.FrameworkElement)" />
       </Docs>
@@ -100,7 +100,7 @@ Windows Presentation Foundation (WPF) extends the .NET Framework add-in model to
       <Docs>
         <param name="root">The <see cref="T:System.Windows.FrameworkElement" /> to be passed across the isolation boundary between the host application and the add-in.</param>
         <summary>Returns an <see cref="T:System.AddIn.Contract.INativeHandleContract" /> that has been converted from a <see cref="T:System.Windows.FrameworkElement" />.</summary>
-        <returns>An <see cref="T:System.AddIn.Contract.INativeHandleContract" /> that is passed from either the host application or the add-in, depending on the direction in which the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] is passed between the two.</returns>
+        <returns>An <see cref="T:System.AddIn.Contract.INativeHandleContract" /> that is passed from either the host application or the add-in, depending on the direction in which the UI is passed between the two.</returns>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">
           <paramref name="root" /> is not the root element of a tree of elements.</exception>
diff --git a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
index e7432268318..d5521cb454a 100644
--- a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
+++ b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
@@ -78,7 +78,7 @@
 ## Remarks  
  In many cases the data that you work with is a collection of objects. For example, a common scenario in data binding is to use an <xref:System.Windows.Controls.ItemsControl> such as a <xref:System.Windows.Controls.ListBox>, <xref:System.Windows.Controls.ListView>, or <xref:System.Windows.Controls.TreeView> to display a collection of records.  
   
- You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event, an event that should be raised whenever the underlying collection changes.  
+ You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the UI automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event, an event that should be raised whenever the underlying collection changes.  
   
  [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface.  
   
diff --git a/xml/System.Collections.Specialized/INotifyCollectionChanged.xml b/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
index dc5fb58bebf..8f7838d9b04 100644
--- a/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
+++ b/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
@@ -54,7 +54,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event that must be raised whenever the underlying collection changes.  
+ You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the UI automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event that must be raised whenever the underlying collection changes.  
   
  [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. For an example, see [How to: Create and Bind to an ObservableCollection](/dotnet/framework/wpf/data/how-to-create-and-bind-to-an-observablecollection).  
   
diff --git a/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
index a331e151f02..9739b42a70f 100644
--- a/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When data items are shown in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], the system creates a <xref:System.Windows.UIElement> subtree for the data items. The system also creates an <xref:System.Windows.Automation.Peers.ItemAutomationPeer> for each data item. When the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] for the data item is created, this <xref:System.Windows.Automation.Peers.TabItemWrapperAutomationPeer> is also created. The two peers then merge to form a single peer.  
+ When data items are shown in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], the system creates a <xref:System.Windows.UIElement> subtree for the data items. The system also creates an <xref:System.Windows.Automation.Peers.ItemAutomationPeer> for each data item. When the UI for the data item is created, this <xref:System.Windows.Automation.Peers.TabItemWrapperAutomationPeer> is also created. The two peers then merge to form a single peer.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Automation/Automation.xml b/xml/System.Windows.Automation/Automation.xml
index 49ae6368c03..0d94458cff5 100644
--- a/xml/System.Windows.Automation/Automation.xml
+++ b/xml/System.Windows.Automation/Automation.xml
@@ -312,9 +312,9 @@
       <Docs>
         <param name="el1">The first [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to compare.</param>
         <param name="el2">The second [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to compare.</param>
-        <summary>Compares two [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements, returning <see langword="true" /> if both refer to the same [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element.</summary>
+        <summary>Compares two [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements, returning <see langword="true" /> if both refer to the same UI element.</summary>
         <returns>
-          <see langword="true" /> if the run time identifiers of the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements are the same; otherwise <see langword="false" />.</returns>
+          <see langword="true" /> if the run time identifiers of the UI elements are the same; otherwise <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
index ecfbeac3e69..733da1f249f 100644
--- a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
+++ b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
@@ -162,7 +162,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The returned rectangle can contain points that are not clickable. Instances where this could happen are when the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item has an irregular shape or clickable region, or it is obscured by other [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements.  
+ The returned rectangle can contain points that are not clickable. Instances where this could happen are when the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item has an irregular shape or clickable region, or it is obscured by other UI elements.  
   
  ]]></format>
         </remarks>
@@ -425,7 +425,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value of the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled%2A> property can change because of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] interactions. You should get an updated cache by calling <xref:System.Windows.Automation.AutomationElement.GetUpdatedCache%2A> if the value of the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled%2A> property might have changed since you issued the cache request.  
+ The value of the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled%2A> property can change because of UI interactions. You should get an updated cache by calling <xref:System.Windows.Automation.AutomationElement.GetUpdatedCache%2A> if the value of the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled%2A> property might have changed since you issued the cache request.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.IsEnabledProperty>.  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 941d2b619c9..95517491e4c 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -306,7 +306,7 @@
   
  Bounding rectangles are of type <xref:System.Windows.Rect>. The returned rectangle is in physical screen coordinates. The default value is <xref:System.Windows.Rect.Empty%2A>. <xref:System.Windows.Rect.Empty%2A> is returned if the item is not currently displaying a [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
   
- The returned rectangle can contain points that are not clickable. Instances where this could happen include when the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] item has an irregular shape or clickable region, or it is obscured by other [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements.  
+ The returned rectangle can contain points that are not clickable. Instances where this could happen include when the UI item has an irregular shape or clickable region, or it is obscured by other UI elements.  
   
    
   
@@ -870,7 +870,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the <see cref="T:System.Windows.Automation.AutomationElement" /> that currently has focus.</summary>
-        <value>The focused [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element.</value>
+        <value>The focused UI element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -945,9 +945,9 @@
         <Parameter Name="hwnd" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hwnd">The handle of the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element.</param>
+        <param name="hwnd">The handle of the UI element.</param>
         <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the specified window handle.</summary>
-        <returns>An <see cref="T:System.Windows.Automation.AutomationElement" /> for the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] item identified by <paramref name="hwnd" />.</returns>
+        <returns>An <see cref="T:System.Windows.Automation.AutomationElement" /> for the UI item identified by <paramref name="hwnd" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Automation.AutomationElement.FromPoint(System.Windows.Point)" />
         <related type="Article" href="/dotnet/framework/ui-automation/obtaining-ui-automation-elements">Obtaining UI Automation Elements</related>
@@ -1009,9 +1009,9 @@
         <Parameter Name="pt" Type="System.Windows.Point" />
       </Parameters>
       <Docs>
-        <param name="pt">The physical screen coordinates on the desktop at which to locate the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element.</param>
+        <param name="pt">The physical screen coordinates on the desktop at which to locate the UI element.</param>
         <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item at specified point on the desktop.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] item at the specified point.</returns>
+        <returns>The UI item at the specified point.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1298,7 +1298,7 @@
 ## Remarks  
  <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> gets the specified pattern based on its availability at the time of the call.  
   
- For some forms of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], this method will incur cross-process performance overhead. Applications can concentrate overhead by caching patterns and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPattern%2A>.  
+ For some forms of UI, this method will incur cross-process performance overhead. Applications can concentrate overhead by caching patterns and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPattern%2A>.  
   
    
   
@@ -1331,7 +1331,7 @@
 ## Remarks  
  The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
   
- For some forms of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
+ For some forms of UI, this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
  ]]></format>
         </remarks>
@@ -1374,11 +1374,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the UI.  
   
  If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, a default property specified by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
- For some forms of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], this method will incur cross-process performance overhead. Concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
+ For some forms of UI, this method will incur cross-process performance overhead. Concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
    
   
@@ -1429,7 +1429,7 @@
   
  The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
   
- For some forms of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
+ For some forms of UI, this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
    
   
@@ -1493,7 +1493,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The identifier is only guaranteed to be unique to the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the desktop on which it was generated. Identifiers can be reused over time.  
+ The identifier is only guaranteed to be unique to the UI of the desktop on which it was generated. Identifiers can be reused over time.  
   
  The format of run-time identifiers might change in future releases. The returned identifier should be treated as an opaque value and used only for comparison; for example, to determine whether an <xref:System.Windows.Automation.AutomationElement> is in the cache.  
   
@@ -1751,7 +1751,7 @@
   
  This property can also be retrieved from the <xref:System.Windows.Automation.AutomationElement.Current%2A> or <xref:System.Windows.Automation.AutomationElement.Cached%2A> properties.  
   
- The content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree provides a view of the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] that only contains elements that represent data within the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ The content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree provides a view of the UI that only contains elements that represent data within the UI.  
   
  An element must be a control to be able to hold content.  
   
@@ -1804,7 +1804,7 @@
   
  This property can also be retrieved from the <xref:System.Windows.Automation.AutomationElement.Current%2A> or <xref:System.Windows.Automation.AutomationElement.Cached%2A> properties.  
   
- Controls are elements that a user perceives as interactive or containing information in the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ Controls are elements that a user perceives as interactive or containing information in the UI.  
   
  Return values of the property are of type <xref:System.Boolean>. The default value for the property is `true`.  
   
@@ -3270,12 +3270,12 @@
         <param name="right">The second <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
         <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</summary>
         <returns>
-          <see langword="true" /> if the two <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element; otherwise <see langword="false" />.</returns>
+          <see langword="true" /> if the two <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same UI element; otherwise <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Two <xref:System.Windows.Automation.AutomationElement> objects that compare as equal might contain different cached information from different points in time. <xref:System.Windows.Automation.AutomationElement.op_Equality%2A> only tests that the objects refer to the same underlying [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] element.  
+ Two <xref:System.Windows.Automation.AutomationElement> objects that compare as equal might contain different cached information from different points in time. <xref:System.Windows.Automation.AutomationElement.op_Equality%2A> only tests that the objects refer to the same underlying UI element.  
   
  ]]></format>
         </remarks>
@@ -3310,7 +3310,7 @@
         <param name="right">The second <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
         <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to different [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements.</summary>
         <returns>
-          <see langword="true" /> if the two objects refer to different [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements; otherwise <see langword="false" />.</returns>
+          <see langword="true" /> if the two objects refer to different UI elements; otherwise <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Automation.AutomationElement.op_Equality(System.Windows.Automation.AutomationElement,System.Windows.Automation.AutomationElement)" />
         <altmember cref="M:System.Windows.Automation.AutomationElement.Equals(System.Object)" />
diff --git a/xml/System.Windows.Automation/AutomationElementMode.xml b/xml/System.Windows.Automation/AutomationElementMode.xml
index 7c77811af20..f204133c114 100644
--- a/xml/System.Windows.Automation/AutomationElementMode.xml
+++ b/xml/System.Windows.Automation/AutomationElementMode.xml
@@ -60,7 +60,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>Specifies that returned elements have a full reference to the underlying [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].</summary>
+        <summary>Specifies that returned elements have a full reference to the underlying UI.</summary>
       </Docs>
     </Member>
     <Member MemberName="None">
@@ -82,7 +82,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Specifies that returned elements have no reference to the underlying [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] and contain only cached information. This mode might be used, for example, to retrieve the names of items in a list box without obtaining references to the items themselves.</summary>
+        <summary>Specifies that returned elements have no reference to the underlying UI and contain only cached information. This mode might be used, for example, to retrieve the names of items in a list box without obtaining references to the items themselves.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Automation/CacheRequest.xml b/xml/System.Windows.Automation/CacheRequest.xml
index 3743805e074..4d00cd778cf 100644
--- a/xml/System.Windows.Automation/CacheRequest.xml
+++ b/xml/System.Windows.Automation/CacheRequest.xml
@@ -264,7 +264,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Automation.AutomationElementMode.Full> is the default value, and specifies that returned elements contain a full reference to the underlying [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]. <xref:System.Windows.Automation.AutomationElementMode.None> specifies that the returned elements have no reference to the underlying [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], and contain only cached information.  
+ <xref:System.Windows.Automation.AutomationElementMode.Full> is the default value, and specifies that returned elements contain a full reference to the underlying UI. <xref:System.Windows.Automation.AutomationElementMode.None> specifies that the returned elements have no reference to the underlying UI, and contain only cached information.  
   
  Certain operations on elements, including <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A>, <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A>, and <xref:System.Windows.Automation.AutomationElement.SetFocus%2A>, require a full reference; attempting to perform these on an element that has none results in an <xref:System.InvalidOperationException>.  
   
diff --git a/xml/System.Windows.Controls.Primitives/IItemContainerGenerator.xml b/xml/System.Windows.Controls.Primitives/IItemContainerGenerator.xml
index 9f5081a045c..013635e6775 100644
--- a/xml/System.Windows.Controls.Primitives/IItemContainerGenerator.xml
+++ b/xml/System.Windows.Controls.Primitives/IItemContainerGenerator.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Controls.ItemsControl> is the base class for containing and displaying one or more data items. <xref:System.Windows.Controls.ItemContainerGenerator> maintains an association between <xref:System.Windows.Controls.ItemsControl> and the list of items that are displayed by <xref:System.Windows.Controls.ItemsControl>. <xref:System.Windows.Controls.ItemContainerGenerator> is also responsible for generating the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] for those items on behalf of <xref:System.Windows.Controls.ItemsControl>. <xref:System.Windows.Controls.Panel>, <xref:System.Windows.Controls.VirtualizingPanel>, and <xref:System.Windows.Controls.VirtualizingStackPanel> also use <xref:System.Windows.Controls.ItemContainerGenerator> for the same reason.  
+ <xref:System.Windows.Controls.ItemsControl> is the base class for containing and displaying one or more data items. <xref:System.Windows.Controls.ItemContainerGenerator> maintains an association between <xref:System.Windows.Controls.ItemsControl> and the list of items that are displayed by <xref:System.Windows.Controls.ItemsControl>. <xref:System.Windows.Controls.ItemContainerGenerator> is also responsible for generating the UI for those items on behalf of <xref:System.Windows.Controls.ItemsControl>. <xref:System.Windows.Controls.Panel>, <xref:System.Windows.Controls.VirtualizingPanel>, and <xref:System.Windows.Controls.VirtualizingStackPanel> also use <xref:System.Windows.Controls.ItemContainerGenerator> for the same reason.  
   
  <xref:System.Windows.Controls.ItemContainerGenerator> implements <xref:System.Windows.Controls.Primitives.IItemContainerGenerator> and is the interface through which each of the mentioned layout elements communicate with <xref:System.Windows.Controls.ItemContainerGenerator>.  
   
diff --git a/xml/System.Windows.Controls/FlowDocumentReader.xml b/xml/System.Windows.Controls/FlowDocumentReader.xml
index c5992972c08..1e416da2d5d 100644
--- a/xml/System.Windows.Controls/FlowDocumentReader.xml
+++ b/xml/System.Windows.Controls/FlowDocumentReader.xml
@@ -58,7 +58,7 @@
   
     -   **Zoom Controls** - The zoom controls enable the user to increase or decrease the zoom level by clicking the plus or minus buttons, respectively.  The zoom controls also include a slider for adjusting the zoom level.  For more information, see <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A>.  
   
- The default toolbar [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] does not include a **Print** button.  
+ The default toolbar UI does not include a **Print** button.  
   
  <xref:System.Windows.Documents.FlowDocument> is the only allowable child element for a <xref:System.Windows.Controls.FlowDocumentReader>.  A <xref:System.Windows.Controls.FlowDocumentReader> element can host no more than one <xref:System.Windows.Documents.FlowDocument>.  
   
@@ -650,7 +650,7 @@
   
  ![Screenshot with callouts: FlowDocumentReader](~/add/media/flowdocrdr-find.png "Screenshot with callouts: FlowDocumentReader")  
   
- When <xref:System.Windows.Controls.FlowDocumentReader.IsFindEnabled%2A> is `false`, the **Find** button does not appear on the <xref:System.Windows.Controls.FlowDocumentReader>[!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ When <xref:System.Windows.Controls.FlowDocumentReader.IsFindEnabled%2A> is `false`, the **Find** button does not appear on the <xref:System.Windows.Controls.FlowDocumentReader>UI.  
   
 <a name="dependencyPropertyInfo_IsFindEnabled"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
index 6d22553d50c..c51ad2f82c8 100644
--- a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
@@ -54,7 +54,7 @@
   
  ![Screenshot: Basic FlowDocumentScrollViewer](~/add/media/flowdocscrollviewer-main.png "Screenshot: Basic FlowDocumentScrollViewer")  
   
- By default, a vertical scrollbar is always shown, and a horizontal scrollbar becomes visible if needed.  The default [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] for <xref:System.Windows.Controls.FlowDocumentScrollViewer> does not include a toolbar; however, the <xref:System.Windows.Controls.FlowDocumentScrollViewer.IsToolBarVisible%2A> property can be used to enable a built-in toolbar.  
+ By default, a vertical scrollbar is always shown, and a horizontal scrollbar becomes visible if needed.  The default UI for <xref:System.Windows.Controls.FlowDocumentScrollViewer> does not include a toolbar; however, the <xref:System.Windows.Controls.FlowDocumentScrollViewer.IsToolBarVisible%2A> property can be used to enable a built-in toolbar.  
   
  <xref:System.Windows.Documents.FlowDocument> is the only allowable child element for a <xref:System.Windows.Controls.FlowDocumentScrollViewer>.  A <xref:System.Windows.Controls.FlowDocumentScrollViewer> element may host no more than one <xref:System.Windows.Documents.FlowDocument>.  
   
diff --git a/xml/System.Windows.Controls/ItemsControl.xml b/xml/System.Windows.Controls/ItemsControl.xml
index e30764297c2..fc3417f7dc8 100644
--- a/xml/System.Windows.Controls/ItemsControl.xml
+++ b/xml/System.Windows.Controls/ItemsControl.xml
@@ -1885,9 +1885,9 @@ ListBox that contains multiple types of objects
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You use the <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A> to specify the visualization of the data objects. If your <xref:System.Windows.Controls.ItemsControl> is bound to a collection object and you do not provide specific display instructions using a <xref:System.Windows.DataTemplate>, the resulting [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of each item is a string representation of each object in the underlying collection.  
+ You use the <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A> to specify the visualization of the data objects. If your <xref:System.Windows.Controls.ItemsControl> is bound to a collection object and you do not provide specific display instructions using a <xref:System.Windows.DataTemplate>, the resulting UI of each item is a string representation of each object in the underlying collection.  
   
- When you set an <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A> on an <xref:System.Windows.Controls.ItemsControl>, the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] is generated as follows (using the <xref:System.Windows.Controls.ListBox> as an example):  
+ When you set an <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A> on an <xref:System.Windows.Controls.ItemsControl>, the UI is generated as follows (using the <xref:System.Windows.Controls.ListBox> as an example):  
   
 1.  During content generation, the <xref:System.Windows.Controls.ItemsControl.ItemsPanel%2A> initiates a request for the <xref:System.Windows.Controls.ItemsControl.ItemContainerGenerator%2A> to create a container for each data item. For <xref:System.Windows.Controls.ListBox>, the container is a <xref:System.Windows.Controls.ListBoxItem>. The generator calls back into the <xref:System.Windows.Controls.ItemsControl> to prepare the container.  
   
@@ -1895,7 +1895,7 @@ ListBox that contains multiple types of objects
   
 3.  Similar to all <xref:System.Windows.Controls.ContentControl> types, the <xref:System.Windows.Controls.ControlTemplate> of a <xref:System.Windows.Controls.ListBoxItem> contains a <xref:System.Windows.Controls.ContentPresenter>. When the template is applied, it creates a <xref:System.Windows.Controls.ContentPresenter> whose <xref:System.Windows.Controls.ContentPresenter.ContentTemplate%2A> is bound to the <xref:System.Windows.Controls.ContentControl.ContentTemplate%2A> of the <xref:System.Windows.Controls.ListBoxItem>.  
   
-4.  Finally, the <xref:System.Windows.Controls.ContentPresenter> applies that <xref:System.Windows.Controls.ContentControl.ContentTemplate%2A> to itself, and that creates the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+4.  Finally, the <xref:System.Windows.Controls.ContentPresenter> applies that <xref:System.Windows.Controls.ContentControl.ContentTemplate%2A> to itself, and that creates the UI.  
   
  If you have more than one <xref:System.Windows.DataTemplate> defined and you want to supply logic to programmatically choose and apply a <xref:System.Windows.DataTemplate>, use the <xref:System.Windows.Controls.ItemsControl.ItemTemplateSelector%2A> property.  
   
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 45bb3e05347..f8d5949fec0 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -48,7 +48,7 @@
   
 -   It can access and use the <xref:System.Windows.Navigation.NavigationService> that navigated to it.  
   
--   It can alter the title, width, height, and navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of its host window (<xref:System.Windows.Controls.Page.WindowTitle%2A>, <xref:System.Windows.Controls.Page.WindowWidth%2A>, <xref:System.Windows.Controls.Page.WindowHeight%2A>, <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>).  
+-   It can alter the title, width, height, and navigation UI of its host window (<xref:System.Windows.Controls.Page.WindowTitle%2A>, <xref:System.Windows.Controls.Page.WindowWidth%2A>, <xref:System.Windows.Controls.Page.WindowHeight%2A>, <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>).  
   
 -   It has designer support in [!INCLUDE[TLA#tla_visualstu](~/includes/tlasharptla-visualstu-md.md)].  
   
@@ -70,7 +70,7 @@
   
 -   Programmatically by using <xref:System.Windows.Navigation.NavigationService>.  
   
--   Visually by using the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the host, including [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, and <xref:System.Windows.Controls.Frame>.  
+-   Visually by using the navigation UI of the host, including [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, and <xref:System.Windows.Controls.Frame>.  
   
  For structured navigation using page functions (<xref:System.Windows.Navigation.PageFunction%601>), see [Structured Navigation Overview](/dotnet/framework/wpf/app-development/structured-navigation-overview) and [Navigation Topologies Overview](/dotnet/framework/wpf/app-development/navigation-topologies-overview).  
   
@@ -999,22 +999,22 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of a <see cref="T:System.Windows.Navigation.NavigationWindow" /> on [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)] is visible.</summary>
+        <summary>Gets or sets a value that indicates whether the navigation UI of a <see cref="T:System.Windows.Navigation.NavigationWindow" /> on [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)] is visible.</summary>
         <value>
-          <see langword="true" /> if the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of a host <see cref="T:System.Windows.Navigation.NavigationWindow" /> is visible; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the navigation UI of a host <see cref="T:System.Windows.Navigation.NavigationWindow" /> is visible; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Navigation.NavigationWindow> displays navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] by default to enable browser-style forwards and backwards navigation. If a page is set as the <xref:System.Windows.Application.StartupUri%2A>, <xref:System.Windows.Application> automatically opens a <xref:System.Windows.Navigation.NavigationWindow> to host the page in. If the page does not want to use the default <xref:System.Windows.Navigation.NavigationWindow> navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], it can set <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> to `false`.  
+ <xref:System.Windows.Navigation.NavigationWindow> displays navigation UI by default to enable browser-style forwards and backwards navigation. If a page is set as the <xref:System.Windows.Application.StartupUri%2A>, <xref:System.Windows.Application> automatically opens a <xref:System.Windows.Navigation.NavigationWindow> to host the page in. If the page does not want to use the default <xref:System.Windows.Navigation.NavigationWindow> navigation UI, it can set <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> to `false`.  
   
 > [!NOTE]
->  Because [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does not integrate with the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] for [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)], it provides its own navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
+>  Because [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does not integrate with the navigation UI for [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)], it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
   
    
   
 ## Examples  
- The following example shows how to use [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] to hide the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of a <xref:System.Windows.Navigation.NavigationWindow>.  
+ The following example shows how to use [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] to hide the navigation UI of a <xref:System.Windows.Navigation.NavigationWindow>.  
   
  [!code-xaml[PageShowsNavigationUISnippets#SetPageShowsNavigationUIXAML1](~/samples/snippets/xaml/VS_Snippets_Wpf/PageShowsNavigationUISnippets/XAML/HomePage.xaml#setpageshowsnavigationuixaml1)]  
 [!code-xaml[PageShowsNavigationUISnippets#SetPageShowsNavigationUIXAML2](~/samples/snippets/xaml/VS_Snippets_Wpf/PageShowsNavigationUISnippets/XAML/HomePage.xaml#setpageshowsnavigationuixaml2)]  
diff --git a/xml/System.Windows.Controls/PasswordBox.xml b/xml/System.Windows.Controls/PasswordBox.xml
index e210c8f883d..2e801d6e8e1 100644
--- a/xml/System.Windows.Controls/PasswordBox.xml
+++ b/xml/System.Windows.Controls/PasswordBox.xml
@@ -30,7 +30,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  <xref:System.Windows.Controls.PasswordBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events.  Consequently, custom event handlers that listen for `MouseUp` or `MouseDown` events from a `PasswordBox` will never be called.  If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.PasswordBox> native handling of these events, and be aware that this has notable effects on the control's [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+>  <xref:System.Windows.Controls.PasswordBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events.  Consequently, custom event handlers that listen for `MouseUp` or `MouseDown` events from a `PasswordBox` will never be called.  If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.PasswordBox> native handling of these events, and be aware that this has notable effects on the control's UI.  
   
 ## Customizing the PasswordBox Control  
  To apply the same property settings to multiple <xref:System.Windows.Controls.PasswordBox> controls, use the <xref:System.Windows.FrameworkElement.Style%2A> property. You can modify the default <xref:System.Windows.Controls.ControlTemplate> to give the control a unique appearance. For more information about creating a <xref:System.Windows.Controls.ControlTemplate>, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  To see the parts and states that are specific to the <xref:System.Windows.Controls.PasswordBox>, see [PasswordBox Styles and Templates](/dotnet/framework/wpf/controls/passwordbox-styles-and-templates).  
diff --git a/xml/System.Windows.Controls/RichTextBox.xml b/xml/System.Windows.Controls/RichTextBox.xml
index e6078db06d6..58ac6991347 100644
--- a/xml/System.Windows.Controls/RichTextBox.xml
+++ b/xml/System.Windows.Controls/RichTextBox.xml
@@ -39,7 +39,7 @@
  <xref:System.Windows.Documents.FlowDocument> is the only supported child element for a <xref:System.Windows.Controls.RichTextBox>.  
   
 > [!IMPORTANT]
->  <xref:System.Windows.Controls.RichTextBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events.  Consequently, custom event handlers that listen for `MouseUp` or `MouseDown` events from a <xref:System.Windows.Controls.RichTextBox> will never be called.  If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.RichTextBox> native handling of these events, and be aware that this has notable effects on the control's [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+>  <xref:System.Windows.Controls.RichTextBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events.  Consequently, custom event handlers that listen for `MouseUp` or `MouseDown` events from a <xref:System.Windows.Controls.RichTextBox> will never be called.  If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.RichTextBox> native handling of these events, and be aware that this has notable effects on the control's UI.  
   
  While <xref:System.Windows.Controls.RichTextBox> supports copying and pasting of images, certain scenarios are currently unsupported and may not work properly.  The following table summarizes these scenarios and expected results.  
   
diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index 62dcf9daf55..7732f5436aa 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -47,7 +47,7 @@
   
  <xref:System.Windows.Controls.TextBlock> is designed to be lightweight, and is geared specifically at integrating small portions of flow content into a [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  <xref:System.Windows.Controls.TextBlock> is optimized for single-line display, and provides good performance for displaying up to a few lines of content.  
   
- <xref:System.Windows.Controls.TextBlock> is not optimized for scenarios that need to display more than a few lines of content; for such scenarios, a <xref:System.Windows.Documents.FlowDocument> coupled with an appropriate viewing control is a better choice than <xref:System.Windows.Controls.TextBlock>, in terms of performance.  After <xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.FlowDocumentScrollViewer> is the next lightest-weight control for displaying flow content, and simply provides a scrolling content area with minimal [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  <xref:System.Windows.Controls.FlowDocumentPageViewer> is optimized around "page-at-a-time" viewing mode for flow content.  Finally, <xref:System.Windows.Controls.FlowDocumentReader> supports the richest set functionality for viewing flow content, but is correspondingly heavier-weight.  
+ <xref:System.Windows.Controls.TextBlock> is not optimized for scenarios that need to display more than a few lines of content; for such scenarios, a <xref:System.Windows.Documents.FlowDocument> coupled with an appropriate viewing control is a better choice than <xref:System.Windows.Controls.TextBlock>, in terms of performance.  After <xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.FlowDocumentScrollViewer> is the next lightest-weight control for displaying flow content, and simply provides a scrolling content area with minimal UI.  <xref:System.Windows.Controls.FlowDocumentPageViewer> is optimized around "page-at-a-time" viewing mode for flow content.  Finally, <xref:System.Windows.Controls.FlowDocumentReader> supports the richest set functionality for viewing flow content, but is correspondingly heavier-weight.  
   
  Horizontally aligning text within a <xref:System.Windows.Controls.TextBlock> is done with the <xref:System.Windows.Controls.TextBlock.TextAlignment%2A> property. Aligning the <xref:System.Windows.Controls.TextBlock> within the layout of the page is done with the <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> and <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> properties.  
   
diff --git a/xml/System.Windows.Controls/TextBox.xml b/xml/System.Windows.Controls/TextBox.xml
index 4b3c683a6d2..349684b5314 100644
--- a/xml/System.Windows.Controls/TextBox.xml
+++ b/xml/System.Windows.Controls/TextBox.xml
@@ -50,7 +50,7 @@ Example of a TextBox
  The best way to hide the border around a <xref:System.Windows.Controls.TextBox> is to set the <xref:System.Windows.Controls.Control.BorderThickness%2A> property of the <xref:System.Windows.Controls.TextBox> to `0`.  
   
 > [!IMPORTANT]
->  <xref:System.Windows.Controls.TextBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events. Consequently, custom event handlers that listen for <xref:System.Windows.UIElement.MouseUp> or <xref:System.Windows.UIElement.MouseDown> events from a <xref:System.Windows.Controls.TextBox> will not be called. If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.TextBox> native handling of these events, and be aware that this has notable effects on the control's [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+>  <xref:System.Windows.Controls.TextBox> has built-in handling for the bubbling  <xref:System.Windows.UIElement.MouseUp> and <xref:System.Windows.UIElement.MouseDown> events. Consequently, custom event handlers that listen for <xref:System.Windows.UIElement.MouseUp> or <xref:System.Windows.UIElement.MouseDown> events from a <xref:System.Windows.Controls.TextBox> will not be called. If you need to respond to these events, listen for the tunneling <xref:System.Windows.UIElement.PreviewMouseUp> and <xref:System.Windows.UIElement.PreviewMouseDown> events instead, or register the handlers with the <xref:System.Windows.EventSetter.HandledEventsToo%2A> argument (this latter option is only available through code). Do not mark the event handled unless you deliberately want to disable <xref:System.Windows.Controls.TextBox> native handling of these events, and be aware that this has notable effects on the control's UI.  
   
  Scrollbars are not visible on a <xref:System.Windows.Controls.TextBox> by default. To make scrollbars visible, set the <xref:System.Windows.Controls.Primitives.TextBoxBase.VerticalScrollBarVisibility%2A> and <xref:System.Windows.Controls.Primitives.TextBoxBase.HorizontalScrollBarVisibility%2A> properties to <xref:System.Windows.Controls.ScrollBarVisibility.Visible> or <xref:System.Windows.Controls.ScrollBarVisibility.Auto>.  
   
diff --git a/xml/System.Windows.Controls/VirtualizationCacheLength.xml b/xml/System.Windows.Controls/VirtualizationCacheLength.xml
index 6c5eac0c498..1a3f360dd85 100644
--- a/xml/System.Windows.Controls/VirtualizationCacheLength.xml
+++ b/xml/System.Windows.Controls/VirtualizationCacheLength.xml
@@ -114,7 +114,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements as they're scrolled into view.  
+ In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
   
  ]]></format>
         </remarks>
@@ -143,7 +143,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements as they're scrolled into view.  
+ In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/VirtualizingStackPanel.xml b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
index 095eab7eef2..9057f316d18 100644
--- a/xml/System.Windows.Controls/VirtualizingStackPanel.xml
+++ b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements only for visible items.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
   
  Virtualization in a <xref:System.Windows.Controls.StackPanel> only occurs when the items control contained in the panel creates its own item containers. You can ensure this happens by using data binding. In scenarios where item containers are created and added to the items control, a <xref:System.Windows.Controls.VirtualizingStackPanel> offers no performance advantage over a <xref:System.Windows.Controls.StackPanel>.  
   
@@ -111,7 +111,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements only for visible items.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of UI elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
   
  ]]></format>
         </remarks>
@@ -1023,7 +1023,7 @@ Notice that the IsVirtualizing attached property is explicitly set to `true`.
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements only for visible items.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of UI elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
   
  ]]></format>
         </remarks>
@@ -1428,7 +1428,7 @@ Notice that the IsVirtualizing attached property is explicitly set to `true`.
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements only for visible items.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of UI elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 67670a6af1a..7bb51d82435 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -569,7 +569,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Windows.Data.Binding.IsAsync%2A> property when the `get` accessor of your binding source property might take a long time. One example is an image property with a `get` accessor that downloads from the Web. Setting <xref:System.Windows.Data.Binding.IsAsync%2A> to `true` avoids blocking the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] while the download occurs.  
+ Use the <xref:System.Windows.Data.Binding.IsAsync%2A> property when the `get` accessor of your binding source property might take a long time. One example is an image property with a `get` accessor that downloads from the Web. Setting <xref:System.Windows.Data.Binding.IsAsync%2A> to `true` avoids blocking the UI while the download occurs.  
   
  While waiting for the value to arrive, the binding reports the <xref:System.Windows.Data.BindingBase.FallbackValue%2A>, if one is available, or the default value of the binding target property.  
   
diff --git a/xml/System.Windows.Data/BindingMode.xml b/xml/System.Windows.Data/BindingMode.xml
index 9faa233e9ed..fc8202ca127 100644
--- a/xml/System.Windows.Data/BindingMode.xml
+++ b/xml/System.Windows.Data/BindingMode.xml
@@ -128,7 +128,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Causes changes to either the source property or the target property to automatically update the other. This type of binding is appropriate for editable forms or other fully-interactive [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] scenarios.</summary>
+        <summary>Causes changes to either the source property or the target property to automatically update the other. This type of binding is appropriate for editable forms or other fully-interactive UI scenarios.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Data/CollectionView.xml b/xml/System.Windows.Data/CollectionView.xml
index de114655b33..458eea253cc 100644
--- a/xml/System.Windows.Data/CollectionView.xml
+++ b/xml/System.Windows.Data/CollectionView.xml
@@ -1492,7 +1492,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method calls <xref:System.Windows.Data.CollectionView.ProcessCollectionChanged%2A> if it is on the correct [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread dispatcher and has never been updated from a different thread, or posts the change to the dispatcher to process it on the correct thread.  
+ This method calls <xref:System.Windows.Data.CollectionView.ProcessCollectionChanged%2A> if it is on the correct UI thread dispatcher and has never been updated from a different thread, or posts the change to the dispatcher to process it on the correct thread.  
   
  ]]></format>
         </remarks>
@@ -1669,10 +1669,10 @@
       </Parameters>
       <Docs>
         <param name="args">The <see cref="T:System.Collections.Specialized.NotifyCollectionChangedEventArgs" /> object to process.</param>
-        <summary>When overridden in a derived class, processes a single change on the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread.</summary>
+        <summary>When overridden in a derived class, processes a single change on the UI thread.</summary>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
-          <para>This method must be overridden in a derived class to process a single change on the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread.</para>
+          <para>This method must be overridden in a derived class to process a single change on the UI thread.</para>
         </block>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Data/DataSourceProvider.xml b/xml/System.Windows.Data/DataSourceProvider.xml
index d576527f070..69bae005f1c 100644
--- a/xml/System.Windows.Data/DataSourceProvider.xml
+++ b/xml/System.Windows.Data/DataSourceProvider.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Data.DataSourceProvider> is a convenience wrapper around an existing data model; it does not replace any data model. A data provider does not attempt to condense the complexity and versatility of a data model such as ADO into one single object with a few properties.  
   
- <xref:System.Windows.Data.DataSourceProvider> is an abstract class. Use one of the derived classes, which are <xref:System.Windows.Data.XmlDataProvider> and <xref:System.Windows.Data.ObjectDataProvider>. The <xref:System.Windows.Data.DataSourceProvider> is aware of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] threading and dispatcher model. It assumes the thread at creation time to be the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread. Events will get marshaled from a worker thread to the UI thread of the application.  
+ <xref:System.Windows.Data.DataSourceProvider> is an abstract class. Use one of the derived classes, which are <xref:System.Windows.Data.XmlDataProvider> and <xref:System.Windows.Data.ObjectDataProvider>. The <xref:System.Windows.Data.DataSourceProvider> is aware of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] threading and dispatcher model. It assumes the thread at creation time to be the UI thread. Events will get marshaled from a worker thread to the UI thread of the application.  
   
  ]]></format>
     </remarks>
@@ -236,8 +236,8 @@
         <ReturnType>System.Windows.Threading.Dispatcher</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the current <see cref="T:System.Windows.Threading.Dispatcher" /> object to the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread to use.</summary>
-        <value>The current <see cref="T:System.Windows.Threading.Dispatcher" /> object to the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread to use. By default, this is the <see cref="T:System.Windows.Threading.Dispatcher" /> object that is associated with the thread on which this instance was created.</value>
+        <summary>Gets or sets the current <see cref="T:System.Windows.Threading.Dispatcher" /> object to the UI thread to use.</summary>
+        <value>The current <see cref="T:System.Windows.Threading.Dispatcher" /> object to the UI thread to use. By default, this is the <see cref="T:System.Windows.Threading.Dispatcher" /> object that is associated with the thread on which this instance was created.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -473,7 +473,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This callback can be called from any thread. This implementation marshals back the result to the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread before setting any of the public properties and before raising any events.  
+ This callback can be called from any thread. This implementation marshals back the result to the UI thread before setting any of the public properties and before raising any events.  
   
  ]]></format>
         </remarks>
@@ -505,14 +505,14 @@
       <Docs>
         <param name="newData">The data that is the result of the query.</param>
         <param name="error">The error that occurred while running the query. This value is <see langword="null" /> if there is no error.</param>
-        <param name="completionWork">Optional delegate that is used to execute completion work on the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread, for example, to set additional properties.</param>
+        <param name="completionWork">Optional delegate that is used to execute completion work on the UI thread, for example, to set additional properties.</param>
         <param name="callbackArguments">Optional arguments to send as a parameter with the <paramref name="completionWork" /> delegate.</param>
         <summary>Derived classes call this method to indicate that a query has finished.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This callback can be called from any thread. This implementation marshals back the result to the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread before setting any of the public properties and before raising any events.  
+ This callback can be called from any thread. This implementation marshals back the result to the UI thread before setting any of the public properties and before raising any events.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/FocusNavigationDirection.xml b/xml/System.Windows.Input/FocusNavigationDirection.xml
index 8c6e0b7c6c9..9e3207a4f44 100644
--- a/xml/System.Windows.Input/FocusNavigationDirection.xml
+++ b/xml/System.Windows.Input/FocusNavigationDirection.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Left, Right, Down, and Up each move focus in that direction based on an approximate representation of the relative item positions in the rendered window. Not all such directional movements are possible, depending on the relative layout of your [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ Left, Right, Down, and Up each move focus in that direction based on an approximate representation of the relative item positions in the rendered window. Not all such directional movements are possible, depending on the relative layout of your UI.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/InputMethod.xml b/xml/System.Windows.Input/InputMethod.xml
index f15cae3c103..966743251bd 100644
--- a/xml/System.Windows.Input/InputMethod.xml
+++ b/xml/System.Windows.Input/InputMethod.xml
@@ -61,7 +61,7 @@
       <Docs>
         <summary>Gets a value that indicates whether or not this input method can display configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
         <value>
-          <see langword="true" /> if configuration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] can be displayed; otherwise, <see langword="false" />.  
+          <see langword="true" /> if configuration UI can be displayed; otherwise, <see langword="false" />.  
   
  This property has no default value.</value>
         <remarks>
@@ -105,7 +105,7 @@
       <Docs>
         <summary>Gets a value that indicates whether this input method can display word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
         <value>
-          <see langword="true" /> if word registration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] can be displayed; otherwise, <see langword="false" />.  
+          <see langword="true" /> if word registration UI can be displayed; otherwise, <see langword="false" />.  
   
  This property has no default value.</value>
         <remarks>To be added.</remarks>
@@ -1109,8 +1109,8 @@
         <Parameter Name="element" Type="System.Windows.UIElement" />
       </Parameters>
       <Docs>
-        <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the configuration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  This parameter can be <see langword="null" />.</param>
-        <summary>Displays configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service, using a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].</summary>
+        <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the configuration UI.  This parameter can be <see langword="null" />.</param>
+        <summary>Displays configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service, using a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Input.InputMethod.CanShowConfigurationUI" />
         <altmember cref="M:System.Windows.Input.InputMethod.ShowConfigureUI" />
@@ -1226,9 +1226,9 @@
         <Parameter Name="registeredText" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the word registration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  This parameter can be <see langword="null" />.</param>
+        <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the word registration UI.  This parameter can be <see langword="null" />.</param>
         <param name="registeredText">A string that specifies a value to register.</param>
-        <summary>Displays word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.  Accepts a specified string as the default value to register, and a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].</summary>
+        <summary>Displays word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.  Accepts a specified string as the default value to register, and a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Input/NavigationCommands.xml b/xml/System.Windows.Input/NavigationCommands.xml
index 9040022358b..740871bb942 100644
--- a/xml/System.Windows.Input/NavigationCommands.xml
+++ b/xml/System.Windows.Input/NavigationCommands.xml
@@ -62,7 +62,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Browse Back" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -137,7 +137,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Browse Forward" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -212,7 +212,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Browse Home" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -290,7 +290,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Browse Stop" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -365,7 +365,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Decrease Zoom" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -441,7 +441,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Favorites" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -518,7 +518,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="First Page" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -594,7 +594,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Go To Page" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -670,7 +670,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Increase Zoom" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -746,7 +746,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Last Page" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -822,7 +822,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Navigate Journal" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -897,7 +897,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Next Page" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -973,7 +973,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Previous Page" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -1049,7 +1049,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Refresh" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -1124,7 +1124,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Search" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
@@ -1203,7 +1203,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the value that represents the <see langword="Zoom" /> command.</summary>
-        <value>The routed [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] command.  
+        <value>The routed UI command.  
   
  <list type="table"><listheader><term> Default Values  
   
diff --git a/xml/System.Windows.Interop/HwndSourceParameters.xml b/xml/System.Windows.Interop/HwndSourceParameters.xml
index 85e28d90da0..d500a4a5f6b 100644
--- a/xml/System.Windows.Interop/HwndSourceParameters.xml
+++ b/xml/System.Windows.Interop/HwndSourceParameters.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This structure is used only in the <xref:System.Windows.Interop.HwndSource> object constructor call.  
   
- The properties whose values are established by this structure are not directly exposed on <xref:System.Windows.Interop.HwndSource> instances when an <xref:System.Windows.Interop.HwndSource> is constructed. However, the values of the <xref:System.Windows.Interop.HwndSourceParameters> structure typically affect general [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] properties such as "Height" and "Width" that might exist in specific hosted objects and their APIs.  
+ The properties whose values are established by this structure are not directly exposed on <xref:System.Windows.Interop.HwndSource> instances when an <xref:System.Windows.Interop.HwndSource> is constructed. However, the values of the <xref:System.Windows.Interop.HwndSourceParameters> structure typically affect general UI properties such as "Height" and "Width" that might exist in specific hosted objects and their APIs.  
   
 > [!IMPORTANT]
 >  Do not construct instances of this structure using the default (parameterless) constructor. An <xref:System.Windows.Interop.HwndSourceParameters> instance that is created by the parameterless constructor results in <xref:System.Windows.Interop.HwndSourceParameters> that cannot be assigned a <xref:System.Windows.Interop.HwndSourceParameters.WindowName%2A> (even though the <xref:System.Windows.Interop.HwndSourceParameters.WindowName%2A> property appears to be settable). If such an instance is applied as the parameters for an <xref:System.Windows.Interop.HwndSource> constructor, the resulting <xref:System.Windows.Interop.HwndSource> cannot display a window.  
diff --git a/xml/System.Windows.Interop/InteropBitmap.xml b/xml/System.Windows.Interop/InteropBitmap.xml
index 9cf4930b481..49785d3bdb8 100644
--- a/xml/System.Windows.Interop/InteropBitmap.xml
+++ b/xml/System.Windows.Interop/InteropBitmap.xml
@@ -233,7 +233,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Forces the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to be rendered.</summary>
+        <summary>Forces the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">The <see cref="T:System.Windows.Interop.InteropBitmap" /> instance is frozen and cannot have its members written to.</exception>
       </Docs>
@@ -264,8 +264,8 @@
         <Parameter Name="dirtyRect" Type="System.Nullable&lt;System.Windows.Int32Rect&gt;" Index="0" FrameworkAlternate="net-5.0;netcore-3.0;netcore-3.1;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="dirtyRect">The area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to be rendered. If this parameter is null, the entire non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] is rendered.</param>
-        <summary>Forces the specified area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to be rendered.</summary>
+        <param name="dirtyRect">The area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered. If this parameter is null, the entire non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI is rendered.</param>
+        <summary>Forces the specified area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">The <see cref="T:System.Windows.Interop.InteropBitmap" /> instance is frozen and cannot have its members written to.</exception>
       </Docs>
diff --git a/xml/System.Windows.Navigation/CustomContentState.xml b/xml/System.Windows.Navigation/CustomContentState.xml
index e7f756a65f7..29f618d4d90 100644
--- a/xml/System.Windows.Navigation/CustomContentState.xml
+++ b/xml/System.Windows.Navigation/CustomContentState.xml
@@ -58,7 +58,7 @@
   
  When the navigation history entry is navigated to, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] checks to see if a custom <xref:System.Windows.Navigation.CustomContentState> object is associated with it. If so, it calls <xref:System.Windows.Navigation.CustomContentState.Replay%2A> to allow the custom <xref:System.Windows.Navigation.CustomContentState> object to apply the state it remembered from the previous navigation.  
   
- A custom <xref:System.Windows.Navigation.CustomContentState> class can override <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> to change the name that appears for the navigation history entry to which the <xref:System.Windows.Navigation.CustomContentState> object is associated. The value that <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> returns is visible from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the various navigators (Internet Explorer 7, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
+ A custom <xref:System.Windows.Navigation.CustomContentState> class can override <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> to change the name that appears for the navigation history entry to which the <xref:System.Windows.Navigation.CustomContentState> object is associated. The value that <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> returns is visible from the navigation UI of the various navigators (Internet Explorer 7, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
  A class that derives from <xref:System.Windows.Navigation.CustomContentState> must be serializable, which means it must at least be augmented with <xref:System.SerializableAttribute>, and optionally implement <xref:System.Runtime.Serialization.ISerializable>.  
   
@@ -122,13 +122,13 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The name for the content that is stored in navigation history. The value of <see cref="P:System.Windows.Navigation.CustomContentState.JournalEntryName" /> is displayed from <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />, and [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].</summary>
+        <summary>The name for the content that is stored in navigation history. The value of <see cref="P:System.Windows.Navigation.CustomContentState.JournalEntryName" /> is displayed from <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />, and [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI.</summary>
         <value>The <see cref="T:System.String" /> name of the content that is stored in navigation history.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Entries stored in back and forward navigation history are typically available from the back and forward drop down navigation buttons on the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of the host navigator, including <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)].  
+ Entries stored in back and forward navigation history are typically available from the back and forward drop down navigation buttons on the navigation UI of the host navigator, including <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)].  
   
  <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> is the <xref:System.String> value that is displayed in a navigation history drop down list.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
index 98cd59b9795..7613aa60e5d 100644
--- a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
+++ b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
@@ -46,7 +46,7 @@
   
  To create the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame> use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to merge their individual back navigation history and forward navigation history into a single list of navigation history entries. The resulting list contains up to nine entries from back navigation history and up to nine entries from forward navigation history, plus an entry for the current content.  
   
- If you create custom navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)], and need to provide an [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, you can use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to similar effect.  
+ If you create custom navigation UI, and need to provide an [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, you can use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to similar effect.  
   
 ## XAML Attribute Usage  
  This class is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 2a8a4139215..35c97d03093 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -77,10 +77,10 @@
   
 -   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] the relevant navigation history entries are also added to Internet Explorer 7 navigation history.  
   
--   When entries in the Internet Explorer 7 navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] are selected, Internet Explorer 7 causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
+-   When entries in the Internet Explorer 7 navigation UI are selected, Internet Explorer 7 causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
   
 > [!NOTE]
->  A <xref:System.Windows.Controls.Frame> can provide its own navigation history, or use the navigation history of the navigator that hosts it. If <xref:System.Windows.Controls.Frame> provides its own navigation history, it can display its own navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] to navigate through the entries in navigation history; those entries are not added to the navigation history of the host navigator (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, Internet Explorer) and, consequently, cannot be navigated to from the navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] of each (see <xref:System.Windows.Controls.Frame.JournalOwnership%2A>).  
+>  A <xref:System.Windows.Controls.Frame> can provide its own navigation history, or use the navigation history of the navigator that hosts it. If <xref:System.Windows.Controls.Frame> provides its own navigation history, it can display its own navigation UI to navigate through the entries in navigation history; those entries are not added to the navigation history of the host navigator (<xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, Internet Explorer) and, consequently, cannot be navigated to from the navigation UI of each (see <xref:System.Windows.Controls.Frame.JournalOwnership%2A>).  
   
  ]]></format>
     </remarks>
@@ -923,7 +923,7 @@
   
 -   <xref:System.Windows.Navigation.NavigationService.Navigate%2A> is called.  
   
--   <xref:System.Windows.Navigation.NavigationService.GoBack%2A> or <xref:System.Windows.Navigation.NavigationService.GoForward%2A> is called (or an entry is selected from a navigation [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]).  
+-   <xref:System.Windows.Navigation.NavigationService.GoBack%2A> or <xref:System.Windows.Navigation.NavigationService.GoForward%2A> is called (or an entry is selected from a navigation UI).  
   
 -   A content fragment is navigated to.  
   
diff --git a/xml/System.Windows.Threading/Dispatcher.xml b/xml/System.Windows.Threading/Dispatcher.xml
index f9cf4cf9718..9d17fba7961 100644
--- a/xml/System.Windows.Threading/Dispatcher.xml
+++ b/xml/System.Windows.Threading/Dispatcher.xml
@@ -30,7 +30,7 @@
   
  If a <xref:System.Windows.Threading.Dispatcher> is shut down, it cannot be restarted.  
   
- In WPF, a <xref:System.Windows.Threading.DispatcherObject> can only be accessed by the <xref:System.Windows.Threading.Dispatcher> it is associated with.  For example, a background thread cannot update the contents of a <xref:System.Windows.Controls.Button> that is associated with the <xref:System.Windows.Threading.Dispatcher> on the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread.  In order for the background thread to access the <xref:System.Windows.Controls.ContentControl.Content%2A> property of the <xref:System.Windows.Controls.Button>, the background thread must delegate the work to the <xref:System.Windows.Threading.Dispatcher> associated with the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] thread.  This is accomplished by using either <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. <xref:System.Windows.Threading.Dispatcher.Invoke%2A> is synchronous and <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A> is asynchronous.  The operation is added to the queue of the <xref:System.Windows.Threading.Dispatcher> at the specified <xref:System.Windows.Threading.DispatcherPriority>.  
+ In WPF, a <xref:System.Windows.Threading.DispatcherObject> can only be accessed by the <xref:System.Windows.Threading.Dispatcher> it is associated with.  For example, a background thread cannot update the contents of a <xref:System.Windows.Controls.Button> that is associated with the <xref:System.Windows.Threading.Dispatcher> on the UI thread.  In order for the background thread to access the <xref:System.Windows.Controls.ContentControl.Content%2A> property of the <xref:System.Windows.Controls.Button>, the background thread must delegate the work to the <xref:System.Windows.Threading.Dispatcher> associated with the UI thread.  This is accomplished by using either <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. <xref:System.Windows.Threading.Dispatcher.Invoke%2A> is synchronous and <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A> is asynchronous.  The operation is added to the queue of the <xref:System.Windows.Threading.Dispatcher> at the specified <xref:System.Windows.Threading.DispatcherPriority>.  
   
  If <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A> is called on a <xref:System.Windows.Threading.Dispatcher> that has shut down, the status property of the returned <xref:System.Windows.Threading.DispatcherOperation> is set to <xref:System.Windows.Threading.DispatcherOperationStatus.Aborted>.  
   
diff --git a/xml/System.Windows/CoerceValueCallback.xml b/xml/System.Windows/CoerceValueCallback.xml
index 014aa36601d..fdc357f3049 100644
--- a/xml/System.Windows/CoerceValueCallback.xml
+++ b/xml/System.Windows/CoerceValueCallback.xml
@@ -51,7 +51,7 @@
    
   
 ## Examples  
- The following example includes an implementation of this callback to coerce the stored value of a dependency property based on other inputs, such as another property's value. In this case, the callback checks to see whether the `ShirtType` property corresponds to a type of shirt that has buttons; if so it establishes a starting default color for the `ButtonColor`, if the shirt type has no buttons, it coerces the `ButtonColor` value back to a starting value, which causes the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] (not shown) to remove that dropdown from the effective choices.  
+ The following example includes an implementation of this callback to coerce the stored value of a dependency property based on other inputs, such as another property's value. In this case, the callback checks to see whether the `ShirtType` property corresponds to a type of shirt that has buttons; if so it establishes a starting default color for the `ButtonColor`, if the shirt type has no buttons, it coerces the `ButtonColor` value back to a starting value, which causes the UI (not shown) to remove that dropdown from the effective choices.  
   
  [!code-csharp[DPCustom#CoerceValueCallback](~/samples/snippets/csharp/VS_Snippets_Wpf/DPCustom/CSharp/default.xaml.cs#coercevaluecallback)]
  [!code-vb[DPCustom#CoerceValueCallback](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DPCustom/visualbasic/default.xaml.vb#coercevaluecallback)]  
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index 64af0022697..db309b3e6f9 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -10359,7 +10359,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
    
   
 ## Examples  
- The following handler captures or releases mouse capture according to mouse button states. The example shows how to use captured mouse movement for alternative purposes other than moving the mouse pointer in the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  
+ The following handler captures or releases mouse capture according to mouse button states. The example shows how to use captured mouse movement for alternative purposes other than moving the mouse pointer in the UI.  
   
  [!code-csharp[ContentElementsSmorgasbord#UIElementMouseCapture](~/samples/snippets/csharp/VS_Snippets_Wpf/ContentElementsSmorgasbord/CSharp/Trackball.cs#uielementmousecapture)]
  [!code-vb[ContentElementsSmorgasbord#UIElementMouseCapture](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ContentElementsSmorgasbord/visualbasic/trackball.vb#uielementmousecapture)]  
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index e48fb954e98..442246b8e36 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -1187,7 +1187,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Setting this property to `true` will override the cursor preferences established by child elements. Doing so in general application [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] might be confusing for the user, particularly if child elements are attempting to specify cursors. Setting <xref:System.Windows.FrameworkElement.ForceCursor%2A> is more appropriate in control subclassing or compositing scenarios.  
+ Setting this property to `true` will override the cursor preferences established by child elements. Doing so in general application UI might be confusing for the user, particularly if child elements are attempting to specify cursors. Setting <xref:System.Windows.FrameworkElement.ForceCursor%2A> is more appropriate in control subclassing or compositing scenarios.  
   
 <a name="dependencyPropertyInfo_ForceCursor"></a>   
 ## Dependency Property Information  
@@ -1705,7 +1705,7 @@
   
  This property essentially provides a WPF framework-level convenience property to set the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive).  
   
- Getting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code is not common, because if you have the appropriate reference in code already, you can just call methods and properties on the element reference and do not generally need the <xref:System.Windows.FrameworkContentElement.Name%2A>. An exception is if the string has some overloaded meaning, for instance if it is useful to display that name in [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]. Setting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code if the original <xref:System.Windows.FrameworkContentElement.Name%2A> was set from markup is also not recommended, and changing the property will not change the object reference. Such object references are created only when the underlying namescopes are explicitly created during [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] loading.  
+ Getting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code is not common, because if you have the appropriate reference in code already, you can just call methods and properties on the element reference and do not generally need the <xref:System.Windows.FrameworkContentElement.Name%2A>. An exception is if the string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code if the original <xref:System.Windows.FrameworkContentElement.Name%2A> was set from markup is also not recommended, and changing the property will not change the object reference. Such object references are created only when the underlying namescopes are explicitly created during [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] loading.  
   
  You must specifically call <xref:System.Windows.FrameworkContentElement.RegisterName%2A> to make an effective change on the <xref:System.Windows.FrameworkContentElement.Name%2A> property of an already loaded element.  
   
@@ -2894,7 +2894,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the value of this property is of type <xref:System.Windows.Controls.ToolTip>, then that is the tool-tip that will be used in the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  If the value is of any other type, then that value will be used as the *content* for a <xref:System.Windows.Controls.ToolTip> provided (constructed) by the system. For more information see <xref:System.Windows.Controls.ToolTipService>. The service class provides attached properties that can be used to further customize a tool-tip.  
+ If the value of this property is of type <xref:System.Windows.Controls.ToolTip>, then that is the tool-tip that will be used in the UI.  If the value is of any other type, then that value will be used as the *content* for a <xref:System.Windows.Controls.ToolTip> provided (constructed) by the system. For more information see <xref:System.Windows.Controls.ToolTipService>. The service class provides attached properties that can be used to further customize a tool-tip.  
   
 <a name="xamlAttributeUsage_ToolTip"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 5349239b993..327c2d413f5 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -1521,7 +1521,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the direction that text and other [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements flow within any parent element that controls their layout.</summary>
-        <value>The direction that text and other [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] elements flow within their parent element, as a value of the enumeration. The default value is <see cref="F:System.Windows.FlowDirection.LeftToRight" />.</value>
+        <value>The direction that text and other UI elements flow within their parent element, as a value of the enumeration. The default value is <see cref="F:System.Windows.FlowDirection.LeftToRight" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1687,7 +1687,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If you set this property to `true` you will override the cursor preferences established by child elements. Doing so in general application [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] might be confusing for the user, particularly if child elements are attempting to specify cursors. Setting <xref:System.Windows.FrameworkElement.ForceCursor%2A> is more appropriate in control subclassing or compositing scenarios.  
+ If you set this property to `true` you will override the cursor preferences established by child elements. Doing so in general application UI might be confusing for the user, particularly if child elements are attempting to specify cursors. Setting <xref:System.Windows.FrameworkElement.ForceCursor%2A> is more appropriate in control subclassing or compositing scenarios.  
   
 <a name="dependencyPropertyInfo_ForceCursor"></a>   
 ## Dependency Property Information  
@@ -3331,7 +3331,7 @@
   
  Names must be unique within a namescope. For more information, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
   
- Getting a <xref:System.Windows.FrameworkElement.Name%2A> if you are creating elements in code is not common. If you have the appropriate reference in code already, you can just call methods and properties on the element reference and will not generally need the <xref:System.Windows.FrameworkElement.Name%2A>. An exception to this is if the <xref:System.Windows.FrameworkElement.Name%2A> string has some overloaded meaning, for instance if it is useful to display that name in [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]. Setting a <xref:System.Windows.FrameworkElement.Name%2A> from code-behind if the original <xref:System.Windows.FrameworkElement.Name%2A> was set from markup is also not recommended, and changing the property after loading the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will not change the original object reference. The object references are created only when the underlying namescopes are explicitly created during parsing. You must specifically call <xref:System.Windows.FrameworkElement.RegisterName%2A> to make an effective change to the <xref:System.Windows.FrameworkElement.Name%2A> property of an already loaded element.  
+ Getting a <xref:System.Windows.FrameworkElement.Name%2A> if you are creating elements in code is not common. If you have the appropriate reference in code already, you can just call methods and properties on the element reference and will not generally need the <xref:System.Windows.FrameworkElement.Name%2A>. An exception to this is if the <xref:System.Windows.FrameworkElement.Name%2A> string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkElement.Name%2A> from code-behind if the original <xref:System.Windows.FrameworkElement.Name%2A> was set from markup is also not recommended, and changing the property after loading the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will not change the original object reference. The object references are created only when the underlying namescopes are explicitly created during parsing. You must specifically call <xref:System.Windows.FrameworkElement.RegisterName%2A> to make an effective change to the <xref:System.Windows.FrameworkElement.Name%2A> property of an already loaded element.  
   
  One notable case where setting <xref:System.Windows.FrameworkElement.Name%2A> from code is important is when registering names for elements that storyboards will run against, so that they can be referenced at run time. Before you can register a name, might also need to instantiate and assign a <xref:System.Windows.NameScope> instance. See the Example section, or [Storyboards Overview](/dotnet/framework/wpf/graphics-multimedia/storyboards-overview).  
   
@@ -3850,7 +3850,7 @@
  The most common usage of this property is an indirect usage within the setter of a style that is supplying a themed style.  
   
 > [!IMPORTANT]
->  If you set <xref:System.Windows.FrameworkElement.OverridesDefaultStyle%2A> to `true` on a control, you will be suppressing the default control template supplied by the theme styles. That control template typically includes the content presenter and other composited elements that provide basic [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] functionality and visualization for the control. If you want the control to continue to support the same features as the default theme styles, you must supply an alternate style with a control template that replicates the same structure. For more information, see [Control Authoring Overview](/dotnet/framework/wpf/controls/control-authoring-overview).  
+>  If you set <xref:System.Windows.FrameworkElement.OverridesDefaultStyle%2A> to `true` on a control, you will be suppressing the default control template supplied by the theme styles. That control template typically includes the content presenter and other composited elements that provide basic UI functionality and visualization for the control. If you want the control to continue to support the same features as the default theme styles, you must supply an alternate style with a control template that replicates the same structure. For more information, see [Control Authoring Overview](/dotnet/framework/wpf/controls/control-authoring-overview).  
   
 <a name="dependencyPropertyInfo_OverridesDefaultStyle"></a>   
 ## Dependency Property Information  
@@ -4949,7 +4949,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the value of this property is of type <xref:System.Windows.Controls.ToolTip>, then that value is the tool-tip that will be used in the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)].  If the value is of any other type, then that value will be used as the *content* for a <xref:System.Windows.Controls.ToolTip> provided (constructed) by the system. For more information, see <xref:System.Windows.Controls.ToolTipService>. The service class provides attached properties that can be used to further customize a <xref:System.Windows.Controls.ToolTip>.  
+ If the value of this property is of type <xref:System.Windows.Controls.ToolTip>, then that value is the tool-tip that will be used in the UI.  If the value is of any other type, then that value will be used as the *content* for a <xref:System.Windows.Controls.ToolTip> provided (constructed) by the system. For more information, see <xref:System.Windows.Controls.ToolTipService>. The service class provides attached properties that can be used to further customize a <xref:System.Windows.Controls.ToolTip>.  
   
 <a name="xamlAttributeUsage_ToolTip"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows/Style.xml b/xml/System.Windows/Style.xml
index ae86dcc6744..016e56fc6a7 100644
--- a/xml/System.Windows/Style.xml
+++ b/xml/System.Windows/Style.xml
@@ -59,7 +59,7 @@
 > [!NOTE]
 >  If there is more than one setter in the setter collection with the same <xref:System.Windows.Setter.Property%2A> property value, the setter that is declared last is used. Similarly, if you set a value for the same property in a style and on an element directly, the value set on the element directly takes precedence.  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] styling and templating model allows maintenance and sharing of a look as well as the separation of presentation and logic. The styling and templating model includes a suite of features that enable you to customize your [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]. This suite of features includes the <xref:System.Windows.Style> class as well as the following:  
+ The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] styling and templating model allows maintenance and sharing of a look as well as the separation of presentation and logic. The styling and templating model includes a suite of features that enable you to customize your UI. This suite of features includes the <xref:System.Windows.Style> class as well as the following:  
   
 -   <xref:System.Windows.Trigger>  
   
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index 1b03e5a696a..283efe7ba31 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -7977,7 +7977,7 @@
       <Docs>
         <summary>Gets a value that indicates whether all [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] effects are enabled.</summary>
         <value>
-          <see langword="true" /> if all [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] effects are enabled; <see langword="false" /> if they are disabled.</value>
+          <see langword="true" /> if all UI effects are enabled; <see langword="false" /> if they are disabled.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index cbdd76753e8..439d4a0c73a 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -1420,7 +1420,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  The value returned by this property will only be a valid measurement if the value of the <xref:System.Windows.UIElement.IsMeasureValid%2A> property is `true`.  
   
- <xref:System.Windows.UIElement.DesiredSize%2A> is typically checked as one of the measurement factors when you implement layout behavior overrides such as <xref:System.Windows.FrameworkElement.ArrangeOverride%2A>, <xref:System.Windows.FrameworkElement.MeasureOverride%2A>, or <xref:System.Windows.UIElement.OnRender%2A> (in the <xref:System.Windows.UIElement.OnRender%2A> case, you might check <xref:System.Windows.UIElement.RenderSize%2A> instead, but this depends on your implementation). Depending on the scenario, <xref:System.Windows.UIElement.DesiredSize%2A> might be fully respected by your implementation logic, constraints on <xref:System.Windows.UIElement.DesiredSize%2A> might be applied, and such constraints might also change other characteristics of either the parent element or child element. For example, a control that supports scrollable regions (but chooses not to derive from the WPF framework-level controls that already enable scrollable regions) could compare available size to <xref:System.Windows.UIElement.DesiredSize%2A>. The control could then set an internal state that enabled scrollbars in the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] for that control. Or, <xref:System.Windows.UIElement.DesiredSize%2A> could potentially also be ignored in certain scenarios.  
+ <xref:System.Windows.UIElement.DesiredSize%2A> is typically checked as one of the measurement factors when you implement layout behavior overrides such as <xref:System.Windows.FrameworkElement.ArrangeOverride%2A>, <xref:System.Windows.FrameworkElement.MeasureOverride%2A>, or <xref:System.Windows.UIElement.OnRender%2A> (in the <xref:System.Windows.UIElement.OnRender%2A> case, you might check <xref:System.Windows.UIElement.RenderSize%2A> instead, but this depends on your implementation). Depending on the scenario, <xref:System.Windows.UIElement.DesiredSize%2A> might be fully respected by your implementation logic, constraints on <xref:System.Windows.UIElement.DesiredSize%2A> might be applied, and such constraints might also change other characteristics of either the parent element or child element. For example, a control that supports scrollable regions (but chooses not to derive from the WPF framework-level controls that already enable scrollable regions) could compare available size to <xref:System.Windows.UIElement.DesiredSize%2A>. The control could then set an internal state that enabled scrollbars in the UI for that control. Or, <xref:System.Windows.UIElement.DesiredSize%2A> could potentially also be ignored in certain scenarios.  
   
    
   
@@ -3117,7 +3117,7 @@ Image with an Elliptical Clip Region
   
  [!code-csharp[PopupSimple#IsFocused](~/samples/snippets/csharp/VS_Snippets_Wpf/PopupSimple/CSharp/Window1.xaml.cs#isfocused)]  
   
- Another common way to achieve this same effect is to place a <xref:System.Windows.Trigger> in the <xref:System.Windows.Style> of a control; this approach does not require handling specific events with code-behind and allows designers greater access to the interactive and graphical nature of the [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)]. For an example, see [How to: Create an Outer Glow Effect](https://msdn.microsoft.com/library/a2ccf19a-d0dc-4e3c-88e3-95d7f7d765b1).  
+ Another common way to achieve this same effect is to place a <xref:System.Windows.Trigger> in the <xref:System.Windows.Style> of a control; this approach does not require handling specific events with code-behind and allows designers greater access to the interactive and graphical nature of the UI. For an example, see [How to: Create an Outer Glow Effect](https://msdn.microsoft.com/library/a2ccf19a-d0dc-4e3c-88e3-95d7f7d765b1).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index 6c27f3b5783..9b2947cb989 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2071,7 +2071,7 @@
   
  Modal windows are primarily used as dialog boxes. A dialog box is a special type of window that applications use to interact with users to complete tasks, such as opening files or printing documents. Dialog boxes commonly allow users to accept or cancel the task for which they were shown before the dialog box is closed. <xref:System.Windows.Window.ShowDialog%2A> returns a <xref:System.Nullable%601><xref:System.Boolean> value that specifies whether the activity was accepted or canceled. The return value is the value of the <xref:System.Windows.Window.DialogResult%2A> property before a window closes. For more information, see <xref:System.Windows.Window.DialogResult%2A>.  
   
- A window that is opened by calling the <xref:System.Windows.Window.ShowDialog%2A> method does not automatically have a relationship with the window that opened it; specifically, the opened window does not know which window opened it. This relationship can be established using the <xref:System.Windows.Window.Owner%2A> property and managed using the <xref:System.Windows.Window.OwnedWindows%2A> property. To support [!INCLUDE[TLA2#tla_ui](~/includes/tla2sharptla-ui-md.md)] automation (see [UI Automation Overview](/dotnet/framework/ui-automation/ui-automation-overview)), <xref:System.Windows.Window.Owner%2A> must be set for a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>.  
+ A window that is opened by calling the <xref:System.Windows.Window.ShowDialog%2A> method does not automatically have a relationship with the window that opened it; specifically, the opened window does not know which window opened it. This relationship can be established using the <xref:System.Windows.Window.Owner%2A> property and managed using the <xref:System.Windows.Window.OwnedWindows%2A> property. To support UI automation (see [UI Automation Overview](/dotnet/framework/ui-automation/ui-automation-overview)), <xref:System.Windows.Window.Owner%2A> must be set for a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>.  
   
  When a modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window (a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>) is closed, the previously activated window is reactivated. If a modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window has an owner window (see <xref:System.Windows.Window.Owner%2A>), the owner window is not reactivated when the modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window is closed unless it was the previously activated window.  
   

From 5bad32dc0a7781d5de34666c4b5ad2f32c9a28e9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:38:30 -0800
Subject: [PATCH 087/236] tla2sharptla-uiautomation

---
 .../AutomationPeer.xml                        | 22 ++++-----
 .../ButtonAutomationPeer.xml                  |  4 +-
 .../GridViewAutomationPeer.xml                |  2 +-
 .../IViewAutomationPeer.xml                   |  2 +-
 .../ItemAutomationPeer.xml                    | 10 ++--
 .../UIElement3DAutomationPeer.xml             |  2 +-
 .../AutomationInteropProvider.xml             | 10 ++--
 .../IGridProvider.xml                         |  4 +-
 .../IRawElementProviderFragment.xml           | 14 +++---
 .../IRawElementProviderHwndOverride.xml       |  2 +-
 .../IRawElementProviderSimple.xml             |  6 +--
 .../ITextProvider.xml                         |  2 +-
 .../ITextRangeProvider.xml                    |  2 +-
 .../ITransformProvider.xml                    |  2 +-
 .../ProviderOptions.xml                       |  2 +-
 .../TextPatternRange.xml                      |  4 +-
 .../AndCondition.xml                          |  2 +-
 .../AsyncContentLoadedState.xml               |  6 +--
 xml/System.Windows.Automation/Automation.xml  | 46 +++++++++----------
 ...onElement+AutomationElementInformation.xml | 20 ++++----
 .../AutomationElement.xml                     | 40 ++++++++--------
 .../AutomationElementIdentifiers.xml          | 46 +++++++++----------
 .../AutomationEventHandler.xml                |  2 +-
 .../AutomationFocusChangedEventHandler.xml    |  2 +-
 .../AutomationIdentifier.xml                  |  2 +-
 .../AutomationProperties.xml                  |  4 +-
 .../AutomationTextAttribute.xml               |  2 +-
 .../CacheRequest.xml                          | 10 ++--
 .../ClientSideProviderDescription.xml         |  2 +-
 xml/System.Windows.Automation/Condition.xml   |  4 +-
 xml/System.Windows.Automation/ControlType.xml | 12 ++---
 xml/System.Windows.Automation/DockPattern.xml |  8 ++--
 .../ExpandCollapsePattern.xml                 | 10 ++--
 ...ItemPattern+GridItemPatternInformation.xml |  4 +-
 .../GridPattern+GridPatternInformation.xml    |  4 +-
 xml/System.Windows.Automation/GridPattern.xml | 10 ++--
 .../GridPatternIdentifiers.xml                |  4 +-
 .../InvokePattern.xml                         |  2 +-
 .../MultipleViewPattern.xml                   |  8 ++--
 xml/System.Windows.Automation/OrCondition.xml |  2 +-
 .../PropertyCondition.xml                     |  2 +-
 ...uePattern+RangeValuePatternInformation.xml | 18 ++++----
 .../RangeValuePattern.xml                     |  2 +-
 ...ScrollPattern+ScrollPatternInformation.xml |  4 +-
 .../ScrollPattern.xml                         | 10 ++--
 .../SelectionItemPattern.xml                  |  2 +-
 .../SelectionPattern.xml                      | 12 ++---
 .../StructureChangeType.xml                   | 12 ++---
 .../StructureChangedEventArgs.xml             |  8 ++--
 ...temPattern+TableItemPatternInformation.xml |  4 +-
 .../TablePattern.xml                          |  6 +--
 xml/System.Windows.Automation/TextPattern.xml |  2 +-
 .../TextPatternIdentifiers.xml                |  4 +-
 .../TogglePattern.xml                         |  8 ++--
 ...ormPattern+TransformPatternInformation.xml |  6 +--
 .../TransformPattern.xml                      | 14 +++---
 xml/System.Windows.Automation/TreeWalker.xml  | 26 +++++------
 .../ValuePattern+ValuePatternInformation.xml  |  6 +--
 .../ValuePattern.xml                          |  4 +-
 .../WindowClosedEventArgs.xml                 |  8 ++--
 .../WindowPattern.xml                         | 10 ++--
 .../UIAutomationClientSideProviders.xml       |  2 +-
 62 files changed, 256 insertions(+), 256 deletions(-)

diff --git a/xml/System.Windows.Automation.Peers/AutomationPeer.xml b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
index 910ea8b52b4..f497bc7a31b 100644
--- a/xml/System.Windows.Automation.Peers/AutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] queries the root of a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application about an element, the root returns the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer for that element. The peer also responds to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] queries about its corresponding element.  
+ When UI Automation queries the root of a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application about an element, the root returns the UI Automation peer for that element. The peer also responds to UI Automation queries about its corresponding element.  
   
  ]]></format>
     </remarks>
@@ -103,7 +103,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets the accelerator key combinations for the element that is associated with the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the accelerator key combinations for the element that is associated with the UI Automation peer.</summary>
         <returns>The accelerator key.</returns>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">A public call to this method is currently in progress.</exception>
@@ -220,7 +220,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets the control type for the element that is associated with the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the control type for the element that is associated with the UI Automation peer.</summary>
         <returns>The control type.</returns>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">A public call to this method is currently in progress.</exception>
@@ -663,17 +663,17 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Tells [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] where in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree to place the <see langword="hwnd" /> being hosted by a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
-        <returns>This method returns the hosted <see langword="hwnd" /> to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] for controls that host <see langword="hwnd" /> objects.</returns>
+        <summary>Tells UI Automation where in the UI Automation tree to place the <see langword="hwnd" /> being hosted by a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
+        <returns>This method returns the hosted <see langword="hwnd" /> to UI Automation for controls that host <see langword="hwnd" /> objects.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method returns the hosted `hwnd` to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] for controls that host `hwnd` objects.  
+ This method returns the hosted `hwnd` to UI Automation for controls that host `hwnd` objects.  
   
  The <xref:System.Windows.Automation.Peers.AutomationPeer> that is associated with an element that immediately hosts an `hwnd` must override this method.  
   
- If this method is not overridden, [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] places the `hwnd` as a child element of the <xref:System.Windows.Interop.HwndSource> that hosts the whole application. Typically, you want to override this default behavior and set [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] to position the hosted `hwnd` parallel to the place where it is located in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] logical tree.  
+ If this method is not overridden, UI Automation places the `hwnd` as a child element of the <xref:System.Windows.Interop.HwndSource> that hosts the whole application. Typically, you want to override this default behavior and set UI Automation to position the hosted `hwnd` parallel to the place where it is located in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] logical tree.  
   
  Except in hosting scenarios, do not allow <xref:System.Windows.Automation.Peers.AutomationPeer> types to override this method.  
   
@@ -1844,16 +1844,16 @@ This method calls the derived implementation of <xref:System.Windows.Automation.
       </Parameters>
       <Docs>
         <param name="eventId">One of the enumeration values.</param>
-        <summary>Gets a value that indicates whether [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is listening for the specified event.</summary>
-        <returns>A <see langword="boolean" /> that indicates whether [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is listening for the event.</returns>
+        <summary>Gets a value that indicates whether UI Automation is listening for the specified event.</summary>
+        <returns>A <see langword="boolean" /> that indicates whether UI Automation is listening for the event.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Typically, you call this method before creating the <xref:System.Windows.Automation.Peers.AutomationPeer> that raises the event. This method is a performance measure because if [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] does not listen for the event, it does not make sense to create a peer to raise one.  
+ Typically, you call this method before creating the <xref:System.Windows.Automation.Peers.AutomationPeer> that raises the event. This method is a performance measure because if UI Automation does not listen for the event, it does not make sense to create a peer to raise one.  
   
 > [!NOTE]
->  This method is static and only answers if a delegate listens for the specified event in [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)], not for an event on a specific element. [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] can create broadcast listeners; therefore the per-element information is irrelevant.  
+>  This method is static and only answers if a delegate listens for the specified event in UI Automation, not for an event on a specific element. UI Automation can create broadcast listeners; therefore the per-element information is irrelevant.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
index 757473264cb..00f1d15c188 100644
--- a/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
@@ -72,7 +72,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets the control type of the element that is associated with the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the control type of the element that is associated with the UI Automation peer.</summary>
         <returns>The <see cref="F:System.Windows.Automation.Peers.AutomationControlType.Button" /> enumeration value.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -96,7 +96,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Gets the name of the control that is associated with this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the name of the control that is associated with this UI Automation peer.</summary>
         <returns>A string that contains "Button".</returns>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/ui-automation/ui-automation-control-types">UI Automation Control Types</related>
diff --git a/xml/System.Windows.Automation.Peers/GridViewAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GridViewAutomationPeer.xml
index 29c6e4bf77e..68a36d4e695 100644
--- a/xml/System.Windows.Automation.Peers/GridViewAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GridViewAutomationPeer.xml
@@ -152,7 +152,7 @@
       </Parameters>
       <Docs>
         <param name="children">Collection of child objects you want to get.</param>
-        <summary>Gets the collection of immediate child elements of the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the collection of immediate child elements of the specified UI Automation peer.</summary>
         <returns>Collection of child objects.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation.Peers/IViewAutomationPeer.xml b/xml/System.Windows.Automation.Peers/IViewAutomationPeer.xml
index cb44b5406bf..518ec89d9f0 100644
--- a/xml/System.Windows.Automation.Peers/IViewAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/IViewAutomationPeer.xml
@@ -106,7 +106,7 @@
       </Parameters>
       <Docs>
         <param name="children">The automation peers for the list items.</param>
-        <summary>Gets the collection of immediate child elements of the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer.</summary>
+        <summary>Gets the collection of immediate child elements of the specified UI Automation peer.</summary>
         <returns>The automation peers for all items in the control. If the view contains interactive or informational elements in addition to the list items, automation peers for these elements must be added to the list.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Controls.ViewBase" />
diff --git a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
index 9531bbbce51..9d042984368 100644
--- a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
@@ -30,9 +30,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Data items that are not also <xref:System.Windows.UIElement> types do not have children; however, they can have a <xref:System.Windows.UIElement> tree and a corresponding [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree.  
+ Data items that are not also <xref:System.Windows.UIElement> types do not have children; however, they can have a <xref:System.Windows.UIElement> tree and a corresponding UI Automation tree.  
   
- For example, a <xref:System.Windows.Controls.ListBox> can have a collection of strings that contain data items. When those items are processed by an <xref:System.Windows.Controls.ItemsControl> for visualization, a <xref:System.Windows.UIElement> tree is created for them. This tree can have a corresponding [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree. After the tree is created, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] merges the <xref:System.Windows.UIElement> tree into a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree. <xref:System.Windows.Automation.Peers.ItemAutomationPeer> works with its <xref:System.Windows.UIElement> counterpart, if it exists, to obtain more information about the <xref:System.Windows.UIElement> tree.  
+ For example, a <xref:System.Windows.Controls.ListBox> can have a collection of strings that contain data items. When those items are processed by an <xref:System.Windows.Controls.ItemsControl> for visualization, a <xref:System.Windows.UIElement> tree is created for them. This tree can have a corresponding UI Automation tree. After the tree is created, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] merges the <xref:System.Windows.UIElement> tree into a UI Automation tree. <xref:System.Windows.Automation.Peers.ItemAutomationPeer> works with its <xref:System.Windows.UIElement> counterpart, if it exists, to obtain more information about the <xref:System.Windows.UIElement> tree.  
   
  Only visible data items, or more precisely, the corresponding <xref:System.Windows.UIElement> trees, have this dualism. Non-visible data items, which have no corresponding <xref:System.Windows.UIElement> trees, have only one <xref:System.Windows.Automation.Peers.ItemAutomationPeer>.  
   
@@ -155,12 +155,12 @@
       <Parameters />
       <Docs>
         <summary>Gets the string that uniquely identifies the <see cref="T:System.Windows.UIElement" /> that corresponds to the data item in the <see cref="P:System.Windows.Controls.ItemsControl.Items" /> collection that is associated with this <see cref="T:System.Windows.Automation.Peers.ItemAutomationPeer" />.</summary>
-        <returns>A string that contains the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] identifier.</returns>
+        <returns>A string that contains the UI Automation identifier.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] identifier is the <xref:System.Windows.Automation.AutomationProperties.AutomationId%2A> property. If the <xref:System.Windows.Automation.AutomationProperties.AutomationId%2A> property is not set, the value is the <xref:System.Windows.FrameworkElement.Name%2A> property.  
+ The value of the UI Automation identifier is the <xref:System.Windows.Automation.AutomationProperties.AutomationId%2A> property. If the <xref:System.Windows.Automation.AutomationProperties.AutomationId%2A> property is not set, the value is the <xref:System.Windows.FrameworkElement.Name%2A> property.  
   
  This method is called by <xref:System.Windows.Automation.Peers.AutomationPeer.GetAutomationId%2A>.  
   
@@ -681,7 +681,7 @@
       <Docs>
         <summary>Gets a value that indicates whether the specified <see cref="T:System.Windows.UIElement" /> can receive and send events.</summary>
         <returns>
-          <see langword="true" /> if the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] peer can receive and send events; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the UI Automation peer can receive and send events; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
index 1603634bcfe..a347c91cbc3 100644
--- a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, any class that inherits from <xref:System.Windows.UIElement3D> uses <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer> to communicate with [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)].  
+ By default, any class that inherits from <xref:System.Windows.UIElement3D> uses <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer> to communicate with UI Automation.  
   
  If you create a class that inherits from <xref:System.Windows.UIElement3D>, you may want to provide an automation peer to support the functionality of your class. Override the <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer.GetClassNameCore%2A> method to return a string that represents the type of the element associated with the <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer>. For example, if you create a class called `My3DElement` and an automation peer called `My3DElementAutomationPeer`, override the <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer.GetClassNameCore%2A> method to return the string "My3DElement".  
   
diff --git a/xml/System.Windows.Automation.Provider/AutomationInteropProvider.xml b/xml/System.Windows.Automation.Provider/AutomationInteropProvider.xml
index ef38f60567d..d3621d9a2a4 100644
--- a/xml/System.Windows.Automation.Provider/AutomationInteropProvider.xml
+++ b/xml/System.Windows.Automation.Provider/AutomationInteropProvider.xml
@@ -76,7 +76,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether any UI Automation client application is subscribed to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] events.</summary>
+        <summary>Gets a value that specifies whether any UI Automation client application is subscribed to UI Automation events.</summary>
         <value>
           <see langword="true" /> if a client is subscribed to events; otherwise <see langword="false" />.</value>
         <remarks>
@@ -120,7 +120,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The interface returned by this method can only be passed back to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)]. Attempting to call a method on the interface will raise an exception.  
+ The interface returned by this method can only be passed back to UI Automation. Attempting to call a method on the interface will raise an exception.  
   
    
   
@@ -253,7 +253,7 @@
       <Docs>
         <param name="element">The element associated with the event.</param>
         <param name="e">Information about the event.</param>
-        <summary>Raises an event when a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property has changed.</summary>
+        <summary>Raises an event when a UI Automation property has changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -291,14 +291,14 @@
       <Docs>
         <param name="provider">The element associated with the event.</param>
         <param name="e">Information about the event.</param>
-        <summary>Raises an event when the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree has changed.</summary>
+        <summary>Raises an event when the UI Automation tree has changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  An example of a change in the tree structure is child elements being added to or removed from a list box, or being expanded or collapsed in a tree view.  
   
- When a child element is removed, the runtime identifier of either the element, or of its container, is passed to the <xref:System.Windows.Automation.StructureChangedEventArgs> constructor. In the current version of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)], however, there is no easy way for an instance of a provider to discover its runtime identifier. The <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.GetRuntimeId%2A> method normally returns an array that contains <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId>, a magic number that instructs the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] system to create a unique identifer for every instance of the control. The raw value provided by <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.GetRuntimeId%2A> should not be used in events, because it is meaningless to clients and cannot be used to identify a specific instance.  
+ When a child element is removed, the runtime identifier of either the element, or of its container, is passed to the <xref:System.Windows.Automation.StructureChangedEventArgs> constructor. In the current version of UI Automation, however, there is no easy way for an instance of a provider to discover its runtime identifier. The <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.GetRuntimeId%2A> method normally returns an array that contains <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId>, a magic number that instructs the UI Automation system to create a unique identifer for every instance of the control. The raw value provided by <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.GetRuntimeId%2A> should not be used in events, because it is meaningless to clients and cannot be used to identify a specific instance.  
   
  Because of this limitation, events of type <xref:System.Windows.Automation.StructureChangeType.ChildAdded> and <xref:System.Windows.Automation.StructureChangeType.ChildRemoved> are not very useful. As an alternative, always use <xref:System.Windows.Automation.StructureChangeType.ChildrenBulkAdded> and <xref:System.Windows.Automation.StructureChangeType.ChildrenBulkRemoved>, passing 0 as the runtime identifer. You cannot use `null`, as this will raise an exception. Clients will be notified that a change has been made in the container (identified by the `sender` parameter passed to the <xref:System.Windows.Automation.StructureChangedEventHandler>), without specific notice of what children have been added or removed.  
   
diff --git a/xml/System.Windows.Automation.Provider/IGridProvider.xml b/xml/System.Windows.Automation.Provider/IGridProvider.xml
index 814b7fe9438..2b1a5979985 100644
--- a/xml/System.Windows.Automation.Provider/IGridProvider.xml
+++ b/xml/System.Windows.Automation.Provider/IGridProvider.xml
@@ -70,7 +70,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Hidden rows and columns, depending on the provider implementation, can be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
+ Hidden rows and columns, depending on the provider implementation, can be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
   
    
   
@@ -123,7 +123,7 @@
  ![Windows Explorer view showing ragged layout.](~/add/media/uia-gridpattern-ragged-array.PNG "Windows Explorer view showing ragged layout.")  
 Example of a Grid Control with Empty Coordinates  
   
--   Hidden rows and columns, depending on the provider implementation, can be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.Provider.IGridProvider.RowCount%2A> and <xref:System.Windows.Automation.Provider.IGridProvider.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they should not be counted.  
+-   Hidden rows and columns, depending on the provider implementation, can be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.Provider.IGridProvider.RowCount%2A> and <xref:System.Windows.Automation.Provider.IGridProvider.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they should not be counted.  
   
    
   
diff --git a/xml/System.Windows.Automation.Provider/IRawElementProviderFragment.xml b/xml/System.Windows.Automation.Provider/IRawElementProviderFragment.xml
index 73dc083ea1d..12ddb0ad8a7 100644
--- a/xml/System.Windows.Automation.Provider/IRawElementProviderFragment.xml
+++ b/xml/System.Windows.Automation.Provider/IRawElementProviderFragment.xml
@@ -144,13 +144,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves an array of fragment roots that are embedded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree rooted at the current element.</summary>
+        <summary>Retrieves an array of fragment roots that are embedded in the UI Automation element tree rooted at the current element.</summary>
         <returns>An array of root fragments, or <see langword="null" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method returns an array of fragments only if the current element is hosting another [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] framework. Most providers return `null`.  
+ This method returns an array of fragments only if the current element is hosting another UI Automation framework. Most providers return `null`.  
   
  ]]></format>
         </remarks>
@@ -184,12 +184,12 @@
 ## Remarks  
  Implementations should return `null` for an element that corresponds to a window handle. Other elements should return an array that contains <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId>, followed by a value that is unique within the fragment.  
   
- It is the provider's responsibility to ensure uniqueness within the fragment; for example, each item in a list must be individually numbered. The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] engine ensures that the identifier is unique among all instances, by translating the <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId> value.  
+ It is the provider's responsibility to ensure uniqueness within the fragment; for example, each item in a list must be individually numbered. The UI Automation engine ensures that the identifier is unique among all instances, by translating the <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId> value.  
   
    
   
 ## Examples  
- The following example code shows an implementation of this method by an element within a fragment, such as an item within a list box. The item has its own unique identifier within this instance of the fragment, and the <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId> value ensures that the identifier returned by the method is unique in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree.  
+ The following example code shows an implementation of this method by an element within a fragment, such as an item within a list box. The item has its own unique identifier within this instance of the fragment, and the <xref:System.Windows.Automation.Provider.AutomationInteropProvider.AppendRuntimeId> value ensures that the identifier returned by the method is unique in the UI Automation tree.  
   
  [!code-csharp[UIAFragmentProvider_snip#101](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAFragmentProvider_snip/CSharp/ListItemFragment.cs#101)]
  [!code-vb[UIAFragmentProvider_snip#101](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAFragmentProvider_snip/VisualBasic/ListItemFragment.vb#101)]  
@@ -221,13 +221,13 @@
       </Parameters>
       <Docs>
         <param name="direction">The direction in which to navigate.</param>
-        <summary>Retrieves the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element in a specified direction within the tree.</summary>
+        <summary>Retrieves the UI Automation element in a specified direction within the tree.</summary>
         <returns>The element in the specified direction, or <see langword="null" /> if there is no element in that direction</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] server's implementations of this method define the structure of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree.  
+ The UI Automation server's implementations of this method define the structure of the UI Automation element tree.  
   
  Navigation must be supported upward to the parent, downward to the first and last child, and laterally to the next and previous siblings, as applicable.  
   
@@ -279,7 +279,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] framework will ensure that the part of the interface that hosts this fragment is already focused before calling this method. Your implementation should update only its internal focus state; for example, by repainting a list item to show that it has the focus. If you prefer that [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] not focus the parent window, set the <xref:System.Windows.Automation.Provider.ProviderOptions.ProviderOwnsSetFocus> option in <xref:System.Windows.Automation.Provider.ProviderOptions> for the fragment root.  
+ The UI Automation framework will ensure that the part of the interface that hosts this fragment is already focused before calling this method. Your implementation should update only its internal focus state; for example, by repainting a list item to show that it has the focus. If you prefer that UI Automation not focus the parent window, set the <xref:System.Windows.Automation.Provider.ProviderOptions.ProviderOwnsSetFocus> option in <xref:System.Windows.Automation.Provider.ProviderOptions> for the fragment root.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Provider/IRawElementProviderHwndOverride.xml b/xml/System.Windows.Automation.Provider/IRawElementProviderHwndOverride.xml
index d9c65793f8a..48361d7b0be 100644
--- a/xml/System.Windows.Automation.Provider/IRawElementProviderHwndOverride.xml
+++ b/xml/System.Windows.Automation.Provider/IRawElementProviderHwndOverride.xml
@@ -65,7 +65,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is implemented by client-side UI Automation providers for fragment roots in fragments that contain window-based child elements, when the HWNDs of those child elements are not logically positioned within the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree. For more information, see Non-WPF Provider Reparenting and Non-WPF Provider Repositioning in the [Server-Side UI Automation Provider Implementation](/dotnet/framework/ui-automation/server-side-ui-automation-provider-implementation) topic.  
+ This method is implemented by client-side UI Automation providers for fragment roots in fragments that contain window-based child elements, when the HWNDs of those child elements are not logically positioned within the UI Automation tree. For more information, see Non-WPF Provider Reparenting and Non-WPF Provider Repositioning in the [Server-Side UI Automation Provider Implementation](/dotnet/framework/ui-automation/server-side-ui-automation-provider-implementation) topic.  
   
  The returned provider must be part of the fragment tree. It can supply additional properties or override properties of the specified component.  
   
diff --git a/xml/System.Windows.Automation.Provider/IRawElementProviderSimple.xml b/xml/System.Windows.Automation.Provider/IRawElementProviderSimple.xml
index 3a3cc0aff12..07842cc958c 100644
--- a/xml/System.Windows.Automation.Provider/IRawElementProviderSimple.xml
+++ b/xml/System.Windows.Automation.Provider/IRawElementProviderSimple.xml
@@ -66,7 +66,7 @@
       </Parameters>
       <Docs>
         <param name="patternId">Identifier of the pattern.</param>
-        <summary>Retrieves an object that provides support for a control pattern on a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Retrieves an object that provides support for a control pattern on a UI Automation element.</summary>
         <returns>Object that implements the pattern interface, or <see langword="null" /> if the pattern is not supported.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -151,7 +151,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is the UI Automation provider for the window of a custom control. [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] uses this provider in combination with your provider implementation for a control hosted in a window. For example, the run-time identifier of the element is obtained from the host provider.  
+ This property is the UI Automation provider for the window of a custom control. UI Automation uses this provider in combination with your provider implementation for a control hosted in a window. For example, the run-time identifier of the element is obtained from the host provider.  
   
  A host provider must be returned in any of the following cases:  
   
@@ -201,7 +201,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] treats different types of providers differently. For example, events from server-side providers are broadcast to all listening UI Automation client processes, but events from client-side providers remain in that client process.  
+ UI Automation treats different types of providers differently. For example, events from server-side providers are broadcast to all listening UI Automation client processes, but events from client-side providers remain in that client process.  
   
    
   
diff --git a/xml/System.Windows.Automation.Provider/ITextProvider.xml b/xml/System.Windows.Automation.Provider/ITextProvider.xml
index 23ce7ad84a7..33b44d31538 100644
--- a/xml/System.Windows.Automation.Provider/ITextProvider.xml
+++ b/xml/System.Windows.Automation.Provider/ITextProvider.xml
@@ -222,7 +222,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.ArgumentException">If a given point is outside the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element associated with the text pattern.</exception>
+        <exception cref="T:System.ArgumentException">If a given point is outside the UI Automation element associated with the text pattern.</exception>
         <altmember cref="T:System.Windows.Automation.Provider.ITextRangeProvider" />
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Provider/ITextRangeProvider.xml b/xml/System.Windows.Automation.Provider/ITextRangeProvider.xml
index f7d3472026d..d245e3cf3e9 100644
--- a/xml/System.Windows.Automation.Provider/ITextRangeProvider.xml
+++ b/xml/System.Windows.Automation.Provider/ITextRangeProvider.xml
@@ -524,7 +524,7 @@ Examples of how a text range is adjusted for Move() and ExpandToEnclosingUnit()
  ![Range adjustments by Move & ExpandToEnclosingUnit](~/add/media/uia-textpattern-moveandexpand-examples.png "Range adjustments by Move & ExpandToEnclosingUnit")  
 Examples of how a text range is adjusted for Move() and ExpandToEnclosingUnit()  
   
- The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree; object boundaries are ignored.  
+ The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the UI Automation tree; object boundaries are ignored.  
   
  ![Text ranges spanned by embedded objects.](~/add/media/uia-textpattern-embeddedobjecttextranges.png "Text ranges spanned by embedded objects.")  
 Example of a text stream with embedded objects and their range spans  
diff --git a/xml/System.Windows.Automation.Provider/ITransformProvider.xml b/xml/System.Windows.Automation.Provider/ITransformProvider.xml
index 72fbd45849b..748f775b69e 100644
--- a/xml/System.Windows.Automation.Provider/ITransformProvider.xml
+++ b/xml/System.Windows.Automation.Provider/ITransformProvider.xml
@@ -99,7 +99,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element can be resized.</summary>
+        <summary>Gets a value that specifies whether the UI Automation element can be resized.</summary>
         <value>
           <see langword="true" /> if the element can be resized; otherwise <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Automation.Provider/ProviderOptions.xml b/xml/System.Windows.Automation.Provider/ProviderOptions.xml
index 6f4ddf9ab82..69abbf37a04 100644
--- a/xml/System.Windows.Automation.Provider/ProviderOptions.xml
+++ b/xml/System.Windows.Automation.Provider/ProviderOptions.xml
@@ -111,7 +111,7 @@
       </ReturnValue>
       <MemberValue>16</MemberValue>
       <Docs>
-        <summary>The UI Automation provider handles its own focus, and does not want [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] to set focus to the nearest window on its behalf when <see cref="M:System.Windows.Automation.AutomationElement.SetFocus" /> is called. This option is typically used by providers for windows that appear to take focus without actually receiving [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] focus, such as menus and drop-down menus.</summary>
+        <summary>The UI Automation provider handles its own focus, and does not want UI Automation to set focus to the nearest window on its behalf when <see cref="M:System.Windows.Automation.AutomationElement.SetFocus" /> is called. This option is typically used by providers for windows that appear to take focus without actually receiving [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] focus, such as menus and drop-down menus.</summary>
       </Docs>
     </Member>
     <Member MemberName="ServerSideProvider">
diff --git a/xml/System.Windows.Automation.Text/TextPatternRange.xml b/xml/System.Windows.Automation.Text/TextPatternRange.xml
index f8e235631b9..1d0896f6211 100644
--- a/xml/System.Windows.Automation.Text/TextPatternRange.xml
+++ b/xml/System.Windows.Automation.Text/TextPatternRange.xml
@@ -629,7 +629,7 @@ Examples of how a text range is adjusted for Move() and ExpandToEnclosingUnit()
  ![Range adjustments by Move & ExpandToEnclosingUnit](~/add/media/uia-textpattern-moveandexpand-examples.png "Range adjustments by Move & ExpandToEnclosingUnit")  
 Examples of how a text range is adjusted for Move() and ExpandToEnclosingUnit()  
   
- The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree; object boundaries are ignored. If a UI Automation client is retrieving the text for the purpose of reciting, interpreting, or analyzing in some manner, the text range should be checked for special cases, such as a table with textual content or other embedded objects. This can be accomplished by calling <xref:System.Windows.Automation.Text.TextPatternRange.GetChildren%2A> to obtain an <xref:System.Windows.Automation.AutomationElement> for each embedded object and then calling <xref:System.Windows.Automation.TextPattern.RangeFromChild%2A> to obtain a text range for each element; this is done recursively until all textual content has been retrieved.  
+ The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the UI Automation tree; object boundaries are ignored. If a UI Automation client is retrieving the text for the purpose of reciting, interpreting, or analyzing in some manner, the text range should be checked for special cases, such as a table with textual content or other embedded objects. This can be accomplished by calling <xref:System.Windows.Automation.Text.TextPatternRange.GetChildren%2A> to obtain an <xref:System.Windows.Automation.AutomationElement> for each embedded object and then calling <xref:System.Windows.Automation.TextPattern.RangeFromChild%2A> to obtain a text range for each element; this is done recursively until all textual content has been retrieved.  
   
  ![Text ranges spanned by embedded objects.](~/add/media/uia-textpattern-embeddedobjecttextranges.png "Text ranges spanned by embedded objects.")  
 Example of a text stream with embedded objects and their range spans  
@@ -759,7 +759,7 @@ Example of a text stream with embedded objects and their range spans
  ![Range adjustments by Move & ExpandToEnclosingUnit](~/add/media/uia-textpattern-moveandexpand-examples.png "Range adjustments by Move & ExpandToEnclosingUnit")  
 Examples of how a text range is adjusted for Move() and ExpandToEnclosingUnit()  
   
- The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree; object boundaries are ignored. If a UI Automation client is retrieving the text for the purpose of reciting, interpreting, or analyzing in some manner, the text range should be checked for special cases, such as a table with textual content or other embedded objects. This can be accomplished by calling <xref:System.Windows.Automation.Text.TextPatternRange.GetChildren%2A> to obtain an <xref:System.Windows.Automation.AutomationElement> for each embedded object and then calling <xref:System.Windows.Automation.TextPattern.RangeFromChild%2A> to obtain a text range for each element; this is done recursively until all textual content has been retrieved.  
+ The textual content (or inner text) of a text container and an embedded object, such as a hyperlink or table cell, is exposed as a single, continuous text stream in both the control view and the content view of the UI Automation tree; object boundaries are ignored. If a UI Automation client is retrieving the text for the purpose of reciting, interpreting, or analyzing in some manner, the text range should be checked for special cases, such as a table with textual content or other embedded objects. This can be accomplished by calling <xref:System.Windows.Automation.Text.TextPatternRange.GetChildren%2A> to obtain an <xref:System.Windows.Automation.AutomationElement> for each embedded object and then calling <xref:System.Windows.Automation.TextPattern.RangeFromChild%2A> to obtain a text range for each element; this is done recursively until all textual content has been retrieved.  
   
  ![Text ranges spanned by embedded objects.](~/add/media/uia-textpattern-embeddedobjecttextranges.png "Text ranges spanned by embedded objects.")  
 Example of a text stream with embedded objects and their range spans  
diff --git a/xml/System.Windows.Automation/AndCondition.xml b/xml/System.Windows.Automation/AndCondition.xml
index b6c72d51e3c..bf2bc2b76b0 100644
--- a/xml/System.Windows.Automation/AndCondition.xml
+++ b/xml/System.Windows.Automation/AndCondition.xml
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to use <xref:System.Windows.Automation.AndCondition> to find [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that match a complex condition.  
+ The following example shows how to use <xref:System.Windows.Automation.AndCondition> to find UI Automation elements that match a complex condition.  
   
  [!code-csharp[UIAClient_snip#176](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAClient_snip/CSharp/ConditionSnips.cs#176)]
  [!code-vb[UIAClient_snip#176](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAClient_snip/VisualBasic/ConditionSnips.vb#176)]  
diff --git a/xml/System.Windows.Automation/AsyncContentLoadedState.xml b/xml/System.Windows.Automation/AsyncContentLoadedState.xml
index 6f4d859b9e5..a1d0bfd085e 100644
--- a/xml/System.Windows.Automation/AsyncContentLoadedState.xml
+++ b/xml/System.Windows.Automation/AsyncContentLoadedState.xml
@@ -49,7 +49,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Specifies that asynchronous loading of the content into the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is beginning.</summary>
+        <summary>Specifies that asynchronous loading of the content into the UI Automation element is beginning.</summary>
       </Docs>
     </Member>
     <Member MemberName="Completed">
@@ -71,7 +71,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>Specifies that asynchronous loading of the content into the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is complete.</summary>
+        <summary>Specifies that asynchronous loading of the content into the UI Automation element is complete.</summary>
       </Docs>
     </Member>
     <Member MemberName="Progress">
@@ -93,7 +93,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>Specifies that asynchronous loading of the content into the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is in progress. UI Automation providers should specify the percent complete so that client applications will know how much more content remains.</summary>
+        <summary>Specifies that asynchronous loading of the content into the UI Automation element is in progress. UI Automation providers should specify the percent complete so that client applications will know how much more content remains.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Automation/Automation.xml b/xml/System.Windows.Automation/Automation.xml
index 0d94458cff5..3c39a9557f0 100644
--- a/xml/System.Windows.Automation/Automation.xml
+++ b/xml/System.Windows.Automation/Automation.xml
@@ -45,10 +45,10 @@
       </Parameters>
       <Docs>
         <param name="eventId">The identifier for the event the method will handle.</param>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to associate with the event handler.</param>
+        <param name="element">The UI Automation element to associate with the event handler.</param>
         <param name="scope">The scope of events to be handled; that is, whether they are on the element itself, or on its ancestors and descendants.</param>
         <param name="eventHandler">The method to call when the specified event occurs.</param>
-        <summary>Registers a method that handles [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] events.</summary>
+        <summary>Registers a method that handles UI Automation events.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -147,16 +147,16 @@
         </Parameter>
       </Parameters>
       <Docs>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element with which to associate the event handler.</param>
+        <param name="element">The UI Automation element with which to associate the event handler.</param>
         <param name="scope">The scope of events to be handled; that is, whether they are on the element itself, or on its ancestors and children.</param>
         <param name="eventHandler">The method to call when the event occurs.</param>
-        <param name="properties">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] properties of interest.</param>
+        <param name="properties">The UI Automation properties of interest.</param>
         <summary>Registers a method that will handle property-changed events.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item specified by the supplied [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element might not support the properties specified by the `properties` parameter.  
+ The [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item specified by the supplied UI Automation element might not support the properties specified by the `properties` parameter.  
   
  `eventHandler` can be an instance of the method, or a reference to the method (`AddressOf` in Visual Basic).  
   
@@ -201,7 +201,7 @@
         <Parameter Name="eventHandler" Type="System.Windows.Automation.StructureChangedEventHandler" />
       </Parameters>
       <Docs>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element with which to associate the event handler.</param>
+        <param name="element">The UI Automation element with which to associate the event handler.</param>
         <param name="scope">The scope of events to be handled; that is, whether they are on the element itself, or on its ancestors and descendants.</param>
         <param name="eventHandler">The method to call when the structure-changed event occurs.</param>
         <summary>Registers the method that will handle structure-changed events.</summary>
@@ -310,9 +310,9 @@
         <Parameter Name="el2" Type="System.Windows.Automation.AutomationElement" />
       </Parameters>
       <Docs>
-        <param name="el1">The first [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to compare.</param>
-        <param name="el2">The second [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to compare.</param>
-        <summary>Compares two [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements, returning <see langword="true" /> if both refer to the same UI element.</summary>
+        <param name="el1">The first UI Automation element to compare.</param>
+        <param name="el2">The second UI Automation element to compare.</param>
+        <summary>Compares two UI Automation elements, returning <see langword="true" /> if both refer to the same UI element.</summary>
         <returns>
           <see langword="true" /> if the run time identifiers of the UI elements are the same; otherwise <see langword="false" />.</returns>
         <remarks>
@@ -346,7 +346,7 @@
         <ReturnType>System.Windows.Automation.Condition</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Represents a predefined view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree that includes only [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that can contain content.</summary>
+        <summary>Represents a predefined view of the UI Automation tree that includes only UI Automation elements that can contain content.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -381,7 +381,7 @@
         <ReturnType>System.Windows.Automation.Condition</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Represents a predefined view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree that includes only [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are controls.</summary>
+        <summary>Represents a predefined view of the UI Automation tree that includes only UI Automation elements that are controls.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -459,9 +459,9 @@
         <Parameter Name="property" Type="System.Windows.Automation.AutomationProperty" />
       </Parameters>
       <Docs>
-        <param name="property">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property identifier of the named property.</param>
-        <summary>Retrieves the name of the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property.</summary>
-        <returns>The friendly name of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property, or a null reference (<see langword="Nothing" /> in Visual Basic) if the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property is not found.</returns>
+        <param name="property">The UI Automation property identifier of the named property.</param>
+        <summary>Retrieves the name of the specified UI Automation property.</summary>
+        <returns>The friendly name of the UI Automation property, or a null reference (<see langword="Nothing" /> in Visual Basic) if the specified UI Automation property is not found.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -493,7 +493,7 @@
         <ReturnType>System.Windows.Automation.Condition</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Represents a predefined view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree that includes all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements.</summary>
+        <summary>Represents a predefined view of the UI Automation tree that includes all UI Automation elements.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -526,7 +526,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Removes all registered [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] event handlers.</summary>
+        <summary>Removes all registered UI Automation event handlers.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Automation.Automation.RemoveAutomationEventHandler(System.Windows.Automation.AutomationEvent,System.Windows.Automation.AutomationElement,System.Windows.Automation.AutomationEventHandler)" />
         <altmember cref="M:System.Windows.Automation.Automation.RemoveAutomationFocusChangedEventHandler(System.Windows.Automation.AutomationFocusChangedEventHandler)" />
@@ -560,9 +560,9 @@
       </Parameters>
       <Docs>
         <param name="eventId">An event identifier.</param>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element on which to remove the event handler.</param>
-        <param name="eventHandler">The handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddAutomationEventHandler(System.Windows.Automation.AutomationEvent,System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.AutomationEventHandler)" /> for the specified event identifier and [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</param>
-        <summary>Removes the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] event handler.</summary>
+        <param name="element">The UI Automation element on which to remove the event handler.</param>
+        <param name="eventHandler">The handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddAutomationEventHandler(System.Windows.Automation.AutomationEvent,System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.AutomationEventHandler)" /> for the specified event identifier and UI Automation element.</param>
+        <summary>Removes the specified UI Automation event handler.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -640,8 +640,8 @@
         <Parameter Name="eventHandler" Type="System.Windows.Automation.AutomationPropertyChangedEventHandler" />
       </Parameters>
       <Docs>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element from which to remove the event handler.</param>
-        <param name="eventHandler">A handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler(System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.AutomationPropertyChangedEventHandler,System.Windows.Automation.AutomationProperty[])" /> for the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</param>
+        <param name="element">The UI Automation element from which to remove the event handler.</param>
+        <param name="eventHandler">A handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler(System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.AutomationPropertyChangedEventHandler,System.Windows.Automation.AutomationProperty[])" /> for the specified UI Automation element.</param>
         <summary>Removes the specified property-changed event handler.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -681,8 +681,8 @@
         <Parameter Name="eventHandler" Type="System.Windows.Automation.StructureChangedEventHandler" />
       </Parameters>
       <Docs>
-        <param name="element">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element from which to remove the event handler.</param>
-        <param name="eventHandler">A handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddStructureChangedEventHandler(System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.StructureChangedEventHandler)" /> for the specified [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</param>
+        <param name="element">The UI Automation element from which to remove the event handler.</param>
+        <param name="eventHandler">A handler method that was passed to <see cref="M:System.Windows.Automation.Automation.AddStructureChangedEventHandler(System.Windows.Automation.AutomationElement,System.Windows.Automation.TreeScope,System.Windows.Automation.StructureChangedEventHandler)" /> for the specified UI Automation element.</param>
         <summary>Removes the specified structure-changed event handler.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Automation.Automation.RemoveAllEventHandlers" />
diff --git a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
index 733da1f249f..2a3bb56c877 100644
--- a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
+++ b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
@@ -64,7 +64,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Accelerator key combinations invoke an action. For example, CTRL + O is often used to invoke the **File Open** dialog box. [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that have the accelerator key property set always implement the <xref:System.Windows.Automation.InvokePattern> class.  
+ Accelerator key combinations invoke an action. For example, CTRL + O is often used to invoke the **File Open** dialog box. UI Automation elements that have the accelerator key property set always implement the <xref:System.Windows.Automation.InvokePattern> class.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
@@ -96,7 +96,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An access key is a character in the text of a menu, menu item, or label of a control such as a button that activates the attached menu function. For example, the letter "O" is often used to invoke the **Open** file common dialog box from a **File** menu.  [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that have the access key property set always implement the <xref:System.Windows.Automation.InvokePattern> class.  
+ An access key is a character in the text of a menu, menu item, or label of a control such as a button that activates the attached menu function. For example, the letter "O" is often used to invoke the **Open** file common dialog box from a **File** menu.  UI Automation elements that have the access key property set always implement the <xref:System.Windows.Automation.InvokePattern> class.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.AccessKeyProperty>.  
   
@@ -122,7 +122,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a string containing the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] for the element.</summary>
+        <summary>Gets a string containing the UI Automation [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] for the element.</summary>
         <value>An ID for an element that is unique among siblings within its container.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -225,7 +225,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Control type describes a known interaction model for arbitrary [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements without relying on a localized control type or combination of complex logic rules.  
+ Control type describes a known interaction model for arbitrary UI Automation elements without relying on a localized control type or combination of complex logic rules.  
   
  The only case where this property can change at run time is for a control that supports <xref:System.Windows.Automation.MultipleViewPattern>. An example is the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] ListView control, which can change from <xref:System.Windows.Automation.ControlType.DataGrid> to <xref:System.Windows.Automation.ControlType.List>, depending on the current view.  
   
@@ -418,7 +418,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is enabled.</summary>
+        <summary>Gets a value that indicates whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the UI Automation element is enabled.</summary>
         <value>
           <see langword="true" /> if the control is enabled; otherwise <see langword="false" />.</value>
         <remarks>
@@ -451,7 +451,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element can accept keyboard focus.</summary>
+        <summary>Gets a value that indicates whether the UI Automation element can accept keyboard focus.</summary>
         <value>
           <see langword="true" /> if the control can receive keyboard focus; otherwise <see langword="false" />.</value>
         <remarks>
@@ -482,7 +482,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is visible on the screen.</summary>
+        <summary>Gets a value that indicates whether the UI Automation element is visible on the screen.</summary>
         <value>
           <see langword="true" /> if the control is not visible; otherwise <see langword="false" />.</value>
         <remarks>
@@ -525,7 +525,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element contains protected content.</summary>
+        <summary>Gets a value that indicates whether the UI Automation element contains protected content.</summary>
         <value>
           <see langword="true" /> if the element contains protected content; otherwise <see langword="false" />.</value>
         <remarks>
@@ -558,7 +558,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is required to be filled out on a form.</summary>
+        <summary>Gets a value that indicates whether the UI Automation element is required to be filled out on a form.</summary>
         <value>
           <see langword="true" /> if the element is required to be filled out; otherwise <see langword="false" />.</value>
         <remarks>
@@ -721,7 +721,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name of an element can be used to find the element in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree when the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A> property is not supported on the element.  
+ The name of an element can be used to find the element in the UI Automation element tree when the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A> property is not supported on the element.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.NameProperty>.  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 95517491e4c..ed09eefd434 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -345,15 +345,15 @@
         <ReturnType>System.Windows.Automation.AutomationElement+AutomationElementInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.AutomationElement" /> object.</summary>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.AutomationElement" /> object.</summary>
         <value>A structure containing the cached property values for the <see cref="T:System.Windows.Automation.AutomationElement" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The accessors for [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] properties are represented as properties of the structure returned by <xref:System.Windows.Automation.AutomationElement.Cached%2A>. You do not need to retrieve the structure; you can access its members directly, as in the example below. For specific information on the properties available and their use, see <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation>.  
+ The accessors for UI Automation properties are represented as properties of the structure returned by <xref:System.Windows.Automation.AutomationElement.Cached%2A>. You do not need to retrieve the structure; you can access its members directly, as in the example below. For specific information on the properties available and their use, see <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation>.  
   
- To get the current value of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] properties on this element use the <xref:System.Windows.Automation.AutomationElement.Current%2A> property.  
+ To get the current value of UI Automation properties on this element use the <xref:System.Windows.Automation.AutomationElement.Current%2A> property.  
   
    
   
@@ -479,7 +479,7 @@
   
  This property can also be retrieved from the <xref:System.Windows.Automation.AutomationElement.Current%2A> or <xref:System.Windows.Automation.AutomationElement.Cached%2A> properties.  
   
- The class name depends on the implementation of the UI Automation provider and therefore cannot be counted upon to be in a standard format. However, if you know the class name you can use it to verify that your application is working with the expected [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.  
+ The class name depends on the implementation of the UI Automation provider and therefore cannot be counted upon to be in a standard format. However, if you know the class name you can use it to verify that your application is working with the expected UI Automation element.  
   
  Return values of the property are of type <xref:System.String>. The default value is an empty string.  
   
@@ -669,9 +669,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The accessors for [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] properties are represented as properties of the structure returned by <xref:System.Windows.Automation.AutomationElement.Current%2A>. You do not need to retrieve the structure; you can access its members directly, as in the example below. For specific information on the properties available and their use, see <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation>.  
+ The accessors for UI Automation properties are represented as properties of the structure returned by <xref:System.Windows.Automation.AutomationElement.Current%2A>. You do not need to retrieve the structure; you can access its members directly, as in the example below. For specific information on the properties available and their use, see <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation>.  
   
- To get the cached value of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] properties on this element, use the <xref:System.Windows.Automation.AutomationElement.Cached%2A> property.  
+ To get the cached value of UI Automation properties on this element, use the <xref:System.Windows.Automation.AutomationElement.Cached%2A> property.  
   
    
   
@@ -783,7 +783,7 @@
   
  When searching for top-level windows on the desktop, be sure to specify <xref:System.Windows.Automation.TreeScope.Children> in `scope`, not <xref:System.Windows.Automation.TreeScope.Descendants>. A search through the entire subtree of the desktop could iterate through thousands of items and lead to a stack overflow.  
   
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
@@ -834,7 +834,7 @@
   
  When searching for a top-level window on the desktop, be sure to specify <xref:System.Windows.Automation.TreeScope.Children> in `scope`, not <xref:System.Windows.Automation.TreeScope.Descendants>. A search through the entire subtree of the desktop could iterate through thousands of items and lead to a stack overflow.  
   
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
@@ -875,7 +875,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
  ]]></format>
         </remarks>
@@ -981,7 +981,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method might be used by a client helper library to enable its callers to access its own native element type. For example, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses this method internally so that it can return an <xref:System.Windows.Automation.AutomationElement> to clients that want to get a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element directly from a <xref:System.Windows.UIElement>.  
+ This method might be used by a client helper library to enable its callers to access its own native element type. For example, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses this method internally so that it can return an <xref:System.Windows.Automation.AutomationElement> to clients that want to get a UI Automation element directly from a <xref:System.Windows.UIElement>.  
   
  ]]></format>
         </remarks>
@@ -1018,7 +1018,7 @@
 ## Remarks  
  <xref:System.Windows.Automation.AutomationElement.FromPoint%2A> returns the element in the logical tree that is closest to the root element.  
   
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
  Although the point is within the bounding rectangle of the returned <xref:System.Windows.Automation.AutomationElement>, it is not necessarily on a clickable part of the control. For example, a round button might not be clickable near one of the corners of its bounding rectangle.  
   
@@ -1139,7 +1139,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, a default property specified by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
+ If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, a default property specified by UI Automation is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
  <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A> retrieves the specified property from the <xref:System.Windows.Automation.AutomationElement>'s cache. To retrieve the current object for the specified property call <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A>.  
   
@@ -1193,7 +1193,7 @@
   
  Passing `false` in `ignoreDefaultValue` is equivalent to calling <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%28System.Windows.Automation.AutomationProperty%29?displayProperty=nameWithType>.  
   
- If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, if `ignoreDefaultValue` is `false`, a default property specified by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
+ If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, if `ignoreDefaultValue` is `false`, a default property specified by UI Automation is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
  This method throws an exception if the requested property was not previously cached.  
   
@@ -1240,7 +1240,7 @@
   
  An <xref:System.Windows.Automation.AutomationElement> is clickable when it satisfies all the following conditions:  
   
--   It is programmatically visible and available with the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree.  
+-   It is programmatically visible and available with the UI Automation tree.  
   
 -   It is scrolled fully into view within its parent container, if any. If the element is clipped, there is no guarantee that it is clickable.  
   
@@ -1367,7 +1367,7 @@
         <Parameter Name="property" Type="System.Windows.Automation.AutomationProperty" />
       </Parameters>
       <Docs>
-        <param name="property">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property identifier specifying which property to retrieve.</param>
+        <param name="property">The UI Automation property identifier specifying which property to retrieve.</param>
         <summary>Retrieves the value of the specified property on this <see cref="T:System.Windows.Automation.AutomationElement" />. An appropriate default value for the property type is returned for properties not explicitly supported by the target [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</summary>
         <returns>An object containing the value of the specified property.</returns>
         <remarks>
@@ -1376,7 +1376,7 @@
 ## Remarks  
  The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the UI.  
   
- If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, a default property specified by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
+ If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, a default property specified by UI Automation is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
  For some forms of UI, this method will incur cross-process performance overhead. Concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
@@ -1415,7 +1415,7 @@
         <Parameter Name="ignoreDefaultValue" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="property">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property identifier specifying which property to retrieve.</param>
+        <param name="property">The UI Automation property identifier specifying which property to retrieve.</param>
         <param name="ignoreDefaultValue">A value that specifies whether a default value should be ignored if the specified property is supported.</param>
         <summary>Retrieves the value of the specified property on this <see cref="T:System.Windows.Automation.AutomationElement" />, optionally ignoring any default property.</summary>
         <returns>An object containing the value of the specified property, or <see cref="F:System.Windows.Automation.AutomationElement.NotSupported" /> if the element does not supply a value and <paramref name="ignoreDefaultValue" /> is <see langword="true" />.</returns>
@@ -1425,7 +1425,7 @@
 ## Remarks  
  Passing `false` in `ignoreDefaultValue` is equivalent to calling <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%28System.Windows.Automation.AutomationProperty%29?displayProperty=nameWithType>.  
   
- If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, if `ignoreDefaultValue` is `false`, a default property specified by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
+ If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, if `ignoreDefaultValue` is `false`, a default property specified by UI Automation is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
  The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
   
@@ -1751,7 +1751,7 @@
   
  This property can also be retrieved from the <xref:System.Windows.Automation.AutomationElement.Current%2A> or <xref:System.Windows.Automation.AutomationElement.Cached%2A> properties.  
   
- The content view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree provides a view of the UI that only contains elements that represent data within the UI.  
+ The content view of the UI Automation tree provides a view of the UI that only contains elements that represent data within the UI.  
   
  An element must be a control to be able to hold content.  
   
@@ -3600,7 +3600,7 @@
         <ReturnType>System.Windows.Automation.AutomationEvent</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the event that is raised when the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree structure is changed.</summary>
+        <summary>Identifies the event that is raised when the UI Automation tree structure is changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElementIdentifiers.xml b/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
index bfbf76f7f50..8e5bae35b88 100644
--- a/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
+++ b/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
@@ -550,7 +550,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.DockPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.DockPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -610,7 +610,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ExpandCollapsePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ExpandCollapsePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -640,7 +640,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.GridItemPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.GridItemPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -670,7 +670,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.GridPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.GridPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -704,7 +704,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.InvokePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.InvokePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -733,7 +733,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ItemContainerPattern" /> is available for this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ItemContainerPattern" /> is available for this UI Automation element.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -785,7 +785,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.MultipleViewPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.MultipleViewPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -815,7 +815,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsOffscreen" /> property, which indicates whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is visible.</summary>
+        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsOffscreen" /> property, which indicates whether the UI Automation element is visible.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -877,7 +877,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.RangeValuePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.RangeValuePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -937,7 +937,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ScrollItemPattern" /> is available for this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ScrollItemPattern" /> is available for this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -967,7 +967,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ScrollPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ScrollPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -997,7 +997,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SelectionItemPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SelectionItemPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1027,7 +1027,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SelectionPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SelectionPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1056,7 +1056,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SynchronizedInputPattern" /> is available for this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.SynchronizedInputPattern" /> is available for this UI Automation element.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1078,7 +1078,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether the <see cref="T:System.Windows.Automation.TableItemPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether the <see cref="T:System.Windows.Automation.TableItemPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1108,7 +1108,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TablePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TablePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1138,7 +1138,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TextPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TextPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1168,7 +1168,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TogglePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TogglePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1198,7 +1198,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TransformPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.TransformPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1228,7 +1228,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ValuePattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.ValuePattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1257,7 +1257,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.VirtualizedItemPattern" /> is available for this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.VirtualizedItemPattern" /> is available for this UI Automation element.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1279,7 +1279,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.WindowPattern" /> is available on this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Identifies the property that indicates whether <see cref="T:System.Windows.Automation.WindowPattern" /> is available on this UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1811,7 +1811,7 @@ The `PositionInSetProperty` works in coordination with <xref:System.Windows.Auto
         <ReturnType>System.Windows.Automation.AutomationEvent</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the event that is raised when the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree structure is changed.</summary>
+        <summary>Identifies the event that is raised when the UI Automation tree structure is changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationEventHandler.xml b/xml/System.Windows.Automation/AutomationEventHandler.xml
index 4ae95aab921..8983b9f9d5e 100644
--- a/xml/System.Windows.Automation/AutomationEventHandler.xml
+++ b/xml/System.Windows.Automation/AutomationEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use an <xref:System.Windows.Automation.AutomationEventHandler> delegate to specify the method that is called by a client to handle [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] events.  
+ Use an <xref:System.Windows.Automation.AutomationEventHandler> delegate to specify the method that is called by a client to handle UI Automation events.  
   
  The <xref:System.Windows.Automation.AutomationElement> represented by `sender` might not have any cached properties or patterns, depending on whether the application subscribed to this event while a <xref:System.Windows.Automation.CacheRequest> was active.  
   
diff --git a/xml/System.Windows.Automation/AutomationFocusChangedEventHandler.xml b/xml/System.Windows.Automation/AutomationFocusChangedEventHandler.xml
index 5446bdbc596..e52415a9a08 100644
--- a/xml/System.Windows.Automation/AutomationFocusChangedEventHandler.xml
+++ b/xml/System.Windows.Automation/AutomationFocusChangedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use an <xref:System.Windows.Automation.AutomationFocusChangedEventHandler> delegate to define the method that is called by a client to handle [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] focus-changed events.  
+ Use an <xref:System.Windows.Automation.AutomationFocusChangedEventHandler> delegate to define the method that is called by a client to handle UI Automation focus-changed events.  
   
  The <xref:System.Windows.Automation.AutomationElement> represented by `sender` might not have any cached properties or patterns, depending on whether the application subscribed to this event while a <xref:System.Windows.Automation.CacheRequest> was active.  
   
diff --git a/xml/System.Windows.Automation/AutomationIdentifier.xml b/xml/System.Windows.Automation/AutomationIdentifier.xml
index e986e283c77..5e726df57f0 100644
--- a/xml/System.Windows.Automation/AutomationIdentifier.xml
+++ b/xml/System.Windows.Automation/AutomationIdentifier.xml
@@ -110,7 +110,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the hash code for this [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] identifier.</summary>
+        <summary>Returns the hash code for this UI Automation identifier.</summary>
         <returns>A 32-bit signed integer hash code.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation/AutomationProperties.xml b/xml/System.Windows.Automation/AutomationProperties.xml
index 6592747cecd..0fe7bc63d00 100644
--- a/xml/System.Windows.Automation/AutomationProperties.xml
+++ b/xml/System.Windows.Automation/AutomationProperties.xml
@@ -265,7 +265,7 @@
       <Docs>
         <param name="element">The <see cref="T:System.Windows.DependencyObject" /> to check.</param>
         <summary>Gets the <see cref="P:System.Windows.Automation.AutomationProperties.AutomationId" /> attached property for the specified <see cref="T:System.Windows.DependencyObject" />.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] identifier for the specified element.</returns>
+        <returns>The UI Automation identifier for the specified element.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1301,7 +1301,7 @@ The `PositionInSet` attached property works in coordination with the <xref:Syste
       </Parameters>
       <Docs>
         <param name="element">The <see cref="T:System.Windows.DependencyObject" /> on which to set the property.</param>
-        <param name="value">The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] identifier value to set.</param>
+        <param name="value">The UI Automation identifier value to set.</param>
         <summary>Sets the <see cref="P:System.Windows.Automation.AutomationProperties.AutomationId" /> attached property for the specified <see cref="T:System.Windows.DependencyObject" />.</summary>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/ui-automation/ui-automation-properties-overview">UI Automation Properties Overview</related>
diff --git a/xml/System.Windows.Automation/AutomationTextAttribute.xml b/xml/System.Windows.Automation/AutomationTextAttribute.xml
index 5bf3e224923..efb81792b06 100644
--- a/xml/System.Windows.Automation/AutomationTextAttribute.xml
+++ b/xml/System.Windows.Automation/AutomationTextAttribute.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Derived from <xref:System.Windows.Automation.AutomationIdentifier>.  
   
- The list of text attributes supported by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] can be found at <xref:System.Windows.Automation.TextPattern>.  
+ The list of text attributes supported by UI Automation can be found at <xref:System.Windows.Automation.TextPattern>.  
   
  The <xref:System.Windows.Automation.AutomationTextAttribute> class is effectively abstract, as it has no constructor and cannot be instantiated by applications.  
   
diff --git a/xml/System.Windows.Automation/CacheRequest.xml b/xml/System.Windows.Automation/CacheRequest.xml
index 4d00cd778cf..021478fb437 100644
--- a/xml/System.Windows.Automation/CacheRequest.xml
+++ b/xml/System.Windows.Automation/CacheRequest.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Retrieving properties and patterns through [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] requires cross-process calls that can slow down performance. By caching values of proprieties and patterns in a batch operation, you can enhance the performance of your application.  
+ Retrieving properties and patterns through UI Automation requires cross-process calls that can slow down performance. By caching values of proprieties and patterns in a batch operation, you can enhance the performance of your application.  
   
  Create a new cache request by calling the class constructor. The request is populated by repeated calls to the <xref:System.Windows.Automation.CacheRequest.Add%2A> method.  
   
@@ -31,7 +31,7 @@
   
 -   Put the request onto the internal stack by calling <xref:System.Windows.Automation.CacheRequest.Push%2A>. Only the topmost request on the stack is active, and it must be the next one removed from the stack by <xref:System.Windows.Automation.CacheRequest.Pop%2A>. Popping the request deactivates it.  
   
- [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements obtained while the request is active will have cached values for the properties and patterns specified.  
+ UI Automation elements obtained while the request is active will have cached values for the properties and patterns specified.  
   
    
   
@@ -442,13 +442,13 @@
         <ReturnType>System.Windows.Automation.Condition</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value specifying the view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree to use when caching.</summary>
-        <value>The view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree. The default view is <see cref="F:System.Windows.Automation.Automation.ControlViewCondition" />.</value>
+        <summary>Gets or sets a value specifying the view of the UI Automation element tree to use when caching.</summary>
+        <value>The view of the UI Automation element tree. The default view is <see cref="F:System.Windows.Automation.Automation.ControlViewCondition" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For additional information on views of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree, see [UI Automation Tree Overview](/dotnet/framework/ui-automation/ui-automation-tree-overview).  
+ For additional information on views of the UI Automation element tree, see [UI Automation Tree Overview](/dotnet/framework/ui-automation/ui-automation-tree-overview).  
   
    
   
diff --git a/xml/System.Windows.Automation/ClientSideProviderDescription.xml b/xml/System.Windows.Automation/ClientSideProviderDescription.xml
index ac5ae1e09d5..0e38ed73dc2 100644
--- a/xml/System.Windows.Automation/ClientSideProviderDescription.xml
+++ b/xml/System.Windows.Automation/ClientSideProviderDescription.xml
@@ -104,7 +104,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] encounters a window of class `className` within the process specified by `imageName`, it calls `clientSideProviderFactoryCallback` to create an instance of the client-side provider.  
+ When UI Automation encounters a window of class `className` within the process specified by `imageName`, it calls `clientSideProviderFactoryCallback` to create an instance of the client-side provider.  
   
  If `className` is `null`, the provider is used for all windows for which no other provider is found.  
   
diff --git a/xml/System.Windows.Automation/Condition.xml b/xml/System.Windows.Automation/Condition.xml
index 58a249a3a07..8eb881921de 100644
--- a/xml/System.Windows.Automation/Condition.xml
+++ b/xml/System.Windows.Automation/Condition.xml
@@ -48,7 +48,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This condition exists only for symmetry with <xref:System.Windows.Automation.Condition.TrueCondition>. It will never enable a match with [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements, and it cannot usefully be combined with any other condition.  
+ This condition exists only for symmetry with <xref:System.Windows.Automation.Condition.TrueCondition>. It will never enable a match with UI Automation elements, and it cannot usefully be combined with any other condition.  
   
  ]]></format>
         </remarks>
@@ -77,7 +77,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- In the following example, <xref:System.Windows.Automation.Condition.TrueCondition> is used to retrieve all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements within the specified scope.  
+ In the following example, <xref:System.Windows.Automation.Condition.TrueCondition> is used to retrieve all UI Automation elements within the specified scope.  
   
  [!code-csharp[UIAClient_snip#178](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAClient_snip/CSharp/ConditionSnips.cs#178)]
  [!code-vb[UIAClient_snip#178](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAClient_snip/VisualBasic/ConditionSnips.vb#178)]  
diff --git a/xml/System.Windows.Automation/ControlType.xml b/xml/System.Windows.Automation/ControlType.xml
index 31d51eed738..51c2a7fa23d 100644
--- a/xml/System.Windows.Automation/ControlType.xml
+++ b/xml/System.Windows.Automation/ControlType.xml
@@ -61,7 +61,7 @@
 ## Remarks  
  Buttons perform a single action when clicked.  
   
- A button can be used as a standalone control or as a subcontrol in another control type. For example, the drop-down arrow in a combo box control is a button. When used as a subcontrol, a button is in the control view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree (not in the content view).  
+ A button can be used as a standalone control or as a subcontrol in another control type. For example, the drop-down arrow in a combo box control is a button. When used as a subcontrol, a button is in the control view of the UI Automation tree (not in the content view).  
   
  ]]></format>
         </remarks>
@@ -178,7 +178,7 @@
   
  Control developers should check the other control types before designating their control as a <xref:System.Windows.Automation.ControlType.Custom> control type to be sure that their control does not provide the same functionality as one of the defined control types.  
   
- A <xref:System.Windows.Automation.ControlType.Custom> control type requires extra work for the provider to implement [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)]. Also, UI Automation client products will not be able to anticipate the control structure, keyboard interaction, and possible control patterns based on the control type of the control.  
+ A <xref:System.Windows.Automation.ControlType.Custom> control type requires extra work for the provider to implement UI Automation. Also, UI Automation client products will not be able to anticipate the control structure, keyboard interaction, and possible control patterns based on the control type of the control.  
   
  ]]></format>
         </remarks>
@@ -326,7 +326,7 @@
       <Parameters />
       <Docs>
         <summary>Retrieves the pattern identifiers that are not supported by the control type.</summary>
-        <returns>An array of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] pattern identifiers.</returns>
+        <returns>An array of UI Automation pattern identifiers.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -548,7 +548,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.ControlType.Image> control type can be used as a standalone control or as a subcontrol in another control type.  For example, a button can use an image rather than text to indicate its functionality to the user.  
   
- When used only for decorative purposes, an image appears in the control view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree (not in the content view).  
+ When used only for decorative purposes, an image appears in the control view of the UI Automation tree (not in the content view).  
   
  ]]></format>
         </remarks>
@@ -580,7 +580,7 @@
 ## Remarks  
  A <xref:System.Windows.Automation.ControlType.List> is a control type that contains <xref:System.Windows.Automation.ControlType.ListItem> and (perhaps) <xref:System.Windows.Automation.ControlType.Group> control types.  
   
- A <xref:System.Windows.Automation.ControlType.List> control can be used as a standalone control or as a subcontrol in another control type. For example, a combo box has a <xref:System.Windows.Automation.ControlType.List> control that contains choices that appear when the drop-down button is clicked. When used as a subcontrol, a <xref:System.Windows.Automation.ControlType.List> is only in the control view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree (not in content view).  
+ A <xref:System.Windows.Automation.ControlType.List> control can be used as a standalone control or as a subcontrol in another control type. For example, a combo box has a <xref:System.Windows.Automation.ControlType.List> control that contains choices that appear when the drop-down button is clicked. When used as a subcontrol, a <xref:System.Windows.Automation.ControlType.List> is only in the control view of the UI Automation tree (not in content view).  
   
  When used as a subcontrol, a <xref:System.Windows.Automation.ControlType.List> does not have a `Name` property assigned.  
   
@@ -1015,7 +1015,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Automation.ControlType.StatusBar> control types are generally subcontrols of <xref:System.Windows.Automation.ControlType.Window> control type [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements.  
+ <xref:System.Windows.Automation.ControlType.StatusBar> control types are generally subcontrols of <xref:System.Windows.Automation.ControlType.Window> control type UI Automation elements.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/DockPattern.xml b/xml/System.Windows.Automation/DockPattern.xml
index 01ab845390b..071411a849d 100644
--- a/xml/System.Windows.Automation/DockPattern.xml
+++ b/xml/System.Windows.Automation/DockPattern.xml
@@ -54,8 +54,8 @@
         <ReturnType>System.Windows.Automation.DockPattern+DockPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.DockPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.DockPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -87,8 +87,8 @@
         <ReturnType>System.Windows.Automation.DockPattern+DockPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.DockPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.DockPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/ExpandCollapsePattern.xml b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
index 858a52b1577..46ed6639a64 100644
--- a/xml/System.Windows.Automation/ExpandCollapsePattern.xml
+++ b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
@@ -52,8 +52,8 @@
         <ReturnType>System.Windows.Automation.ExpandCollapsePattern+ExpandCollapsePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ExpandCollapsePattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.ExpandCollapsePattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -131,8 +131,8 @@
         <ReturnType>System.Windows.Automation.ExpandCollapsePattern+ExpandCollapsePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ExpandCollapsePattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.ExpandCollapsePattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -223,7 +223,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIAExpandCollapsePattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAExpandCollapsePattern_snip/CSharp/UIAExpandCollapsePattern_snippets.cs#100)]
  [!code-vb[UIAExpandCollapsePattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAExpandCollapsePattern_snip/VisualBasic/UIAExpandCollapsePattern_snippets.vb#100)]  
diff --git a/xml/System.Windows.Automation/GridItemPattern+GridItemPatternInformation.xml b/xml/System.Windows.Automation/GridItemPattern+GridItemPatternInformation.xml
index ec484f7122b..e048ea1c3df 100644
--- a/xml/System.Windows.Automation/GridItemPattern+GridItemPatternInformation.xml
+++ b/xml/System.Windows.Automation/GridItemPattern+GridItemPatternInformation.xml
@@ -122,8 +122,8 @@
         <ReturnType>System.Windows.Automation.AutomationElement</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element that supports <see cref="T:System.Windows.Automation.GridPattern" /> and represents the container of the cell or item.</summary>
-        <value>A [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element that supports the GridPattern and represents the table cell or item container. The default is a null reference (<see langword="Nothing" /> in Microsoft Visual Basic .NET).</value>
+        <summary>Gets a UI Automation element that supports <see cref="T:System.Windows.Automation.GridPattern" /> and represents the container of the cell or item.</summary>
+        <value>A UI Automation element that supports the GridPattern and represents the table cell or item container. The default is a null reference (<see langword="Nothing" /> in Microsoft Visual Basic .NET).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/GridPattern+GridPatternInformation.xml b/xml/System.Windows.Automation/GridPattern+GridPatternInformation.xml
index 985f5e6951e..ce7341273ef 100644
--- a/xml/System.Windows.Automation/GridPattern+GridPatternInformation.xml
+++ b/xml/System.Windows.Automation/GridPattern+GridPatternInformation.xml
@@ -48,7 +48,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Hidden rows and columns, depending on the provider implementation, may be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they are not counted.  
+ Hidden rows and columns, depending on the provider implementation, may be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they are not counted.  
   
  The default value is 0.  
   
@@ -92,7 +92,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Hidden rows and columns, depending on the provider implementation, may be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
+ Hidden rows and columns, depending on the provider implementation, may be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
   
  The default value is 0.  
   
diff --git a/xml/System.Windows.Automation/GridPattern.xml b/xml/System.Windows.Automation/GridPattern.xml
index 4a565656f43..9a265a95999 100644
--- a/xml/System.Windows.Automation/GridPattern.xml
+++ b/xml/System.Windows.Automation/GridPattern.xml
@@ -51,8 +51,8 @@
         <ReturnType>System.Windows.Automation.GridPattern+GridPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.GridPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.GridPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -121,8 +121,8 @@
         <ReturnType>System.Windows.Automation.GridPattern+GridPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.GridPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.GridPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -167,7 +167,7 @@
 ## Remarks  
  Grid coordinates are zero-based with the upper left (or upper right cell depending on locale) having coordinates (0,0).  
   
- If a cell is empty, a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is still returned in order to support retrieval of the <xref:System.Windows.Automation.GridItemPattern.GridItemPatternInformation.ContainingGrid%2A> property for that cell. This is possible when the layout of child elements in the grid is similar to a ragged array as shown here.  
+ If a cell is empty, a UI Automation element is still returned in order to support retrieval of the <xref:System.Windows.Automation.GridItemPattern.GridItemPatternInformation.ContainingGrid%2A> property for that cell. This is possible when the layout of child elements in the grid is similar to a ragged array as shown here.  
   
  ![Windows Explorer view showing ragged layout.](~/add/media/uia-gridpattern-ragged-array.PNG "Windows Explorer view showing ragged layout.")  
 Example of a Grid Control with Empty Coordinates  
diff --git a/xml/System.Windows.Automation/GridPatternIdentifiers.xml b/xml/System.Windows.Automation/GridPatternIdentifiers.xml
index 9d93a6f509c..b696f9317c3 100644
--- a/xml/System.Windows.Automation/GridPatternIdentifiers.xml
+++ b/xml/System.Windows.Automation/GridPatternIdentifiers.xml
@@ -56,7 +56,7 @@
 ## Remarks  
  This identifier is used by UI Automation providers. UI Automation client applications should use the equivalent field in <xref:System.Windows.Automation.GridPattern>.  
   
- Hidden rows and columns, depending on the provider implementation, may be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they are not be counted.  
+ Hidden rows and columns, depending on the provider implementation, may be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they are not be counted.  
   
  The default value is 0.  
   
@@ -120,7 +120,7 @@
 ## Remarks  
  This identifier is used by UI Automation providers. UI Automation client applications should use the equivalent field in <xref:System.Windows.Automation.GridPattern>.  
   
- Hidden rows and columns, depending on the provider implementation, may be loaded in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
+ Hidden rows and columns, depending on the provider implementation, may be loaded in the UI Automation tree and will therefore be reflected in the <xref:System.Windows.Automation.GridPattern.GridPatternInformation.RowCount%2A> and <xref:System.Windows.Automation.GridPattern.GridPatternInformation.ColumnCount%2A> properties. If the hidden rows and columns have not yet been loaded they will not be counted.  
   
  The default value is 0.  
   
diff --git a/xml/System.Windows.Automation/InvokePattern.xml b/xml/System.Windows.Automation/InvokePattern.xml
index f357e7e11d4..fcf71f21eb8 100644
--- a/xml/System.Windows.Automation/InvokePattern.xml
+++ b/xml/System.Windows.Automation/InvokePattern.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Controls support <xref:System.Windows.Automation.InvokePattern> if the same behavior is not exposed through another control pattern. For example, if the <xref:System.Windows.Automation.InvokePattern.Invoke%2A> method on a control performs the same action as the <xref:System.Windows.Automation.ExpandCollapsePattern.Expand%2A> or <xref:System.Windows.Automation.ExpandCollapsePattern.Collapse%2A> method, the control will not support <xref:System.Windows.Automation.InvokePattern>.  
   
- [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that represent controls such as check boxes and radio buttons, which maintain a state, instead support <xref:System.Windows.Automation.TogglePattern> or <xref:System.Windows.Automation.SelectionItemPattern>.  
+ UI Automation elements that represent controls such as check boxes and radio buttons, which maintain a state, instead support <xref:System.Windows.Automation.TogglePattern> or <xref:System.Windows.Automation.SelectionItemPattern>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Automation/MultipleViewPattern.xml b/xml/System.Windows.Automation/MultipleViewPattern.xml
index 84e5bc4c761..0380b3d4a5b 100644
--- a/xml/System.Windows.Automation/MultipleViewPattern.xml
+++ b/xml/System.Windows.Automation/MultipleViewPattern.xml
@@ -48,8 +48,8 @@
         <ReturnType>System.Windows.Automation.MultipleViewPattern+MultipleViewPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.MultipleViewPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.MultipleViewPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -81,8 +81,8 @@
         <ReturnType>System.Windows.Automation.MultipleViewPattern+MultipleViewPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.MultipleViewPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.MultipleViewPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/OrCondition.xml b/xml/System.Windows.Automation/OrCondition.xml
index e881c77af5e..74283a0616e 100644
--- a/xml/System.Windows.Automation/OrCondition.xml
+++ b/xml/System.Windows.Automation/OrCondition.xml
@@ -55,7 +55,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- In the following example, an <xref:System.Windows.Automation.OrCondition> is used to retrieve [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are either buttons or radio buttons.  
+ In the following example, an <xref:System.Windows.Automation.OrCondition> is used to retrieve UI Automation elements that are either buttons or radio buttons.  
   
  [!code-csharp[UIAClient_snip#175](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAClient_snip/CSharp/ConditionSnips.cs#175)]
  [!code-vb[UIAClient_snip#175](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAClient_snip/VisualBasic/ConditionSnips.vb#175)]  
diff --git a/xml/System.Windows.Automation/PropertyCondition.xml b/xml/System.Windows.Automation/PropertyCondition.xml
index b9fc99b2243..76f78ce9cea 100644
--- a/xml/System.Windows.Automation/PropertyCondition.xml
+++ b/xml/System.Windows.Automation/PropertyCondition.xml
@@ -62,7 +62,7 @@
    
   
 ## Examples  
- In the following example, a <xref:System.Windows.Automation.PropertyCondition> specifies that the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element to be found has a control type of <xref:System.Windows.Automation.ControlType.List>. The <xref:System.Windows.Automation.PropertyCondition> is then used to obtain the list element from a combo box.  
+ In the following example, a <xref:System.Windows.Automation.PropertyCondition> specifies that the UI Automation element to be found has a control type of <xref:System.Windows.Automation.ControlType.List>. The <xref:System.Windows.Automation.PropertyCondition> is then used to obtain the list element from a combo box.  
   
  [!code-csharp[UIAClient_snip#180](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAClient_snip/CSharp/ClientForm.cs#180)]
  [!code-vb[UIAClient_snip#180](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAClient_snip/VisualBasic/ClientForm.vb#180)]  
diff --git a/xml/System.Windows.Automation/RangeValuePattern+RangeValuePatternInformation.xml b/xml/System.Windows.Automation/RangeValuePattern+RangeValuePatternInformation.xml
index 6ed8e610230..0ef16773ff6 100644
--- a/xml/System.Windows.Automation/RangeValuePattern+RangeValuePatternInformation.xml
+++ b/xml/System.Windows.Automation/RangeValuePattern+RangeValuePatternInformation.xml
@@ -42,7 +42,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the value of a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is read-only.</summary>
+        <summary>Gets a value that specifies whether the value of a UI Automation element is read-only.</summary>
         <value>
           <see langword="true" /> if the value is read-only; <see langword="false" /> if it can be modified. The default is <see langword="true" />.</value>
         <remarks>
@@ -123,8 +123,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the maximum range value supported by the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
-        <value>The maximum value supported by the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Maximum" />. The default value is 0.0.</value>
+        <summary>Gets the maximum range value supported by the UI Automation element.</summary>
+        <value>The maximum value supported by the UI Automation element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Maximum" />. The default value is 0.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -161,8 +161,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the minimum range value supported by the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
-        <value>The minimum value supported by the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Minimum" />. The default value is 0.0.</value>
+        <summary>Gets the minimum range value supported by the UI Automation element.</summary>
+        <value>The minimum value supported by the UI Automation element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Minimum" />. The default value is 0.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -199,8 +199,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the small-change value, unique to the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element, which is added to or subtracted from the elements <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Value" /> property.</summary>
-        <value>The small-change value unique to the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.SmallChange" />. The default value is 0.0.</value>
+        <summary>Gets the small-change value, unique to the UI Automation element, which is added to or subtracted from the elements <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Value" /> property.</summary>
+        <value>The small-change value unique to the UI Automation element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.SmallChange" />. The default value is 0.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -237,8 +237,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current value of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
-        <value>The current value of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Value" />. The default value is 0.0.</value>
+        <summary>Gets the current value of the UI Automation element.</summary>
+        <value>The current value of the UI Automation element or <see langword="null" /> if the element does not support <see cref="P:System.Windows.Automation.RangeValuePattern.RangeValuePatternInformation.Value" />. The default value is 0.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/RangeValuePattern.xml b/xml/System.Windows.Automation/RangeValuePattern.xml
index 801e24ac004..d42af303227 100644
--- a/xml/System.Windows.Automation/RangeValuePattern.xml
+++ b/xml/System.Windows.Automation/RangeValuePattern.xml
@@ -314,7 +314,7 @@
       </Parameters>
       <Docs>
         <param name="value">The new value of the element.</param>
-        <summary>Sets the value associated with the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
+        <summary>Sets the value associated with the UI Automation element.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/ScrollPattern+ScrollPatternInformation.xml b/xml/System.Windows.Automation/ScrollPattern+ScrollPatternInformation.xml
index 172f47393e8..f1bc7b3dd6a 100644
--- a/xml/System.Windows.Automation/ScrollPattern+ScrollPatternInformation.xml
+++ b/xml/System.Windows.Automation/ScrollPattern+ScrollPatternInformation.xml
@@ -48,7 +48,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property can be dynamic. For example, the content area of the UI Automation element might not be larger than the current viewable area, meaning <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.HorizontallyScrollable%2A> is `false`. However, resizing the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or adding child items can increase the bounds of the content area beyond the viewable area, indicating that <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.HorizontallyScrollable%2A> is `true`.  
+ This property can be dynamic. For example, the content area of the UI Automation element might not be larger than the current viewable area, meaning <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.HorizontallyScrollable%2A> is `false`. However, resizing the UI Automation element or adding child items can increase the bounds of the content area beyond the viewable area, indicating that <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.HorizontallyScrollable%2A> is `true`.  
   
    
   
@@ -155,7 +155,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property can be dynamic. For example, the content area of the UI Automation element might not be larger than the current viewable area, meaning <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.VerticallyScrollable%2A> is `false`. However, resizing the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element or adding child items can increase the bounds of the content area beyond the viewable area, indicating that <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.VerticallyScrollable%2A> is `true`.  
+ This property can be dynamic. For example, the content area of the UI Automation element might not be larger than the current viewable area, meaning <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.VerticallyScrollable%2A> is `false`. However, resizing the UI Automation element or adding child items can increase the bounds of the content area beyond the viewable area, indicating that <xref:System.Windows.Automation.ScrollPattern.ScrollPatternInformation.VerticallyScrollable%2A> is `true`.  
   
    
   
diff --git a/xml/System.Windows.Automation/ScrollPattern.xml b/xml/System.Windows.Automation/ScrollPattern.xml
index 245a87fd9c9..298e91a11e6 100644
--- a/xml/System.Windows.Automation/ScrollPattern.xml
+++ b/xml/System.Windows.Automation/ScrollPattern.xml
@@ -48,8 +48,8 @@
         <ReturnType>System.Windows.Automation.ScrollPattern+ScrollPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ScrollPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.ScrollPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -81,8 +81,8 @@
         <ReturnType>System.Windows.Automation.ScrollPattern+ScrollPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ScrollPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.ScrollPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -123,7 +123,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIAScrollPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAScrollPattern_snip/CSharp/UIAScrollPattern_snippets.cs#100)]
  [!code-vb[UIAScrollPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAScrollPattern_snip/VisualBasic/UIAScrollPattern_snippets.vb#100)]  
diff --git a/xml/System.Windows.Automation/SelectionItemPattern.xml b/xml/System.Windows.Automation/SelectionItemPattern.xml
index f3f8f0190fa..7dffcbd49c9 100644
--- a/xml/System.Windows.Automation/SelectionItemPattern.xml
+++ b/xml/System.Windows.Automation/SelectionItemPattern.xml
@@ -274,7 +274,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIASelectionItemPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIASelectionItemPattern_snip/CSharp/UIASelectionItemPattern_snippets.cs#100)]
  [!code-vb[UIASelectionItemPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIASelectionItemPattern_snip/VisualBasic/UIASelectionItemPattern_snippets.vb#100)]  
diff --git a/xml/System.Windows.Automation/SelectionPattern.xml b/xml/System.Windows.Automation/SelectionPattern.xml
index a844eea50a1..f12ecf8ac9d 100644
--- a/xml/System.Windows.Automation/SelectionPattern.xml
+++ b/xml/System.Windows.Automation/SelectionPattern.xml
@@ -49,8 +49,8 @@
         <ReturnType>System.Windows.Automation.SelectionPattern+SelectionPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.SelectionPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.SelectionPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -92,7 +92,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIASelectionPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIASelectionPattern_snip/CSharp/UIASelectionPattern_snippets.cs#100)]
  [!code-vb[UIASelectionPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIASelectionPattern_snip/VisualBasic/UIASelectionPattern_snippets.vb#100)]  
@@ -119,8 +119,8 @@
         <ReturnType>System.Windows.Automation.SelectionPattern+SelectionPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.SelectionPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.SelectionPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -200,7 +200,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIASelectionPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIASelectionPattern_snip/CSharp/UIASelectionPattern_snippets.cs#100)]
  [!code-vb[UIASelectionPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIASelectionPattern_snip/VisualBasic/UIASelectionPattern_snippets.vb#100)]  
diff --git a/xml/System.Windows.Automation/StructureChangeType.xml b/xml/System.Windows.Automation/StructureChangeType.xml
index fcc677cc562..7e6968064a7 100644
--- a/xml/System.Windows.Automation/StructureChangeType.xml
+++ b/xml/System.Windows.Automation/StructureChangeType.xml
@@ -49,7 +49,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>A child element was added to the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree.</summary>
+        <summary>A child element was added to the UI Automation element tree.</summary>
       </Docs>
     </Member>
     <Member MemberName="ChildRemoved">
@@ -71,7 +71,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>A child element was removed from the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree.</summary>
+        <summary>A child element was removed from the UI Automation element tree.</summary>
       </Docs>
     </Member>
     <Member MemberName="ChildrenBulkAdded">
@@ -93,7 +93,7 @@
       </ReturnValue>
       <MemberValue>3</MemberValue>
       <Docs>
-        <summary>Child elements were added to the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree.</summary>
+        <summary>Child elements were added to the UI Automation element tree.</summary>
       </Docs>
     </Member>
     <Member MemberName="ChildrenBulkRemoved">
@@ -115,7 +115,7 @@
       </ReturnValue>
       <MemberValue>4</MemberValue>
       <Docs>
-        <summary>Child elements were removed from the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree.</summary>
+        <summary>Child elements were removed from the UI Automation element tree.</summary>
       </Docs>
     </Member>
     <Member MemberName="ChildrenInvalidated">
@@ -137,7 +137,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>Child elements were invalidated in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree. This might mean that one or more children were added or removed, depending on the UI Automation providers implementation.</summary>
+        <summary>Child elements were invalidated in the UI Automation element tree. This might mean that one or more children were added or removed, depending on the UI Automation providers implementation.</summary>
       </Docs>
     </Member>
     <Member MemberName="ChildrenReordered">
@@ -159,7 +159,7 @@
       </ReturnValue>
       <MemberValue>5</MemberValue>
       <Docs>
-        <summary>The order of the child elements in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree changed.</summary>
+        <summary>The order of the child elements in the UI Automation element tree changed.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Automation/StructureChangedEventArgs.xml b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
index 87b46a6f298..6b88efa6ac3 100644
--- a/xml/System.Windows.Automation/StructureChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
@@ -45,7 +45,7 @@
       </Parameters>
       <Docs>
         <param name="structureChangeType">A single value that specifies the type of change.</param>
-        <param name="runtimeId">The runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element whose structure changed.</param>
+        <param name="runtimeId">The runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the UI Automation element whose structure changed.</param>
         <summary>Initializes a new instance of the <see cref="P:System.Windows.Automation.StructureChangedEventArgs.StructureChangeType" /> class, specifying the type of change and the [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the element whose structure changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -97,8 +97,8 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element whose structure changed.</summary>
-        <returns>The runtime ID of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element whose structure changed.</returns>
+        <summary>Retrieves the UI Automation runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the UI Automation element whose structure changed.</summary>
+        <returns>The runtime ID of the UI Automation element whose structure changed.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -136,7 +136,7 @@
         <ReturnType>System.Windows.Automation.StructureChangeType</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating the type of change that occurred in the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree structure.</summary>
+        <summary>Gets a value indicating the type of change that occurred in the UI Automation tree structure.</summary>
         <value>The type of changed that occurred.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation/TableItemPattern+TableItemPatternInformation.xml b/xml/System.Windows.Automation/TableItemPattern+TableItemPatternInformation.xml
index 488dc2d5a09..acbaf5d3ae8 100644
--- a/xml/System.Windows.Automation/TableItemPattern+TableItemPatternInformation.xml
+++ b/xml/System.Windows.Automation/TableItemPattern+TableItemPatternInformation.xml
@@ -114,8 +114,8 @@
         <ReturnType>System.Windows.Automation.AutomationElement</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element that supports the GridPattern control pattern and represents the table cell or item container.</summary>
-        <value>A [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element that supports the GridPattern control pattern and represents the table cell or item container.</value>
+        <summary>Gets a UI Automation element that supports the GridPattern control pattern and represents the table cell or item container.</summary>
+        <value>A UI Automation element that supports the GridPattern control pattern and represents the table cell or item container.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/TablePattern.xml b/xml/System.Windows.Automation/TablePattern.xml
index 5b79ee2149f..4ac61eee009 100644
--- a/xml/System.Windows.Automation/TablePattern.xml
+++ b/xml/System.Windows.Automation/TablePattern.xml
@@ -55,8 +55,8 @@
         <ReturnType>System.Windows.Automation.TablePattern+TablePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TablePattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.TablePattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -133,7 +133,7 @@
         <ReturnType>System.Windows.Automation.TablePattern+TablePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TablePattern" />.</summary>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.TablePattern" />.</summary>
         <value>To be added.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation/TextPattern.xml b/xml/System.Windows.Automation/TextPattern.xml
index 000dc640f17..c1c660962f6 100644
--- a/xml/System.Windows.Automation/TextPattern.xml
+++ b/xml/System.Windows.Automation/TextPattern.xml
@@ -1809,7 +1809,7 @@
  Some text controls handle the text insertion point (cursor) as a zero-width text selection and might raise `TextSelectionChangedEvent` when the cursor is moved.  
   
 > [!NOTE]
->  To follow cursor movements, UI Automation clients are advised to keep track of insertion point changes by listening for corresponding [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element events rather than depending on <xref:System.Windows.Automation.TextPattern.TextSelectionChangedEvent>.  
+>  To follow cursor movements, UI Automation clients are advised to keep track of insertion point changes by listening for corresponding UI Automation element events rather than depending on <xref:System.Windows.Automation.TextPattern.TextSelectionChangedEvent>.  
   
  This identifier is used by UI Automation client applications UI Automation providers should use the equivalent field in <xref:System.Windows.Automation.TextPatternIdentifiers>.  
   
diff --git a/xml/System.Windows.Automation/TextPatternIdentifiers.xml b/xml/System.Windows.Automation/TextPatternIdentifiers.xml
index 8164c6e0845..39018c73450 100644
--- a/xml/System.Windows.Automation/TextPatternIdentifiers.xml
+++ b/xml/System.Windows.Automation/TextPatternIdentifiers.xml
@@ -1196,9 +1196,9 @@
  Some text controls handle the text insertion point (cursor) as a zero-width text selection and might raise `TextSelectionChangedEvent` when the cursor is moved.  
   
 > [!NOTE]
->  To follow cursor movements, UI Automation clients are advised to keep track of insertion point changes by listening for corresponding [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element events rather than depending on <xref:System.Windows.Automation.TextPattern.TextSelectionChangedEvent>.  
+>  To follow cursor movements, UI Automation clients are advised to keep track of insertion point changes by listening for corresponding UI Automation element events rather than depending on <xref:System.Windows.Automation.TextPattern.TextSelectionChangedEvent>.  
   
- This identifier is used by [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] providers. Client applications should use the equivalent field in <xref:System.Windows.Automation.TextPattern>.  
+ This identifier is used by UI Automation providers. Client applications should use the equivalent field in <xref:System.Windows.Automation.TextPattern>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/TogglePattern.xml b/xml/System.Windows.Automation/TogglePattern.xml
index 26974056c4d..703b7bbd654 100644
--- a/xml/System.Windows.Automation/TogglePattern.xml
+++ b/xml/System.Windows.Automation/TogglePattern.xml
@@ -41,8 +41,8 @@
         <ReturnType>System.Windows.Automation.TogglePattern+TogglePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TogglePattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.TogglePattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -74,8 +74,8 @@
         <ReturnType>System.Windows.Automation.TogglePattern+TogglePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TogglePattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.TogglePattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/TransformPattern+TransformPatternInformation.xml b/xml/System.Windows.Automation/TransformPattern+TransformPatternInformation.xml
index c81e0562ca6..a7eb5a56415 100644
--- a/xml/System.Windows.Automation/TransformPattern+TransformPatternInformation.xml
+++ b/xml/System.Windows.Automation/TransformPattern+TransformPatternInformation.xml
@@ -41,7 +41,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element can be moved.</summary>
+        <summary>Gets a value that specifies whether the UI Automation element can be moved.</summary>
         <value>
           <see langword="true" /> if the element can be moved; otherwise <see langword="false" />.</value>
         <remarks>
@@ -82,7 +82,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element can be resized.</summary>
+        <summary>Gets a value that specifies whether the UI Automation element can be resized.</summary>
         <value>
           <see langword="true" /> if the element can be resized; otherwise <see langword="false" />.</value>
         <remarks>
@@ -123,7 +123,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element can be rotated.</summary>
+        <summary>Gets a value that specifies whether the UI Automation element can be rotated.</summary>
         <value>
           <see langword="true" /> if the element can be rotated; otherwise <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Automation/TransformPattern.xml b/xml/System.Windows.Automation/TransformPattern.xml
index fd28679c64c..12c90686540 100644
--- a/xml/System.Windows.Automation/TransformPattern.xml
+++ b/xml/System.Windows.Automation/TransformPattern.xml
@@ -48,8 +48,8 @@
         <ReturnType>System.Windows.Automation.TransformPattern+TransformPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TransformPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.TransformPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -91,7 +91,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIATransformPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIATransformPattern_snip/CSharp/UIATransformPattern_snippets.cs#100)]
  [!code-vb[UIATransformPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIATransformPattern_snip/VisualBasic/UIATransformPattern_snippets.vb#100)]  
@@ -128,7 +128,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIATransformPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIATransformPattern_snip/CSharp/UIATransformPattern_snippets.cs#100)]
  [!code-vb[UIATransformPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIATransformPattern_snip/VisualBasic/UIATransformPattern_snippets.vb#100)]  
@@ -165,7 +165,7 @@
    
   
 ## Examples  
- In the following example, a root element is passed to a function that returns a collection of [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that are descendants of the root and satisfy a set of property conditions.  
+ In the following example, a root element is passed to a function that returns a collection of UI Automation elements that are descendants of the root and satisfy a set of property conditions.  
   
  [!code-csharp[UIATransformPattern_snip#100](~/samples/snippets/csharp/VS_Snippets_Wpf/UIATransformPattern_snip/CSharp/UIATransformPattern_snippets.cs#100)]
  [!code-vb[UIATransformPattern_snip#100](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIATransformPattern_snip/VisualBasic/UIATransformPattern_snippets.vb#100)]  
@@ -192,8 +192,8 @@
         <ReturnType>System.Windows.Automation.TransformPattern+TransformPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.TransformPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.TransformPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/TreeWalker.xml b/xml/System.Windows.Automation/TreeWalker.xml
index fb9fc7cf152..cdc890bb551 100644
--- a/xml/System.Windows.Automation/TreeWalker.xml
+++ b/xml/System.Windows.Automation/TreeWalker.xml
@@ -21,13 +21,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- UI Automation clients view the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements on the desktop as a set of <xref:System.Windows.Automation.AutomationElement> objects arranged in a tree structure.  
+ UI Automation clients view the UI Automation elements on the desktop as a set of <xref:System.Windows.Automation.AutomationElement> objects arranged in a tree structure.  
   
- Using the <xref:System.Windows.Automation.TreeWalker> class, a client application can navigate the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree by selecting a view of the tree and stepping from one <xref:System.Windows.Automation.AutomationElement> to another in a specified direction using the <xref:System.Windows.Automation.TreeWalker.GetFirstChild%2A>, <xref:System.Windows.Automation.TreeWalker.GetLastChild%2A>, <xref:System.Windows.Automation.TreeWalker.GetPreviousSibling%2A>, <xref:System.Windows.Automation.TreeWalker.GetNextSibling%2A>, and <xref:System.Windows.Automation.TreeWalker.GetParent%2A> methods.  
+ Using the <xref:System.Windows.Automation.TreeWalker> class, a client application can navigate the UI Automation tree by selecting a view of the tree and stepping from one <xref:System.Windows.Automation.AutomationElement> to another in a specified direction using the <xref:System.Windows.Automation.TreeWalker.GetFirstChild%2A>, <xref:System.Windows.Automation.TreeWalker.GetLastChild%2A>, <xref:System.Windows.Automation.TreeWalker.GetPreviousSibling%2A>, <xref:System.Windows.Automation.TreeWalker.GetNextSibling%2A>, and <xref:System.Windows.Automation.TreeWalker.GetParent%2A> methods.  
   
- Navigating the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] tree using <xref:System.Windows.Automation.TreeWalker> can result in cross-process calls and is not as efficient as locating an element using the <xref:System.Windows.Automation.AutomationElement.FindAll%2A> or <xref:System.Windows.Automation.AutomationElement.FindFirst%2A> methods.  
+ Navigating the UI Automation tree using <xref:System.Windows.Automation.TreeWalker> can result in cross-process calls and is not as efficient as locating an element using the <xref:System.Windows.Automation.AutomationElement.FindAll%2A> or <xref:System.Windows.Automation.AutomationElement.FindFirst%2A> methods.  
   
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
  ]]></format>
     </remarks>
@@ -54,15 +54,15 @@
         <Parameter Name="condition" Type="System.Windows.Automation.Condition" />
       </Parameters>
       <Docs>
-        <param name="condition">The view of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element tree that <see cref="T:System.Windows.Automation.TreeWalker" /> will navigate.</param>
+        <param name="condition">The view of the UI Automation element tree that <see cref="T:System.Windows.Automation.TreeWalker" /> will navigate.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Automation.TreeWalker" /> class.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements that do not match `condition` are skipped over when <xref:System.Windows.Automation.TreeWalker> is used to navigate the element tree.  
+ UI Automation elements that do not match `condition` are skipped over when <xref:System.Windows.Automation.TreeWalker> is used to navigate the element tree.  
   
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
@@ -132,7 +132,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
@@ -174,7 +174,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
@@ -713,7 +713,7 @@
 ## Remarks  
  The element is normalized by navigating up the ancestor chain in the tree until an element that satisfies the view condition for the <xref:System.Windows.Automation.TreeWalker> object is reached. If the root element is reached, the root element is returned even if it does not satisfy the view condition.  
   
- This method is useful for applications that obtain references to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
+ This method is useful for applications that obtain references to UI Automation elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
   
  ]]></format>
         </remarks>
@@ -749,7 +749,7 @@
 ## Remarks  
  The element is normalized by navigating up the ancestor chain in the tree until an element that satisfies the view condition for the <xref:System.Windows.Automation.TreeWalker> object is reached. If the root element is reached, the root element is returned even if it does not satisfy the view condition.  
   
- This method is useful for applications that obtain references to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
+ This method is useful for applications that obtain references to UI Automation elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
   
  ]]></format>
         </remarks>
@@ -790,7 +790,7 @@
 ## Remarks  
  The element is normalized by navigating up the ancestor chain in the tree until an element that satisfies the view condition for the <xref:System.Windows.Automation.TreeWalker> object is reached. If the root element is reached, the root element is returned even if it does not satisfy the view condition.  
   
- This method is useful for applications that obtain references to [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
+ This method is useful for applications that obtain references to UI Automation elements by hit-testing. The application might want to work only with specific types of elements, and can use <xref:System.Windows.Automation.TreeWalker.Normalize%2A> to make sure that no matter what element is initially retrieved (for example, when a scroll bar gets the input focus), only the element of interest (such as a content element) is ultimately retrieved.  
   
  ]]></format>
         </remarks>
@@ -822,7 +822,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your client application might try to find elements in its own user interface, you must make all [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] calls on a separate thread.  
+ If your client application might try to find elements in its own user interface, you must make all UI Automation calls on a separate thread.  
   
    
   
diff --git a/xml/System.Windows.Automation/ValuePattern+ValuePatternInformation.xml b/xml/System.Windows.Automation/ValuePattern+ValuePatternInformation.xml
index 2f7b140bac9..d77ce686e6d 100644
--- a/xml/System.Windows.Automation/ValuePattern+ValuePatternInformation.xml
+++ b/xml/System.Windows.Automation/ValuePattern+ValuePatternInformation.xml
@@ -42,7 +42,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the value of a [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is read-only.</summary>
+        <summary>Gets a value that specifies whether the value of a UI Automation element is read-only.</summary>
         <value>
           <see langword="true" /> if the value is read-only; <see langword="false" /> if it can be modified.</value>
         <remarks>
@@ -82,8 +82,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the value of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element.</summary>
-        <value>The value of the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element as a string. The default is an empty string.</value>
+        <summary>Gets the value of the UI Automation element.</summary>
+        <value>The value of the UI Automation element as a string. The default is an empty string.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/ValuePattern.xml b/xml/System.Windows.Automation/ValuePattern.xml
index 58309af0aba..4b5d9901f7b 100644
--- a/xml/System.Windows.Automation/ValuePattern.xml
+++ b/xml/System.Windows.Automation/ValuePattern.xml
@@ -42,7 +42,7 @@
         <ReturnType>System.Windows.Automation.ValuePattern+ValuePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ValuePattern" />.</summary>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.ValuePattern" />.</summary>
         <value>The cached property values.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -76,7 +76,7 @@
         <ReturnType>System.Windows.Automation.ValuePattern+ValuePatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.ValuePattern" />.</summary>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.ValuePattern" />.</summary>
         <value>The current property values.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation/WindowClosedEventArgs.xml b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
index 8610d6f8035..14f2f3420f4 100644
--- a/xml/System.Windows.Automation/WindowClosedEventArgs.xml
+++ b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
@@ -21,9 +21,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- To subscribe to window-closed events, call <xref:System.Windows.Automation.Automation.AddAutomationEventHandler%2A>, specifying <xref:System.Windows.Automation.WindowPattern.WindowClosedEvent> in the `eventId` parameter and supplying an [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] event handler that takes a <xref:System.Windows.Automation.WindowClosedEventArgs> parameter.  
+ To subscribe to window-closed events, call <xref:System.Windows.Automation.Automation.AddAutomationEventHandler%2A>, specifying <xref:System.Windows.Automation.WindowPattern.WindowClosedEvent> in the `eventId` parameter and supplying an UI Automation event handler that takes a <xref:System.Windows.Automation.WindowClosedEventArgs> parameter.  
   
- When your application receives a window-closed event, the `sender` parameter of the event handler cannot be used to obtain information about the window that has closed, because the corresponding [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] element is no longer valid.  
+ When your application receives a window-closed event, the `sender` parameter of the event handler cannot be used to obtain information about the window that has closed, because the corresponding UI Automation element is no longer valid.  
   
    
   
@@ -78,8 +78,8 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] associated with this event.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] runtime ID of the window on which the event was raised.</returns>
+        <summary>Retrieves the UI Automation runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] associated with this event.</summary>
+        <returns>The UI Automation runtime ID of the window on which the event was raised.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/WindowPattern.xml b/xml/System.Windows.Automation/WindowPattern.xml
index cc0d176fbdc..eda3fb6487c 100644
--- a/xml/System.Windows.Automation/WindowPattern.xml
+++ b/xml/System.Windows.Automation/WindowPattern.xml
@@ -48,8 +48,8 @@
         <ReturnType>System.Windows.Automation.WindowPattern+WindowPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.WindowPattern" />.</summary>
-        <value>A structure containing the cached [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the cached UI Automation property values for this <see cref="T:System.Windows.Automation.WindowPattern" />.</summary>
+        <value>A structure containing the cached UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -197,8 +197,8 @@
         <ReturnType>System.Windows.Automation.WindowPattern+WindowPatternInformation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for this <see cref="T:System.Windows.Automation.WindowPattern" />.</summary>
-        <value>A structure containing the current [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] property values for the control pattern.</value>
+        <summary>Gets the current UI Automation property values for this <see cref="T:System.Windows.Automation.WindowPattern" />.</summary>
+        <value>A structure containing the current UI Automation property values for the control pattern.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -432,7 +432,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A client application may need to listen for <xref:System.Windows.Automation.WindowPattern.WindowClosedEvent> from a cached object since a window is removed from the [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] control view structure immediately upon being closed.  
+ A client application may need to listen for <xref:System.Windows.Automation.WindowPattern.WindowClosedEvent> from a cached object since a window is removed from the UI Automation control view structure immediately upon being closed.  
   
  This identifier is used by UI Automation client applications. UI Automation providers should use the equivalent field in <xref:System.Windows.Automation.WindowPatternIdentifiers>.  
   
diff --git a/xml/UIAutomationClientsideProviders/UIAutomationClientSideProviders.xml b/xml/UIAutomationClientsideProviders/UIAutomationClientSideProviders.xml
index 9c151457fb7..f40d4abe7d9 100644
--- a/xml/UIAutomationClientsideProviders/UIAutomationClientSideProviders.xml
+++ b/xml/UIAutomationClientsideProviders/UIAutomationClientSideProviders.xml
@@ -49,7 +49,7 @@
         <ReturnType>System.Windows.Automation.ClientSideProviderDescription[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Provides information about client-side [!INCLUDE[TLA2#tla_uiautomation](~/includes/tla2sharptla-uiautomation-md.md)] providers.</summary>
+        <summary>Provides information about client-side UI Automation providers.</summary>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/ui-automation/implement-ui-automation-providers-in-a-client-application">Implement UI Automation Providers in a Client Application</related>
         <related type="Article" href="/dotnet/framework/ui-automation/create-a-client-side-ui-automation-provider">Create Client-side UI Automation Providers</related>

From 5578de0a86dce020d8fad2792ba191153d8ccaa8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:38:58 -0800
Subject: [PATCH 088/236] tla2sharptla-url

---
 xml/System.Windows.Data/XmlDataProvider.xml              | 2 +-
 xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index 8b47236b030..8a9b58c0c0b 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -419,7 +419,7 @@
   
  [!code-xaml[XMLDataSource2#XmlFileExample](~/samples/snippets/csharp/VS_Snippets_Wpf/XmlDataSource2/CS/Window1.xaml#xmlfileexample)]  
   
- If the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data resides in a remote [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, you define access to the data by assigning an appropriate [!INCLUDE[TLA2#tla_url](~/includes/tla2sharptla-url-md.md)] to the <xref:System.Windows.Data.XmlDataProvider.Source%2A> attribute as follows:  
+ If the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data resides in a remote [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, you define access to the data by assigning an appropriate URL to the <xref:System.Windows.Data.XmlDataProvider.Source%2A> attribute as follows:  
   
 ```  
 <XmlDataProvider x:Key="BookData" Source="http://MyUrl" XPath="Books"/>  
diff --git a/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml b/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
index 9a8d0911a25..26fbd8ebce5 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
@@ -220,8 +220,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a [!INCLUDE[TLA2#tla_url](~/includes/tla2sharptla-url-md.md)] string that identifies the signature type.</summary>
-        <value>A [!INCLUDE[TLA2#tla_url](~/includes/tla2sharptla-url-md.md)] string that identifies the signature type. The default signature type is <see cref="F:System.Security.Cryptography.Xml.SignedXml.XmlDsigC14NTransformUrl" />.</value>
+        <summary>Gets a URL string that identifies the signature type.</summary>
+        <value>A URL string that identifies the signature type. The default signature type is <see cref="F:System.Security.Cryptography.Xml.SignedXml.XmlDsigC14NTransformUrl" />.</value>
         <remarks>To be added.</remarks>
         <related type="ExternalDocumentation" href="https://go.microsoft.com/fwlink/?LinkId=74494">Digital Signing Framework of the Open Packaging Conventions</related>
       </Docs>

From c18b1395f2f21a35a0ee2c9f52c40e9014efa620 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:39:17 -0800
Subject: [PATCH 089/236] tla2sharptla-wdp

---
 xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml | 6 +++---
 xml/System.Windows.Media.Imaging/WmpBitmapEncoder.xml | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
index 2ee3b988cbe..1c6c15865ef 100644
--- a/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] images achieve lossy and lossless compression by using a single algorithm. [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] images support existing metadata standards. For additional information about this format, see the [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
+ [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. Windows Media Photo images achieve lossy and lossless compression by using a single algorithm. Windows Media Photo images support existing metadata standards. For additional information about this format, see the [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
   
  ]]></format>
     </remarks>
@@ -86,7 +86,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a Windows Media Photo encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -132,7 +132,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a Windows Media Photo encoded image.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Imaging/WmpBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/WmpBitmapEncoder.xml
index 4437be29a9f..c60bd2f5355 100644
--- a/xml/System.Windows.Media.Imaging/WmpBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/WmpBitmapEncoder.xml
@@ -21,9 +21,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] images achieve lossy and lossless compression by using a single algorithm. [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] images support existing metadata standards. For additional information about this format, see [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
+ Windows Media Photo is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. Windows Media Photo images achieve lossy and lossless compression by using a single algorithm. Windows Media Photo images support existing metadata standards. For additional information about this format, see [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
   
- [!INCLUDE[TLA2#tla_wdp](~/includes/tla2sharptla-wdp-md.md)] files do not support preview, global thumbnails, frame level thumbnails, or multiple frames.  
+ Windows Media Photo files do not support preview, global thumbnails, frame level thumbnails, or multiple frames.  
   
  Encoding does not work in partial trust. See [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security) for information on partial trust.  
   

From 2f2153a0fb8a5968e8431eba56e75e3803fce468 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:39:37 -0800
Subject: [PATCH 090/236] tla2sharptla-win32

---
 xml/Microsoft.Win32/CommonDialog.xml          |  4 ++--
 xml/Microsoft.Win32/FileDialog.xml            |  6 ++---
 .../ProviderOptions.xml                       |  2 +-
 ...onElement+AutomationElementInformation.xml |  2 +-
 .../AutomationElement.xml                     |  2 +-
 xml/System.Windows.Automation/ControlType.xml |  2 +-
 .../StructureChangedEventArgs.xml             |  2 +-
 xml/System.Windows.Input/KeyInterop.xml       |  6 ++---
 .../ComponentDispatcher.xml                   |  2 +-
 xml/System.Windows.Interop/HwndHost.xml       |  4 ++--
 xml/System.Windows.Interop/HwndSource.xml     | 24 +++++++++----------
 xml/System.Windows.Interop/HwndSourceHook.xml |  2 +-
 .../IKeyboardInputSite.xml                    |  2 +-
 .../WindowInteropHelper.xml                   | 10 ++++----
 xml/System.Windows.Media/FontFamily.xml       |  2 +-
 xml/System.Windows/Window.xml                 |  2 +-
 16 files changed, 37 insertions(+), 37 deletions(-)

diff --git a/xml/Microsoft.Win32/CommonDialog.xml b/xml/Microsoft.Win32/CommonDialog.xml
index ad8ef66c2ac..958f5b1d02b 100644
--- a/xml/Microsoft.Win32/CommonDialog.xml
+++ b/xml/Microsoft.Win32/CommonDialog.xml
@@ -103,8 +103,8 @@
         <Parameter Name="lParam" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hwnd">Window handle for the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] dialog.</param>
-        <param name="msg">Windows message to be processed by the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] dialog.</param>
+        <param name="hwnd">Window handle for the Win32 dialog.</param>
+        <param name="msg">Windows message to be processed by the Win32 dialog.</param>
         <param name="wParam">Parameters for dialog actions.</param>
         <param name="lParam">Parameters for dialog actions.</param>
         <summary>Defines the common dialog box hook procedure that is overridden to add specific functionality to a common dialog box.</summary>
diff --git a/xml/Microsoft.Win32/FileDialog.xml b/xml/Microsoft.Win32/FileDialog.xml
index a084fdb62de..097d1bb5079 100644
--- a/xml/Microsoft.Win32/FileDialog.xml
+++ b/xml/Microsoft.Win32/FileDialog.xml
@@ -566,8 +566,8 @@
         <Parameter Name="lParam" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="hwnd">Window handle for the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] dialog.</param>
-        <param name="msg">Message to be processed by the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] dialog.</param>
+        <param name="hwnd">Window handle for the Win32 dialog.</param>
+        <param name="msg">Message to be processed by the Win32 dialog.</param>
         <param name="wParam">Parameters for dialog actions.</param>
         <param name="lParam">Parameters for dialog actions.</param>
         <summary>Defines the common file dialog hook procedure that is overridden to add common functionality to a file dialog.</summary>
@@ -943,7 +943,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether the dialog accepts only valid [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] file names.</summary>
+        <summary>Gets or sets a value indicating whether the dialog accepts only valid Win32 file names.</summary>
         <value>
           <see langword="true" /> if warnings will be shown when an invalid file name is provided; otherwise, <see langword="false" />. The default is <see langword="true" />.</value>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Automation.Provider/ProviderOptions.xml b/xml/System.Windows.Automation.Provider/ProviderOptions.xml
index 69abbf37a04..3b2d3767dc8 100644
--- a/xml/System.Windows.Automation.Provider/ProviderOptions.xml
+++ b/xml/System.Windows.Automation.Provider/ProviderOptions.xml
@@ -111,7 +111,7 @@
       </ReturnValue>
       <MemberValue>16</MemberValue>
       <Docs>
-        <summary>The UI Automation provider handles its own focus, and does not want UI Automation to set focus to the nearest window on its behalf when <see cref="M:System.Windows.Automation.AutomationElement.SetFocus" /> is called. This option is typically used by providers for windows that appear to take focus without actually receiving [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] focus, such as menus and drop-down menus.</summary>
+        <summary>The UI Automation provider handles its own focus, and does not want UI Automation to set focus to the nearest window on its behalf when <see cref="M:System.Windows.Automation.AutomationElement.SetFocus" /> is called. This option is typically used by providers for windows that appear to take focus without actually receiving Win32 focus, such as menus and drop-down menus.</summary>
       </Docs>
     </Member>
     <Member MemberName="ServerSideProvider">
diff --git a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
index 2a3bb56c877..3bccea3f1f1 100644
--- a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
+++ b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
@@ -227,7 +227,7 @@
 ## Remarks  
  Control type describes a known interaction model for arbitrary UI Automation elements without relying on a localized control type or combination of complex logic rules.  
   
- The only case where this property can change at run time is for a control that supports <xref:System.Windows.Automation.MultipleViewPattern>. An example is the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] ListView control, which can change from <xref:System.Windows.Automation.ControlType.DataGrid> to <xref:System.Windows.Automation.ControlType.List>, depending on the current view.  
+ The only case where this property can change at run time is for a control that supports <xref:System.Windows.Automation.MultipleViewPattern>. An example is the Win32 ListView control, which can change from <xref:System.Windows.Automation.ControlType.DataGrid> to <xref:System.Windows.Automation.ControlType.List>, depending on the current view.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.ControlTypeProperty>.  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index ed09eefd434..461569561af 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -225,7 +225,7 @@
  Instances of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are uniquely identified on the desktop by their <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty> properties.  
   
 > [!NOTE]
->  <xref:System.Windows.Automation.AutomationElement.AutomationIdProperty> is supported by all UI Automation elements in the control view except top-level application windows, UI Automation elements derived from [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] controls that do not have an ID or x:Uid, and UI Automation elements derived from [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] controls that do not have a control ID.  
+>  <xref:System.Windows.Automation.AutomationElement.AutomationIdProperty> is supported by all UI Automation elements in the control view except top-level application windows, UI Automation elements derived from [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] controls that do not have an ID or x:Uid, and UI Automation elements derived from Win32 controls that do not have a control ID.  
   
    
   
diff --git a/xml/System.Windows.Automation/ControlType.xml b/xml/System.Windows.Automation/ControlType.xml
index 51c2a7fa23d..8759b2e2735 100644
--- a/xml/System.Windows.Automation/ControlType.xml
+++ b/xml/System.Windows.Automation/ControlType.xml
@@ -25,7 +25,7 @@
   
  This class contains static fields, which are themselves <xref:System.Windows.Automation.ControlType> objects, to identify the standard types of controls. There is also a <xref:System.Windows.Automation.ControlType.Custom> type for controls that do not match one of the defined types.  
   
- The only case where a control's control type might change at run time is where the control supports <xref:System.Windows.Automation.MultipleViewPattern>. An example is the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] list view, which can be a <xref:System.Windows.Automation.ControlType.DataGrid> or <xref:System.Windows.Automation.ControlType.List>, depending on the current view.  
+ The only case where a control's control type might change at run time is where the control supports <xref:System.Windows.Automation.MultipleViewPattern>. An example is the Win32 list view, which can be a <xref:System.Windows.Automation.ControlType.DataGrid> or <xref:System.Windows.Automation.ControlType.List>, depending on the current view.  
   
  Control types do not have a one-to-one equivalence to control patterns. A control can be of only one type, but it may support multiple patterns or no patterns at all, depending on its specific functionality.  
   
diff --git a/xml/System.Windows.Automation/StructureChangedEventArgs.xml b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
index 6b88efa6ac3..d4311160091 100644
--- a/xml/System.Windows.Automation/StructureChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
@@ -51,7 +51,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The values that can be returned in `structureChangeType` depend on the implementation of the UI Automation provider. For example, when items are added to or removed from a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] list box, if the provider is not able to determine the number of items added or removed, it might specify <xref:System.Windows.Automation.StructureChangeType.ChildrenInvalidated> and not <xref:System.Windows.Automation.StructureChangeType.ChildAdded> or <xref:System.Windows.Automation.StructureChangeType.ChildRemoved>.  
+ The values that can be returned in `structureChangeType` depend on the implementation of the UI Automation provider. For example, when items are added to or removed from a Win32 list box, if the provider is not able to determine the number of items added or removed, it might specify <xref:System.Windows.Automation.StructureChangeType.ChildrenInvalidated> and not <xref:System.Windows.Automation.StructureChangeType.ChildAdded> or <xref:System.Windows.Automation.StructureChangeType.ChildRemoved>.  
   
  The following table describes the information in the event received by the <xref:System.Windows.Automation.StructureChangedEventHandler> for different structure changes.  
   
diff --git a/xml/System.Windows.Input/KeyInterop.xml b/xml/System.Windows.Input/KeyInterop.xml
index 5f2e0948e54..62d8e57ad84 100644
--- a/xml/System.Windows.Input/KeyInterop.xml
+++ b/xml/System.Windows.Input/KeyInterop.xml
@@ -42,7 +42,7 @@
       </Parameters>
       <Docs>
         <param name="virtualKey">The virtual key to convert.</param>
-        <summary>Converts a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] Virtual-Key into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" />.</summary>
+        <summary>Converts a Win32 Virtual-Key into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" />.</summary>
         <returns>The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] key.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -69,8 +69,8 @@
       </Parameters>
       <Docs>
         <param name="key">The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to convert.</param>
-        <summary>Converts a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" /> into a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] Virtual-Key.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] Virtual-Key.</returns>
+        <summary>Converts a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" /> into a Win32 Virtual-Key.</summary>
+        <returns>The Win32 Virtual-Key.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Interop/ComponentDispatcher.xml b/xml/System.Windows.Interop/ComponentDispatcher.xml
index c339d32d10c..763093b7153 100644
--- a/xml/System.Windows.Interop/ComponentDispatcher.xml
+++ b/xml/System.Windows.Interop/ComponentDispatcher.xml
@@ -26,7 +26,7 @@
   
  The methods are static but they are backed by per-thread data structures.  The static methods allow singleton access but the <xref:System.Windows.Interop.ComponentDispatcher> is sorting out the appropriate per-thread operations.  
   
- The owner of the message pump is defined by the code that calls the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] function [GetMessage](/windows/win32/api/winuser/nf-winuser-getmessage). The owner calls <xref:System.Windows.Interop.ComponentDispatcher.RaiseThreadMessage%2A> for every keyboard message. This method raises the <xref:System.Windows.Interop.ComponentDispatcher.ThreadFilterMessage> event with the messages contained in the event data. If that event is not handled, the owner raises the <xref:System.Windows.Interop.ComponentDispatcher.ThreadPreprocessMessage> event with the messages contained in the event argument.  
+ The owner of the message pump is defined by the code that calls the Win32 function [GetMessage](/windows/win32/api/winuser/nf-winuser-getmessage). The owner calls <xref:System.Windows.Interop.ComponentDispatcher.RaiseThreadMessage%2A> for every keyboard message. This method raises the <xref:System.Windows.Interop.ComponentDispatcher.ThreadFilterMessage> event with the messages contained in the event data. If that event is not handled, the owner raises the <xref:System.Windows.Interop.ComponentDispatcher.ThreadPreprocessMessage> event with the messages contained in the event argument.  
   
 > [!NOTE]
 >  Only keyboard messages are supported.  
diff --git a/xml/System.Windows.Interop/HwndHost.xml b/xml/System.Windows.Interop/HwndHost.xml
index 5140a4324f7..776a25d29e8 100644
--- a/xml/System.Windows.Interop/HwndHost.xml
+++ b/xml/System.Windows.Interop/HwndHost.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- To host a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window, create a class that derives from <xref:System.Windows.Interop.HwndHost>. Override the <xref:System.Windows.Interop.HwndHost.BuildWindowCore%2A> method and create your [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window as a child of the parent window that is passed into the method.  
+ To host a Win32 window, create a class that derives from <xref:System.Windows.Interop.HwndHost>. Override the <xref:System.Windows.Interop.HwndHost.BuildWindowCore%2A> method and create your Win32 window as a child of the parent window that is passed into the method.  
   
 > [!IMPORTANT]
 >  Although <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement>, various properties of <xref:System.Windows.Interop.HwndHost> that come from <xref:System.Windows.FrameworkElement> and other intermediate classes such as <xref:System.Windows.UIElement> are not generally mapped to possible [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] equivalents. Also, not all <xref:System.Windows.FrameworkElement> / <xref:System.Windows.UIElement> input events transfer across the interoperation boundary. <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement> primarily so that an <xref:System.Windows.Interop.HwndHost> instance can be inserted into the widest variety of possible content models, and so that default <xref:System.Windows.FrameworkElement> layout characteristics can apply. For more details on <xref:System.Windows.Interop.HwndHost>, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
@@ -99,7 +99,7 @@
       <Docs>
         <param name="hwndParent">The window handle of the parent window.</param>
         <summary>When overridden in a derived class, creates the window to be hosted.</summary>
-        <returns>The handle to the child [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window to create.</returns>
+        <returns>The handle to the child Win32 window to create.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Interop/HwndSource.xml b/xml/System.Windows.Interop/HwndSource.xml
index d9e807bbc08..9a93e7bd045 100644
--- a/xml/System.Windows.Interop/HwndSource.xml
+++ b/xml/System.Windows.Interop/HwndSource.xml
@@ -37,7 +37,7 @@
 > [!IMPORTANT]
 >  Many members of this class are unavailable in the Internet security zone.  
   
- An <xref:System.Windows.Interop.HwndSource> implements a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window that can contain [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content in the window is arranged, measured, and rendered; and is interactive to input. Because the <xref:System.Windows.Interop.HwndSource> is specifically designed to interoperate with [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)], this class exposes several low-level [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] features. You can use this class to do the following:  
+ An <xref:System.Windows.Interop.HwndSource> implements a Win32 window that can contain [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content in the window is arranged, measured, and rendered; and is interactive to input. Because the <xref:System.Windows.Interop.HwndSource> is specifically designed to interoperate with Win32, this class exposes several low-level Win32 features. You can use this class to do the following:  
   
 -   Specify window styles, window class styles, and extended window styles.  
   
@@ -47,13 +47,13 @@
   
 -   Destroy the window.  
   
- The <xref:System.Windows.Interop.HwndSource> class is designed for general interoperability and is not designed as a managed HWND wrapper. In general, it does not provide managed methods for manipulating the window or properties for inspecting its state. Instead, the <xref:System.Windows.Interop.HwndSource> class provides access to the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window handle (HWND) through the <xref:System.Windows.Interop.HwndSource.Handle%2A> property, which can be passed by means of PInvoke techniques to [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] APIs in order to manipulate the window.  
+ The <xref:System.Windows.Interop.HwndSource> class is designed for general interoperability and is not designed as a managed HWND wrapper. In general, it does not provide managed methods for manipulating the window or properties for inspecting its state. Instead, the <xref:System.Windows.Interop.HwndSource> class provides access to the Win32 window handle (HWND) through the <xref:System.Windows.Interop.HwndSource.Handle%2A> property, which can be passed by means of PInvoke techniques to Win32 APIs in order to manipulate the window.  
   
  **Construction**  
   
  Many aspects of the <xref:System.Windows.Interop.HwndSource> can only be specified at construction time. To create an <xref:System.Windows.Interop.HwndSource>, first create an <xref:System.Windows.Interop.HwndSourceParameters> structure and populate it with the desired parameters. These parameters include the following:  
   
--   The class, window, and extended window styles. You must use PInvoke to change the styles after the window is created. Not all styles can be changed after the window is created. Consult the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] documentation before changing window styles.  
+-   The class, window, and extended window styles. You must use PInvoke to change the styles after the window is created. Not all styles can be changed after the window is created. Consult the Win32 documentation before changing window styles.  
   
 -   The initial position of the window.  
   
@@ -69,7 +69,7 @@
   
  **Object Lifetime**  
   
- An <xref:System.Windows.Interop.HwndSource> is a regular [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, and its lifetime is managed by the garbage collector. Because the <xref:System.Windows.Interop.HwndSource> represents an unmanaged resource, <xref:System.Windows.Interop.HwndSource> implements <xref:System.IDisposable>. Synchronously calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> immediately destroys the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window if called from the owner thread. If called from another thread, the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] window is destroyed asynchronously. Calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> explicitly from the interoperating code might be necessary for certain interoperation scenarios.  
+ An <xref:System.Windows.Interop.HwndSource> is a regular [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, and its lifetime is managed by the garbage collector. Because the <xref:System.Windows.Interop.HwndSource> represents an unmanaged resource, <xref:System.Windows.Interop.HwndSource> implements <xref:System.IDisposable>. Synchronously calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> immediately destroys the Win32 window if called from the owner thread. If called from another thread, the Win32 window is destroyed asynchronously. Calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> explicitly from the interoperating code might be necessary for certain interoperation scenarios.  
   
  **Window Procedures**  
   
@@ -179,8 +179,8 @@
       </Parameters>
       <Docs>
         <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
-        <param name="style">The [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
-        <param name="exStyle">The extended [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
+        <param name="style">The Win32 styles for the window.</param>
+        <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
         <param name="y">The position of the window's upper edge.</param>
         <param name="name">The name of the window.</param>
@@ -231,8 +231,8 @@
       </Parameters>
       <Docs>
         <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
-        <param name="style">The [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
-        <param name="exStyle">The extended [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
+        <param name="style">The Win32 styles for the window.</param>
+        <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
         <param name="y">The position of the window's upper edge.</param>
         <param name="width">The width of the window.</param>
@@ -286,8 +286,8 @@
       </Parameters>
       <Docs>
         <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
-        <param name="style">The [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
-        <param name="exStyle">The extended [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] styles for the window.</param>
+        <param name="style">The Win32 styles for the window.</param>
+        <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
         <param name="y">The position of the window's upper edge.</param>
         <param name="width">The width of the window.</param>
@@ -386,7 +386,7 @@
   
  Most [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] messages that reach the <xref:System.Windows.Interop.HwndSource> have an approximate [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] equivalent. You use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to handle the cases where the message has no [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] equivalent.  
   
- The <xref:System.Windows.Interop.HwndSourceHook> delegate resembles the parameter profile of a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] main window procedure. All window messages that the main window procedure of the <xref:System.Windows.Interop.HwndSource> parent window receives are also forwarded to the <xref:System.Windows.Interop.HwndSourceHook> delegates.  
+ The <xref:System.Windows.Interop.HwndSourceHook> delegate resembles the parameter profile of a Win32 main window procedure. All window messages that the main window procedure of the <xref:System.Windows.Interop.HwndSource> parent window receives are also forwarded to the <xref:System.Windows.Interop.HwndSourceHook> delegates.  
   
  Hooks are called in the order that they were added. If any hook returns `handled`=`true` for a message, the hooks after it in the call order are not called for that message.  
   
@@ -527,7 +527,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can use the handle that is obtained from <xref:System.Windows.Interop.HwndSource.CreateHandleRef%2A> to reference the <xref:System.Windows.Interop.HwndSource> from [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] code. Use the handle for operations such as message handling and window behavior.  
+ You can use the handle that is obtained from <xref:System.Windows.Interop.HwndSource.CreateHandleRef%2A> to reference the <xref:System.Windows.Interop.HwndSource> from Win32 code. Use the handle for operations such as message handling and window behavior.  
   
  To get just the handle, use <xref:System.Windows.Interop.HwndSource.Handle%2A>.  
   
diff --git a/xml/System.Windows.Interop/HwndSourceHook.xml b/xml/System.Windows.Interop/HwndSourceHook.xml
index 29aa7664cf2..77cedeeb57b 100644
--- a/xml/System.Windows.Interop/HwndSourceHook.xml
+++ b/xml/System.Windows.Interop/HwndSourceHook.xml
@@ -31,7 +31,7 @@
     <param name="lParam">The message's lParam value.</param>
     <param name="handled">A value that indicates whether the message was handled. Set the value to <see langword="true" /> if the message was handled; otherwise, <see langword="false" />.</param>
     <summary>Represents the method that handles Win32 window messages.</summary>
-    <returns>The appropriate return value depends on the particular message. See the message documentation details for the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] message being handled.</returns>
+    <returns>The appropriate return value depends on the particular message. See the message documentation details for the Win32 message being handled.</returns>
     <remarks>
       <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Interop/IKeyboardInputSite.xml b/xml/System.Windows.Interop/IKeyboardInputSite.xml
index 3af86bc0dbd..f758157187b 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSite.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSite.xml
@@ -24,7 +24,7 @@
   
  For a discussion of the input architecture specifically implemented for [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] interoperation, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
   
- For more information about [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]-[!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] interoperation scenarios, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
+ For more information about [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]-Win32 interoperation scenarios, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Interop/WindowInteropHelper.xml b/xml/System.Windows.Interop/WindowInteropHelper.xml
index 5efe7f21ace..9c680b0d9a1 100644
--- a/xml/System.Windows.Interop/WindowInteropHelper.xml
+++ b/xml/System.Windows.Interop/WindowInteropHelper.xml
@@ -21,16 +21,16 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Members of this class allows the caller to have internal access to the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] HWND and the parent HWND of a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window>.  The proper security checks are performed by those members.  
+ Members of this class allows the caller to have internal access to the Win32 HWND and the parent HWND of a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window>.  The proper security checks are performed by those members.  
   
  Use this class whenever you need a more specific object based on its HWND.  
   
- An example scenario is if you need to host a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] application. Initialize the <xref:System.Windows.Interop.WindowInteropHelper> with a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window object for the dialog box. You can then get the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window's handle (HWND) from the <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> property and specify the owner for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window with the <xref:System.Windows.Interop.WindowInteropHelper.Owner%2A> property. The following code example shows how to use <xref:System.Windows.Interop.WindowInteropHelper> when hosting a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] application.  
+ An example scenario is if you need to host a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a Win32 application. Initialize the <xref:System.Windows.Interop.WindowInteropHelper> with a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window object for the dialog box. You can then get the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window's handle (HWND) from the <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> property and specify the owner for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window with the <xref:System.Windows.Interop.WindowInteropHelper.Owner%2A> property. The following code example shows how to use <xref:System.Windows.Interop.WindowInteropHelper> when hosting a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a Win32 application.  
   
  [!code-csharp[CorePseudocode#WindowInteropHelper](~/samples/snippets/csharp/VS_Snippets_Wpf/CorePseudocode/CSharp/corepseudocode.cs#windowinterophelper)]
  [!code-vb[CorePseudocode#WindowInteropHelper](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CorePseudocode/visualbasic/corepseudocode.vb#windowinterophelper)]  
   
- Another scenario supported by this class is to obtain a <xref:System.Windows.Interop.HwndSource> object from a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window> object. The <xref:System.Windows.Interop.HwndSource> enables direct processing of [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] messages through the <xref:System.Windows.Interop.HwndSource.AddHook%2A> method. By using <xref:System.Windows.Interop.HwndSource> and <xref:System.Windows.Interop.HwndSource.AddHook%2A> in place of a <xref:System.Windows.Window> you can still handle messages that have no equivalent or handling in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. Create a <xref:System.Windows.Interop.WindowInteropHelper> with the <xref:System.Windows.Window> source, then call <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> on the <xref:System.Windows.Interop.WindowInteropHelper> to get from HWND to <xref:System.Windows.Interop.HwndSource>.  
+ Another scenario supported by this class is to obtain a <xref:System.Windows.Interop.HwndSource> object from a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window> object. The <xref:System.Windows.Interop.HwndSource> enables direct processing of Win32 messages through the <xref:System.Windows.Interop.HwndSource.AddHook%2A> method. By using <xref:System.Windows.Interop.HwndSource> and <xref:System.Windows.Interop.HwndSource.AddHook%2A> in place of a <xref:System.Windows.Window> you can still handle messages that have no equivalent or handling in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. Create a <xref:System.Windows.Interop.WindowInteropHelper> with the <xref:System.Windows.Window> source, then call <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> on the <xref:System.Windows.Interop.WindowInteropHelper> to get from HWND to <xref:System.Windows.Interop.HwndSource>.  
   
  ]]></format>
     </remarks>
@@ -63,7 +63,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The window can be a dialog box, or a window that is otherwise not suitable for being hosted within the bounds of a [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] application.  
+ The window can be a dialog box, or a window that is otherwise not suitable for being hosted within the bounds of a Win32 application.  
   
  ]]></format>
         </remarks>
@@ -179,7 +179,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can reparent windows by setting this property. As is true for general [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] programming, do not reparent windows that are already in use.  
+ You can reparent windows by setting this property. As is true for general Win32 programming, do not reparent windows that are already in use.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index 8558604f72f..d23ada9f9ae 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -98,7 +98,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  [!code-xaml[FontSnippets#FontFallbackSnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontFamilySnippets.xaml#fontfallbacksnippet2)]  
   
 ## Composite Fonts  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] platform provides a composite font feature to allow the construction of full range multilingual fonts, and to avoid displaying missing glyphs. Composite fonts replace the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] font linking, font fallback, font binding, font association, and end-user-defined characters (EUDC) mechanisms.  
+ The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] platform provides a composite font feature to allow the construction of full range multilingual fonts, and to avoid displaying missing glyphs. Composite fonts replace the Win32 font linking, font fallback, font binding, font association, and end-user-defined characters (EUDC) mechanisms.  
   
  A composite font family is available to applications through the <xref:System.Windows.Media.FontFamily> and <xref:System.Windows.Media.Typeface> constructors just like any other font family. Each composite font family is named, and, as with other fonts, can provide localized variants of its name in multiple languages.  
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index 9b2947cb989..e5567ed9f42 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -172,7 +172,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The rules that determine whether the window is activated are the same as those used by the [!INCLUDE[TLA2#tla_win32](~/includes/tla2sharptla-win32-md.md)] `SetForegroundWindow` function (User32.dll).  
+ The rules that determine whether the window is activated are the same as those used by the Win32 `SetForegroundWindow` function (User32.dll).  
   
  If the window is activated in a Windows Presentation Foundation application that is not the user's foreground application, <xref:System.Windows.Application.Activated> event is raised.  
   

From ce25697d76c0eecd801bc6b0a59be658c2e2ccc9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:40:10 -0800
Subject: [PATCH 091/236] tla2sharptla-winclient

---
 .../ObservableCollection`1.xml                |  2 +-
 .../INotifyCollectionChanged.xml              |  2 +-
 .../PresentationTraceSources.xml              |  2 +-
 .../ItemAutomationPeer.xml                    |  2 +-
 .../AutomationElement.xml                     |  2 +-
 .../Popup.xml                                 |  4 +-
 .../RepeatButton.xml                          |  2 +-
 .../ToggleButton.xml                          |  2 +-
 xml/System.Windows.Controls/Button.xml        |  2 +-
 xml/System.Windows.Controls/ComboBox.xml      |  2 +-
 .../ContentControl.xml                        |  2 +-
 .../ControlTemplate.xml                       |  2 +-
 .../DataErrorValidationRule.xml               |  2 +-
 xml/System.Windows.Controls/DataGridRow.xml   |  2 +-
 .../ExceptionValidationRule.xml               |  2 +-
 .../FlowDocumentPageViewer.xml                |  2 +-
 .../HeaderedItemsControl.xml                  |  2 +-
 xml/System.Windows.Controls/InkCanvas.xml     |  2 +-
 xml/System.Windows.Controls/InkPresenter.xml  |  2 +-
 xml/System.Windows.Controls/Label.xml         |  2 +-
 xml/System.Windows.Controls/ListBox.xml       |  2 +-
 xml/System.Windows.Controls/ListBoxItem.xml   |  2 +-
 xml/System.Windows.Controls/Menu.xml          |  2 +-
 xml/System.Windows.Controls/MenuItem.xml      |  2 +-
 .../NotifyDataErrorValidationRule.xml         |  2 +-
 xml/System.Windows.Controls/Panel.xml         |  2 +-
 xml/System.Windows.Controls/ProgressBar.xml   |  2 +-
 xml/System.Windows.Controls/RadioButton.xml   |  2 +-
 xml/System.Windows.Controls/Separator.xml     |  2 +-
 xml/System.Windows.Controls/TabControl.xml    |  2 +-
 xml/System.Windows.Controls/TabItem.xml       |  2 +-
 xml/System.Windows.Controls/ToolBar.xml       |  2 +-
 xml/System.Windows.Controls/Validation.xml    |  4 +-
 .../ValidationError.xml                       |  2 +-
 .../ValidationResult.xml                      |  8 ++--
 .../ValidationRule.xml                        |  2 +-
 xml/System.Windows.Data/Binding.xml           |  6 +--
 xml/System.Windows.Data/BindingBase.xml       |  2 +-
 xml/System.Windows.Data/CollectionView.xml    |  2 +-
 xml/System.Windows.Data/XmlDataProvider.xml   |  2 +-
 xml/System.Windows.Documents/Typography.xml   |  2 +-
 .../ElementHost.xml                           | 30 ++++++-------
 .../PropertyTranslator.xml                    |  2 +-
 .../AccessKeyPressedEventHandler.xml          |  2 +-
 xml/System.Windows.Input/ICommandSource.xml   |  2 +-
 xml/System.Windows.Input/InputBinding.xml     |  8 ++--
 .../InputEventHandler.xml                     |  2 +-
 xml/System.Windows.Input/InputManager.xml     | 26 +++++------
 xml/System.Windows.Input/KeyBinding.xml       |  2 +-
 xml/System.Windows.Input/KeyEventArgs.xml     |  2 +-
 xml/System.Windows.Input/KeyEventHandler.xml  |  2 +-
 xml/System.Windows.Input/Keyboard.xml         | 24 +++++-----
 xml/System.Windows.Input/KeyboardDevice.xml   |  2 +-
 .../KeyboardEventArgs.xml                     |  2 +-
 .../KeyboardEventHandler.xml                  |  2 +-
 .../KeyboardFocusChangedEventArgs.xml         |  2 +-
 .../KeyboardFocusChangedEventHandler.xml      |  2 +-
 xml/System.Windows.Input/Manipulation.xml     |  2 +-
 xml/System.Windows.Input/Mouse.xml            | 38 ++++++++--------
 xml/System.Windows.Input/MouseBinding.xml     |  2 +-
 .../MouseButtonEventHandler.xml               |  2 +-
 xml/System.Windows.Input/MouseEventArgs.xml   |  2 +-
 .../MouseEventHandler.xml                     |  2 +-
 .../MouseWheelEventHandler.xml                |  2 +-
 .../NotifyInputEventArgs.xml                  |  4 +-
 .../NotifyInputEventHandler.xml               |  4 +-
 .../PreProcessInputEventArgs.xml              |  4 +-
 .../PreProcessInputEventHandler.xml           |  4 +-
 .../ProcessInputEventArgs.xml                 |  4 +-
 .../ProcessInputEventHandler.xml              |  4 +-
 .../QueryCursorEventHandler.xml               |  2 +-
 xml/System.Windows.Input/RestoreFocusMode.xml |  4 +-
 xml/System.Windows.Input/Stylus.xml           | 44 +++++++++----------
 .../StylusPointProperties.xml                 |  2 +-
 .../TextCompositionEventHandler.xml           |  2 +-
 .../CursorInteropHelper.xml                   |  2 +-
 xml/System.Windows.Interop/HwndSource.xml     | 12 ++---
 .../IKeyboardInputSite.xml                    |  2 +-
 xml/System.Windows.Interop/Imaging.xml        |  2 +-
 .../WindowInteropHelper.xml                   |  8 ++--
 .../ContentWrapperAttribute.xml               |  2 +-
 .../DictionaryKeyPropertyAttribute.xml        |  2 +-
 xml/System.Windows.Markup/INameScope.xml      |  2 +-
 xml/System.Windows.Markup/StaticExtension.xml |  2 +-
 xml/System.Windows.Markup/TypeExtension.xml   |  2 +-
 xml/System.Windows.Markup/ValueSerializer.xml |  2 +-
 ...itespaceSignificantCollectionAttribute.xml |  2 +-
 .../XamlDesignerSerializationManager.xml      |  2 +-
 xml/System.Windows.Markup/XamlReader.xml      |  2 +-
 .../TextFormatter.xml                         |  2 +-
 .../TextRunTypographyProperties.xml           |  2 +-
 .../TextSource.xml                            |  2 +-
 xml/System.Windows.Media/Brush.xml            |  2 +-
 xml/System.Windows.Media/CachingHint.xml      |  2 +-
 .../CompositionTarget.xml                     |  2 +-
 xml/System.Windows.Media/ContainerVisual.xml  |  8 ++--
 .../DisableDpiAwarenessAttribute.xml          |  4 +-
 xml/System.Windows.Media/DrawingContext.xml   |  2 +-
 xml/System.Windows.Media/FontFamily.xml       |  8 ++--
 xml/System.Windows.Media/FormattedText.xml    |  2 +-
 xml/System.Windows.Media/GlyphTypeface.xml    |  2 +-
 xml/System.Windows.Media/Matrix.xml           |  4 +-
 xml/System.Windows.Media/RenderCapability.xml |  8 ++--
 xml/System.Windows.Media/RenderOptions.xml    |  8 ++--
 xml/System.Windows.Media/SolidColorBrush.xml  |  2 +-
 xml/System.Windows.Media/Visual.xml           | 16 +++----
 xml/System.Windows.Media/VisualCollection.xml |  2 +-
 xml/System.Windows.Media/VisualTreeHelper.xml | 10 ++---
 ...dPropertyBrowsableForChildrenAttribute.xml |  2 +-
 .../AutoResizedEventHandler.xml               |  2 +-
 xml/System.Windows/BaseValueSource.xml        |  2 +-
 .../ColorConvertedBitmapExtension.xml         |  2 +-
 xml/System.Windows/ContentOperations.xml      |  2 +-
 xml/System.Windows/DependencyObject.xml       | 10 ++---
 xml/System.Windows/DependencyProperty.xml     | 24 +++++-----
 .../DependencyPropertyChangedEventHandler.xml |  2 +-
 .../DependencyPropertyHelper.xml              |  2 +-
 xml/System.Windows/DragEventHandler.xml       |  2 +-
 .../DynamicResourceExtension.xml              |  4 +-
 xml/System.Windows/EventManager.xml           |  6 +--
 .../FrameworkContentElement.xml               |  6 +--
 xml/System.Windows/FrameworkElement.xml       | 20 ++++-----
 .../FrameworkPropertyMetadata.xml             |  2 +-
 xml/System.Windows/FreezableCollection`1.xml  |  2 +-
 .../GiveFeedbackEventHandler.xml              |  2 +-
 xml/System.Windows/IInputElement.xml          |  2 +-
 xml/System.Windows/IWeakEventListener.xml     |  2 +-
 xml/System.Windows/LostFocusEventManager.xml  |  2 +-
 xml/System.Windows/PropertyMetadata.xml       |  2 +-
 .../QueryContinueDragEventHandler.xml         |  2 +-
 xml/System.Windows/ResourceDictionary.xml     |  2 +-
 xml/System.Windows/RoutedEventHandler.xml     |  2 +-
 xml/System.Windows/SizeChangedInfo.xml        |  2 +-
 .../SourceChangedEventHandler.xml             |  2 +-
 .../StaticResourceExtension.xml               |  4 +-
 xml/System.Windows/Style.xml                  | 10 ++---
 .../TemplateBindingExtension.xml              |  2 +-
 .../ThemeDictionaryExtension.xml              |  4 +-
 xml/System.Windows/Trigger.xml                |  2 +-
 xml/System.Windows/TriggerBase.xml            |  2 +-
 xml/System.Windows/UIElement.xml              |  4 +-
 xml/System.Windows/UIElement3D.xml            |  2 +-
 xml/System.Windows/ValueSource.xml            |  2 +-
 xml/System.Windows/VisualState.xml            |  2 +-
 xml/System.Windows/VisualStateManager.xml     |  2 +-
 xml/System.Xaml/AmbientPropertyValue.xml      |  2 +-
 xml/System.Xaml/IAmbientProvider.xml          |  2 +-
 xml/System.Xaml/XamlServices.xml              |  8 ++--
 xml/ns-System.Windows.Forms.Integration.xml   |  6 +--
 149 files changed, 316 insertions(+), 316 deletions(-)

diff --git a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
index d5521cb454a..bb88ac1ffcb 100644
--- a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
+++ b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
@@ -80,7 +80,7 @@
   
  You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the UI automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event, an event that should be raised whenever the underlying collection changes.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface.  
+ WPF provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface.  
   
  Before implementing your own collection, consider using <xref:System.Collections.ObjectModel.ObservableCollection%601> or one of the existing collection classes, such as <xref:System.Collections.Generic.List%601>, <xref:System.Collections.ObjectModel.Collection%601>, and <xref:System.ComponentModel.BindingList%601>, among many others. If you have an advanced scenario and want to implement your own collection, consider using <xref:System.Collections.IList>, which provides a non-generic collection of objects that can be individually accessed by index. Implementing <xref:System.Collections.IList> provides the best performance with the data binding engine.  
   
diff --git a/xml/System.Collections.Specialized/INotifyCollectionChanged.xml b/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
index 8f7838d9b04..ce22137ebfe 100644
--- a/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
+++ b/xml/System.Collections.Specialized/INotifyCollectionChanged.xml
@@ -56,7 +56,7 @@
 ## Remarks  
  You can enumerate over any collection that implements the <xref:System.Collections.IEnumerable> interface. However, to set up dynamic bindings so that insertions or deletions in the collection update the UI automatically, the collection must implement the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. This interface exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event that must be raised whenever the underlying collection changes.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. For an example, see [How to: Create and Bind to an ObservableCollection](/dotnet/framework/wpf/data/how-to-create-and-bind-to-an-observablecollection).  
+ WPF provides the <xref:System.Collections.ObjectModel.ObservableCollection%601> class, which is a built-in implementation of a data collection that exposes the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface. For an example, see [How to: Create and Bind to an ObservableCollection](/dotnet/framework/wpf/data/how-to-create-and-bind-to-an-observablecollection).  
   
  The individual data objects within the collection must satisfy the requirements described in the [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
   
diff --git a/xml/System.Diagnostics/PresentationTraceSources.xml b/xml/System.Diagnostics/PresentationTraceSources.xml
index 5a6c4797cfd..c6fe858df44 100644
--- a/xml/System.Diagnostics/PresentationTraceSources.xml
+++ b/xml/System.Diagnostics/PresentationTraceSources.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Debug tracing is only available when a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application is running in full trust mode.  
+ Debug tracing is only available when a WPF application is running in full trust mode.  
   
  In order to enable tracing, you first must set a registry key, then you must configure trace sources.  
   
diff --git a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
index 9d042984368..aa2688b668c 100644
--- a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
@@ -32,7 +32,7 @@
 ## Remarks  
  Data items that are not also <xref:System.Windows.UIElement> types do not have children; however, they can have a <xref:System.Windows.UIElement> tree and a corresponding UI Automation tree.  
   
- For example, a <xref:System.Windows.Controls.ListBox> can have a collection of strings that contain data items. When those items are processed by an <xref:System.Windows.Controls.ItemsControl> for visualization, a <xref:System.Windows.UIElement> tree is created for them. This tree can have a corresponding UI Automation tree. After the tree is created, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] merges the <xref:System.Windows.UIElement> tree into a UI Automation tree. <xref:System.Windows.Automation.Peers.ItemAutomationPeer> works with its <xref:System.Windows.UIElement> counterpart, if it exists, to obtain more information about the <xref:System.Windows.UIElement> tree.  
+ For example, a <xref:System.Windows.Controls.ListBox> can have a collection of strings that contain data items. When those items are processed by an <xref:System.Windows.Controls.ItemsControl> for visualization, a <xref:System.Windows.UIElement> tree is created for them. This tree can have a corresponding UI Automation tree. After the tree is created, WPF merges the <xref:System.Windows.UIElement> tree into a UI Automation tree. <xref:System.Windows.Automation.Peers.ItemAutomationPeer> works with its <xref:System.Windows.UIElement> counterpart, if it exists, to obtain more information about the <xref:System.Windows.UIElement> tree.  
   
  Only visible data items, or more precisely, the corresponding <xref:System.Windows.UIElement> trees, have this dualism. Non-visible data items, which have no corresponding <xref:System.Windows.UIElement> trees, have only one <xref:System.Windows.Automation.Peers.ItemAutomationPeer>.  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 461569561af..7c6638b8c1c 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -981,7 +981,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method might be used by a client helper library to enable its callers to access its own native element type. For example, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses this method internally so that it can return an <xref:System.Windows.Automation.AutomationElement> to clients that want to get a UI Automation element directly from a <xref:System.Windows.UIElement>.  
+ This method might be used by a client helper library to enable its callers to access its own native element type. For example, WPF uses this method internally so that it can return an <xref:System.Windows.Automation.AutomationElement> to clients that want to get a UI Automation element directly from a <xref:System.Windows.UIElement>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls.Primitives/Popup.xml b/xml/System.Windows.Controls.Primitives/Popup.xml
index ee06403c3e1..8192028601b 100644
--- a/xml/System.Windows.Controls.Primitives/Popup.xml
+++ b/xml/System.Windows.Controls.Primitives/Popup.xml
@@ -1468,7 +1468,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the WPF infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1497,7 +1497,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the WPF infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls.Primitives/RepeatButton.xml b/xml/System.Windows.Controls.Primitives/RepeatButton.xml
index d3d07ca7ed4..f2da23a4c43 100644
--- a/xml/System.Windows.Controls.Primitives/RepeatButton.xml
+++ b/xml/System.Windows.Controls.Primitives/RepeatButton.xml
@@ -263,7 +263,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.RepeatButtonAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.RepeatButtonAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls.Primitives/ToggleButton.xml b/xml/System.Windows.Controls.Primitives/ToggleButton.xml
index fe77fa66961..42932aa3761 100644
--- a/xml/System.Windows.Controls.Primitives/ToggleButton.xml
+++ b/xml/System.Windows.Controls.Primitives/ToggleButton.xml
@@ -451,7 +451,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ToggleButtonAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ToggleButtonAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Button.xml b/xml/System.Windows.Controls/Button.xml
index d309187bd83..f34a4a41e61 100644
--- a/xml/System.Windows.Controls/Button.xml
+++ b/xml/System.Windows.Controls/Button.xml
@@ -331,7 +331,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Creates an appropriate <see cref="T:System.Windows.Automation.Peers.ButtonAutomationPeer" /> for this control as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Creates an appropriate <see cref="T:System.Windows.Automation.Peers.ButtonAutomationPeer" /> for this control as part of the WPF infrastructure.</summary>
         <returns>A <see cref="T:System.Windows.Automation.Peers.ButtonAutomationPeer" /> for this control.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ComboBox.xml b/xml/System.Windows.Controls/ComboBox.xml
index 025ae7f7cf5..3ae3226da6e 100644
--- a/xml/System.Windows.Controls/ComboBox.xml
+++ b/xml/System.Windows.Controls/ComboBox.xml
@@ -726,7 +726,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ComboBoxAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ComboBoxAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ContentControl.xml b/xml/System.Windows.Controls/ContentControl.xml
index 2e776434b07..7046e29b7ef 100644
--- a/xml/System.Windows.Controls/ContentControl.xml
+++ b/xml/System.Windows.Controls/ContentControl.xml
@@ -194,7 +194,7 @@ Four buttons with different types of content
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Because the <xref:System.Windows.Controls.ContentControl.Content%2A> property is of type <xref:System.Object>, there are no restrictions on what you can put in a <xref:System.Windows.Controls.ContentControl>. The <xref:System.Windows.Controls.ContentControl.Content%2A> is displayed by a <xref:System.Windows.Controls.ContentPresenter>, which is in the <xref:System.Windows.Controls.ControlTemplate> of the <xref:System.Windows.Controls.ContentControl>.  Every <xref:System.Windows.Controls.ContentControl> type in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] has a <xref:System.Windows.Controls.ContentPresenter> in its default <xref:System.Windows.Controls.ControlTemplate>.  For more information about how the <xref:System.Windows.Controls.ContentPresenter> displays <xref:System.Windows.Controls.ContentControl.Content%2A>, see <xref:System.Windows.Controls.ContentPresenter>.  
+ Because the <xref:System.Windows.Controls.ContentControl.Content%2A> property is of type <xref:System.Object>, there are no restrictions on what you can put in a <xref:System.Windows.Controls.ContentControl>. The <xref:System.Windows.Controls.ContentControl.Content%2A> is displayed by a <xref:System.Windows.Controls.ContentPresenter>, which is in the <xref:System.Windows.Controls.ControlTemplate> of the <xref:System.Windows.Controls.ContentControl>.  Every <xref:System.Windows.Controls.ContentControl> type in WPF has a <xref:System.Windows.Controls.ContentPresenter> in its default <xref:System.Windows.Controls.ControlTemplate>.  For more information about how the <xref:System.Windows.Controls.ContentPresenter> displays <xref:System.Windows.Controls.ContentControl.Content%2A>, see <xref:System.Windows.Controls.ContentPresenter>.  
   
 <a name="dependencyPropertyInfo_Content"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/ControlTemplate.xml b/xml/System.Windows.Controls/ControlTemplate.xml
index 665b579fe83..9181646b8af 100644
--- a/xml/System.Windows.Controls/ControlTemplate.xml
+++ b/xml/System.Windows.Controls/ControlTemplate.xml
@@ -33,7 +33,7 @@
 ## Remarks  
  The <xref:System.Windows.Controls.ControlTemplate> allows you to specify the visual structure of a control. The control author can define the default <xref:System.Windows.Controls.ControlTemplate> and the application author can override the <xref:System.Windows.Controls.ControlTemplate> to reconstruct the visual structure of the control.  
   
- Control templating is one of the many features offered by the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] styling and templating model. The styling and templating model provides you with such great flexibility that in many cases you do not need to write your own controls. If you are an application author that wants to change the visualization of your control or to replace the <xref:System.Windows.Controls.ControlTemplate> of an existing control, see the [Styling and Templating](/dotnet/framework/wpf/controls/styling-and-templating) topic for examples and an in-depth discussion.  
+ Control templating is one of the many features offered by the WPF styling and templating model. The styling and templating model provides you with such great flexibility that in many cases you do not need to write your own controls. If you are an application author that wants to change the visualization of your control or to replace the <xref:System.Windows.Controls.ControlTemplate> of an existing control, see the [Styling and Templating](/dotnet/framework/wpf/controls/styling-and-templating) topic for examples and an in-depth discussion.  
   
  If you are writing your own control, see "Create a Custom Control" in the [Control Authoring Overview](/dotnet/framework/wpf/controls/control-authoring-overview).  
   
diff --git a/xml/System.Windows.Controls/DataErrorValidationRule.xml b/xml/System.Windows.Controls/DataErrorValidationRule.xml
index d13e1b57581..0f26a46031c 100644
--- a/xml/System.Windows.Controls/DataErrorValidationRule.xml
+++ b/xml/System.Windows.Controls/DataErrorValidationRule.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> object. If your source object implements the <xref:System.ComponentModel.IDataErrorInfo> interface, you can use the built-in rule <xref:System.Windows.Controls.DataErrorValidationRule> to check for errors raised by the <xref:System.ComponentModel.IDataErrorInfo> implementation.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> object. If your source object implements the <xref:System.ComponentModel.IDataErrorInfo> interface, you can use the built-in rule <xref:System.Windows.Controls.DataErrorValidationRule> to check for errors raised by the <xref:System.ComponentModel.IDataErrorInfo> implementation.  
   
  An alternative syntax to setting the <xref:System.Windows.Controls.DataErrorValidationRule> explicitly is to set the <xref:System.Windows.Data.Binding.ValidatesOnDataErrors%2A> property to `true` on your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object.  
   
diff --git a/xml/System.Windows.Controls/DataGridRow.xml b/xml/System.Windows.Controls/DataGridRow.xml
index a64d53cad65..1fe34980394 100644
--- a/xml/System.Windows.Controls/DataGridRow.xml
+++ b/xml/System.Windows.Controls/DataGridRow.xml
@@ -915,7 +915,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>Always call the base implementation as the first operation in your implementation. Failure to do this will significantly disable the entire [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system, which causes incorrect values to be reported. The specific <see cref="T:System.Windows.Controls.DataGridRow" /> implementation is also responsible for maintaining the correct state for the <see cref="P:System.Windows.Controls.DataGridRow.AlternationIndex" /> property, which affects the visible user interface and invalidates the visual tree based on property value changes at appropriate times.</para>
+          <para>Always call the base implementation as the first operation in your implementation. Failure to do this will significantly disable the entire WPF property system, which causes incorrect values to be reported. The specific <see cref="T:System.Windows.Controls.DataGridRow" /> implementation is also responsible for maintaining the correct state for the <see cref="P:System.Windows.Controls.DataGridRow.AlternationIndex" /> property, which affects the visible user interface and invalidates the visual tree based on property value changes at appropriate times.</para>
         </block>
         <altmember cref="T:System.Windows.Controls.DataGrid" />
         <altmember cref="P:System.Windows.Controls.DataGridRow.AlternationIndex" />
diff --git a/xml/System.Windows.Controls/ExceptionValidationRule.xml b/xml/System.Windows.Controls/ExceptionValidationRule.xml
index d994891658c..5c287010615 100644
--- a/xml/System.Windows.Controls/ExceptionValidationRule.xml
+++ b/xml/System.Windows.Controls/ExceptionValidationRule.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> object. The <xref:System.Windows.Controls.ExceptionValidationRule> class is a built-in rule that checks for exceptions that are thrown during the updates of the binding source property. You can provide custom logic to specify how the binding engine handles these exceptions by using a <xref:System.Windows.Data.UpdateSourceExceptionFilterCallback>. For more information, see <xref:System.Windows.Data.Binding.UpdateSourceExceptionFilter%2A>.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> object. The <xref:System.Windows.Controls.ExceptionValidationRule> class is a built-in rule that checks for exceptions that are thrown during the updates of the binding source property. You can provide custom logic to specify how the binding engine handles these exceptions by using a <xref:System.Windows.Data.UpdateSourceExceptionFilterCallback>. For more information, see <xref:System.Windows.Data.Binding.UpdateSourceExceptionFilter%2A>.  
   
  An alternative syntax to setting the <xref:System.Windows.Controls.ExceptionValidationRule> explicitly is to set the <xref:System.Windows.Data.Binding.ValidatesOnExceptions%2A> property to `true` on your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object.  
   
diff --git a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
index c10bad2e148..c137ae17462 100644
--- a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
@@ -792,7 +792,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/HeaderedItemsControl.xml b/xml/System.Windows.Controls/HeaderedItemsControl.xml
index 7b07f9fe9bd..95ef4a0109d 100644
--- a/xml/System.Windows.Controls/HeaderedItemsControl.xml
+++ b/xml/System.Windows.Controls/HeaderedItemsControl.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this class to create a control that contains a heading (or title) and multiple items. The <xref:System.Windows.Controls.HeaderedItemsControl.Header%2A?displayProperty=nameWithType> property can be any type. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] ships three controls that inherit from <xref:System.Windows.Controls.HeaderedItemsControl>:  
+ Use this class to create a control that contains a heading (or title) and multiple items. The <xref:System.Windows.Controls.HeaderedItemsControl.Header%2A?displayProperty=nameWithType> property can be any type. WPF ships three controls that inherit from <xref:System.Windows.Controls.HeaderedItemsControl>:  
   
 -   <xref:System.Windows.Controls.MenuItem>  
   
diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index 082747150a6..7220bf2102d 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -1939,7 +1939,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.InkCanvasAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.InkCanvasAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>To be added.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/InkPresenter.xml b/xml/System.Windows.Controls/InkPresenter.xml
index b0b844830ed..18a39ed4110 100644
--- a/xml/System.Windows.Controls/InkPresenter.xml
+++ b/xml/System.Windows.Controls/InkPresenter.xml
@@ -274,7 +274,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.InkPresenterAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.InkPresenterAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>To be added.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Label.xml b/xml/System.Windows.Controls/Label.xml
index 4f0eb2b9e3d..180207a39f3 100644
--- a/xml/System.Windows.Controls/Label.xml
+++ b/xml/System.Windows.Controls/Label.xml
@@ -107,7 +107,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.LabelAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.LabelAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ListBox.xml b/xml/System.Windows.Controls/ListBox.xml
index b7d3e5ed972..a184c351f66 100644
--- a/xml/System.Windows.Controls/ListBox.xml
+++ b/xml/System.Windows.Controls/ListBox.xml
@@ -211,7 +211,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ListBoxAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ListBoxAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ListBoxItem.xml b/xml/System.Windows.Controls/ListBoxItem.xml
index 145f0edb010..acd7d33fa1a 100644
--- a/xml/System.Windows.Controls/ListBoxItem.xml
+++ b/xml/System.Windows.Controls/ListBoxItem.xml
@@ -174,7 +174,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ListBoxItemAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ListBoxItemAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Menu.xml b/xml/System.Windows.Controls/Menu.xml
index 46ba7a26e9c..32a9b23c3ea 100644
--- a/xml/System.Windows.Controls/Menu.xml
+++ b/xml/System.Windows.Controls/Menu.xml
@@ -178,7 +178,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.MenuAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.MenuAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/MenuItem.xml b/xml/System.Windows.Controls/MenuItem.xml
index bc9a32f27a7..04e71c535be 100644
--- a/xml/System.Windows.Controls/MenuItem.xml
+++ b/xml/System.Windows.Controls/MenuItem.xml
@@ -1447,7 +1447,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.MenuItemAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.MenuItemAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>A <see cref="T:System.Windows.Automation.Peers.MenuItemAutomationPeer" /> for this <see cref="T:System.Windows.Controls.MenuItem" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/NotifyDataErrorValidationRule.xml b/xml/System.Windows.Controls/NotifyDataErrorValidationRule.xml
index 327f5344c55..943e0abf9a4 100644
--- a/xml/System.Windows.Controls/NotifyDataErrorValidationRule.xml
+++ b/xml/System.Windows.Controls/NotifyDataErrorValidationRule.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.BindingGroup> object. The <xref:System.Windows.Controls.NotifyDataErrorValidationRule> class is a built-in rule that checks for exceptions that are thrown during the updates of the binding source property. You can provide custom logic to specify how the binding engine handles these exceptions by using a <xref:System.Windows.Data.UpdateSourceExceptionFilterCallback>. For more information, see <xref:System.Windows.Data.Binding.UpdateSourceExceptionFilter%2A>.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with a <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.BindingGroup> object. The <xref:System.Windows.Controls.NotifyDataErrorValidationRule> class is a built-in rule that checks for exceptions that are thrown during the updates of the binding source property. You can provide custom logic to specify how the binding engine handles these exceptions by using a <xref:System.Windows.Data.UpdateSourceExceptionFilterCallback>. For more information, see <xref:System.Windows.Data.Binding.UpdateSourceExceptionFilter%2A>.  
   
  An alternative syntax to setting the <xref:System.Windows.Controls.NotifyDataErrorValidationRule> explicitly is to set the <xref:System.Windows.Data.Binding.ValidatesOnExceptions%2A> property to `true` on your <xref:System.Windows.Data.Binding>, <xref:System.Windows.Data.MultiBinding>, or <xref:System.Windows.Data.BindingGroup> object. By default, the value of <xref:System.Windows.Data.Binding.ValidatesOnExceptions%2A> is `true`, so you do not need to explicitly use a <xref:System.Windows.Controls.NotifyDataErrorValidationRule>.  
   
diff --git a/xml/System.Windows.Controls/Panel.xml b/xml/System.Windows.Controls/Panel.xml
index 9dcd5c64d69..0bbee2c1694 100644
--- a/xml/System.Windows.Controls/Panel.xml
+++ b/xml/System.Windows.Controls/Panel.xml
@@ -38,7 +38,7 @@
 ## Remarks  
  A <xref:System.Windows.Controls.Panel> contains a collection of <xref:System.Windows.UIElement> objects, which are in the <xref:System.Windows.Controls.Panel.Children%2A> property. Adding a <xref:System.Windows.UIElement> child to a <xref:System.Windows.Controls.Panel> implicitly adds it to the <xref:System.Windows.Controls.UIElementCollection> for the <xref:System.Windows.Controls.Panel> element.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a comprehensive suite of derived <xref:System.Windows.Controls.Panel> implementations, enabling many complex layouts. If you want to implement new layout containers, use the <xref:System.Windows.FrameworkElement.MeasureOverride%2A> and <xref:System.Windows.FrameworkElement.ArrangeOverride%2A> methods. For a demonstration of how to use these methods, see [Create a Custom Content-Wrapping Panel Sample](https://go.microsoft.com/fwlink/?LinkID=159979).  
+ WPF provides a comprehensive suite of derived <xref:System.Windows.Controls.Panel> implementations, enabling many complex layouts. If you want to implement new layout containers, use the <xref:System.Windows.FrameworkElement.MeasureOverride%2A> and <xref:System.Windows.FrameworkElement.ArrangeOverride%2A> methods. For a demonstration of how to use these methods, see [Create a Custom Content-Wrapping Panel Sample](https://go.microsoft.com/fwlink/?LinkID=159979).  
   
  <xref:System.Windows.Controls.Panel> elements do not receive mouse or stylus events if a <xref:System.Windows.Controls.Panel.Background%2A> is not defined. If you need to handle mouse or stylus events but do not want a background for your <xref:System.Windows.Controls.Panel>, use <xref:System.Windows.Media.Brushes.Transparent%2A>.  
   
diff --git a/xml/System.Windows.Controls/ProgressBar.xml b/xml/System.Windows.Controls/ProgressBar.xml
index 27241fdcb51..7b9a9564668 100644
--- a/xml/System.Windows.Controls/ProgressBar.xml
+++ b/xml/System.Windows.Controls/ProgressBar.xml
@@ -189,7 +189,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ProgressBarAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ProgressBarAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/RadioButton.xml b/xml/System.Windows.Controls/RadioButton.xml
index 3ef4a4a8ca7..89db6d941b7 100644
--- a/xml/System.Windows.Controls/RadioButton.xml
+++ b/xml/System.Windows.Controls/RadioButton.xml
@@ -231,7 +231,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.RadioButtonAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.RadioButtonAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Separator.xml b/xml/System.Windows.Controls/Separator.xml
index 488d99c2e9f..caedab552bc 100644
--- a/xml/System.Windows.Controls/Separator.xml
+++ b/xml/System.Windows.Controls/Separator.xml
@@ -87,7 +87,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.SeparatorAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.SeparatorAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/TabControl.xml b/xml/System.Windows.Controls/TabControl.xml
index cfefe8c591f..2ba07fa9ad1 100644
--- a/xml/System.Windows.Controls/TabControl.xml
+++ b/xml/System.Windows.Controls/TabControl.xml
@@ -435,7 +435,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.TabControlAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.TabControlAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/TabItem.xml b/xml/System.Windows.Controls/TabItem.xml
index 5e1bc40af3e..8ff466954bc 100644
--- a/xml/System.Windows.Controls/TabItem.xml
+++ b/xml/System.Windows.Controls/TabItem.xml
@@ -277,7 +277,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.TabItemAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.TabItemAutomationPeer" /> implementation for this control, as part of the WPF automation infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ToolBar.xml b/xml/System.Windows.Controls/ToolBar.xml
index 26f744fe689..fe365f9d214 100644
--- a/xml/System.Windows.Controls/ToolBar.xml
+++ b/xml/System.Windows.Controls/ToolBar.xml
@@ -714,7 +714,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ToolBarAutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.ToolBarAutomationPeer" /> implementation for this control, as part of the WPF infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Validation.xml b/xml/System.Windows.Controls/Validation.xml
index 4d9c3942052..3489363560c 100644
--- a/xml/System.Windows.Controls/Validation.xml
+++ b/xml/System.Windows.Controls/Validation.xml
@@ -110,7 +110,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. Validation occurs during binding target-to-binding source value transfer before the converter is called. The following describes the validation process:  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. Validation occurs during binding target-to-binding source value transfer before the converter is called. The following describes the validation process:  
   
 1.  When a value is being transferred from the target property to the source property, the data binding engine first removes any <xref:System.Windows.Controls.ValidationError> that may have been added to the <xref:System.Windows.Controls.Validation.Errors%2A?displayProperty=nameWithType> attached property of the bound element. It then checks if there are any custom <xref:System.Windows.Controls.ValidationRule>s defined for that <xref:System.Windows.Data.Binding>, in which case it calls the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method on each of the <xref:System.Windows.Controls.ValidationRule>s until one of them runs into an error or until all of them pass.  
   
@@ -256,7 +256,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model allows you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. If the user enters an invalid value, you may want to provide some feedback about the error on the application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. One way to provide such feedback is to set the <xref:System.Windows.Controls.Validation>.<xref:System.Windows.Controls.Validation.ErrorTemplate%2A> attached property to a custom <xref:System.Windows.Controls.ControlTemplate>.  
+ The WPF data binding model allows you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. If the user enters an invalid value, you may want to provide some feedback about the error on the application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. One way to provide such feedback is to set the <xref:System.Windows.Controls.Validation>.<xref:System.Windows.Controls.Validation.ErrorTemplate%2A> attached property to a custom <xref:System.Windows.Controls.ControlTemplate>.  
   
  For a detailed discussion of validation, see the Data Validation section of the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Controls/ValidationError.xml b/xml/System.Windows.Controls/ValidationError.xml
index b2c487531f5..d92bae08bd2 100644
--- a/xml/System.Windows.Controls/ValidationError.xml
+++ b/xml/System.Windows.Controls/ValidationError.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate validation rules with your <xref:System.Windows.Data.Binding> object. Validation occurs during target-to-source value transfer before the converter is called. The following describes the validation process.  
+ The WPF data binding model enables you to associate validation rules with your <xref:System.Windows.Data.Binding> object. Validation occurs during target-to-source value transfer before the converter is called. The following describes the validation process.  
   
 1.  When a value is being transferred from the target property to the source property, the data binding engine first removes any <xref:System.Windows.Controls.ValidationError> that might have been added to the <xref:System.Windows.Controls.Validation.Errors%2A?displayProperty=nameWithType> attached property of the bound element. It then checks whether any custom validation rules are defined for that <xref:System.Windows.Data.Binding>, in which case it calls the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method on each <xref:System.Windows.Controls.ValidationRule> until one of them fails or until all of them pass.  
   
diff --git a/xml/System.Windows.Controls/ValidationResult.xml b/xml/System.Windows.Controls/ValidationResult.xml
index 1779cb303bd..e20cb76318e 100644
--- a/xml/System.Windows.Controls/ValidationResult.xml
+++ b/xml/System.Windows.Controls/ValidationResult.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
   
  For a detailed discussion of the validation process, see "Data Validation" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -71,7 +71,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
   
  For a detailed discussion of the validation process, see "Data Validation" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -154,7 +154,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
   
  For a detailed discussion of the validation process, see "Data Validation" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -226,7 +226,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by subclassing the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. The <xref:System.Windows.Controls.ValidationRule.Validate%2A> method returns a <xref:System.Windows.Controls.ValidationResult> object to report whether the checked value is valid.  
   
  For a detailed discussion of the validation process, see "Data Validation" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Controls/ValidationRule.xml b/xml/System.Windows.Controls/ValidationRule.xml
index 3f6b2f9f6ad..19b6683e8db 100644
--- a/xml/System.Windows.Controls/ValidationRule.xml
+++ b/xml/System.Windows.Controls/ValidationRule.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you use the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model, you can associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your binding object. To create custom rules, make a subclass of this class and implement the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. Optionally, use the built-in <xref:System.Windows.Controls.ExceptionValidationRule>, which catches exceptions that are thrown during source updates, or the <xref:System.Windows.Controls.DataErrorValidationRule>, which checks for errors raised by the <xref:System.ComponentModel.IDataErrorInfo> implementation of the source object.  
+ When you use the WPF data binding model, you can associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your binding object. To create custom rules, make a subclass of this class and implement the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method. Optionally, use the built-in <xref:System.Windows.Controls.ExceptionValidationRule>, which catches exceptions that are thrown during source updates, or the <xref:System.Windows.Controls.DataErrorValidationRule>, which checks for errors raised by the <xref:System.ComponentModel.IDataErrorInfo> implementation of the source object.  
   
  The binding engine checks each <xref:System.Windows.Controls.ValidationRule> that is associated with a binding every time it transfers an input value, which is the binding target property value, to the binding source property.  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 7bb51d82435..d825f706000 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -27,13 +27,13 @@
   
  ![Basic data binding diagram](~/add/media/databindingmostbasic.png "Basic data binding diagram")  
   
- The figure demonstrates the following fundamental [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding concepts.  
+ The figure demonstrates the following fundamental WPF data binding concepts.  
   
 -   Each binding typically has these four components: a binding target object, a target property, a binding source, and a <xref:System.Windows.Data.Binding.Path%2A> to the value in the binding source to use. For example, if you want to bind the content of a <xref:System.Windows.Controls.TextBox> to the Name property of an Employee object, your target object is the <xref:System.Windows.Controls.TextBox>, the target property is the <xref:System.Windows.Controls.TextBox.Text%2A> property, the value to use is Name, and the source object is the Employee object.  
   
 -   The target property must be a dependency property. This also means that you cannot bind a field. Most properties of <xref:System.Windows.UIElement> objects are dependency properties and most dependency properties, except read-only ones, support data binding by default. (Only <xref:System.Windows.DependencyObject> types can define dependency properties and all <xref:System.Windows.UIElement> objects derive from <xref:System.Windows.DependencyObject>.)  
   
--   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding supports data in the form of CLR objects and [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data.  
+-   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. WPF data binding supports data in the form of CLR objects and [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data.  
   
  Use the <xref:System.Windows.Data.Binding.Mode%2A> property to specify the direction of the data flow. To detect source changes in one-way or two-way bindings, the source must implement a suitable property change notification mechanism such as <xref:System.ComponentModel.INotifyPropertyChanged>. For an example, see [How to: Implement Property Change Notification](/dotnet/framework/wpf/data/how-to-implement-property-change-notification). The <xref:System.Windows.Data.Binding.UpdateSourceTrigger%2A> property specifies the timing of source updates. For more information, see "Basic Data Binding Concepts" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -1513,7 +1513,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by deriving from the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method, or you can use the built-in <xref:System.Windows.Controls.ExceptionValidationRule>, which invalidates a value if there are exceptions during source updates.  
+ The WPF data binding model enables you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> or <xref:System.Windows.Data.MultiBinding> object. You can create custom rules by deriving from the <xref:System.Windows.Controls.ValidationRule> class and implementing the <xref:System.Windows.Controls.ValidationRule.Validate%2A> method, or you can use the built-in <xref:System.Windows.Controls.ExceptionValidationRule>, which invalidates a value if there are exceptions during source updates.  
   
  The binding engine checks each <xref:System.Windows.Controls.ValidationRule> associated with a binding each time an input value (the binding target property value) is transferred to the binding source property. For a detailed discussion of the validation process, see the Data Validation section in the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Data/BindingBase.xml b/xml/System.Windows.Data/BindingBase.xml
index 5bc5ee2d684..2ddb507148d 100644
--- a/xml/System.Windows.Data/BindingBase.xml
+++ b/xml/System.Windows.Data/BindingBase.xml
@@ -237,7 +237,7 @@
 ## Remarks  
  This implementation provides the base syntax support for binding through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] for all provided practical derived classes (<xref:System.Windows.Data.Binding>, <xref:System.Windows.Data.PriorityBinding>, and <xref:System.Windows.Data.MultiBinding>).  
   
- The <xref:System.Windows.Data.BindingBase> class implementation of this method is expected to return an expression object that is the result of a binding. Binding a property works by targeting a given <xref:System.Windows.DependencyProperty> on a given <xref:System.Windows.DependencyObject>. These two pieces of information are transmitted by querying for an <xref:System.Windows.Markup.IProvideValueTarget> implementation on the `serviceProvider`, which the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] reader makes available during parsing of a binding. This base class implementation is responsible for checking for a valid <xref:System.Windows.DependencyProperty> and <xref:System.Windows.DependencyObject>. If these are found, the actual implementation of returning a binding expression falls to various derived classes, as implemented by having the base class call an internal abstract method. Otherwise, the extension returns the binding object itself. Returning the binding itself results in a type mismatch error, but this should not occur under normal circumstances.  
+ The <xref:System.Windows.Data.BindingBase> class implementation of this method is expected to return an expression object that is the result of a binding. Binding a property works by targeting a given <xref:System.Windows.DependencyProperty> on a given <xref:System.Windows.DependencyObject>. These two pieces of information are transmitted by querying for an <xref:System.Windows.Markup.IProvideValueTarget> implementation on the `serviceProvider`, which the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] reader makes available during parsing of a binding. This base class implementation is responsible for checking for a valid <xref:System.Windows.DependencyProperty> and <xref:System.Windows.DependencyObject>. If these are found, the actual implementation of returning a binding expression falls to various derived classes, as implemented by having the base class call an internal abstract method. Otherwise, the extension returns the binding object itself. Returning the binding itself results in a type mismatch error, but this should not occur under normal circumstances.  
   
 > [!IMPORTANT]
 >  Because the syntax for binding through [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] as implemented in this method relies on implementing an internal override, and because <xref:System.Windows.Data.BindingBase.ProvideValue%2A?displayProperty=nameWithType> itself is sealed, a custom binding class that derives from <xref:System.Windows.Data.BindingBase> will not function correctly as a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] markup extension.  
diff --git a/xml/System.Windows.Data/CollectionView.xml b/xml/System.Windows.Data/CollectionView.xml
index 458eea253cc..4f243cc369d 100644
--- a/xml/System.Windows.Data/CollectionView.xml
+++ b/xml/System.Windows.Data/CollectionView.xml
@@ -44,7 +44,7 @@
   
  Because a view does not change the underlying source collection, a source collection can have multiple views associated with it. By using views, you can display the same data in different ways. For example, you can use two views on a collection of `Task` objects to show tasks sorted by priority on one part of the page and grouped by area on another part of the page.  
   
- In [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications, all collections have an associated default collection view. Rather than working with the collection directly, the binding engine always accesses the collection through the associated view. To get the default view, use the <xref:System.Windows.Data.CollectionViewSource.GetDefaultView%2A?displayProperty=nameWithType> method. An internal class based on <xref:System.Windows.Data.CollectionView> is the default view for collections that implement only <xref:System.Collections.IEnumerable>. <xref:System.Windows.Data.ListCollectionView> is the default view for collections that implement <xref:System.Collections.IList>. <xref:System.Windows.Data.BindingListCollectionView> is the default view for collections that implement <xref:System.ComponentModel.IBindingListView> or <xref:System.ComponentModel.IBindingList>.  
+ In WPF applications, all collections have an associated default collection view. Rather than working with the collection directly, the binding engine always accesses the collection through the associated view. To get the default view, use the <xref:System.Windows.Data.CollectionViewSource.GetDefaultView%2A?displayProperty=nameWithType> method. An internal class based on <xref:System.Windows.Data.CollectionView> is the default view for collections that implement only <xref:System.Collections.IEnumerable>. <xref:System.Windows.Data.ListCollectionView> is the default view for collections that implement <xref:System.Collections.IList>. <xref:System.Windows.Data.BindingListCollectionView> is the default view for collections that implement <xref:System.ComponentModel.IBindingListView> or <xref:System.ComponentModel.IBindingList>.  
   
  Alternatively, you can create a view of your collection in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by using the <xref:System.Windows.Data.CollectionViewSource> class and then bind your control to that view. The <xref:System.Windows.Data.CollectionViewSource> class is the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representation of the <xref:System.Windows.Data.CollectionView> class. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
   
diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index 8a9b58c0c0b..9b677633b21 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -104,7 +104,7 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the WPF infrastructure and is not intended to be used directly from your code.</summary>
         <value>The base URI.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Documents/Typography.xml b/xml/System.Windows.Documents/Typography.xml
index 2ab830a819a..3dde58ffa1c 100644
--- a/xml/System.Windows.Documents/Typography.xml
+++ b/xml/System.Windows.Documents/Typography.xml
@@ -4274,7 +4274,7 @@ Example of standard set of ligatures
   
  [!code-xaml[OpenTypeFontSamples#4](~/samples/snippets/csharp/VS_Snippets_Wpf/OpenTypeFontSamples/CS/PageOne.xaml#4)]   
   
- By default, OpenTypes fonts in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] enable standard ligatures. For example, if you use the Palatino Linotype font, the standard ligatures "fi", "ff", and "fl" appear as a combined character glyph. Notice that the pair of characters for each standard ligature touch each other.  
+ By default, OpenTypes fonts in WPF enable standard ligatures. For example, if you use the Palatino Linotype font, the standard ligatures "fi", "ff", and "fl" appear as a combined character glyph. Notice that the pair of characters for each standard ligature touch each other.  
   
  ![Text using OpenType standard ligatures](~/add/media/opentypefont06.gif "Text using OpenType standard ligatures")  
 Example of standard ligatures enabled by default  
diff --git a/xml/System.Windows.Forms.Integration/ElementHost.xml b/xml/System.Windows.Forms.Integration/ElementHost.xml
index 223a9914310..8ff3bf1b929 100644
--- a/xml/System.Windows.Forms.Integration/ElementHost.xml
+++ b/xml/System.Windows.Forms.Integration/ElementHost.xml
@@ -43,21 +43,21 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Windows.Forms.Integration.ElementHost> control to place a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.UIElement> on your [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control or form.  
+ Use the <xref:System.Windows.Forms.Integration.ElementHost> control to place a WPF <xref:System.Windows.UIElement> on your [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control or form.  
   
- To host a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control in a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element, use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> element.  
+ To host a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control in a WPF element, use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> element.  
   
 > [!NOTE]
->  WindowsFormsIntegration.dll is installed with the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] assemblies. The default location for the assembly is %programfiles%\Reference Assemblies\Microsoft\Framework\v3.0\WindowsFormsIntegration.dll.  
+>  WindowsFormsIntegration.dll is installed with the WPF assemblies. The default location for the assembly is %programfiles%\Reference Assemblies\Microsoft\Framework\v3.0\WindowsFormsIntegration.dll.  
   
- To host a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element in a Windows Form, you must assign the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element to the <xref:System.Windows.Forms.Integration.ElementHost.Child%2A> property.  
+ To host a WPF element in a Windows Form, you must assign the WPF element to the <xref:System.Windows.Forms.Integration.ElementHost.Child%2A> property.  
   
- Use the <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A> property to assign custom mappings between an <xref:System.Windows.Forms.Integration.ElementHost> control and its hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
+ Use the <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A> property to assign custom mappings between an <xref:System.Windows.Forms.Integration.ElementHost> control and its hosted WPF element. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
   
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost> control to host a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element. For more information, see [Walkthrough: Hosting a 3-D WPF Composite Control in Windows Forms](/dotnet/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms).  
+ The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost> control to host a WPF element. For more information, see [Walkthrough: Hosting a 3-D WPF Composite Control in Windows Forms](/dotnet/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms).  
   
  [!code-csharp[HostingWpfUserControlInWf#11](~/samples/snippets/csharp/VS_Snippets_Wpf/HostingWpfUserControlInWf/CSharp/WpfUserControlHost/Form1.cs#11)]
  [!code-vb[HostingWpfUserControlInWf#11](~/samples/snippets/visualbasic/VS_Snippets_Wpf/HostingWpfUserControlInWf/VisualBasic/WpfUserControlHost/Form1.vb#11)]  
@@ -275,7 +275,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost.Child%2A> property to assign a hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element. For more information, see [Walkthrough: Hosting a 3-D WPF Composite Control in Windows Forms](/dotnet/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms).  
+ The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost.Child%2A> property to assign a hosted WPF element. For more information, see [Walkthrough: Hosting a 3-D WPF Composite Control in Windows Forms](/dotnet/framework/wpf/advanced/walkthrough-hosting-a-3-d-wpf-composite-control-in-windows-forms).  
   
  [!code-csharp[HostingWpfUserControlInWf#11](~/samples/snippets/csharp/VS_Snippets_Wpf/HostingWpfUserControlInWf/CSharp/WpfUserControlHost/Form1.cs#11)]
  [!code-vb[HostingWpfUserControlInWf#11](~/samples/snippets/visualbasic/VS_Snippets_Wpf/HostingWpfUserControlInWf/VisualBasic/WpfUserControlHost/Form1.vb#11)]  
@@ -810,7 +810,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Call the <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method to forward all keyboard messages when a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window is opened modelessly. The <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method installs a message filter in the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application. The filter forwards all keyboard messages when the modeless window is active.  
+ Call the <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method to forward all keyboard messages when a WPF window is opened modelessly. The <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method installs a message filter in the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application. The filter forwards all keyboard messages when the modeless window is active.  
   
  ]]></format>
         </remarks>
@@ -983,7 +983,7 @@
         <Parameter Name="proposedSize" Type="System.Drawing.Size" />
       </Parameters>
       <Docs>
-        <param name="proposedSize">The custom-sized area for a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element.</param>
+        <param name="proposedSize">The custom-sized area for a WPF element.</param>
         <summary>Overrides the base class implementation <see cref="M:System.Windows.Forms.Control.GetPreferredSize(System.Drawing.Size)" /> to provide correct layout behavior for the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] elements.</summary>
         <returns>The <see cref="T:System.Drawing.Size" /> computed by the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control, given the constraints specified by <paramref name="proposedSize" />.</returns>
         <remarks>To be added.</remarks>
@@ -1108,7 +1108,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The host container is the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.FrameworkElement>, which is the parent container for the hosted element. The host container is always at the root of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element hierarchy. To access the parent of the hosted element, access <xref:System.Windows.Forms.Integration.ElementHost.HostContainer%2A> directly.  
+ The host container is the WPF <xref:System.Windows.FrameworkElement>, which is the parent container for the hosted element. The host container is always at the root of the WPF element hierarchy. To access the parent of the hosted element, access <xref:System.Windows.Forms.Integration.ElementHost.HostContainer%2A> directly.  
   
  ]]></format>
         </remarks>
@@ -2328,7 +2328,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a key message is not handled by the hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
+ If a key message is not handled by the hosted WPF element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
   
  ]]></format>
         </remarks>
@@ -2364,7 +2364,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a key message is not handled by the hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
+ If a key message is not handled by the hosted WPF element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
   
  ]]></format>
         </remarks>
@@ -2400,17 +2400,17 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the property map, which determines how setting properties on the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control affects the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
-        <value>A <see cref="T:System.Windows.Forms.Integration.PropertyMap" /> that maps <see cref="T:System.Windows.Forms.Integration.ElementHost" /> to properties on the hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element.</value>
+        <value>A <see cref="T:System.Windows.Forms.Integration.PropertyMap" /> that maps <see cref="T:System.Windows.Forms.Integration.ElementHost" /> to properties on the hosted WPF element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] technologies have two similar but different property models. *Property mapping* supports interoperation between the two architectures. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
+ The [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF technologies have two similar but different property models. *Property mapping* supports interoperation between the two architectures. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
   
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A> property to translate the <xref:System.Windows.FrameworkElement.Margin%2A> property for a hosted [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element. For more information, see [Walkthrough: Mapping Properties Using the ElementHost Control](/dotnet/framework/wpf/advanced/walkthrough-mapping-properties-using-the-elementhost-control).  
+ The following code example demonstrates how to use the <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A> property to translate the <xref:System.Windows.FrameworkElement.Margin%2A> property for a hosted WPF element. For more information, see [Walkthrough: Mapping Properties Using the ElementHost Control](/dotnet/framework/wpf/advanced/walkthrough-mapping-properties-using-the-elementhost-control).  
   
  [!code-csharp[PropertyMappingWithElementHost#12](~/samples/snippets/csharp/VS_Snippets_Wpf/PropertyMappingWithElementHost/CSharp/PropertyMappingWithElementHost/Form1.cs#12)]
  [!code-vb[PropertyMappingWithElementHost#12](~/samples/snippets/visualbasic/VS_Snippets_Wpf/PropertyMappingWithElementHost/VisualBasic/PropertyMappingWithElementHost/Form1.vb#12)]  
diff --git a/xml/System.Windows.Forms.Integration/PropertyTranslator.xml b/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
index ee3273c5423..2839d749d45 100644
--- a/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
+++ b/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Forms.Integration.PropertyTranslator> delegate is used by the <xref:System.Windows.Forms.Integration.PropertyMap> class to implement property mapping between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
+ The <xref:System.Windows.Forms.Integration.PropertyTranslator> delegate is used by the <xref:System.Windows.Forms.Integration.PropertyMap> class to implement property mapping between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/AccessKeyPressedEventHandler.xml b/xml/System.Windows.Input/AccessKeyPressedEventHandler.xml
index 0e1f7a27f36..54c50e71fbf 100644
--- a/xml/System.Windows.Input/AccessKeyPressedEventHandler.xml
+++ b/xml/System.Windows.Input/AccessKeyPressedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Access keys in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] are handled by a manager class that acts somewhat like a service for access keys, and forwards access key input to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input system. Rather than handling access key pressed events specifically by attaching a handler for the <xref:System.Windows.Input.AccessKeyManager.AccessKeyPressed> attached event on a specific object, it is generally a better practice to associate the access key with a particular command through a command binding, and then handle the routed commands through the corresponding routed events. This technique provides a unified event system for user input regardless of what input mode initiated the input. For more information, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview).  
+ Access keys in WPF are handled by a manager class that acts somewhat like a service for access keys, and forwards access key input to the WPF input system. Rather than handling access key pressed events specifically by attaching a handler for the <xref:System.Windows.Input.AccessKeyManager.AccessKeyPressed> attached event on a specific object, it is generally a better practice to associate the access key with a particular command through a command binding, and then handle the routed commands through the corresponding routed events. This technique provides a unified event system for user input regardless of what input mode initiated the input. For more information, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/ICommandSource.xml b/xml/System.Windows.Input/ICommandSource.xml
index 9e90938e17b..ad647e11956 100644
--- a/xml/System.Windows.Input/ICommandSource.xml
+++ b/xml/System.Windows.Input/ICommandSource.xml
@@ -24,7 +24,7 @@
   
  Normally, a command source will listen to the <xref:System.Windows.Input.ICommand.CanExecuteChanged> event on the command.  This informs the command source when conditions change on the command target, such as loss of keyboard focus.  The command source can then query the command using the <xref:System.Windows.Input.ICommand.CanExecute%2A> method.  
   
- Some of the classes in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] that implement <xref:System.Windows.Input.ICommandSource> are: <xref:System.Windows.Controls.Primitives.ButtonBase>, <xref:System.Windows.Controls.MenuItem>, and <xref:System.Windows.Documents.Hyperlink>.  
+ Some of the classes in WPF that implement <xref:System.Windows.Input.ICommandSource> are: <xref:System.Windows.Controls.Primitives.ButtonBase>, <xref:System.Windows.Controls.MenuItem>, and <xref:System.Windows.Documents.Hyperlink>.  
   
  In the Windows Presentation Foundation commanding system, the <xref:System.Windows.Input.InputBinding.CommandTarget%2A> property on a <xref:System.Windows.Input.ICommandSource> is only applicable when the <xref:System.Windows.Input.ICommand> is a <xref:System.Windows.Input.RoutedCommand>.  If the <xref:System.Windows.Input.InputBinding.CommandTarget%2A> is set on a <xref:System.Windows.Input.ICommandSource> and the corresponding command is not a <xref:System.Windows.Input.RoutedCommand>, the command target is ignored.  
   
diff --git a/xml/System.Windows.Input/InputBinding.xml b/xml/System.Windows.Input/InputBinding.xml
index f159bf7f54d..2ad2ca713a4 100644
--- a/xml/System.Windows.Input/InputBinding.xml
+++ b/xml/System.Windows.Input/InputBinding.xml
@@ -37,7 +37,7 @@
   
  An <xref:System.Windows.Input.InputBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> with the <xref:System.Windows.Input.CommandManager>.  
   
- The <xref:System.Windows.Input.InputBinding> class itself does not support XAML usage because it does not expose a public parameterless constructor (there is a parameterless constructor, but it is protected). However, derived classes can expose a public constructor and therefore can set properties on the derived class that are inherited from <xref:System.Windows.Input.InputBinding> with a XAML usage. Two existing <xref:System.Windows.Input.InputBinding>-derived classes that can be instantiated in XAML and can set properties in XAML are <xref:System.Windows.Input.KeyBinding> and <xref:System.Windows.Input.MouseBinding>. The typical property in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] programming that is set in XAML and takes one or more <xref:System.Windows.Input.InputBinding> objects as values is the <xref:System.Windows.UIElement.InputBindings%2A?displayProperty=nameWithType> property.  
+ The <xref:System.Windows.Input.InputBinding> class itself does not support XAML usage because it does not expose a public parameterless constructor (there is a parameterless constructor, but it is protected). However, derived classes can expose a public constructor and therefore can set properties on the derived class that are inherited from <xref:System.Windows.Input.InputBinding> with a XAML usage. Two existing <xref:System.Windows.Input.InputBinding>-derived classes that can be instantiated in XAML and can set properties in XAML are <xref:System.Windows.Input.KeyBinding> and <xref:System.Windows.Input.MouseBinding>. The typical property in WPF programming that is set in XAML and takes one or more <xref:System.Windows.Input.InputBinding> objects as values is the <xref:System.Windows.UIElement.InputBindings%2A?displayProperty=nameWithType> property.  
   
 <a name="xamlObjectElementUsage_InputBinding"></a>   
 ## XAML Object Element Usage  
@@ -118,7 +118,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Input.InputBinding> is not technically an abstract class, but the parameterless constructor is deliberately protected access. This has the effect of making <xref:System.Windows.Input.InputBinding> an "abstract" class for XAML. There are existing properties in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] that have XAML usages that expect objects of type <xref:System.Windows.Input.InputBinding>, but you cannot specify an <xref:System.Windows.Input.InputBinding> instance in XAML. Instead, you can specify one of the device-specific <xref:System.Windows.Input.InputBinding> derived classes as values, for instance <xref:System.Windows.Input.KeyBinding> or <xref:System.Windows.Input.MouseBinding>.  
+ <xref:System.Windows.Input.InputBinding> is not technically an abstract class, but the parameterless constructor is deliberately protected access. This has the effect of making <xref:System.Windows.Input.InputBinding> an "abstract" class for XAML. There are existing properties in WPF that have XAML usages that expect objects of type <xref:System.Windows.Input.InputBinding>, but you cannot specify an <xref:System.Windows.Input.InputBinding> instance in XAML. Instead, you can specify one of the device-specific <xref:System.Windows.Input.InputBinding> derived classes as values, for instance <xref:System.Windows.Input.KeyBinding> or <xref:System.Windows.Input.MouseBinding>.  
   
  ]]></format>
         </remarks>
@@ -370,7 +370,7 @@
  A string that is processed by a particular command. Strings are the common type used for command parameters because they can be easily set in XAML. For the expected string format and its purpose, see the documentation for the particular command that the input binding is associated with. Many commands do not expect parameters.  
   
  `commandParameterObject`  
- An object that is processed by a particular command. All existing [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] commands use strings. Therefore, this property element syntax is only relevant for custom command scenarios. In order to support this syntax, the `commandParameterObject` object must also support object element syntax (must have a public parameterless constructor).  
+ An object that is processed by a particular command. All existing WPF commands use strings. Therefore, this property element syntax is only relevant for custom command scenarios. In order to support this syntax, the `commandParameterObject` object must also support object element syntax (must have a public parameterless constructor).  
   
  ]]></format>
         </remarks>
@@ -541,7 +541,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The input gesture is the action that invokes the command. Examples of input gestures in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] are <xref:System.Windows.Input.KeyGesture> and <xref:System.Windows.Input.MouseGesture>. A <xref:System.Windows.Input.KeyGesture> is a combination of a <xref:System.Windows.Input.Key> and a set of <xref:System.Windows.Input.ModifierKeys>. A <xref:System.Windows.Input.MouseGesture> is a combination of a <xref:System.Windows.Input.MouseAction> and a set of <xref:System.Windows.Input.ModifierKeys>.  
+ The input gesture is the action that invokes the command. Examples of input gestures in WPF are <xref:System.Windows.Input.KeyGesture> and <xref:System.Windows.Input.MouseGesture>. A <xref:System.Windows.Input.KeyGesture> is a combination of a <xref:System.Windows.Input.Key> and a set of <xref:System.Windows.Input.ModifierKeys>. A <xref:System.Windows.Input.MouseGesture> is a combination of a <xref:System.Windows.Input.MouseAction> and a set of <xref:System.Windows.Input.ModifierKeys>.  
   
  The <xref:System.Windows.Input.InputBinding> class itself does not support XAML usage, because it does not expose a public parameterless constructor (there is a parameterless constructor, but it is protected). However, derived classes can expose a public constructor and thus can set properties that are inherited from <xref:System.Windows.Input.InputBinding> with a XAML usage. Two existing <xref:System.Windows.Input.InputBinding> derived classes that can be instantiated in XAML and can set properties in XAML are <xref:System.Windows.Input.KeyBinding> and <xref:System.Windows.Input.MouseBinding>.  
   
diff --git a/xml/System.Windows.Input/InputEventHandler.xml b/xml/System.Windows.Input/InputEventHandler.xml
index 7589698bc66..f9146fd805b 100644
--- a/xml/System.Windows.Input/InputEventHandler.xml
+++ b/xml/System.Windows.Input/InputEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- No existing event in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses the <xref:System.Windows.Input.KeyboardEventHandler> delegate. The event data type for this class, <xref:System.Windows.Input.InputEventArgs>, is the base class for various more specific event data classes for input. <xref:System.Windows.Input.InputEventArgs> defines the event data properties of input events that are common regardless of the device that initiated the event.  
+ No existing event in WPF uses the <xref:System.Windows.Input.KeyboardEventHandler> delegate. The event data type for this class, <xref:System.Windows.Input.InputEventArgs>, is the base class for various more specific event data classes for input. <xref:System.Windows.Input.InputEventArgs> defines the event data properties of input events that are common regardless of the device that initiated the event.  
   
  An example of a delegate that uses <xref:System.Windows.Input.InputEventArgs> derived event data and that corresponds to an existing input event is <xref:System.Windows.Input.KeyboardFocusChangedEventHandler>.  
   
diff --git a/xml/System.Windows.Input/InputManager.xml b/xml/System.Windows.Input/InputManager.xml
index 5b2714ca054..6c332e929f2 100644
--- a/xml/System.Windows.Input/InputManager.xml
+++ b/xml/System.Windows.Input/InputManager.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.InputManager> class is responsible for coordinating all of the input systems in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ The <xref:System.Windows.Input.InputManager> class is responsible for coordinating all of the input systems in WPF.  
   
  A filter is any code that listens to <xref:System.Windows.Input.InputManager.PreProcessInput> or <xref:System.Windows.Input.InputManager.PostProcessInput>.  Filters can modify the input staging area.  
   
@@ -29,13 +29,13 @@
   
  The <xref:System.Windows.Input.InputManager> controls the input staging area.  The input staging area processes input into [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] events.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
@@ -343,13 +343,13 @@
   
  The handlers attached to <xref:System.Windows.Input.InputManager.PostNotifyInput> are invoked in reverse order so that handlers added by the users are invoked before handlers in the system.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
@@ -405,13 +405,13 @@
   
  The handlers attached to <xref:System.Windows.Input.InputManager.PostProcessInput> are invoked in reverse order so that handlers added by the users are invoked before handlers in the system.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
@@ -467,13 +467,13 @@
   
  The handlers attached to <xref:System.Windows.Input.InputManager.PreNotifyInput> are invoked in reverse order so that handlers added by the users are invoked before handlers in the system.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
@@ -531,13 +531,13 @@
   
  Calling <xref:System.Windows.Input.PreProcessInputEventArgs.Cancel%2A> on the <xref:System.Windows.Input.PreProcessInputEventArgs> passed to the <xref:System.Windows.Input.PreProcessInputEventHandler> will cancel the processing of the input.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
@@ -649,13 +649,13 @@
   
  The specified input is processed by all the filters and monitors and is finally dispatched to the appropriate element as an input event.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/KeyBinding.xml b/xml/System.Windows.Input/KeyBinding.xml
index 3196a9b352d..8ed8613b57b 100644
--- a/xml/System.Windows.Input/KeyBinding.xml
+++ b/xml/System.Windows.Input/KeyBinding.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Input.KeyBinding> associates a <xref:System.Windows.Input.KeyGesture> with a <xref:System.Windows.Input.ICommand>, such as a <xref:System.Windows.Input.RoutedCommand>. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] commanding system .  In general, when the <xref:System.Windows.Input.KeyGesture> is executed the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
+ A <xref:System.Windows.Input.KeyBinding> associates a <xref:System.Windows.Input.KeyGesture> with a <xref:System.Windows.Input.ICommand>, such as a <xref:System.Windows.Input.RoutedCommand>. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the WPF commanding system .  In general, when the <xref:System.Windows.Input.KeyGesture> is executed the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
   
  With the exception of the function keys and the numeric keypad keys, a valid <xref:System.Windows.Input.KeyGesture> must contain exactly one <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  Function keys and numeric keypad keys do not require a modifier key in order to be a valid <xref:System.Windows.Input.KeyGesture>. It is possible to specify an invalid <xref:System.Windows.Input.KeyGesture> and a <xref:System.Windows.Input.KeyBinding> with an invalid associated gesture, either through [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] or code. For instance, there is no validation that prevents creating and binding a <xref:System.Windows.Input.KeyGesture> that contains only a nonfunction key, or only modifiers but no key. Such a <xref:System.Windows.Input.KeyBinding> will never attempt to invoke its associated command.  
   
diff --git a/xml/System.Windows.Input/KeyEventArgs.xml b/xml/System.Windows.Input/KeyEventArgs.xml
index 1e973328443..c08956d7059 100644
--- a/xml/System.Windows.Input/KeyEventArgs.xml
+++ b/xml/System.Windows.Input/KeyEventArgs.xml
@@ -31,7 +31,7 @@
   
 -   <xref:System.Windows.Input.Keyboard.PreviewKeyDown?displayProperty=nameWithType>  
   
- This event data class is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This event data class is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.KeyUp?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/KeyEventHandler.xml b/xml/System.Windows.Input/KeyEventHandler.xml
index 384801f5a7a..163b9e1eb99 100644
--- a/xml/System.Windows.Input/KeyEventHandler.xml
+++ b/xml/System.Windows.Input/KeyEventHandler.xml
@@ -39,7 +39,7 @@
   
 -   <xref:System.Windows.Input.Keyboard.PreviewKeyDown?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.KeyUp?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/Keyboard.xml b/xml/System.Windows.Input/Keyboard.xml
index 8296c1e18bd..0e483cd5770 100644
--- a/xml/System.Windows.Input/Keyboard.xml
+++ b/xml/System.Windows.Input/Keyboard.xml
@@ -444,7 +444,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the behavior of [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] when restoring focus.</summary>
-        <value>An enumeration value that specifies the behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
+        <value>An enumeration value that specifies the behavior of WPF when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -599,7 +599,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Keyboard focus refers to the object that is receiving keyboard input. The element with keyboard focus has <xref:System.Windows.IInputElement.IsKeyboardFocused%2A> set to `true`.  There can be only one element with keyboard focus on the entire desktop.  Logical focus refers to the object within a focus scope that has focus.  For more information on focus, keyboard focus, and logical focus, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview) and [Focus Overview](/dotnet/framework/wpf/advanced/focus-overview).  
   
@@ -815,7 +815,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyboardInputProviderAcquireFocus"></a>   
 ## Routed Event Information  
@@ -879,7 +879,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyDown"></a>   
 ## Routed Event Information  
@@ -955,7 +955,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyUp"></a>   
 ## Routed Event Information  
@@ -1021,7 +1021,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Keyboard focus refers to the object that is receiving keyboard input. The element with keyboard focus has <xref:System.Windows.IInputElement.IsKeyboardFocused%2A> set to `true`.  There can be only one element with keyboard focus on the entire desktop.  Logical focus refers to the object within a focus scope that has focus.  For more information on focus, keyboard focus, and logical focus, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview) and [Focus Overview](/dotnet/framework/wpf/advanced/focus-overview).  
   
@@ -1141,7 +1141,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  If the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus> event or the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus> event is handled, keyboard focus does not change.  
   
@@ -1209,7 +1209,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyboardInputProviderAcquireFocus"></a>   
 ## Routed Event Information  
@@ -1273,7 +1273,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyDown"></a>   
 ## Routed Event Information  
@@ -1338,7 +1338,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyUp"></a>   
 ## Routed Event Information  
@@ -1403,7 +1403,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  If the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus> event or the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus> event is handled, keyboard focus does not change.  
   
@@ -1483,7 +1483,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  
+ This property supports the WPF infrastructure and is not intended to be used directly from your code.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/KeyboardDevice.xml b/xml/System.Windows.Input/KeyboardDevice.xml
index f4d1ddd5895..4ab996593d2 100644
--- a/xml/System.Windows.Input/KeyboardDevice.xml
+++ b/xml/System.Windows.Input/KeyboardDevice.xml
@@ -159,7 +159,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the behavior of [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] when restoring focus.</summary>
-        <value>An enumeration value that specifies the behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
+        <value>An enumeration value that specifies the behavior of WPF when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Input/KeyboardEventArgs.xml b/xml/System.Windows.Input/KeyboardEventArgs.xml
index a4a52b3da99..3803caaa577 100644
--- a/xml/System.Windows.Input/KeyboardEventArgs.xml
+++ b/xml/System.Windows.Input/KeyboardEventArgs.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- No existing keyboard event in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses the <xref:System.Windows.Input.KeyboardEventArgs>. <xref:System.Windows.Input.KeyboardEventArgs> serves as the base class for the more specific <xref:System.Windows.Input.KeyEventArgs> and <xref:System.Windows.Input.KeyboardFocusChangedEventArgs> event data classes, which are used by existing [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] events such as <xref:System.Windows.UIElement.KeyDown?displayProperty=nameWithType> and <xref:System.Windows.UIElement.LostKeyboardFocus?displayProperty=nameWithType>.  
+ No existing keyboard event in WPF uses the <xref:System.Windows.Input.KeyboardEventArgs>. <xref:System.Windows.Input.KeyboardEventArgs> serves as the base class for the more specific <xref:System.Windows.Input.KeyEventArgs> and <xref:System.Windows.Input.KeyboardFocusChangedEventArgs> event data classes, which are used by existing WPF events such as <xref:System.Windows.UIElement.KeyDown?displayProperty=nameWithType> and <xref:System.Windows.UIElement.LostKeyboardFocus?displayProperty=nameWithType>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/KeyboardEventHandler.xml b/xml/System.Windows.Input/KeyboardEventHandler.xml
index c59dbab743b..0f34a3dd992 100644
--- a/xml/System.Windows.Input/KeyboardEventHandler.xml
+++ b/xml/System.Windows.Input/KeyboardEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- No existing keyboard event in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] uses the <xref:System.Windows.Input.KeyboardEventHandler> delegate. <xref:System.Windows.Input.KeyboardEventHandler> uses the <xref:System.Windows.Input.KeyboardEventArgs> base class as its event data class. <xref:System.Windows.Input.KeyboardEventArgs> serves as the base class for the more specific <xref:System.Windows.Input.KeyEventArgs> and <xref:System.Windows.Input.KeyboardFocusChangedEventArgs> event data classes. These event data classes are used by the <xref:System.Windows.Input.KeyEventHandler> and <xref:System.Windows.Input.KeyboardFocusChangedEventHandler> delegates, and those delegates are used by existing [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] events such as <xref:System.Windows.UIElement.KeyDown?displayProperty=nameWithType> and <xref:System.Windows.UIElement.LostKeyboardFocus?displayProperty=nameWithType>.  
+ No existing keyboard event in WPF uses the <xref:System.Windows.Input.KeyboardEventHandler> delegate. <xref:System.Windows.Input.KeyboardEventHandler> uses the <xref:System.Windows.Input.KeyboardEventArgs> base class as its event data class. <xref:System.Windows.Input.KeyboardEventArgs> serves as the base class for the more specific <xref:System.Windows.Input.KeyEventArgs> and <xref:System.Windows.Input.KeyboardFocusChangedEventArgs> event data classes. These event data classes are used by the <xref:System.Windows.Input.KeyEventHandler> and <xref:System.Windows.Input.KeyboardFocusChangedEventHandler> delegates, and those delegates are used by existing WPF events such as <xref:System.Windows.UIElement.KeyDown?displayProperty=nameWithType> and <xref:System.Windows.UIElement.LostKeyboardFocus?displayProperty=nameWithType>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/KeyboardFocusChangedEventArgs.xml b/xml/System.Windows.Input/KeyboardFocusChangedEventArgs.xml
index 50644dd62fa..bd6875adb5a 100644
--- a/xml/System.Windows.Input/KeyboardFocusChangedEventArgs.xml
+++ b/xml/System.Windows.Input/KeyboardFocusChangedEventArgs.xml
@@ -27,7 +27,7 @@
   
 -   <xref:System.Windows.Input.Keyboard.LostKeyboardFocus?displayProperty=nameWithType>  
   
- This event data class is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This event data class is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.GotKeyboardFocus?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/KeyboardFocusChangedEventHandler.xml b/xml/System.Windows.Input/KeyboardFocusChangedEventHandler.xml
index e70a18e156e..8a7f1ef2c30 100644
--- a/xml/System.Windows.Input/KeyboardFocusChangedEventHandler.xml
+++ b/xml/System.Windows.Input/KeyboardFocusChangedEventHandler.xml
@@ -35,7 +35,7 @@
   
 -   <xref:System.Windows.Input.Keyboard.LostKeyboardFocus?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.GotKeyboardFocus?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/Manipulation.xml b/xml/System.Windows.Input/Manipulation.xml
index cff12905245..15a9aab95fe 100644
--- a/xml/System.Windows.Input/Manipulation.xml
+++ b/xml/System.Windows.Input/Manipulation.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A manipulation occurs when touch is interpreted as a physical action that is applied to an object. In [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], manipulation events interpret input as a translation, expansion, or rotation manipulation. You usually interact with manipulations through the manipulation events that are defined on the <xref:System.Windows.UIElement>. However, the <xref:System.Windows.Input.Manipulation> class defines static methods that you can use to interact with manipulations.  
+ A manipulation occurs when touch is interpreted as a physical action that is applied to an object. In WPF, manipulation events interpret input as a translation, expansion, or rotation manipulation. You usually interact with manipulations through the manipulation events that are defined on the <xref:System.Windows.UIElement>. However, the <xref:System.Windows.Input.Manipulation> class defines static methods that you can use to interact with manipulations.  
   
  For more information about manipulations, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview). For an example of an application that responds to manipulations, see [Walkthrough: Creating Your First Touch Application](/dotnet/framework/wpf/advanced/walkthrough-creating-your-first-touch-application).  
   
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 01672659041..253911b1519 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -751,7 +751,7 @@
 ## Remarks  
  When an element captures the mouse, it receives mouse input whether or not the cursor is within its borders.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Because of the bubbling routing, the actual element that has capture might be a child element, not necessarily the element where the event handler is actually attached. Check the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event arguments to determine the actual element that has mouse capture.  
   
@@ -854,7 +854,7 @@
 ## Remarks  
  When an element captures the mouse, it receives mouse input whether or not the cursor is within its borders. T  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Because of the bubbling routing, the actual element that lost capture might be a child element, not necessarily the element where the event handler is actually attached. Check the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event arguments to determine the actual element that lost capture.  
   
@@ -957,7 +957,7 @@
 ## Remarks  
  To determine which mouse button was depressed, check the <xref:System.Windows.Input.MouseButtonEventArgs.ChangedButton%2A> property in the <xref:System.Windows.Input.MouseButtonEventArgs> passed to the handler.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
   
@@ -970,7 +970,7 @@
   
 -   Register a handler on the control procedurally by calling <xref:System.Windows.UIElement.AddHandler%2A> and choosing the signature option that enables handlers to listen for events even if they are already marked as handled in the routed event data.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying mouse routed event be surfaced as CLR events along the route. Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by further children toward the source, and how would that affect compositing a control where the compositing pieces might have expected mouse behaviors?  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying mouse routed event be surfaced as CLR events along the route. Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by further children toward the source, and how would that affect compositing a control where the compositing pieces might have expected mouse behaviors?  
   
 <a name="routedEventInfo_MouseDown"></a>   
 ## Routed Event Information  
@@ -1035,7 +1035,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event uses the direct event handling routing strategy. Direct routed events are not raised along a route (they are only handled in the same element on which they are raised).  They do, however, enable other aspects of routed event behaviors, such as event triggers in styles.  
   
@@ -1102,7 +1102,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event uses the direct event handling routing strategy. Direct routed events do not follow a route (they are only handled in the same element on which they are raised).  They do, however, enable other aspects of routed event behaviors, such as event triggers in styles.  
   
@@ -1168,7 +1168,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 ## Routed Event Information  
   
@@ -1234,11 +1234,11 @@
 ## Remarks  
  Which mouse button was released is determined by checking the arguments of the event.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events all along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events all along the route.  
   
  Similar issues exist with tunneling mouse events.  Should you handle the event and not have it be handled by children further towards the source, and how would that affect compositing in a control where the compositing pieces might have expected mouse behaviors?  
   
@@ -1306,7 +1306,7 @@
 ## Remarks  
  Focus or mouse capture take precedence over where the mouse pointer is.  If you receive this event from a focused or captured element, the mouse pointer might in fact be over another element at the time.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_MouseWheel"></a>   
 ## Routed Event Information  
@@ -1446,11 +1446,11 @@
 ## Remarks  
  Which mouse button was depressed is determined by checking the arguments of the event. This is an attached event (using tunneling routing strategy) that is intended through attached event syntax to be referenced by existing [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements that take input.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
 <a name="routedEventInfo_PreviewMouseDown"></a>   
 ## Routed Event Information  
@@ -1515,7 +1515,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event is not resurfaced on base elements. It is mainly of concern to control authors that are attempting to reconcile mouse capture and mouse input within their control compositing.  
   
@@ -1582,7 +1582,7 @@
 ## Remarks  
  This event occurs both when the mouse pointer is newly moved in the element bounds, and also when the mouse pointer moves while still remaining in the element bounds.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewMouseMove"></a>   
 ## Routed Event Information  
@@ -1649,11 +1649,11 @@
 ## Remarks  
  Which mouse button was released is determined by checking the arguments of the event.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
   
- For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
+ For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
 ## Routed Event Information  
   
@@ -1717,7 +1717,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event is not resurfaced on base elements. It is mainly of concern to control authors that are attempting to reconcile mouse capture and mouse input within their control compositing.  
   
@@ -1786,7 +1786,7 @@
 ## Remarks  
  Focus or mouse capture take precedence over where the mouse pointer is; therefore, if you receive this event from a focused or captured element, the mouse pointer might in fact be over another element at the time.  
   
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewMouseWheel"></a>   
 ## Routed Event Information  
@@ -1888,7 +1888,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_Querycursor"></a>   
 ## Routed Event Information  
diff --git a/xml/System.Windows.Input/MouseBinding.xml b/xml/System.Windows.Input/MouseBinding.xml
index 28a8c1619e1..33ebf1e348b 100644
--- a/xml/System.Windows.Input/MouseBinding.xml
+++ b/xml/System.Windows.Input/MouseBinding.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Input.MouseBinding> associates a <xref:System.Windows.Input.MouseGesture> with an <xref:System.Windows.Input.ICommand> implementation. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] commanding system. In general, when the <xref:System.Windows.Input.MouseGesture> is executed, the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
+ A <xref:System.Windows.Input.MouseBinding> associates a <xref:System.Windows.Input.MouseGesture> with an <xref:System.Windows.Input.ICommand> implementation. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the WPF commanding system. In general, when the <xref:System.Windows.Input.MouseGesture> is executed, the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
   
  When defining a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], there are two ways to specify the <xref:System.Windows.Input.MouseGesture>. The first way to establish a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is to define the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element, which enables a syntax to specify mouse actions and modifiers as a single string; for example, "CTRL+LeftClick". The second way is to define the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element. Both ways of setting the <xref:System.Windows.Input.MouseGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> and the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attributes are both set, the gesture is invalid. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], even if you do not specify modifiers; this avoids ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
diff --git a/xml/System.Windows.Input/MouseButtonEventHandler.xml b/xml/System.Windows.Input/MouseButtonEventHandler.xml
index c1b0734d961..cd151eea49f 100644
--- a/xml/System.Windows.Input/MouseButtonEventHandler.xml
+++ b/xml/System.Windows.Input/MouseButtonEventHandler.xml
@@ -43,7 +43,7 @@
   
 -   <xref:System.Windows.Input.Mouse.PreviewMouseUpOutsideCapturedElement?displayProperty=nameWithType>  
   
- This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.MouseDown?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/MouseEventArgs.xml b/xml/System.Windows.Input/MouseEventArgs.xml
index 522e96b5c44..3d41deee2fd 100644
--- a/xml/System.Windows.Input/MouseEventArgs.xml
+++ b/xml/System.Windows.Input/MouseEventArgs.xml
@@ -35,7 +35,7 @@
   
 -   <xref:System.Windows.Input.Mouse.PreviewMouseMove?displayProperty=nameWithType>  
   
- This event data class is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This event data class is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.MouseEnter?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/MouseEventHandler.xml b/xml/System.Windows.Input/MouseEventHandler.xml
index 85e5a2d250c..72c102bb676 100644
--- a/xml/System.Windows.Input/MouseEventHandler.xml
+++ b/xml/System.Windows.Input/MouseEventHandler.xml
@@ -43,7 +43,7 @@
   
 -   <xref:System.Windows.Input.Mouse.PreviewMouseMove?displayProperty=nameWithType>  
   
- This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.MouseEnter?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/MouseWheelEventHandler.xml b/xml/System.Windows.Input/MouseWheelEventHandler.xml
index a26cbffa4fd..a992d2095db 100644
--- a/xml/System.Windows.Input/MouseWheelEventHandler.xml
+++ b/xml/System.Windows.Input/MouseWheelEventHandler.xml
@@ -35,7 +35,7 @@
   
 -   <xref:System.Windows.Input.Mouse.PreviewMouseWheel?displayProperty=nameWithType>  
   
- This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.MouseWheel?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/NotifyInputEventArgs.xml b/xml/System.Windows.Input/NotifyInputEventArgs.xml
index b4726bfb0b1..150243411cb 100644
--- a/xml/System.Windows.Input/NotifyInputEventArgs.xml
+++ b/xml/System.Windows.Input/NotifyInputEventArgs.xml
@@ -25,13 +25,13 @@
   
  <xref:System.Windows.Input.NotifyInputEventArgs> is used with the <xref:System.Windows.Input.InputManager.PreNotifyInput> and <xref:System.Windows.Input.InputManager.PostNotifyInput> events.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/NotifyInputEventHandler.xml b/xml/System.Windows.Input/NotifyInputEventHandler.xml
index 7cf03d2badb..e92ffb59ac4 100644
--- a/xml/System.Windows.Input/NotifyInputEventHandler.xml
+++ b/xml/System.Windows.Input/NotifyInputEventHandler.xml
@@ -33,13 +33,13 @@
   
  The <xref:System.Windows.Input.NotifyInputEventHandler> is used with the <xref:System.Windows.Input.InputManager.PreNotifyInput> and <xref:System.Windows.Input.InputManager.PostNotifyInput> events.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/PreProcessInputEventArgs.xml b/xml/System.Windows.Input/PreProcessInputEventArgs.xml
index 480b00e2d80..41ff2a91693 100644
--- a/xml/System.Windows.Input/PreProcessInputEventArgs.xml
+++ b/xml/System.Windows.Input/PreProcessInputEventArgs.xml
@@ -29,13 +29,13 @@
   
  <xref:System.Windows.Input.PreProcessInputEventArgs> is used with the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/PreProcessInputEventHandler.xml b/xml/System.Windows.Input/PreProcessInputEventHandler.xml
index 165ea28885d..0c0305e1ae7 100644
--- a/xml/System.Windows.Input/PreProcessInputEventHandler.xml
+++ b/xml/System.Windows.Input/PreProcessInputEventHandler.xml
@@ -31,13 +31,13 @@
 ## Remarks  
  The <xref:System.Windows.Input.PreProcessInputEventHandler> is used with the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/ProcessInputEventArgs.xml b/xml/System.Windows.Input/ProcessInputEventArgs.xml
index fbd46198920..ce125468603 100644
--- a/xml/System.Windows.Input/ProcessInputEventArgs.xml
+++ b/xml/System.Windows.Input/ProcessInputEventArgs.xml
@@ -27,13 +27,13 @@
   
  <xref:System.Windows.Input.ProcessInputEventArgs> is used with the <xref:System.Windows.Input.InputManager.PostProcessInput> event.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/ProcessInputEventHandler.xml b/xml/System.Windows.Input/ProcessInputEventHandler.xml
index 66f0d4f3649..5fd412452e6 100644
--- a/xml/System.Windows.Input/ProcessInputEventHandler.xml
+++ b/xml/System.Windows.Input/ProcessInputEventHandler.xml
@@ -33,13 +33,13 @@
   
  Process input events enable access to the <xref:System.Windows.Input.InputManager> staging area, which processes input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
   
- Input is processed in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] in the follow stages:  
+ Input is processed in WPF in the follow stages:  
   
 1.  Pre-process stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreProcessInput> event.  
   
 2.  Pre-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
-3.  The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] input event or events are raised.  
+3.  The WPF input event or events are raised.  
   
 4.  Post-notify stage.  The input manager raises the <xref:System.Windows.Input.InputManager.PostNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/QueryCursorEventHandler.xml b/xml/System.Windows.Input/QueryCursorEventHandler.xml
index 283f82b4df7..b4f6e4da151 100644
--- a/xml/System.Windows.Input/QueryCursorEventHandler.xml
+++ b/xml/System.Windows.Input/QueryCursorEventHandler.xml
@@ -33,7 +33,7 @@
   
 -   <xref:System.Windows.Input.Mouse.QueryCursor?displayProperty=nameWithType>  
   
- This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is used with the following routed events. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.QueryCursor?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Input/RestoreFocusMode.xml b/xml/System.Windows.Input/RestoreFocusMode.xml
index ee11581b755..8ce92aee505 100644
--- a/xml/System.Windows.Input/RestoreFocusMode.xml
+++ b/xml/System.Windows.Input/RestoreFocusMode.xml
@@ -36,7 +36,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automatically tries to restore focus to the element that last had focus.</summary>
+        <summary>WPF automatically tries to restore focus to the element that last had focus.</summary>
       </Docs>
     </Member>
     <Member MemberName="None">
@@ -57,7 +57,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not restore focus.</summary>
+        <summary>WPF does not restore focus.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Input/Stylus.xml b/xml/System.Windows.Input/Stylus.xml
index 407a46437bf..26e278eb4dc 100644
--- a/xml/System.Windows.Input/Stylus.xml
+++ b/xml/System.Windows.Input/Stylus.xml
@@ -1057,7 +1057,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. Attached events are, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. The WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_GotStylusCapture"></a>   
 ## Routed Event Information  
@@ -1376,7 +1376,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_LostStylusCapture"></a>   
 ## Routed Event Information  
@@ -1441,7 +1441,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusButtonDown"></a>   
 ## Routed Event Information  
@@ -1506,7 +1506,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusButtonUp"></a>   
 ## Routed Event Information  
@@ -1571,7 +1571,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusDown"></a>   
 ## Routed Event Information  
@@ -1636,7 +1636,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusInAirMove"></a>   
 ## Routed Event Information  
@@ -1701,7 +1701,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusInRange"></a>   
 ## Routed Event Information  
@@ -1766,7 +1766,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusMove"></a>   
 ## Routed Event Information  
@@ -1831,7 +1831,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusOutOfRange"></a>   
 ## Routed Event Information  
@@ -1896,7 +1896,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusSystemGesture"></a>   
 ## Routed Event Information  
@@ -1961,7 +1961,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusUp"></a>   
 ## Routed Event Information  
@@ -2813,7 +2813,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusButtonDown"></a>   
 ## Routed Event Information  
@@ -2878,7 +2878,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusButtonUp"></a>   
 ## Routed Event Information  
@@ -2943,7 +2943,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusDown"></a>   
 ## Routed Event Information  
@@ -3008,7 +3008,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusEnter"></a>   
 ## Routed Event Information  
@@ -3073,7 +3073,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusInAirMove"></a>   
 ## Routed Event Information  
@@ -3138,7 +3138,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusInRange"></a>   
 ## Routed Event Information  
@@ -3203,7 +3203,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusLeave"></a>   
 ## Routed Event Information  
@@ -3268,7 +3268,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusMove"></a>   
 ## Routed Event Information  
@@ -3333,7 +3333,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route.  Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route.  Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusOutOfRange"></a>   
 ## Routed Event Information  
@@ -3398,7 +3398,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusSystemGesture"></a>   
 ## Routed Event Information  
@@ -3463,7 +3463,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusUp"></a>   
 ## Routed Event Information  
diff --git a/xml/System.Windows.Input/StylusPointProperties.xml b/xml/System.Windows.Input/StylusPointProperties.xml
index 46ac0f411f8..8bbdd892def 100644
--- a/xml/System.Windows.Input/StylusPointProperties.xml
+++ b/xml/System.Windows.Input/StylusPointProperties.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] ships with pre-defined <xref:System.Windows.Input.StylusPointProperty> objects for properties that are commonly collected by a stylus and a digitizer. You can use these built-in properties to create a <xref:System.Windows.Input.StylusPointDescription>.  
+ The WPF ships with pre-defined <xref:System.Windows.Input.StylusPointProperty> objects for properties that are commonly collected by a stylus and a digitizer. You can use these built-in properties to create a <xref:System.Windows.Input.StylusPointDescription>.  
   
    
   
diff --git a/xml/System.Windows.Input/TextCompositionEventHandler.xml b/xml/System.Windows.Input/TextCompositionEventHandler.xml
index be0713d5230..83651534f1d 100644
--- a/xml/System.Windows.Input/TextCompositionEventHandler.xml
+++ b/xml/System.Windows.Input/TextCompositionEventHandler.xml
@@ -43,7 +43,7 @@
   
 -   <xref:System.Windows.Input.TextCompositionManager.PreviewTextInputUpdate?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward some of the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward some of the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.TextInput?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows.Interop/CursorInteropHelper.xml b/xml/System.Windows.Interop/CursorInteropHelper.xml
index b175c4ac5cb..159a93356df 100644
--- a/xml/System.Windows.Interop/CursorInteropHelper.xml
+++ b/xml/System.Windows.Interop/CursorInteropHelper.xml
@@ -54,7 +54,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Setting a custom cursor image requires security permissions even if done in pure [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] programming. See <xref:System.Windows.Input.Cursor>.  
+ Setting a custom cursor image requires security permissions even if done in pure WPF programming. See <xref:System.Windows.Input.Cursor>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Interop/HwndSource.xml b/xml/System.Windows.Interop/HwndSource.xml
index 9a93e7bd045..62286d8966e 100644
--- a/xml/System.Windows.Interop/HwndSource.xml
+++ b/xml/System.Windows.Interop/HwndSource.xml
@@ -37,7 +37,7 @@
 > [!IMPORTANT]
 >  Many members of this class are unavailable in the Internet security zone.  
   
- An <xref:System.Windows.Interop.HwndSource> implements a Win32 window that can contain [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content in the window is arranged, measured, and rendered; and is interactive to input. Because the <xref:System.Windows.Interop.HwndSource> is specifically designed to interoperate with Win32, this class exposes several low-level Win32 features. You can use this class to do the following:  
+ An <xref:System.Windows.Interop.HwndSource> implements a Win32 window that can contain WPF content. The WPF content in the window is arranged, measured, and rendered; and is interactive to input. Because the <xref:System.Windows.Interop.HwndSource> is specifically designed to interoperate with Win32, this class exposes several low-level Win32 features. You can use this class to do the following:  
   
 -   Specify window styles, window class styles, and extended window styles.  
   
@@ -57,13 +57,13 @@
   
 -   The initial position of the window.  
   
--   The initial size of the window, which includes whether the size is specified or should be determined from the determined size of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content.  
+-   The initial size of the window, which includes whether the size is specified or should be determined from the determined size of the WPF content.  
   
 -   The parent window.  
   
 -   The <xref:System.Windows.Interop.HwndSourceHook> to include in the window procedure chain. If you specify a hook at construction time, it receives all messages for the window. You can use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to add a hook after the window is created.  
   
--   The transparency settings. A top-level window can be configured to blend with the other windows on the desktop according to the per-pixel transparency of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content. To enable this, set the <xref:System.Windows.Interop.HwndSourceParameters.UsesPerPixelOpacity%2A> property in the <xref:System.Windows.Interop.HwndSourceParameters> to `true`. This property can only be specified at construction time, and only through the <xref:System.Windows.Interop.HwndSource.%23ctor%28System.Windows.Interop.HwndSourceParameters%29> constructor signature, and it imposes several limitations.  
+-   The transparency settings. A top-level window can be configured to blend with the other windows on the desktop according to the per-pixel transparency of the WPF content. To enable this, set the <xref:System.Windows.Interop.HwndSourceParameters.UsesPerPixelOpacity%2A> property in the <xref:System.Windows.Interop.HwndSourceParameters> to `true`. This property can only be specified at construction time, and only through the <xref:System.Windows.Interop.HwndSource.%23ctor%28System.Windows.Interop.HwndSourceParameters%29> constructor signature, and it imposes several limitations.  
   
  After you populate the <xref:System.Windows.Interop.HwndSourceParameters> structure, pass it to the <xref:System.Windows.Interop.HwndSource.%23ctor%28System.Windows.Interop.HwndSourceParameters%29> constructor for the <xref:System.Windows.Interop.HwndSource>.  
   
@@ -384,7 +384,7 @@
 > [!IMPORTANT]
 >  This method is not available in the Internet security zone.  
   
- Most [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] messages that reach the <xref:System.Windows.Interop.HwndSource> have an approximate [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] equivalent. You use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to handle the cases where the message has no [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] equivalent.  
+ Most [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] messages that reach the <xref:System.Windows.Interop.HwndSource> have an approximate WPF equivalent. You use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to handle the cases where the message has no WPF equivalent.  
   
  The <xref:System.Windows.Interop.HwndSourceHook> delegate resembles the parameter profile of a Win32 main window procedure. All window messages that the main window procedure of the <xref:System.Windows.Interop.HwndSource> parent window receives are also forwarded to the <xref:System.Windows.Interop.HwndSourceHook> delegates.  
   
@@ -420,7 +420,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The native behavior of <xref:System.Windows.Interop.HwndSource> is to automatically resize content and the window region based on changes reported through the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] layout system. The window does not resize if it is currently minimized or if <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> is set to <xref:System.Windows.SizeToContent.Manual>.  
+ The native behavior of <xref:System.Windows.Interop.HwndSource> is to automatically resize content and the window region based on changes reported through the WPF layout system. The window does not resize if it is currently minimized or if <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> is set to <xref:System.Windows.SizeToContent.Manual>.  
   
  ]]></format>
         </remarks>
@@ -1128,7 +1128,7 @@
 ## Remarks  
  Use this property to connect a <xref:System.Windows.Controls.Page> or another root visual to the <xref:System.Windows.Interop.HwndSource>.  
   
- Scale transformations should not be applied to the <xref:System.Windows.Interop.HwndSource.RootVisual%2A> of an <xref:System.Windows.Interop.HwndSource> because this can disable <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> behavior. The content will scale, but the enclosing window will not. Instead of applying the transformation to the object that is the <xref:System.Windows.Interop.HwndSource.RootVisual%2A>, apply the transformation to an object that is a child element of the <xref:System.Windows.Interop.HwndSource.RootVisual%2A>. You might need to add an extra enclosing element to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content, such as a panel, in order to provide a scaleable object.  
+ Scale transformations should not be applied to the <xref:System.Windows.Interop.HwndSource.RootVisual%2A> of an <xref:System.Windows.Interop.HwndSource> because this can disable <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> behavior. The content will scale, but the enclosing window will not. Instead of applying the transformation to the object that is the <xref:System.Windows.Interop.HwndSource.RootVisual%2A>, apply the transformation to an object that is a child element of the <xref:System.Windows.Interop.HwndSource.RootVisual%2A>. You might need to add an extra enclosing element to the WPF content, such as a panel, in order to provide a scaleable object.  
   
  You can add a <xref:System.Windows.Window> as the root visual, but only as a top-level window (with WS_OVERLAPPED), not as a child window.  
   
diff --git a/xml/System.Windows.Interop/IKeyboardInputSite.xml b/xml/System.Windows.Interop/IKeyboardInputSite.xml
index f758157187b..fe9e54f17b7 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSite.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSite.xml
@@ -24,7 +24,7 @@
   
  For a discussion of the input architecture specifically implemented for [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] interoperation, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
   
- For more information about [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]-Win32 interoperation scenarios, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
+ For more information about WPF-Win32 interoperation scenarios, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Interop/Imaging.xml b/xml/System.Windows.Interop/Imaging.xml
index a206c703f8f..f7850b2182f 100644
--- a/xml/System.Windows.Interop/Imaging.xml
+++ b/xml/System.Windows.Interop/Imaging.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class provides creation mechanisms for the primary bitmap imaging class in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], <xref:System.Windows.Media.Imaging.BitmapSource>. This includes methods that create a <xref:System.Windows.Media.Imaging.BitmapSource> based on [!INCLUDE[TLA#tla_gdi](~/includes/tlasharptla-gdi-md.md)] objects , and memory sections.  
+ This class provides creation mechanisms for the primary bitmap imaging class in WPF, <xref:System.Windows.Media.Imaging.BitmapSource>. This includes methods that create a <xref:System.Windows.Media.Imaging.BitmapSource> based on [!INCLUDE[TLA#tla_gdi](~/includes/tlasharptla-gdi-md.md)] objects , and memory sections.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Interop/WindowInteropHelper.xml b/xml/System.Windows.Interop/WindowInteropHelper.xml
index 9c680b0d9a1..d72beec5dca 100644
--- a/xml/System.Windows.Interop/WindowInteropHelper.xml
+++ b/xml/System.Windows.Interop/WindowInteropHelper.xml
@@ -21,16 +21,16 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Members of this class allows the caller to have internal access to the Win32 HWND and the parent HWND of a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window>.  The proper security checks are performed by those members.  
+ Members of this class allows the caller to have internal access to the Win32 HWND and the parent HWND of a WPF <xref:System.Windows.Window>.  The proper security checks are performed by those members.  
   
  Use this class whenever you need a more specific object based on its HWND.  
   
- An example scenario is if you need to host a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a Win32 application. Initialize the <xref:System.Windows.Interop.WindowInteropHelper> with a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window object for the dialog box. You can then get the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window's handle (HWND) from the <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> property and specify the owner for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window with the <xref:System.Windows.Interop.WindowInteropHelper.Owner%2A> property. The following code example shows how to use <xref:System.Windows.Interop.WindowInteropHelper> when hosting a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dialog box in a Win32 application.  
+ An example scenario is if you need to host a WPF dialog box in a Win32 application. Initialize the <xref:System.Windows.Interop.WindowInteropHelper> with a WPF window object for the dialog box. You can then get the WPF window's handle (HWND) from the <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> property and specify the owner for the WPF window with the <xref:System.Windows.Interop.WindowInteropHelper.Owner%2A> property. The following code example shows how to use <xref:System.Windows.Interop.WindowInteropHelper> when hosting a WPF dialog box in a Win32 application.  
   
  [!code-csharp[CorePseudocode#WindowInteropHelper](~/samples/snippets/csharp/VS_Snippets_Wpf/CorePseudocode/CSharp/corepseudocode.cs#windowinterophelper)]
  [!code-vb[CorePseudocode#WindowInteropHelper](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CorePseudocode/visualbasic/corepseudocode.vb#windowinterophelper)]  
   
- Another scenario supported by this class is to obtain a <xref:System.Windows.Interop.HwndSource> object from a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Window> object. The <xref:System.Windows.Interop.HwndSource> enables direct processing of Win32 messages through the <xref:System.Windows.Interop.HwndSource.AddHook%2A> method. By using <xref:System.Windows.Interop.HwndSource> and <xref:System.Windows.Interop.HwndSource.AddHook%2A> in place of a <xref:System.Windows.Window> you can still handle messages that have no equivalent or handling in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. Create a <xref:System.Windows.Interop.WindowInteropHelper> with the <xref:System.Windows.Window> source, then call <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> on the <xref:System.Windows.Interop.WindowInteropHelper> to get from HWND to <xref:System.Windows.Interop.HwndSource>.  
+ Another scenario supported by this class is to obtain a <xref:System.Windows.Interop.HwndSource> object from a WPF <xref:System.Windows.Window> object. The <xref:System.Windows.Interop.HwndSource> enables direct processing of Win32 messages through the <xref:System.Windows.Interop.HwndSource.AddHook%2A> method. By using <xref:System.Windows.Interop.HwndSource> and <xref:System.Windows.Interop.HwndSource.AddHook%2A> in place of a <xref:System.Windows.Window> you can still handle messages that have no equivalent or handling in WPF. Create a <xref:System.Windows.Interop.WindowInteropHelper> with the <xref:System.Windows.Window> source, then call <xref:System.Windows.Interop.WindowInteropHelper.Handle%2A> on the <xref:System.Windows.Interop.WindowInteropHelper> to get from HWND to <xref:System.Windows.Interop.HwndSource>.  
   
  ]]></format>
     </remarks>
@@ -57,7 +57,7 @@
         <Parameter Name="window" Type="System.Windows.Window" />
       </Parameters>
       <Docs>
-        <param name="window">A [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] window object.</param>
+        <param name="window">A WPF window object.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Interop.WindowInteropHelper" /> class for a specified [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Markup/ContentWrapperAttribute.xml b/xml/System.Windows.Markup/ContentWrapperAttribute.xml
index 088fecb19bb..0ec15d4b2c9 100644
--- a/xml/System.Windows.Markup/ContentWrapperAttribute.xml
+++ b/xml/System.Windows.Markup/ContentWrapperAttribute.xml
@@ -44,7 +44,7 @@
 ## Remarks  
  Foreign content refers to cases where the type system constraints on the type of the content property do not capture all of the possible content cases that XAML usage for the owning type would support. For example, XAML support for content of a particular type might support strings in a strongly typed generic <xref:System.Collections.ObjectModel.Collection%601>.  
   
- <xref:System.Windows.Documents.InlineCollection> is an example of a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] class that has the <xref:System.Windows.Markup.ContentWrapperAttribute> attribute applied. In this case there are two separate attributed wrapper classes.  
+ <xref:System.Windows.Documents.InlineCollection> is an example of a WPF class that has the <xref:System.Windows.Markup.ContentWrapperAttribute> attribute applied. In this case there are two separate attributed wrapper classes.  
   
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.ContentWrapperAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
diff --git a/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml b/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
index 73556c4a68c..209b4a928c1 100644
--- a/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
+++ b/xml/System.Windows.Markup/DictionaryKeyPropertyAttribute.xml
@@ -38,7 +38,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Items in an <xref:System.Collections.IDictionary> dictionary (such as the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.ResourceDictionary>) require a key. In XAML, the key is typically specified by `x:Key` attribute in the XAML markup for each item in the <xref:System.Collections.IDictionary>. The <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is applied to classes that work with an implicit key, where the key to use for <xref:System.Collections.IDictionary> inclusion comes from a different property value in the class. Instances of the class applying the <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> can be included in an <xref:System.Collections.IDictionary> without an explicit key so long as the property referenced by <xref:System.Collections.IDictionary> has a value that is valid as a key in that dictionary implementation.  
+ Items in an <xref:System.Collections.IDictionary> dictionary (such as the WPF <xref:System.Windows.ResourceDictionary>) require a key. In XAML, the key is typically specified by `x:Key` attribute in the XAML markup for each item in the <xref:System.Collections.IDictionary>. The <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is applied to classes that work with an implicit key, where the key to use for <xref:System.Collections.IDictionary> inclusion comes from a different property value in the class. Instances of the class applying the <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> can be included in an <xref:System.Collections.IDictionary> without an explicit key so long as the property referenced by <xref:System.Collections.IDictionary> has a value that is valid as a key in that dictionary implementation.  
   
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.DictionaryKeyPropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
diff --git a/xml/System.Windows.Markup/INameScope.xml b/xml/System.Windows.Markup/INameScope.xml
index 08ebb702337..c16e53c80c1 100644
--- a/xml/System.Windows.Markup/INameScope.xml
+++ b/xml/System.Windows.Markup/INameScope.xml
@@ -36,7 +36,7 @@
  In previous versions of the .NET Framework, this interface existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.INameScope> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- This interface is implemented by the WPF class <xref:System.Windows.NameScope>. Most XAML namescope operations in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] operate by using <xref:System.Windows.NameScope> instances, but information is occasionally communicated internally by using <xref:System.Windows.Markup.INameScope> references.  
+ This interface is implemented by the WPF class <xref:System.Windows.NameScope>. Most XAML namescope operations in WPF operate by using <xref:System.Windows.NameScope> instances, but information is occasionally communicated internally by using <xref:System.Windows.Markup.INameScope> references.  
   
  Examples of WPF classes that use a factory or defer metaphor combined with XAML representation are <xref:System.Windows.Style> and <xref:System.Windows.FrameworkTemplate>. These implementations usually rely on the explicit versions of the interface methods available from the <xref:System.Windows.NameScope> class.  
   
diff --git a/xml/System.Windows.Markup/StaticExtension.xml b/xml/System.Windows.Markup/StaticExtension.xml
index 9267c4cbd4e..395d34213e1 100644
--- a/xml/System.Windows.Markup/StaticExtension.xml
+++ b/xml/System.Windows.Markup/StaticExtension.xml
@@ -181,7 +181,7 @@
   
  This value is not evaluated when you set it; so long as the value is not `null` it will be accepted. The actual parsing and evaluation of the value is deferred until <xref:System.Windows.Markup.StaticExtension.ProvideValue%2A> is called during parsing.  
   
- Under the normal scenario of use by the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] XAML processor, the XAML processor passes a type resolver for CLR types as part of its service contract, and this resolver is used on the <xref:System.Windows.Markup.StaticExtension.ProvideValue%2A> call.  
+ Under the normal scenario of use by the WPF XAML processor, the XAML processor passes a type resolver for CLR types as part of its service contract, and this resolver is used on the <xref:System.Windows.Markup.StaticExtension.ProvideValue%2A> call.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/TypeExtension.xml b/xml/System.Windows.Markup/TypeExtension.xml
index 16cd522dc0c..c38e8f70012 100644
--- a/xml/System.Windows.Markup/TypeExtension.xml
+++ b/xml/System.Windows.Markup/TypeExtension.xml
@@ -53,7 +53,7 @@
 >  The `{x:Type}` functionality is generally for user code invocation from markup. For code that is implementing XAML support, type resolution services come from <xref:System.Windows.Markup.IXamlTypeResolver> and are related to the implementation of the acting XAML schema context. Do not attempt to reference <xref:System.Windows.Markup.TypeExtension.ProvideValue%2A> as a substitute for a <xref:System.Windows.Markup.IXamlTypeResolver> service provider; the context you pass in might not be valid for a type resolution, and attempts to call without valid services will fail.  
   
 ## WPF Usage Notes  
- Type references are commonly used for style, template, and databinding feature areas in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], when these features are referenced by XAML.  
+ Type references are commonly used for style, template, and databinding feature areas in WPF, when these features are referenced by XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/ValueSerializer.xml b/xml/System.Windows.Markup/ValueSerializer.xml
index 294a947b2eb..5007d344ec9 100644
--- a/xml/System.Windows.Markup/ValueSerializer.xml
+++ b/xml/System.Windows.Markup/ValueSerializer.xml
@@ -579,7 +579,7 @@
  Overriding this method is an advanced scenario. Overriding should only be necessary if you are implementing a system where CLR type system ownertype-property relationships available to a XAML schema context do not report enough information.  
   
 ## WPF Usage Notes  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system implements an internal value serializer that overrides <xref:System.Windows.Markup.ValueSerializer.TypeReferences%2A> because a dependency property has a concept that it can have added owners. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] expressions also have special internal handling.  
+ The WPF property system implements an internal value serializer that overrides <xref:System.Windows.Markup.ValueSerializer.TypeReferences%2A> because a dependency property has a concept that it can have added owners. WPF expressions also have special internal handling.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml b/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
index d11937fff34..a204adff12f 100644
--- a/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
+++ b/xml/System.Windows.Markup/WhitespaceSignificantCollectionAttribute.xml
@@ -43,7 +43,7 @@
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.WhitespaceSignificantCollectionAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- <xref:System.Windows.Documents.InlineCollection> is an example [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] class where this attribute is applied.  
+ <xref:System.Windows.Documents.InlineCollection> is an example WPF class where this attribute is applied.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XamlDesignerSerializationManager.xml b/xml/System.Windows.Markup/XamlDesignerSerializationManager.xml
index 2ccbd559dd7..362c003f718 100644
--- a/xml/System.Windows.Markup/XamlDesignerSerializationManager.xml
+++ b/xml/System.Windows.Markup/XamlDesignerSerializationManager.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The <xref:System.Windows.Markup.XamlDesignerSerializationManager> attempts to optimize access to services that are called frequently during the serialization process.  
   
- A <xref:System.Windows.Markup.XamlDesignerSerializationManager> is also used as an input for certain specialized `ShouldSerialize` methods on [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] classes such as <xref:System.Windows.Controls.TextBlock.ShouldSerializeInlines%2A?displayProperty=nameWithType>, and for an overload of <xref:System.Windows.Markup.XamlWriter.Save%2A?displayProperty=nameWithType>.  
+ A <xref:System.Windows.Markup.XamlDesignerSerializationManager> is also used as an input for certain specialized `ShouldSerialize` methods on WPF classes such as <xref:System.Windows.Controls.TextBlock.ShouldSerializeInlines%2A?displayProperty=nameWithType>, and for an overload of <xref:System.Windows.Markup.XamlWriter.Save%2A?displayProperty=nameWithType>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index e29a69c483e..85b893323bd 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -41,7 +41,7 @@
 ## Code Access Security, Loose XAML, and XamlReader  
  XAML is a markup language that directly represents object instantiation and execution. Therefore, elements created in XAML have the same ability to interact with system resources (network access, file system IO, for example) as the equivalent generated code does.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] supports the .NET security framework [!INCLUDE[TLA#tla_cas](~/includes/tlasharptla-cas-md.md)]. This means that [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
+ WPF supports the .NET security framework [!INCLUDE[TLA#tla_cas](~/includes/tlasharptla-cas-md.md)]. This means that WPF content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
   
  The implications of these statements for <xref:System.Windows.Markup.XamlReader> is that your application design must make trust decisions about the XAML you decide to load. If you are loading XAML that is not trusted, consider implementing your own sandboxing technique for how you load the resulting object graph.  
   
diff --git a/xml/System.Windows.Media.TextFormatting/TextFormatter.xml b/xml/System.Windows.Media.TextFormatting/TextFormatter.xml
index b47e576d87f..cd566656324 100644
--- a/xml/System.Windows.Media.TextFormatting/TextFormatter.xml
+++ b/xml/System.Windows.Media.TextFormatting/TextFormatter.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.TextFormatting.TextFormatter> is the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] text engine that provides services for formatting text and breaking text lines. <xref:System.Windows.Media.TextFormatting.TextFormatter> can handle different text character formats and paragraph styles, and includes support for international text layout.  
+ <xref:System.Windows.Media.TextFormatting.TextFormatter> is the WPF text engine that provides services for formatting text and breaking text lines. <xref:System.Windows.Media.TextFormatting.TextFormatter> can handle different text character formats and paragraph styles, and includes support for international text layout.  
   
  Unlike a traditional text API, the <xref:System.Windows.Media.TextFormatting.TextFormatter> interacts with a text layout client through a set of callback methods. It requires the client to provide these methods in an implementation of the <xref:System.Windows.Media.TextFormatting.TextSource> class. The following diagram illustrates the interaction of the text formatter client and the text layout client.  
   
diff --git a/xml/System.Windows.Media.TextFormatting/TextRunTypographyProperties.xml b/xml/System.Windows.Media.TextFormatting/TextRunTypographyProperties.xml
index 18314e2bd53..0d63eb23474 100644
--- a/xml/System.Windows.Media.TextFormatting/TextRunTypographyProperties.xml
+++ b/xml/System.Windows.Media.TextFormatting/TextRunTypographyProperties.xml
@@ -742,7 +742,7 @@ Example of slashed zero numerals
  ![Text using OpenType standard ligatures](~/add/media/opentypefont04.gif "Text using OpenType standard ligatures")  
 Example of a standard set of ligatures  
   
- By default, OpenType fonts in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] enable standard ligatures. For example, if you use the Palatino Linotype font, the standard ligatures "fi", "ff", and "fl" appear as a combined character glyph. Notice that the characters of each standard ligature touch each other.  
+ By default, OpenType fonts in WPF enable standard ligatures. For example, if you use the Palatino Linotype font, the standard ligatures "fi", "ff", and "fl" appear as a combined character glyph. Notice that the characters of each standard ligature touch each other.  
   
  ![Text using OpenType standard ligatures](~/add/media/opentypefont06.gif "Text using OpenType standard ligatures")  
 Example of standard ligatures enabled by default  
diff --git a/xml/System.Windows.Media.TextFormatting/TextSource.xml b/xml/System.Windows.Media.TextFormatting/TextSource.xml
index 9574ff2cb3b..f7dfff01b03 100644
--- a/xml/System.Windows.Media.TextFormatting/TextSource.xml
+++ b/xml/System.Windows.Media.TextFormatting/TextSource.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  All access to the text in the <xref:System.Windows.Media.TextFormatting.TextSource> object is through the <xref:System.Windows.Media.TextFormatting.TextSource.GetTextRun%2A>, which is designed to allow the text layout client to virtualize text in any way it chooses.  
   
- <xref:System.Windows.Media.TextFormatting.TextFormatter> is the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] text engine that provides services for formatting text and breaking text lines. <xref:System.Windows.Media.TextFormatting.TextFormatter> can handle different text character formats and paragraph styles, and includes support for international text layout. Unlike a traditional text API, the <xref:System.Windows.Media.TextFormatting.TextFormatter> interacts with a text layout client through a set of callback methods. It requires the client to provide these methods in an implementation of the <xref:System.Windows.Media.TextFormatting.TextSource> class. The following list describes the three members you must override:  
+ <xref:System.Windows.Media.TextFormatting.TextFormatter> is the WPF text engine that provides services for formatting text and breaking text lines. <xref:System.Windows.Media.TextFormatting.TextFormatter> can handle different text character formats and paragraph styles, and includes support for international text layout. Unlike a traditional text API, the <xref:System.Windows.Media.TextFormatting.TextFormatter> interacts with a text layout client through a set of callback methods. It requires the client to provide these methods in an implementation of the <xref:System.Windows.Media.TextFormatting.TextSource> class. The following list describes the three members you must override:  
   
 -   <xref:System.Windows.Media.TextFormatting.TextSource.GetTextRun%2A>: Retrieves a <xref:System.Windows.Media.TextFormatting.TextRun> starting at a specified <xref:System.Windows.Media.TextFormatting.TextSource> position.  
   
diff --git a/xml/System.Windows.Media/Brush.xml b/xml/System.Windows.Media/Brush.xml
index c8fb8ee05ad..d8d0d291ae0 100644
--- a/xml/System.Windows.Media/Brush.xml
+++ b/xml/System.Windows.Media/Brush.xml
@@ -41,7 +41,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Media.Brush> "paints" or "fills" an area with its output. Different brushes have different types of output. Some brushes paint an area with a solid color, others with a gradient, pattern, image, or drawing. The following list describes the different types of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] brushes:  
+ A <xref:System.Windows.Media.Brush> "paints" or "fills" an area with its output. Different brushes have different types of output. Some brushes paint an area with a solid color, others with a gradient, pattern, image, or drawing. The following list describes the different types of WPF brushes:  
   
 -   <xref:System.Windows.Media.SolidColorBrush>: Paints an area with a solid <xref:System.Windows.Media.Color>.  
   
diff --git a/xml/System.Windows.Media/CachingHint.xml b/xml/System.Windows.Media/CachingHint.xml
index 0661d36f0a0..2cc275f18d9 100644
--- a/xml/System.Windows.Media/CachingHint.xml
+++ b/xml/System.Windows.Media/CachingHint.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] is to re-render the entire content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
+ By default, WPF does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of WPF is to re-render the entire content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
   
  By setting the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> attached property on the brush to Cache, you can increase performance by using cached versions of the tiled brush objects.  
   
diff --git a/xml/System.Windows.Media/CompositionTarget.xml b/xml/System.Windows.Media/CompositionTarget.xml
index 86d27a10e4e..044c2c3304e 100644
--- a/xml/System.Windows.Media/CompositionTarget.xml
+++ b/xml/System.Windows.Media/CompositionTarget.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.CompositionTarget> is a class that represents the display surface on which your application is being drawn. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] animation engine provides many features for creating frame-based animation. However, there are application scenarios in which you need control over rendering on a per frame basis. The <xref:System.Windows.Media.CompositionTarget> object provides the ability to create custom animations based on a per-frame callback.  
+ <xref:System.Windows.Media.CompositionTarget> is a class that represents the display surface on which your application is being drawn. The WPF animation engine provides many features for creating frame-based animation. However, there are application scenarios in which you need control over rendering on a per frame basis. The <xref:System.Windows.Media.CompositionTarget> object provides the ability to create custom animations based on a per-frame callback.  
   
 > [!NOTE]
 >  For a complete code sample using <xref:System.Windows.Media.CompositionTarget>, see [Using the CompositionTarget Sample](https://go.microsoft.com/fwlink/?LinkID=160045).  
diff --git a/xml/System.Windows.Media/ContainerVisual.xml b/xml/System.Windows.Media/ContainerVisual.xml
index 52abafa0441..fa56ba1ac78 100644
--- a/xml/System.Windows.Media/ContainerVisual.xml
+++ b/xml/System.Windows.Media/ContainerVisual.xml
@@ -669,9 +669,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -708,9 +708,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/DisableDpiAwarenessAttribute.xml b/xml/System.Windows.Media/DisableDpiAwarenessAttribute.xml
index bdfc501b642..01496227784 100644
--- a/xml/System.Windows.Media/DisableDpiAwarenessAttribute.xml
+++ b/xml/System.Windows.Media/DisableDpiAwarenessAttribute.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications are dpi aware, which affects how user interface layout is calculated. However, an application can disable dpi awareness by adding the <xref:System.Windows.Media.DisableDpiAwarenessAttribute> to the application assembly.  
+ By default, WPF applications are dpi aware, which affects how user interface layout is calculated. However, an application can disable dpi awareness by adding the <xref:System.Windows.Media.DisableDpiAwarenessAttribute> to the application assembly.  
   
 > [!CAUTION]
 >  It is **not** recommended that you set this attribute for your application, unless you need all user interface elements of your application to be non-dpi aware.  
@@ -35,7 +35,7 @@
    
   
 ## Examples  
- The following example shows how to disable Dpi awareness for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application by declaring <xref:System.Windows.Media.DisableDpiAwarenessAttribute> at the assembly level.  
+ The following example shows how to disable Dpi awareness for the WPF application by declaring <xref:System.Windows.Media.DisableDpiAwarenessAttribute> at the assembly level.  
   
  [!code-csharp[DisableDpiAwareness#DisableDpiAwarenessAttribute1](~/samples/snippets/csharp/VS_Snippets_Wpf/DisableDpiAwareness/CSharp/Window1.xaml.cs#disabledpiawarenessattribute1)]
  [!code-vb[DisableDpiAwareness#DisableDpiAwarenessAttribute1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DisableDpiAwareness/visualbasic/window1.xaml.vb#disabledpiawarenessattribute1)]  
diff --git a/xml/System.Windows.Media/DrawingContext.xml b/xml/System.Windows.Media/DrawingContext.xml
index d08bcbddcef..cc478ef40aa 100644
--- a/xml/System.Windows.Media/DrawingContext.xml
+++ b/xml/System.Windows.Media/DrawingContext.xml
@@ -1082,7 +1082,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the WPF infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index d23ada9f9ae..286f4ac1594 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -69,7 +69,7 @@ Example of typefaces that are members of the "Times New Roman" font family
   
  [!code-xaml[FontSnippets#FontPackageSnippet1](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml#fontpackagesnippet1)]  
   
- A [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application can package fonts as either a content item, a resource item, or a library resource item. For more information, see [Packaging Fonts with Applications](/dotnet/framework/wpf/advanced/packaging-fonts-with-applications).  
+ A WPF application can package fonts as either a content item, a resource item, or a library resource item. For more information, see [Packaging Fonts with Applications](/dotnet/framework/wpf/advanced/packaging-fonts-with-applications).  
   
 ## Font Fallback  
  Font fallback refers to the automatic substitution of a font other than the font that is selected by the client application. There are two primary reasons why font fallback is invoked:  
@@ -78,9 +78,9 @@ Example of typefaces that are members of the "Times New Roman" font family
   
 -   The font that is specified by the client application does not contain the glyphs that are required to render text.  
   
- In[!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], the font fallback mechanism uses the default fallback font family, "Global User Interface", as the substitute font. This font is defined as a composite font, whose file name is "GlobalUserInterface.CompositeFont". For more information about composite fonts, see the Composite Fonts section in this topic.  
+ InWPF, the font fallback mechanism uses the default fallback font family, "Global User Interface", as the substitute font. This font is defined as a composite font, whose file name is "GlobalUserInterface.CompositeFont". For more information about composite fonts, see the Composite Fonts section in this topic.  
   
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] font fallback mechanism replaces previous [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] font substitution technologies.  
+ The WPF font fallback mechanism replaces previous [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] font substitution technologies.  
   
 ## Defining a Font Fallback Sequence in Code  
  You can define a font fallback sequence in your code, which lets you define an alternate font. When you create a <xref:System.Windows.Media.FontFamily> object, provide multiple font family names, separated by commas, for the <xref:System.String> parameter, such as "Comic Sans MS, Verdana". In this case, if the glyphs from the "Comic Sans MS" typeface are not available, glyphs from the "Verdana" typeface are used. If neither "Comic Sans MS" nor "Verdana" have the required glyphs, the fallback font family of the typeface is used, which is "Global User Interface" by default.  
@@ -98,7 +98,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  [!code-xaml[FontSnippets#FontFallbackSnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontFamilySnippets.xaml#fontfallbacksnippet2)]  
   
 ## Composite Fonts  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] platform provides a composite font feature to allow the construction of full range multilingual fonts, and to avoid displaying missing glyphs. Composite fonts replace the Win32 font linking, font fallback, font binding, font association, and end-user-defined characters (EUDC) mechanisms.  
+ The WPF platform provides a composite font feature to allow the construction of full range multilingual fonts, and to avoid displaying missing glyphs. Composite fonts replace the Win32 font linking, font fallback, font binding, font association, and end-user-defined characters (EUDC) mechanisms.  
   
  A composite font family is available to applications through the <xref:System.Windows.Media.FontFamily> and <xref:System.Windows.Media.Typeface> constructors just like any other font family. Each composite font family is named, and, as with other fonts, can provide localized variants of its name in multiple languages.  
   
diff --git a/xml/System.Windows.Media/FormattedText.xml b/xml/System.Windows.Media/FormattedText.xml
index eea483c7945..8a55ac50d9d 100644
--- a/xml/System.Windows.Media/FormattedText.xml
+++ b/xml/System.Windows.Media/FormattedText.xml
@@ -26,7 +26,7 @@
  ![Text displayed using FormattedText object](~/add/media/formattedtext01.jpg "Text displayed using FormattedText object")  
 Example of a formatted text string  
   
- In terms of text features in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], <xref:System.Windows.Media.FormattedText> is considered "low-level" because it processes text as graphical elements. Other aspects of text in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] handle text in the context of controls that are dedicated to text (<xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.TextBox>), implement the flow document model (see [Flow Document Overview](/dotnet/framework/wpf/advanced/flow-document-overview)), or support the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document model (see [Documents in WPF](/dotnet/framework/wpf/advanced/documents-in-wpf)).  
+ In terms of text features in WPF, <xref:System.Windows.Media.FormattedText> is considered "low-level" because it processes text as graphical elements. Other aspects of text in WPF handle text in the context of controls that are dedicated to text (<xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.TextBox>), implement the flow document model (see [Flow Document Overview](/dotnet/framework/wpf/advanced/flow-document-overview)), or support the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document model (see [Documents in WPF](/dotnet/framework/wpf/advanced/documents-in-wpf)).  
   
  Many of the setter methods in <xref:System.Windows.Media.FormattedText> have similarities to attached properties that are supported by <xref:System.Windows.Documents.TextElement>, but the <xref:System.Windows.Documents.TextElement> attached properties apply to the higher-level text support either for flow or [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)].  
   
diff --git a/xml/System.Windows.Media/GlyphTypeface.xml b/xml/System.Windows.Media/GlyphTypeface.xml
index 4df93709453..3ee4fad08b4 100644
--- a/xml/System.Windows.Media/GlyphTypeface.xml
+++ b/xml/System.Windows.Media/GlyphTypeface.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Media.GlyphTypeface> object is a low level text object that corresponds to a single face of a font family as represented by an OpenType font file, or serialized as a block of memory in a document. The correct <xref:System.Windows.Media.GlyphTypeface> to use for a run of characters in a given logical font is normally determined by the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] font system and recorded in the <xref:System.Windows.Media.GlyphRun> objects generated by the <xref:System.Windows.Media.FormattedText> object and line formatting text APIs.  
+ The <xref:System.Windows.Media.GlyphTypeface> object is a low level text object that corresponds to a single face of a font family as represented by an OpenType font file, or serialized as a block of memory in a document. The correct <xref:System.Windows.Media.GlyphTypeface> to use for a run of characters in a given logical font is normally determined by the WPF font system and recorded in the <xref:System.Windows.Media.GlyphRun> objects generated by the <xref:System.Windows.Media.FormattedText> object and line formatting text APIs.  
   
  The <xref:System.Windows.Media.GlyphTypeface> provides properties and methods for:  
   
diff --git a/xml/System.Windows.Media/Matrix.xml b/xml/System.Windows.Media/Matrix.xml
index df1257ff00a..63d24a52f89 100644
--- a/xml/System.Windows.Media/Matrix.xml
+++ b/xml/System.Windows.Media/Matrix.xml
@@ -42,7 +42,7 @@
 ## Remarks  
  A 3x3 matrix is used for transformations in a 2-D x-y plane. Affine transformation matrices can be multiplied to form any number of linear transformations, such as rotation and skew (shear), followed by translation. An affine transformation matrix has its final column equal to (0, 0, 1), so only the members in the first two columns need to be specified.  Note that vectors are expressed as row-vectors, not column vectors.  
   
- A [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] <xref:System.Windows.Media.Matrix> is stored using row-major order and has the following structure:  
+ A WPF <xref:System.Windows.Media.Matrix> is stored using row-major order and has the following structure:  
   
 ||||  
 |-|-|-|  
@@ -56,7 +56,7 @@
   
  (<xref:System.Windows.Media.Matrix.M11%2A>, <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.M22%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, <xref:System.Windows.Media.Matrix.OffsetY%2A>)  
   
- Although you can use a <xref:System.Windows.Media.Matrix> structure directly to translate individual points, or with a <xref:System.Windows.Media.MatrixTransform> to transform objects, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] also provides a set of classes that enable you to transform objects without working directly with matrices: <xref:System.Windows.Media.RotateTransform>, <xref:System.Windows.Media.ScaleTransform>, <xref:System.Windows.Media.SkewTransform>, and <xref:System.Windows.Media.TranslateTransform>.  
+ Although you can use a <xref:System.Windows.Media.Matrix> structure directly to translate individual points, or with a <xref:System.Windows.Media.MatrixTransform> to transform objects, WPF also provides a set of classes that enable you to transform objects without working directly with matrices: <xref:System.Windows.Media.RotateTransform>, <xref:System.Windows.Media.ScaleTransform>, <xref:System.Windows.Media.SkewTransform>, and <xref:System.Windows.Media.TranslateTransform>.  
   
 <a name="xamlAttributeUsage_Matrix"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Media/RenderCapability.xml b/xml/System.Windows.Media/RenderCapability.xml
index 1d1c1c8d65b..291961aa08a 100644
--- a/xml/System.Windows.Media/RenderCapability.xml
+++ b/xml/System.Windows.Media/RenderCapability.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A rendering tier defines a level of graphics hardware capability and performance for a device that runs a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application. The features of the graphics hardware that most affect the rendering tier levels are the following:  
+ A rendering tier defines a level of graphics hardware capability and performance for a device that runs a WPF application. The features of the graphics hardware that most affect the rendering tier levels are the following:  
   
 -   Video RAM: The amount of video memory on the graphics hardware determines the size and number of buffers that can be used for compositing graphics.  
   
@@ -31,7 +31,7 @@
   
 -   Multitexture Support: Multitexture support refers to the ability to apply two or more distinct textures during a blending operation on a 3D graphics object. The degree of multitexture support is determined by the number of multitexture units on the graphics hardware.  
   
- The pixel shader, vertex shader, and multitexture features are used to define specific DirectX version levels, which, in turn, are used to define the different rendering tiers in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For a full description of the rendering tiers, see [Graphics Rendering Tiers](/dotnet/framework/wpf/advanced/graphics-rendering-tiers).  
+ The pixel shader, vertex shader, and multitexture features are used to define specific DirectX version levels, which, in turn, are used to define the different rendering tiers in WPF. For a full description of the rendering tiers, see [Graphics Rendering Tiers](/dotnet/framework/wpf/advanced/graphics-rendering-tiers).  
   
  ]]></format>
     </remarks>
@@ -254,8 +254,8 @@
 |Return value|Rendering tier|Notes|  
 |------------------|--------------------|-----------|  
 |0x00000000|0|No graphics hardware acceleration is available for the application on the device. All graphics features use software acceleration. The DirectX version level is less than version 9.0.|  
-|0x00010000|1|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
-|0x00020000|2|Most of the graphics features of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] will use hardware acceleration provided the necessary system resources have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
+|0x00010000|1|Most of the graphics features of WPF will use hardware acceleration if the necessary system resources are available and have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
+|0x00020000|2|Most of the graphics features of WPF will use hardware acceleration provided the necessary system resources have not been exhausted. This corresponds to a DirectX version that is greater than or equal to 9.0.|  
   
  The following table shows the differences in graphics hardware requirements for rendering tier 1 and rendering tier 2:  
   
diff --git a/xml/System.Windows.Media/RenderOptions.xml b/xml/System.Windows.Media/RenderOptions.xml
index 82f27b4767f..9066232ceb1 100644
--- a/xml/System.Windows.Media/RenderOptions.xml
+++ b/xml/System.Windows.Media/RenderOptions.xml
@@ -111,7 +111,7 @@
 ## Remarks  
  This attached property is supported by <xref:System.Windows.Media.TileBrush> and its derived types. It is intended to be used with brushes that have intermediate surfaces, such as <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush>. It only has an effect when the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> property is set to <xref:System.Windows.Media.CachingHint.Cache>.  
   
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching the content provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
+ By default, WPF does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching the content provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of WPF is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
   
  By setting the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> attached property on the brush to <xref:System.Windows.Media.CachingHint.Cache>, you can increase performance by using cached versions of the tiled brush objects.  
   
@@ -184,7 +184,7 @@
 ## Remarks  
  This attached property is supported by <xref:System.Windows.Media.TileBrush> and its derived types. It is intended to be used with brushes that have intermediate surfaces, such as <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush>. It only has an effect when the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> property is set to <xref:System.Windows.Media.CachingHint.Cache>.  
   
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching the content provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way the default behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
+ By default, WPF does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching the content provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way the default behavior of WPF is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
   
  By setting the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> attached property on the brush to <xref:System.Windows.Media.CachingHint.Cache>, you can increase performance by using cached versions of the tiled brush objects.  
   
@@ -257,7 +257,7 @@
 ## Remarks  
  This attached property is supported by <xref:System.Windows.Media.TileBrush> and its derived types. It is intended to be used with brushes that have intermediate surfaces, such as <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush>.  
   
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
+ By default, WPF does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of WPF is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
   
  By setting the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> attached property of the brush to <xref:System.Windows.Media.CachingHint.Cache>, you can increase performance by using cached versions of the tiled brush objects.  
   
@@ -944,7 +944,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
+ By default, WPF does not cache the rendered contents of <xref:System.Windows.Media.DrawingBrush> and <xref:System.Windows.Media.VisualBrush> objects. In static scenarios, where neither the contents nor the use of the brush in the scene is changing, not caching provides a benefit because it conserves video memory. When a brush with static content is used in a non-static way, the default behavior of WPF is to re-render all the content of the brush every frame, even though the content is unchanging. For example, this will happen when a static <xref:System.Windows.Media.DrawingBrush> or <xref:System.Windows.Media.VisualBrush> is mapped to the surface of a rotating 3D object. Re-rendering the static content can have a negative impact on performance.  
   
  By setting the <xref:System.Windows.Media.RenderOptions.CachingHint%2A> attached property of the brush to <xref:System.Windows.Media.CachingHint.Cache>, you can increase performance by using cached versions of the tiled brush objects.  
   
diff --git a/xml/System.Windows.Media/SolidColorBrush.xml b/xml/System.Windows.Media/SolidColorBrush.xml
index 2bbdcf86283..be8144ec6a3 100644
--- a/xml/System.Windows.Media/SolidColorBrush.xml
+++ b/xml/System.Windows.Media/SolidColorBrush.xml
@@ -331,7 +331,7 @@
       </Parameters>
       <Docs>
         <param name="reader">The binary reader to read the <see cref="T:System.Windows.Media.SolidColorBrush" /> from.</param>
-        <summary>This member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the WPF infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The deserialized <see cref="T:System.Windows.Media.SolidColorBrush" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media/Visual.xml b/xml/System.Windows.Media/Visual.xml
index 592b6e1f0ee..106de7ba793 100644
--- a/xml/System.Windows.Media/Visual.xml
+++ b/xml/System.Windows.Media/Visual.xml
@@ -22,9 +22,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Media.Visual> class is the basic abstraction from which every <xref:System.Windows.FrameworkElement> object derives. It also serves as the entry point for writing new controls in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], and in many ways can be thought of as an equivalent of a window handle (HWND) in the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] application model.  
+ The <xref:System.Windows.Media.Visual> class is the basic abstraction from which every <xref:System.Windows.FrameworkElement> object derives. It also serves as the entry point for writing new controls in WPF, and in many ways can be thought of as an equivalent of a window handle (HWND) in the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] application model.  
   
- The <xref:System.Windows.Media.Visual> object is a core [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] object, whose primary role is to provide rendering support. User interface controls, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBox>, derive from the <xref:System.Windows.Media.Visual> class, and use the <xref:System.Windows.Media.Visual> defined properties for persisting their rendering data. The <xref:System.Windows.Media.Visual> object provides support for the following:  
+ The <xref:System.Windows.Media.Visual> object is a core WPF object, whose primary role is to provide rendering support. User interface controls, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBox>, derive from the <xref:System.Windows.Media.Visual> class, and use the <xref:System.Windows.Media.Visual> defined properties for persisting their rendering data. The <xref:System.Windows.Media.Visual> object provides support for the following:  
   
 -   Output display: Rendering the persisted, serialized drawing content of a visual.  
   
@@ -36,7 +36,7 @@
   
 -   Bounding box calculations: Determining the bounding rectangle of a visual.  
   
- Architecturally, the <xref:System.Windows.Media.Visual> object does not include support for other application development requirements / [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] features that are not immediately related to its rendering, such as the following:  
+ Architecturally, the <xref:System.Windows.Media.Visual> object does not include support for other application development requirements / WPF features that are not immediately related to its rendering, such as the following:  
   
 -   Event handling  
   
@@ -48,7 +48,7 @@
   
 -   Globalization  
   
- <xref:System.Windows.Media.Visual> is provided as a public abstract class from which further classes can be derived. The following illustration shows the hierarchy of the existing visual objects that are defined in the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] architecture.  
+ <xref:System.Windows.Media.Visual> is provided as a public abstract class from which further classes can be derived. The following illustration shows the hierarchy of the existing visual objects that are defined in the WPF architecture.  
   
  ![Diagram of classes derived from the Visual object](~/add/media/visualclass01.png "Diagram of classes derived from the Visual object")  
 Visual class hierarchy  
@@ -1312,9 +1312,9 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -1345,9 +1345,9 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/VisualCollection.xml b/xml/System.Windows.Media/VisualCollection.xml
index 3f102f8a89b..2b10981ae42 100644
--- a/xml/System.Windows.Media/VisualCollection.xml
+++ b/xml/System.Windows.Media/VisualCollection.xml
@@ -685,7 +685,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IEnumerable.GetEnumerator" />.</summary>
+        <summary>This member supports the WPF infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IEnumerable.GetEnumerator" />.</summary>
         <returns>An object that can be used to iterate through the collection.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media/VisualTreeHelper.xml b/xml/System.Windows.Media/VisualTreeHelper.xml
index e9ee2ce9234..8c416f8d6f3 100644
--- a/xml/System.Windows.Media/VisualTreeHelper.xml
+++ b/xml/System.Windows.Media/VisualTreeHelper.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Nodes in the visual tree can be either <xref:System.Windows.Media.Visual> or <xref:System.Windows.Media.Media3D.Visual3D> objects. Methods that are specific to a type of visual object are typed as either <xref:System.Windows.Media.Visual> or <xref:System.Windows.Media.Media3D.Visual3D>. However, some methods in the <xref:System.Windows.Media.VisualTreeHelper> class can accept a <xref:System.Windows.DependencyObject> value that represents either type of visual object.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] supports programmatic access to several different tree structures of objects. Primarily, this is exposed as a visual tree and a logical tree. In some cases, the logical tree is a more useful representation of the elements in a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application, but conceptually the logical tree is implemented at a level beyond the <xref:System.Windows.Media.Visual> class. Unlike the visual tree, the logical tree can represent nonvisual data objects, such as <xref:System.Windows.Documents.ListItem>. For more information on the logical tree, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf). The logical tree also is supported by a similar utility method class, <xref:System.Windows.LogicalTreeHelper>.  
+ WPF supports programmatic access to several different tree structures of objects. Primarily, this is exposed as a visual tree and a logical tree. In some cases, the logical tree is a more useful representation of the elements in a WPF application, but conceptually the logical tree is implemented at a level beyond the <xref:System.Windows.Media.Visual> class. Unlike the visual tree, the logical tree can represent nonvisual data objects, such as <xref:System.Windows.Documents.ListItem>. For more information on the logical tree, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf). The logical tree also is supported by a similar utility method class, <xref:System.Windows.LogicalTreeHelper>.  
   
    
   
@@ -771,9 +771,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
@@ -808,9 +808,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
- However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
+ However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
index 8d60cc9453c..eba96de481f 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
@@ -185,7 +185,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Most of the attached properties defined by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] that apply <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> do so with the default of <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> as `false`.  
+ Most of the attached properties defined by WPF that apply <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> do so with the default of <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> as `false`.  
   
 <a name="xamlTextUsage_IncludeDescendants"></a>   
 ## XAML Text Usage  
diff --git a/xml/System.Windows/AutoResizedEventHandler.xml b/xml/System.Windows/AutoResizedEventHandler.xml
index 9c5b2631e13..b757d81f816 100644
--- a/xml/System.Windows/AutoResizedEventHandler.xml
+++ b/xml/System.Windows/AutoResizedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Interop.HwndSource.AutoResized> event is raised when the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] layout system causes a <xref:System.Windows.Interop.HwndSource> to resize automatically. A typical handler implementation would communicate size changes to the HWND contained within the <xref:System.Windows.Interop.HwndSource>.  
+ The <xref:System.Windows.Interop.HwndSource.AutoResized> event is raised when the WPF layout system causes a <xref:System.Windows.Interop.HwndSource> to resize automatically. A typical handler implementation would communicate size changes to the HWND contained within the <xref:System.Windows.Interop.HwndSource>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/BaseValueSource.xml b/xml/System.Windows/BaseValueSource.xml
index 913d987880d..3c6618e4832 100644
--- a/xml/System.Windows/BaseValueSource.xml
+++ b/xml/System.Windows/BaseValueSource.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  This enumeration is used by a property within the <xref:System.Windows.ValueSource> structure, which in turn is obtained by calling a <xref:System.Windows.DependencyPropertyHelper.GetValueSource%2A> method against a particular dependency property.  
   
- Each value of this enumeration indicates that a particular aspect of the overall [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system was responsible for the effective value determination of a certain dependency property value on a specific dependency object. To learn more about the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system and the precedence at which each aspect of the property system operates, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
+ Each value of this enumeration indicates that a particular aspect of the overall WPF property system was responsible for the effective value determination of a certain dependency property value on a specific dependency object. To learn more about the WPF property system and the precedence at which each aspect of the property system operates, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
   
  The value Default is not the default value of the enumeration.  
   
diff --git a/xml/System.Windows/ColorConvertedBitmapExtension.xml b/xml/System.Windows/ColorConvertedBitmapExtension.xml
index d5af34a4476..721b3670334 100644
--- a/xml/System.Windows/ColorConvertedBitmapExtension.xml
+++ b/xml/System.Windows/ColorConvertedBitmapExtension.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
   
 <a name="xamlTextUsage_ColorConvertedBitmapExtension"></a>   
 ## XAML Text Usage  
diff --git a/xml/System.Windows/ContentOperations.xml b/xml/System.Windows/ContentOperations.xml
index 6e547fed868..8cd06ef68f3 100644
--- a/xml/System.Windows/ContentOperations.xml
+++ b/xml/System.Windows/ContentOperations.xml
@@ -57,7 +57,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Most practical <xref:System.Windows.ContentElement> derived classes in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] are also a <xref:System.Windows.FrameworkContentElement> derived class. For these classes, the <xref:System.Windows.FrameworkContentElement.Parent%2A> property should be used instead.  
+ Most practical <xref:System.Windows.ContentElement> derived classes in WPF are also a <xref:System.Windows.FrameworkContentElement> derived class. For these classes, the <xref:System.Windows.FrameworkContentElement.Parent%2A> property should be used instead.  
   
  <xref:System.Windows.FrameworkContentElement.Parent%2A> returns the parent element in the logical tree, which might not be the same element as returned by <xref:System.Windows.ContentOperations.GetParent%2A>. <xref:System.Windows.ContentOperations.GetParent%2A> exists specifically to correct for certain architectural issues whereby a <xref:System.Windows.ContentElement> class that is not also a <xref:System.Windows.FrameworkContentElement> exists in a tree that is not strictly speaking either the logical tree or the visual tree.  
   
diff --git a/xml/System.Windows/DependencyObject.xml b/xml/System.Windows/DependencyObject.xml
index 370de3ee55c..87884f5edf0 100644
--- a/xml/System.Windows/DependencyObject.xml
+++ b/xml/System.Windows/DependencyObject.xml
@@ -39,7 +39,7 @@
   
 -   Dependency property hosting support. You register a dependency property by calling the <xref:System.Windows.DependencyProperty.Register%2A> method, and storing the method's return value as a public static field in your class.  
   
--   Attached property hosting support. You register an attached property by calling the <xref:System.Windows.DependencyProperty.RegisterAttached%2A> method, and storing the method's return value as a public static read-only field in your class. (There are also additional member requirements; note that this represents a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] specific implementation for attached properties. For details, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).) Your attached property can then be set on any class that derives from <xref:System.Windows.DependencyObject>.  
+-   Attached property hosting support. You register an attached property by calling the <xref:System.Windows.DependencyProperty.RegisterAttached%2A> method, and storing the method's return value as a public static read-only field in your class. (There are also additional member requirements; note that this represents a WPF specific implementation for attached properties. For details, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).) Your attached property can then be set on any class that derives from <xref:System.Windows.DependencyObject>.  
   
 -   Get, set, and clear utility methods for values of any dependency properties that exist on the <xref:System.Windows.DependencyObject>.  
   
@@ -199,7 +199,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In addition to being explicitly invoked through calling <xref:System.Windows.DependencyObject.CoerceValue%2A>, the <xref:System.Windows.CoerceValueCallback> for a dependency property is also invoked internally whenever the dependency property value is being re-evaluated by the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system.  
+ In addition to being explicitly invoked through calling <xref:System.Windows.DependencyObject.CoerceValue%2A>, the <xref:System.Windows.CoerceValueCallback> for a dependency property is also invoked internally whenever the dependency property value is being re-evaluated by the WPF property system.  
   
  When you invoke the <xref:System.Windows.DependencyObject.CoerceValue%2A> method, you are ultimately invoking the coerce value callback for the property that you specify. Typically you will invoke <xref:System.Windows.DependencyObject.CoerceValue%2A> only if you know that a coerce value callback exists, and if you know the callback's criteria for coercion.  
   
@@ -302,7 +302,7 @@
         </remarks>
         <block subset="none" type="overrides">
           <para>
-            <see cref="T:System.Windows.DependencyObject" /> overrides and then seals two basic <see cref="T:System.Object" /> methods: <see cref="M:System.Windows.DependencyObject.Equals(System.Object)" /> and <see cref="M:System.Windows.DependencyObject.GetHashCode" />. The overrides call the <see cref="T:System.Object" /> implementations, resulting in an object equality behavior. The purpose of these deliberate overrides is to prevent derived classes from trying to define a value equality for a <see cref="T:System.Windows.DependencyObject" />. Value equalities for <see cref="T:System.Windows.DependencyObject" /> will never be accurate because of the innate property value-changing capabilities of a <see cref="T:System.Windows.DependencyObject" /> and its dependency properties. This includes fundamental [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] features such as data binding and the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system.</para>
+            <see cref="T:System.Windows.DependencyObject" /> overrides and then seals two basic <see cref="T:System.Object" /> methods: <see cref="M:System.Windows.DependencyObject.Equals(System.Object)" /> and <see cref="M:System.Windows.DependencyObject.GetHashCode" />. The overrides call the <see cref="T:System.Object" /> implementations, resulting in an object equality behavior. The purpose of these deliberate overrides is to prevent derived classes from trying to define a value equality for a <see cref="T:System.Windows.DependencyObject" />. Value equalities for <see cref="T:System.Windows.DependencyObject" /> will never be accurate because of the innate property value-changing capabilities of a <see cref="T:System.Windows.DependencyObject" /> and its dependency properties. This includes fundamental WPF features such as data binding and the WPF property system.</para>
         </block>
       </Docs>
     </Member>
@@ -330,7 +330,7 @@
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
           <para>
-            <see cref="T:System.Windows.DependencyObject" /> overrides and then seals two <see cref="T:System.Object" /> methods: <see cref="M:System.Windows.DependencyObject.Equals(System.Object)" /> and <see cref="M:System.Windows.DependencyObject.GetHashCode" />. The overrides call the <see cref="T:System.Object" /> implementations, resulting in an object equality behavior. The purpose of these deliberate overrides is to prevent derived classes from trying to define a value equality for a <see cref="T:System.Windows.DependencyObject" />. Value equalities for <see cref="T:System.Windows.DependencyObject" /> will never be accurate because of the innate property value-changing capabilities of a <see cref="T:System.Windows.DependencyObject" /> and its dependency properties. This includes fundamental [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] features such as data binding and the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system.</para>
+            <see cref="T:System.Windows.DependencyObject" /> overrides and then seals two <see cref="T:System.Object" /> methods: <see cref="M:System.Windows.DependencyObject.Equals(System.Object)" /> and <see cref="M:System.Windows.DependencyObject.GetHashCode" />. The overrides call the <see cref="T:System.Object" /> implementations, resulting in an object equality behavior. The purpose of these deliberate overrides is to prevent derived classes from trying to define a value equality for a <see cref="T:System.Windows.DependencyObject" />. Value equalities for <see cref="T:System.Windows.DependencyObject" /> will never be accurate because of the innate property value-changing capabilities of a <see cref="T:System.Windows.DependencyObject" /> and its dependency properties. This includes fundamental WPF features such as data binding and the WPF property system.</para>
         </block>
       </Docs>
     </Member>
@@ -538,7 +538,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>Always call the base implementation. Failure to do this will significantly disable the entire [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system, causing incorrect values to be reported.</para>
+          <para>Always call the base implementation. Failure to do this will significantly disable the entire WPF property system, causing incorrect values to be reported.</para>
         </block>
         <altmember cref="T:System.Windows.FrameworkElement" />
       </Docs>
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index 9c0b5a08ac3..1380b9ec996 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -49,13 +49,13 @@
   
 -   The property can report when the previous value of the property has been changed and the property value can be coerced. For more information, see [Dependency Property Callbacks and Validation](/dotnet/framework/wpf/advanced/dependency-property-callbacks-and-validation).  
   
--   The property reports information to [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], such as whether changing a property value should require the layout system to recompose the visuals for an element.  
+-   The property reports information to WPF, such as whether changing a property value should require the layout system to recompose the visuals for an element.  
   
 -   The property receives support in the [!INCLUDE[wpfdesigner_current_long](~/includes/wpfdesigner-current-long-md.md)].  For example, the property can be edited in the **Properties** window.  
   
  To learn more about dependency properties, see [Dependency Properties Overview](/dotnet/framework/wpf/advanced/dependency-properties-overview). If you want properties on your custom types to support the capabilities in the preceding list, you should create a dependency property.  To learn how to create custom dependency properties, see [Custom Dependency Properties](/dotnet/framework/wpf/advanced/custom-dependency-properties).  
   
- An attached property is a property that enables any object to report information to the type that defines the attached property. In [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], any type that inherits from <xref:System.Windows.DependencyObject> can use an attached property regardless of whether the type inherits from the type that defines the property. An attached property is a feature of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language.  To set an attached property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], use the *ownerType*.*propertyName* syntax. An example of an attached property is the <xref:System.Windows.Controls.DockPanel.Dock%2A?displayProperty=nameWithType> property. If you want to create a property that can be used on all <xref:System.Windows.DependencyObject> types, then you should create an attached property. To learn more about attached properties, including how to create them, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property that enables any object to report information to the type that defines the attached property. In WPF, any type that inherits from <xref:System.Windows.DependencyObject> can use an attached property regardless of whether the type inherits from the type that defines the property. An attached property is a feature of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language.  To set an attached property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], use the *ownerType*.*propertyName* syntax. An example of an attached property is the <xref:System.Windows.Controls.DockPanel.Dock%2A?displayProperty=nameWithType> property. If you want to create a property that can be used on all <xref:System.Windows.DependencyObject> types, then you should create an attached property. To learn more about attached properties, including how to create them, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
 <a name="xamlAttributeUsage_DependencyProperty"></a>   
 ## XAML Attribute Usage  
@@ -144,7 +144,7 @@
   
  The return value of this method is typically used to declare and expose the dependency property by storing a dependency property identifier. The identifier provides access to the dependency property if you want to call property system APIs against the dependency property, particularly as it exists on the adding owner class. The same property name for both original owner and added owner should be used to indicate the similar functionality. You should use the <xref:System.Windows.DependencyProperty> return value of the <xref:System.Windows.DependencyProperty.AddOwner%2A> method to define the dependency property identifier, and also to declare CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
   
- The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating the dependency properties that are declared within [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> based on the original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a new static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
+ The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating the dependency properties that are declared within WPF. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> based on the original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a new static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
   
  ]]></format>
         </remarks>
@@ -184,11 +184,11 @@
   
  The return value of this method is used to declare and expose the dependency property, particularly as it exists on the adding owner class. Generally, the same property name for both original owner and added owner should be used to indicate the similar functionality. It is good practice to expose the identifiers, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>.  
   
- The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating APIs declared within [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> on original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
+ The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating APIs declared within WPF. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> on original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
   
  The added owner's dependency property identifier should be used for operations such as <xref:System.Windows.DependencyObject.GetValue%2A>. However, type-specific operations involving either types or instances of the class that was added as owner with different metadata will still return the expected results even if the original (not the added owner's) dependency property identifier is specified in calls to methods such as <xref:System.Windows.DependencyObject.GetValue%2A> or <xref:System.Windows.DependencyProperty.GetMetadata%2A>. The metadata for the added owner is perpetuated by the <xref:System.Windows.DependencyProperty.AddOwner%2A> call itself, not necessarily referenced exclusively by the adding owner class identifier field. Nevertheless, it is good practice to expose the  identifier, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>, because failing to do so creates disparity between the CLR and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representations of your properties.  
   
- The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist. Only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics, such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A>, are replaced if they are specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
+ The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist. Only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics, such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A>, are replaced if they are specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by WPF dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
   
  ]]></format>
         </remarks>
@@ -634,7 +634,7 @@
   
  After metadata for a particular derived class override is established with this method, subsequent attempts to override metadata on this same derived class will raise an exception.  
   
- The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist; only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A> are replaced if specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
+ The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist; only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A> are replaced if specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by WPF dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
   
  ]]></format>
         </remarks>
@@ -1027,7 +1027,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached properties as dependency properties. Because the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1085,7 +1085,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached properties as dependency properties. Because the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1134,7 +1134,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] implements attached properties as dependency properties. Because the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1317,7 +1317,7 @@
 ## Remarks  
  This method returns the type <xref:System.Windows.DependencyPropertyKey>, whereas <xref:System.Windows.DependencyProperty.RegisterAttached%2A> returns the type <xref:System.Windows.DependencyProperty>. Typically, the keys that represent read-only properties are not made public, because the keys can be used to set the dependency property value by calling <xref:System.Windows.DependencyObject.SetValue%28System.Windows.DependencyPropertyKey%2CSystem.Object%29>. Your class design will affect your requirements, but it is generally recommended to limit the access and visibility of any <xref:System.Windows.DependencyPropertyKey> to only those parts of your code that are necessary to set that dependency property as part of class or application logic. It is also recommended that you expose a dependency property identifier for the read-only dependency property, by exposing the value of <xref:System.Windows.DependencyPropertyKey.DependencyProperty%2A?displayProperty=nameWithType> as a `public static readonly` field on your class.  
   
- Read-only dependency properties are a fairly typical scenario both in the existing API and for customization scenarios, because other [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] features might require a dependency property even if that property is not intended to be settable by callers. You can use the value of a read-only dependency property as the basis for other property system operations that take a dependency property, such as basing a <xref:System.Windows.Trigger> on the dependency property in a style.  
+ Read-only dependency properties are a fairly typical scenario both in the existing API and for customization scenarios, because other WPF features might require a dependency property even if that property is not intended to be settable by callers. You can use the value of a read-only dependency property as the basis for other property system operations that take a dependency property, such as basing a <xref:System.Windows.Trigger> on the dependency property in a style.  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1431,12 +1431,12 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies a static value that is used by the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system rather than <see langword="null" /> to indicate that the property exists, but does not have its value set by the property system.</summary>
+        <summary>Specifies a static value that is used by the WPF property system rather than <see langword="null" /> to indicate that the property exists, but does not have its value set by the property system.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.DependencyProperty.UnsetValue> is a sentinel value that is used for scenarios where the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system is unable to determine a requested <xref:System.Windows.DependencyProperty> value. <xref:System.Windows.DependencyProperty.UnsetValue> is used rather than `null`, because `null` could be a valid property value, as well as a valid (and frequently used) <xref:System.Windows.PropertyMetadata.DefaultValue%2A>.  
+ <xref:System.Windows.DependencyProperty.UnsetValue> is a sentinel value that is used for scenarios where the WPF property system is unable to determine a requested <xref:System.Windows.DependencyProperty> value. <xref:System.Windows.DependencyProperty.UnsetValue> is used rather than `null`, because `null` could be a valid property value, as well as a valid (and frequently used) <xref:System.Windows.PropertyMetadata.DefaultValue%2A>.  
   
  <xref:System.Windows.DependencyProperty.UnsetValue> is never returned out of <xref:System.Windows.DependencyObject.GetValue%2A?displayProperty=nameWithType>. When you call <xref:System.Windows.DependencyObject.GetValue%2A?displayProperty=nameWithType> on a dependency property on a <xref:System.Windows.DependencyObject> instance, one of the following applies:  
   
diff --git a/xml/System.Windows/DependencyPropertyChangedEventHandler.xml b/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
index 6a285bc6be6..71fa419476c 100644
--- a/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
+++ b/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
@@ -33,7 +33,7 @@
   
  An event that uses this handler is exposed as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event, not as a routed event. Typically these events follow the naming pattern `Is(`*PropertyName*`)Changed`, where *PropertyName* is the <xref:System.Windows.DependencyProperty.Name%2A?displayProperty=nameWithType> of the property that changed. The arguments of the event are used to query the old and new value of the property, as reported by the particular event. Typically there is a 1:1 correspondence between properties that change and a particular event that reports the change. It is also possible, though uncommon, to have the same event report changes to more than one property. In this case, the <xref:System.Windows.DependencyPropertyChangedEventArgs> should be checked to determine the property that changed.  
   
- The event data class <xref:System.Windows.DependencyPropertyChangedEventArgs> has a wider usage than just this delegate. <xref:System.Windows.DependencyPropertyChangedEventArgs> is also used to communicate data for <xref:System.Windows.PropertyChangedCallback> implementations, which are part of the customization features and internals of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system, and by the <xref:System.Windows.DependencyObject.OnPropertyChanged%2A> virtual method, which can be overridden to provide class-specific notifications whenever any dependency property on the object changes.  
+ The event data class <xref:System.Windows.DependencyPropertyChangedEventArgs> has a wider usage than just this delegate. <xref:System.Windows.DependencyPropertyChangedEventArgs> is also used to communicate data for <xref:System.Windows.PropertyChangedCallback> implementations, which are part of the customization features and internals of the WPF property system, and by the <xref:System.Windows.DependencyObject.OnPropertyChanged%2A> virtual method, which can be overridden to provide class-specific notifications whenever any dependency property on the object changes.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/DependencyPropertyHelper.xml b/xml/System.Windows/DependencyPropertyHelper.xml
index 04ff94d3340..45ccd4ec936 100644
--- a/xml/System.Windows/DependencyPropertyHelper.xml
+++ b/xml/System.Windows/DependencyPropertyHelper.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The[!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system is fairly complex, and relies on rationalizing the values that potentially come from a variety of inputs, based on an established value determination precedence. Because these sources potentially come from run-time code, from compiled markup, or even from run-time user settings, it can be useful to know exactly which participant in the dependency property value system established the value you obtain when calling <xref:System.Windows.DependencyObject.GetValue%2A> at run-time on that property. If the value came from a different source than you had intended, you might need to adjust some aspect of your application. The value source might be a style, a theme, a local value, an animation, a binding, or a run-time based value such as system settings through themes or system resources. For more information, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
+ TheWPF property system is fairly complex, and relies on rationalizing the values that potentially come from a variety of inputs, based on an established value determination precedence. Because these sources potentially come from run-time code, from compiled markup, or even from run-time user settings, it can be useful to know exactly which participant in the dependency property value system established the value you obtain when calling <xref:System.Windows.DependencyObject.GetValue%2A> at run-time on that property. If the value came from a different source than you had intended, you might need to adjust some aspect of your application. The value source might be a style, a theme, a local value, an animation, a binding, or a run-time based value such as system settings through themes or system resources. For more information, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
   
  Another mechanism that reports on the property in general, rather than a specific instance of the property on an object, is the property metadata. The property metadata is findable by calling <xref:System.Windows.DependencyProperty.GetMetadata%2A> and examining the returned <xref:System.Windows.PropertyMetadata> (or one of several possible derived classes that the returned property metadata is castable to).  
   
diff --git a/xml/System.Windows/DragEventHandler.xml b/xml/System.Windows/DragEventHandler.xml
index 0b4b12af653..be38c61fc1c 100644
--- a/xml/System.Windows/DragEventHandler.xml
+++ b/xml/System.Windows/DragEventHandler.xml
@@ -47,7 +47,7 @@
   
 -   <xref:System.Windows.DragDrop.PreviewDrop?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.DragEnter?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows/DynamicResourceExtension.xml b/xml/System.Windows/DynamicResourceExtension.xml
index 85212c982e1..3aa430e2961 100644
--- a/xml/System.Windows/DynamicResourceExtension.xml
+++ b/xml/System.Windows/DynamicResourceExtension.xml
@@ -33,7 +33,7 @@
 ## Remarks  
  Dynamic resource references are necessary when referencing content that might change at run-time. The reasons for the content change might be application-initiated or might be external. One example is if you are including styles that rely on system resources that report user-configured preferences, such as themes, font settings and so on.  
   
- This class is a markup extension implementation. Markup extension classes in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] exist mainly to provide infrastructure support for some aspect of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by the markup extension classes are not typically called from directly user code. This class particularly supports the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. For more information about dynamic resource references, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
+ This class is a markup extension implementation. Markup extension classes in WPF exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by the markup extension classes are not typically called from directly user code. This class particularly supports the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. For more information about dynamic resource references, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
   
 <a name="xamlTextUsage_DynamicResourceExtension"></a>   
 ## XAML Text Usage  
@@ -135,7 +135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) values during object creation.  
+ This method supports WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) values during object creation.  
   
  The property to be set by the provided value must be of type <xref:System.Windows.DependencyProperty>.  
   
diff --git a/xml/System.Windows/EventManager.xml b/xml/System.Windows/EventManager.xml
index 310613770ca..3d5c250b1cd 100644
--- a/xml/System.Windows/EventManager.xml
+++ b/xml/System.Windows/EventManager.xml
@@ -62,7 +62,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- More <xref:System.Windows.RoutedEvent> objects can be registered later. This method gets a snapshot and the collection of routed events is writeable throughout an application's lifetime. The collection returned might be quite large. Even just counting the events that are part of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] APIs, the collection count is in the high hundreds.  
+ More <xref:System.Windows.RoutedEvent> objects can be registered later. This method gets a snapshot and the collection of routed events is writeable throughout an application's lifetime. The collection returned might be quite large. Even just counting the events that are part of the WPF APIs, the collection count is in the high hundreds.  
   
  ]]></format>
         </remarks>
@@ -145,7 +145,7 @@
   
  Class handlers are invoked before instance handlers. You can implement a class handler that has the behavior of marking the event as handled. Therefore, instance handlers for a class-handled event are not invoked unless the instance handlers register specifically for handled events.  
   
- Many of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] base element events provide class handling virtual methods. By overriding these methods in classes that inherit the base classes, you can implement class handling without calling <xref:System.Windows.EventManager.RegisterClassHandler%2A> in static constructors. These class handling methods typically exist for input events and have names that start with "On" and end with the name of the event being class handled.  
+ Many of the WPF base element events provide class handling virtual methods. By overriding these methods in classes that inherit the base classes, you can implement class handling without calling <xref:System.Windows.EventManager.RegisterClassHandler%2A> in static constructors. These class handling methods typically exist for input events and have names that start with "On" and end with the name of the event being class handled.  
   
  For more information about class handling, see [Marking Routed Events as Handled, and Class Handling](/dotnet/framework/wpf/advanced/marking-routed-events-as-handled-and-class-handling).  
   
@@ -201,7 +201,7 @@
   
  Class handlers are invoked before instance handlers. You can implement a class handler that has the behavior of marking the event as handled. Therefore, instance handlers for a class-handled event are not invoked unless the instance handlers register specifically for handled events.  
   
- Many of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] base element events provide class handling virtual methods. By overriding these methods in classes that inherit the base classes, you can implement class handling without calling <xref:System.Windows.EventManager.RegisterClassHandler%2A> in static constructors. These class handling methods typically exist for input events and have names that start with "On" and end with the name of the event being class handled.  
+ Many of the WPF base element events provide class handling virtual methods. By overriding these methods in classes that inherit the base classes, you can implement class handling without calling <xref:System.Windows.EventManager.RegisterClassHandler%2A> in static constructors. These class handling methods typically exist for input events and have names that start with "On" and end with the name of the event being class handled.  
   
  For more information about class handling, see [Marking Routed Events as Handled, and Class Handling](/dotnet/framework/wpf/advanced/marking-routed-events-as-handled-and-class-handling).  
   
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 442246b8e36..cd334cff5dc 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -60,7 +60,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.FrameworkContentElement> does not yet define its own rendering behavior; instantiating an actual <xref:System.Windows.FrameworkContentElement> class instance in code or markup is possible but displays nothing in a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. Rendering logic must be provided by classes that take <xref:System.Windows.FrameworkContentElement> child elements as part of their content model, or in <xref:System.Windows.FrameworkContentElement> derived classes.  
+ <xref:System.Windows.FrameworkContentElement> does not yet define its own rendering behavior; instantiating an actual <xref:System.Windows.FrameworkContentElement> class instance in code or markup is possible but displays nothing in a WPF application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. Rendering logic must be provided by classes that take <xref:System.Windows.FrameworkContentElement> child elements as part of their content model, or in <xref:System.Windows.FrameworkContentElement> derived classes.  
   
  <xref:System.Windows.FrameworkContentElement> deliberately parallels many of the same APIs as <xref:System.Windows.FrameworkElement>. Note that certain APIs found on <xref:System.Windows.FrameworkElement> will not have a <xref:System.Windows.FrameworkContentElement> equivalent. Several of the <xref:System.Windows.FrameworkElement> APIs are for functionality such as geometry representation or layout, which are not relevant for a <xref:System.Windows.FrameworkContentElement>.  
   
@@ -676,7 +676,7 @@
   
  The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented with no programmatic values from any source, the default cursor over a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application will be an arrow.  
   
- Each movement of the mouse over a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application raises a <xref:System.Windows.ContentElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor via the arguments of this event. If that happens, the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkContentElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkContentElement.ForceCursor%2A> is set.  
+ Each movement of the mouse over a WPF application raises a <xref:System.Windows.ContentElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor via the arguments of this event. If that happens, the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkContentElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkContentElement.ForceCursor%2A> is set.  
   
  If not creating a custom cursor, typically you set this property to a static property value of the <xref:System.Windows.Input.Cursors> class.  
   
@@ -1926,7 +1926,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>Always call the base implementation, as the first operation in your implementation. Failure to do this will significantly disable the entire [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system, which causes incorrect values to be reported.</para>
+          <para>Always call the base implementation, as the first operation in your implementation. Failure to do this will significantly disable the entire WPF property system, which causes incorrect values to be reported.</para>
         </block>
         <altmember cref="M:System.Windows.FrameworkElement.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)" />
         <altmember cref="M:System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)" />
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 327c2d413f5..b09a288f4a1 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -63,9 +63,9 @@
   
  <xref:System.Windows.FrameworkElement> extends <xref:System.Windows.UIElement> and adds the following capabilities:  
   
--   **Layout system definition**: <xref:System.Windows.FrameworkElement> provides specific WPF framework-level implementations for certain methods that were defined as virtual members in  <xref:System.Windows.UIElement>. Most notably, <xref:System.Windows.FrameworkElement> seals certain WPF core-level layout overrides, and instead provides a WPF framework-level equivalent that derived classes should override instead. For example, <xref:System.Windows.FrameworkElement> seals <xref:System.Windows.UIElement.ArrangeCore%2A> but provides <xref:System.Windows.FrameworkElement.ArrangeOverride%2A>. These changes reflect the fact that at the WPF framework-level there is a full layout system in place that can render any <xref:System.Windows.FrameworkElement> derived class. At the WPF core level, certain members that will structure a general [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] based layout solution are in place, but the actual engine of the layout system is not defined. For more information, see [Layout](/dotnet/framework/wpf/advanced/layout).  
+-   **Layout system definition**: <xref:System.Windows.FrameworkElement> provides specific WPF framework-level implementations for certain methods that were defined as virtual members in  <xref:System.Windows.UIElement>. Most notably, <xref:System.Windows.FrameworkElement> seals certain WPF core-level layout overrides, and instead provides a WPF framework-level equivalent that derived classes should override instead. For example, <xref:System.Windows.FrameworkElement> seals <xref:System.Windows.UIElement.ArrangeCore%2A> but provides <xref:System.Windows.FrameworkElement.ArrangeOverride%2A>. These changes reflect the fact that at the WPF framework-level there is a full layout system in place that can render any <xref:System.Windows.FrameworkElement> derived class. At the WPF core level, certain members that will structure a general WPF based layout solution are in place, but the actual engine of the layout system is not defined. For more information, see [Layout](/dotnet/framework/wpf/advanced/layout).  
   
--   **The logical tree:** The general [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] programming model is often expressed in terms of being a tree of elements. Support for expressing the tree of elements as a logical tree, and accompanying support for defining that tree in markup is implemented at the <xref:System.Windows.FrameworkElement> level. Note however that <xref:System.Windows.FrameworkElement> deliberately does not define a content model, and leaves that responsibility to derived classes. For more information, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf).  
+-   **The logical tree:** The general WPF programming model is often expressed in terms of being a tree of elements. Support for expressing the tree of elements as a logical tree, and accompanying support for defining that tree in markup is implemented at the <xref:System.Windows.FrameworkElement> level. Note however that <xref:System.Windows.FrameworkElement> deliberately does not define a content model, and leaves that responsibility to derived classes. For more information, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf).  
   
 -   **Object lifetime events:** It is often useful to know when an element is initialized (the constructor is called) or when the element is first loaded into a logical tree. <xref:System.Windows.FrameworkElement> defines several events related to object lifetime that provide useful hooks for code-behind operations that involve elements, such as adding more child elements. For more information, see [Object Lifetime Events](/dotnet/framework/wpf/advanced/object-lifetime-events).  
   
@@ -75,7 +75,7 @@
   
 -   **More animation support:** Some animation support was already defined at the WPF core level, but <xref:System.Windows.FrameworkElement> extends this by implementing <xref:System.Windows.FrameworkElement.BeginStoryboard%2A> and related members.  
   
- As can be seen from the class hierarchy, many [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] classes derive from <xref:System.Windows.FrameworkElement>, either directly or through intermediate base classes such as <xref:System.Windows.Controls.Panel> or <xref:System.Windows.Controls.Control>.  
+ As can be seen from the class hierarchy, many WPF classes derive from <xref:System.Windows.FrameworkElement>, either directly or through intermediate base classes such as <xref:System.Windows.Controls.Panel> or <xref:System.Windows.Controls.Control>.  
   
  If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
   
@@ -277,7 +277,7 @@
 ## Remarks  
  Use this method for the implementation of collections on objects that represent logical child elements of an element. Collection maintenance for child element collections might be done in property getters or setters, class handling of Changed events, constructors, or within the collection types themselves.  
   
- For control authors, manipulating the logical tree at this level is not the recommended practice, unless none of the content models for available base control classes are appropriate for your control scenario. Consider subclassing at the level of <xref:System.Windows.Controls.ContentControl>, <xref:System.Windows.Controls.ItemsControl>, and <xref:System.Windows.Controls.HeaderedItemsControl>. These classes provide a content model with particular enforcement of logical tree child elements through dedicated APIs, as well as support for other features typically desirable in a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] control such as styling through templates. For more information on how to use <xref:System.Windows.FrameworkElement.LogicalChildren%2A> and <xref:System.Windows.FrameworkElement.AddLogicalChild%2A>, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf).  
+ For control authors, manipulating the logical tree at this level is not the recommended practice, unless none of the content models for available base control classes are appropriate for your control scenario. Consider subclassing at the level of <xref:System.Windows.Controls.ContentControl>, <xref:System.Windows.Controls.ItemsControl>, and <xref:System.Windows.Controls.HeaderedItemsControl>. These classes provide a content model with particular enforcement of logical tree child elements through dedicated APIs, as well as support for other features typically desirable in a WPF control such as styling through templates. For more information on how to use <xref:System.Windows.FrameworkElement.LogicalChildren%2A> and <xref:System.Windows.FrameworkElement.AddLogicalChild%2A>, see [Trees in WPF](/dotnet/framework/wpf/advanced/trees-in-wpf).  
   
  <xref:System.Windows.FrameworkElement.AddLogicalChild%2A> may throw an exception if called at a time when the logical tree is being iterated by another process.  
   
@@ -1061,7 +1061,7 @@
   
  To revert the behavior of setting this property to the eventual default, set it to `null` again.  
   
- The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented without programmatic values from any source, the default cursor that is visually over a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application will be an arrow. However, the transient cursor changes are not set to the <xref:System.Windows.FrameworkElement.Cursor%2A> values of the elements when they are passed over. The <xref:System.Windows.FrameworkElement.Cursor%2A> property will only report non null values in cases where it was actually set, for instance through code or a style. Each movement of the mouse over a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] application raises a <xref:System.Windows.UIElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor through the arguments of this event. This is the mechanism that produces the visually apparent cursor in most cases. If a <xref:System.Windows.UIElement.QueryCursor> handler returns a cursor result, then the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkElement.ForceCursor%2A> is set.  
+ The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented without programmatic values from any source, the default cursor that is visually over a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application will be an arrow. However, the transient cursor changes are not set to the <xref:System.Windows.FrameworkElement.Cursor%2A> values of the elements when they are passed over. The <xref:System.Windows.FrameworkElement.Cursor%2A> property will only report non null values in cases where it was actually set, for instance through code or a style. Each movement of the mouse over a WPF application raises a <xref:System.Windows.UIElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor through the arguments of this event. This is the mechanism that produces the visually apparent cursor in most cases. If a <xref:System.Windows.UIElement.QueryCursor> handler returns a cursor result, then the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkElement.ForceCursor%2A> is set.  
   
  If not are not creating a custom cursor, you typically set this property to a static property value of the <xref:System.Windows.Input.Cursors> class. Setting <xref:System.Windows.FrameworkElement.Cursor%2A> in code requires one of the following:  
   
@@ -1872,7 +1872,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Templates in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] have a self-contained namescope. This is because templates are re-used, and any name defined in a template cannot remain unique when multiple instances of a control each instantiate its template. Call the <xref:System.Windows.FrameworkElement.GetTemplateChild%2A> method to return references to objects that come from the template after it is instantiated. You cannot use the <xref:System.Windows.FrameworkElement.FindName%2A?displayProperty=nameWithType> method to find items from templates because <xref:System.Windows.FrameworkElement.FindName%2A?displayProperty=nameWithType> acts in a more general scope, and there is no connection between the <xref:System.Windows.Controls.ControlTemplate> class itself and the instantiated template once it is applied.  
+ Templates in WPF have a self-contained namescope. This is because templates are re-used, and any name defined in a template cannot remain unique when multiple instances of a control each instantiate its template. Call the <xref:System.Windows.FrameworkElement.GetTemplateChild%2A> method to return references to objects that come from the template after it is instantiated. You cannot use the <xref:System.Windows.FrameworkElement.FindName%2A?displayProperty=nameWithType> method to find items from templates because <xref:System.Windows.FrameworkElement.FindName%2A?displayProperty=nameWithType> acts in a more general scope, and there is no connection between the <xref:System.Windows.Controls.ControlTemplate> class itself and the instantiated template once it is applied.  
   
  <xref:System.Windows.FrameworkTemplate.FindName%2A?displayProperty=nameWithType> supplies the same function as this method. <xref:System.Windows.FrameworkTemplate.FindName%2A?displayProperty=nameWithType> is public instead of protected, and it uses correct name-scoping considerations that allow it to access the template within an element and find named items within it. Use <xref:System.Windows.FrameworkTemplate.FindName%2A?displayProperty=nameWithType> when you need to get an element outside of its parent control.  
   
@@ -3023,7 +3023,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>The following non-compiling code shows this implementation pattern.  <c>VisualChildren</c> represents an enumerable collection property of children that your own element should define. The property can be named anything. <c>VisualChildren</c> is a placeholder name for purposes of this example, <c>VisualChildren</c> is not an API as provided by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] or a part of a naming pattern. 
+          <para>The following non-compiling code shows this implementation pattern.  <c>VisualChildren</c> represents an enumerable collection property of children that your own element should define. The property can be named anything. <c>VisualChildren</c> is a placeholder name for purposes of this example, <c>VisualChildren</c> is not an API as provided by WPF or a part of a naming pattern. 
   
  [!code-csharp[CorePseudocode#FEMeasureOverride](~/samples/snippets/csharp/VS_Snippets_Wpf/CorePseudocode/CSharp/corepseudocode.cs#femeasureoverride)]
  [!code-vb[CorePseudocode#FEMeasureOverride](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CorePseudocode/visualbasic/corepseudocode.vb#femeasureoverride)]</para>
@@ -3339,7 +3339,7 @@
   
  Typically used root elements (<xref:System.Windows.Window>, <xref:System.Windows.Controls.Page> for example) implement the interface <xref:System.Windows.Markup.INameScope>. Implementations of this interface are expected to enforce that names be unambiguous within their scope. The root elements that define this interface also define the namescope behavior boundaries for all the related APIs.  
   
- The <xref:System.Windows.FrameworkElement.Name%2A> property also serves as an identifier for other processes. For instance, the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] automation model will use <xref:System.Windows.FrameworkElement.Name%2A> as the AutomationId for clients and providers.  
+ The <xref:System.Windows.FrameworkElement.Name%2A> property also serves as an identifier for other processes. For instance, the WPF automation model will use <xref:System.Windows.FrameworkElement.Name%2A> as the AutomationId for clients and providers.  
   
  The string values used for <xref:System.Windows.FrameworkElement.Name%2A> have some restrictions, as imposed by the underlying [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive) defined by the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] specification. Most notably, a <xref:System.Windows.FrameworkElement.Name%2A> must start with a letter or the underscore character (_), and must contain only letters, digits, or underscores. For more information, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
   
@@ -3619,7 +3619,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>Always call the base implementation, as the first operation in your implementation. Failure to do this will significantly disable the entire [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system, which causes incorrect values to be reported. The specific <see cref="T:System.Windows.FrameworkElement" /> implementation is also responsible for maintaining proper state for a variety of properties that affect the visible user interface. These include invalidating the visual tree based on changes to style at appropriate times.</para>
+          <para>Always call the base implementation, as the first operation in your implementation. Failure to do this will significantly disable the entire WPF property system, which causes incorrect values to be reported. The specific <see cref="T:System.Windows.FrameworkElement" /> implementation is also responsible for maintaining proper state for a variety of properties that affect the visible user interface. These include invalidating the visual tree based on changes to style at appropriate times.</para>
         </block>
         <altmember cref="M:System.Windows.DependencyObject.OnPropertyChanged(System.Windows.DependencyPropertyChangedEventArgs)" />
         <altmember cref="T:System.Windows.PropertyChangedCallback" />
@@ -4099,7 +4099,7 @@
 ## Remarks  
  Use this method for the implementation of collections on objects that represent logical children of an element. This might be done in property getters or setters, class handlers of `Changed` events, constructors, or within the collection types themselves.  
   
- For control authors, manipulating the logical tree at this level is not the recommended practice, unless none of the provided base control class' content models are appropriate. Consider subclassing at the level of <xref:System.Windows.Controls.ContentControl>, <xref:System.Windows.Controls.ItemsControl>, and <xref:System.Windows.Controls.HeaderedItemsControl>. These classes provide a content model with particular enforcement of logical children through dedicated APIs, as well as support for other features typically desirable in a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] control such as styling through templates.  
+ For control authors, manipulating the logical tree at this level is not the recommended practice, unless none of the provided base control class' content models are appropriate. Consider subclassing at the level of <xref:System.Windows.Controls.ContentControl>, <xref:System.Windows.Controls.ItemsControl>, and <xref:System.Windows.Controls.HeaderedItemsControl>. These classes provide a content model with particular enforcement of logical children through dedicated APIs, as well as support for other features typically desirable in a WPF control such as styling through templates.  
   
    
   
diff --git a/xml/System.Windows/FrameworkPropertyMetadata.xml b/xml/System.Windows/FrameworkPropertyMetadata.xml
index 6df7beee56e..7398cf33038 100644
--- a/xml/System.Windows/FrameworkPropertyMetadata.xml
+++ b/xml/System.Windows/FrameworkPropertyMetadata.xml
@@ -911,7 +911,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Property value inheritance is a feature of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system at the WPF framework level, whereby certain dependency properties can be locally set on an element at or near the root of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element tree and then have their value inherited by all elements within the logical tree of child elements that also possess that property. Property value inheritance is not enabled by default, and enabling it does have some performance implications. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
+ Property value inheritance is a feature of the WPF property system at the WPF framework level, whereby certain dependency properties can be locally set on an element at or near the root of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element tree and then have their value inherited by all elements within the logical tree of child elements that also possess that property. Property value inheritance is not enabled by default, and enabling it does have some performance implications. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
   
 > [!NOTE]
 >  Although property value inheritance might appear to work for nonattached dependency properties, the inheritance behavior for a nonattached property through certain object-object divisions in the runtime tree is undefined. Always use <xref:System.Windows.DependencyProperty.RegisterAttached%2A> to register properties where you specify <xref:System.Windows.FrameworkPropertyMetadata.Inherits%2A> in the metadata.  
diff --git a/xml/System.Windows/FreezableCollection`1.xml b/xml/System.Windows/FreezableCollection`1.xml
index 7907763f11b..01452cdd6fa 100644
--- a/xml/System.Windows/FreezableCollection`1.xml
+++ b/xml/System.Windows/FreezableCollection`1.xml
@@ -61,7 +61,7 @@
 ### XAML Usage for FreezableCollection  
  <xref:System.Windows.FreezableCollection%601> supports a limited [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax.  
   
--   As an object element at the root, you can theoretically specify an unconstrained <xref:System.Windows.FreezableCollection%601> object element, which must also specify the [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) to declare the constraint. However, this is not a common scenario, because to do this, the <xref:System.Windows.FreezableCollection%601> must be the root element. This limitation exists because the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] can only support [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) when the element it is being set on is the root element, and you must use  on any open constraint generic if you want to instantiate a generic type in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. It is unlikely that you want a <xref:System.Windows.FreezableCollection%601> as the root element, even as loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+-   As an object element at the root, you can theoretically specify an unconstrained <xref:System.Windows.FreezableCollection%601> object element, which must also specify the [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) to declare the constraint. However, this is not a common scenario, because to do this, the <xref:System.Windows.FreezableCollection%601> must be the root element. This limitation exists because the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation in WPF can only support [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) when the element it is being set on is the root element, and you must use  on any open constraint generic if you want to instantiate a generic type in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. It is unlikely that you want a <xref:System.Windows.FreezableCollection%601> as the root element, even as loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
   
 -   If you derive from <xref:System.Windows.FreezableCollection%601> and apply a type constraint in the derived collection, the derived collection can support a variety of usages. This is possible because the constraint in your derivation eliminates the need to pass .  
   
diff --git a/xml/System.Windows/GiveFeedbackEventHandler.xml b/xml/System.Windows/GiveFeedbackEventHandler.xml
index 923f01ecbbe..1ce98fec383 100644
--- a/xml/System.Windows/GiveFeedbackEventHandler.xml
+++ b/xml/System.Windows/GiveFeedbackEventHandler.xml
@@ -35,7 +35,7 @@
   
 -   <xref:System.Windows.DragDrop.PreviewGiveFeedback?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.GiveFeedback?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows/IInputElement.xml b/xml/System.Windows/IInputElement.xml
index 44e616078fe..150fb72f264 100644
--- a/xml/System.Windows/IInputElement.xml
+++ b/xml/System.Windows/IInputElement.xml
@@ -20,7 +20,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Although this interface is public, it is not intended to be implemented in application or framework-building scenarios. This interface is public because of the inheritance requirements for connecting the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] core to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework. You can also use this interface as a casting mechanism to enforce that the input events and properties will come from either a <xref:System.Windows.FrameworkElement> or <xref:System.Windows.FrameworkContentElement>, which can be handled in the same input model. For more information, see [WPF Architecture](/dotnet/framework/wpf/advanced/wpf-architecture) and also see [Base Elements Overview](/dotnet/framework/wpf/advanced/base-elements-overview).  
+>  Although this interface is public, it is not intended to be implemented in application or framework-building scenarios. This interface is public because of the inheritance requirements for connecting the WPF core to the WPF framework. You can also use this interface as a casting mechanism to enforce that the input events and properties will come from either a <xref:System.Windows.FrameworkElement> or <xref:System.Windows.FrameworkContentElement>, which can be handled in the same input model. For more information, see [WPF Architecture](/dotnet/framework/wpf/advanced/wpf-architecture) and also see [Base Elements Overview](/dotnet/framework/wpf/advanced/base-elements-overview).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/IWeakEventListener.xml b/xml/System.Windows/IWeakEventListener.xml
index 35206f64f4d..6dfa6d7a29b 100644
--- a/xml/System.Windows/IWeakEventListener.xml
+++ b/xml/System.Windows/IWeakEventListener.xml
@@ -59,7 +59,7 @@
         <param name="e">Event data.</param>
         <summary>Receives events from the centralized event manager.</summary>
         <returns>
-          <see langword="true" /> if the listener handled the event. It is considered an error by the <see cref="T:System.Windows.WeakEventManager" /> handling in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] to register a listener for an event that the listener does not handle. Regardless, the method should return <see langword="false" /> if it receives an event that it does not recognize or handle.</returns>
+          <see langword="true" /> if the listener handled the event. It is considered an error by the <see cref="T:System.Windows.WeakEventManager" /> handling in WPF to register a listener for an event that the listener does not handle. Regardless, the method should return <see langword="false" /> if it receives an event that it does not recognize or handle.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/LostFocusEventManager.xml b/xml/System.Windows/LostFocusEventManager.xml
index e1be6f99272..04433e938c8 100644
--- a/xml/System.Windows/LostFocusEventManager.xml
+++ b/xml/System.Windows/LostFocusEventManager.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  In order to be listeners in this pattern, your listener objects must implement <xref:System.Windows.IWeakEventListener>. You do not need to implement <xref:System.Windows.IWeakEventListener> on the class that is the source of the events.  
   
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding uses this <xref:System.Windows.WeakEventManager> so that internal classes that update bindings can attach listeners for a <xref:System.Windows.UIElement.LostFocus?displayProperty=nameWithType> or <xref:System.Windows.ContentElement.LostFocus?displayProperty=nameWithType> event on an object that is the target of a binding. This supports notification for the <xref:System.Windows.Data.UpdateSourceTrigger.LostFocus> mode of data binding, without creating strong references to data binding targets.  
+ WPF data binding uses this <xref:System.Windows.WeakEventManager> so that internal classes that update bindings can attach listeners for a <xref:System.Windows.UIElement.LostFocus?displayProperty=nameWithType> or <xref:System.Windows.ContentElement.LostFocus?displayProperty=nameWithType> event on an object that is the target of a binding. This supports notification for the <xref:System.Windows.Data.UpdateSourceTrigger.LostFocus> mode of data binding, without creating strong references to data binding targets.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/PropertyMetadata.xml b/xml/System.Windows/PropertyMetadata.xml
index 3167cbc0749..05e90999a56 100644
--- a/xml/System.Windows/PropertyMetadata.xml
+++ b/xml/System.Windows/PropertyMetadata.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Property metadata can be defined and used during dependency property registration when calling the <xref:System.Windows.DependencyProperty.Register%2A> method (or variations for attached properties or read-only dependency properties), or after original owner registration when calling the <xref:System.Windows.DependencyPropertyKey.OverrideMetadata%2A> method. <xref:System.Windows.DependencyProperty.AddOwner%2A> also takes property metadata.  
   
- This class is a concrete base class that can be used in each of these calls. However, it is very common to specify metadata using one of the derived classes such as <xref:System.Windows.FrameworkPropertyMetadata>. These derived classes support more detailed metadata carried as Boolean property values, which are useful for either detecting or enabling some property system and layout behaviors that are only implemented at the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] framework level.  
+ This class is a concrete base class that can be used in each of these calls. However, it is very common to specify metadata using one of the derived classes such as <xref:System.Windows.FrameworkPropertyMetadata>. These derived classes support more detailed metadata carried as Boolean property values, which are useful for either detecting or enabling some property system and layout behaviors that are only implemented at the WPF framework level.  
   
  Several properties of this class are read-write to the object model, but can only be written prior to the instance being used in a property system operation such as <xref:System.Windows.DependencyProperty.Register%2A> or <xref:System.Windows.DependencyPropertyKey.OverrideMetadata%2A>. Each of these properties could also have been set by the constructor but are exposed so that <xref:System.Windows.PropertyMetadata.Merge%2A> method implementations can set them.  
   
diff --git a/xml/System.Windows/QueryContinueDragEventHandler.xml b/xml/System.Windows/QueryContinueDragEventHandler.xml
index 16ef2f0402d..6b4b2a43c69 100644
--- a/xml/System.Windows/QueryContinueDragEventHandler.xml
+++ b/xml/System.Windows/QueryContinueDragEventHandler.xml
@@ -35,7 +35,7 @@
   
 -   <xref:System.Windows.DragDrop.PreviewQueryContinueDrag?displayProperty=nameWithType>  
   
- This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)].  
+ This delegate is also used with the following routed events on base elements. These routed events forward the previously listed attached events to make them more accessible to the general element model in WPF.  
   
 -   <xref:System.Windows.UIElement.QueryContinueDrag?displayProperty=nameWithType>  
   
diff --git a/xml/System.Windows/ResourceDictionary.xml b/xml/System.Windows/ResourceDictionary.xml
index de4a27d6ed4..c8656dcd5aa 100644
--- a/xml/System.Windows/ResourceDictionary.xml
+++ b/xml/System.Windows/ResourceDictionary.xml
@@ -63,7 +63,7 @@
   
  In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], the <xref:System.Windows.ResourceDictionary> class is typically an implicit collection element that is the object element value of several `Resources` properties, when given in property element syntax. For details on implicit collections in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). An exception is when you want to specify a merged dictionary; for details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
   
- Another possible [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage is to declare a resource dictionary as a discrete [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, and either load it at run time with <xref:System.Windows.Markup.XamlReader.Load%2A> or include it in a (full-trust) project as a resource or loose file. In this case, <xref:System.Windows.ResourceDictionary> can be declared as an object element, serving as the root element of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. You must map the appropriate XML namespace values (default for the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] namespace and typically `x:` for the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] namespace) onto the <xref:System.Windows.ResourceDictionary> element if you plan to use it as the root element. Then you can add child elements that define the resources, each with an [x:Key](/dotnet/framework/xaml-services/x-key-directive) value.  
+ Another possible [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage is to declare a resource dictionary as a discrete [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, and either load it at run time with <xref:System.Windows.Markup.XamlReader.Load%2A> or include it in a (full-trust) project as a resource or loose file. In this case, <xref:System.Windows.ResourceDictionary> can be declared as an object element, serving as the root element of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. You must map the appropriate XML namespace values (default for the WPF namespace and typically `x:` for the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] namespace) onto the <xref:System.Windows.ResourceDictionary> element if you plan to use it as the root element. Then you can add child elements that define the resources, each with an [x:Key](/dotnet/framework/xaml-services/x-key-directive) value.  
   
 <a name="xamlImplicitCollectionUsage_ResourceDictionary"></a>   
 ## XAML Implicit Collection Usage  
diff --git a/xml/System.Windows/RoutedEventHandler.xml b/xml/System.Windows/RoutedEventHandler.xml
index 9fc8ac5e066..680a3a9c5c2 100644
--- a/xml/System.Windows/RoutedEventHandler.xml
+++ b/xml/System.Windows/RoutedEventHandler.xml
@@ -37,7 +37,7 @@
   
  If you do intend to take advantage of the inherent features of routed events and write your handlers accordingly, the two most important properties of the event data that you will work with when writing event handlers are <xref:System.Windows.RoutedEventArgs.Source%2A> and <xref:System.Windows.RoutedEventArgs.Handled%2A>.  
   
- For certain combinations of input events and [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] control classes, the element that raises the event is not the first element that has the opportunity to handle it. If the input event has a Preview version of the event, then the root of the element tree has first opportunity, can set <xref:System.Windows.RoutedEventArgs.Handled%2A> to `true` in the shared event data, and can influence how the input event is reported to remaining elements in its event route. The Preview handling behavior can give the appearance that a particular routed event is not raised as expected. For more information, see [Preview Events](/dotnet/framework/wpf/advanced/preview-events) and [Input Overview](/dotnet/framework/wpf/advanced/input-overview).  
+ For certain combinations of input events and WPF control classes, the element that raises the event is not the first element that has the opportunity to handle it. If the input event has a Preview version of the event, then the root of the element tree has first opportunity, can set <xref:System.Windows.RoutedEventArgs.Handled%2A> to `true` in the shared event data, and can influence how the input event is reported to remaining elements in its event route. The Preview handling behavior can give the appearance that a particular routed event is not raised as expected. For more information, see [Preview Events](/dotnet/framework/wpf/advanced/preview-events) and [Input Overview](/dotnet/framework/wpf/advanced/input-overview).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/SizeChangedInfo.xml b/xml/System.Windows/SizeChangedInfo.xml
index d8c0de95838..9a4f93893e5 100644
--- a/xml/System.Windows/SizeChangedInfo.xml
+++ b/xml/System.Windows/SizeChangedInfo.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class parallels some of the members <xref:System.Windows.SizeChangedEventArgs> class, which is used to report event data for <xref:System.Windows.FrameworkElement.SizeChanged>, but the two classes serve different purposes.  <xref:System.Windows.SizeChangedInfo> is specifically used for <xref:System.Windows.UIElement.OnRenderSizeChanged%2A> overrides, which offers class handling for an event that is not exposed as a public event in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For details, see <xref:System.Windows.UIElement.OnRenderSizeChanged%2A>.  
+ This class parallels some of the members <xref:System.Windows.SizeChangedEventArgs> class, which is used to report event data for <xref:System.Windows.FrameworkElement.SizeChanged>, but the two classes serve different purposes.  <xref:System.Windows.SizeChangedInfo> is specifically used for <xref:System.Windows.UIElement.OnRenderSizeChanged%2A> overrides, which offers class handling for an event that is not exposed as a public event in WPF. For details, see <xref:System.Windows.UIElement.OnRenderSizeChanged%2A>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/SourceChangedEventHandler.xml b/xml/System.Windows/SourceChangedEventHandler.xml
index 481b2552391..894b6a2f98a 100644
--- a/xml/System.Windows/SourceChangedEventHandler.xml
+++ b/xml/System.Windows/SourceChangedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The "SourceChanged" event that this delegate represents handlers for is not exposed as a public [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event, as is the case with most routed events. Instead, "SourceChanged" is a routed event that remains private to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] infrastructure and is direct routed. Because it is direct routed, `sender` and the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event data are always the same object. You can add and remove handlers to this event despite the private access level of the event itself by using the public methods <xref:System.Windows.PresentationSource.AddSourceChangedHandler%2A> and <xref:System.Windows.PresentationSource.RemoveSourceChangedHandler%2A>.  
+ The "SourceChanged" event that this delegate represents handlers for is not exposed as a public [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event, as is the case with most routed events. Instead, "SourceChanged" is a routed event that remains private to the WPF infrastructure and is direct routed. Because it is direct routed, `sender` and the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event data are always the same object. You can add and remove handlers to this event despite the private access level of the event itself by using the public methods <xref:System.Windows.PresentationSource.AddSourceChangedHandler%2A> and <xref:System.Windows.PresentationSource.RemoveSourceChangedHandler%2A>.  
   
  The `sender` of the event will be a derived class of <xref:System.Windows.PresentationSource>.  
   
diff --git a/xml/System.Windows/StaticResourceExtension.xml b/xml/System.Windows/StaticResourceExtension.xml
index 5bb93000a8e..e9388bec08f 100644
--- a/xml/System.Windows/StaticResourceExtension.xml
+++ b/xml/System.Windows/StaticResourceExtension.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a markup extension implementation. Markup extension classes in WPF exist mainly to provide infrastructure support for some aspect of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] XAML  processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) usage from XAML. For more information on the mechanics of static resource lookup in WPF XAML, see [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) or [XAML Resources](/dotnet/framework/wpf/advanced/xaml-resources).  
+ This class is a markup extension implementation. Markup extension classes in WPF exist mainly to provide infrastructure support for some aspect of the WPF XAML  processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) usage from XAML. For more information on the mechanics of static resource lookup in WPF XAML, see [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) or [XAML Resources](/dotnet/framework/wpf/advanced/xaml-resources).  
   
  `{StaticResource}` is a markup extension that is specific to the WPF implementation of XAML. You can use `{StaticResource}` when referencing the default XAML namespace for WPF, without using a prefix. In contrast, markup extensions that are defined for XAML language support (such as `{x:Type}`) require the prefix for the XAML language XAML namespace in the usage. For more information, see [Markup Extensions and WPF XAML](/dotnet/framework/wpf/advanced/markup-extensions-and-wpf-xaml).  
   
@@ -128,7 +128,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] XAML processor implementation, and is not intended to be called directly. The XAML processor implementation uses this method for proper handling of `StaticResource` extension values during object creation.  
+ This method supports WPF XAML processor implementation, and is not intended to be called directly. The XAML processor implementation uses this method for proper handling of `StaticResource` extension values during object creation.  
   
  The property to be set can be identified by a <xref:System.Reflection.PropertyInfo> (standard property) or <xref:System.Windows.DependencyProperty> (dependency property).  
   
diff --git a/xml/System.Windows/Style.xml b/xml/System.Windows/Style.xml
index 016e56fc6a7..f85e1b71a87 100644
--- a/xml/System.Windows/Style.xml
+++ b/xml/System.Windows/Style.xml
@@ -87,7 +87,7 @@
  [!code-xaml[PhotoStoreDemoStyled#1](~/samples/snippets/csharp/VS_Snippets_Wpf/PhotoStoreDemoStyled/CS/window1.xaml#1)]   
   
 > [!NOTE]
->  Many [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] controls consist of a combination of other [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] controls, so creating a style that applies to all controls of a type can have broad impact. For instance, if you create a style that targets the <xref:System.Windows.Controls.TextBlock> controls in a <xref:System.Windows.Controls.Canvas>, the style is applied to all <xref:System.Windows.Controls.TextBlock> controls in the canvas, even if the <xref:System.Windows.Controls.TextBlock> is part of another control, such as a <xref:System.Windows.Controls.ListBox>.  
+>  Many WPF controls consist of a combination of other WPF controls, so creating a style that applies to all controls of a type can have broad impact. For instance, if you create a style that targets the <xref:System.Windows.Controls.TextBlock> controls in a <xref:System.Windows.Controls.Canvas>, the style is applied to all <xref:System.Windows.Controls.TextBlock> controls in the canvas, even if the <xref:System.Windows.Controls.TextBlock> is part of another control, such as a <xref:System.Windows.Controls.ListBox>.  
   
  For information on how to extend or inherit from a defined style, see the <xref:System.Windows.Style.BasedOn%2A> page.  
   
@@ -232,11 +232,11 @@
    
   
 ## Examples  
- There are several ways that styles in [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] can be extended or inherited. Styles can be based on other styles through this property. When you use this property, the new style will inherit the values of the original style that are not explicitly redefined in the new style. In the following example, `Style2` inherits the <xref:System.Windows.Controls.Control.Background%2A?displayProperty=nameWithType> value of `Yellow`, and adds a <xref:System.Windows.Controls.Control.Foreground%2A?displayProperty=nameWithType> value of `Blue`.  
+ There are several ways that styles in WPF can be extended or inherited. Styles can be based on other styles through this property. When you use this property, the new style will inherit the values of the original style that are not explicitly redefined in the new style. In the following example, `Style2` inherits the <xref:System.Windows.Controls.Control.Background%2A?displayProperty=nameWithType> value of `Yellow`, and adds a <xref:System.Windows.Controls.Control.Foreground%2A?displayProperty=nameWithType> value of `Blue`.  
   
  [!code-xaml[StyleOvw01#ExtendingStyle](~/samples/snippets/csharp/VS_Snippets_Wpf/StyleOvw01/CS/Page1.xaml#extendingstyle)]   
   
- Similarly, styles can be based on the style of an existing [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element, as in the following example where the new style is based on the style of a <xref:System.Windows.Controls.TextBlock> element.  
+ Similarly, styles can be based on the style of an existing WPF element, as in the following example where the new style is based on the style of a <xref:System.Windows.Controls.TextBlock> element.  
   
  [!code-xaml[PhotoStoreDemoStyled#2](~/samples/snippets/csharp/VS_Snippets_Wpf/PhotoStoreDemoStyled/CS/window1.xaml#2)]   
   
@@ -705,7 +705,7 @@
   
  Setting the <xref:System.Windows.Style.TargetType%2A> property to the <xref:System.Windows.Controls.TextBlock> type without setting an `x:Key` implicitly sets the `x:Key` to `{x:Type TextBlock}`. This also means that if you give the above <xref:System.Windows.Style> an `x:Key` value of anything other than `{x:Type TextBlock}`, the <xref:System.Windows.Style> would not be applied to all <xref:System.Windows.Controls.TextBlock> elements automatically. Instead, you need to apply the style to the <xref:System.Windows.Controls.TextBlock> elements explicitly.  
   
- Many [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] controls consist of a combination of other [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] controls, so creating a style that applies to all controls of a type can have broad impact. For instance, if you create a style that targets the <xref:System.Windows.Controls.TextBox> controls in a <xref:System.Windows.Controls.Canvas>, the style is applied to all <xref:System.Windows.Controls.TextBox> controls in the canvas, even if the <xref:System.Windows.Controls.TextBox> is part of another control, such as a <xref:System.Windows.Controls.ComboBox>.  
+ Many WPF controls consist of a combination of other WPF controls, so creating a style that applies to all controls of a type can have broad impact. For instance, if you create a style that targets the <xref:System.Windows.Controls.TextBox> controls in a <xref:System.Windows.Controls.Canvas>, the style is applied to all <xref:System.Windows.Controls.TextBox> controls in the canvas, even if the <xref:System.Windows.Controls.TextBox> is part of another control, such as a <xref:System.Windows.Controls.ComboBox>.  
   
  ]]></format>
         </remarks>
@@ -742,7 +742,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] styling and templating model enables you to specify triggers within your <xref:System.Windows.Style>. Essentially, triggers are objects that enable you to apply changes when certain conditions (such as when a certain property value becomes `true`, or when an event occurs) are satisfied.  
+ The WPF styling and templating model enables you to specify triggers within your <xref:System.Windows.Style>. Essentially, triggers are objects that enable you to apply changes when certain conditions (such as when a certain property value becomes `true`, or when an event occurs) are satisfied.  
   
 <a name="xamlPropertyElementUsage_Triggers"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows/TemplateBindingExtension.xml b/xml/System.Windows/TemplateBindingExtension.xml
index db91da6fc70..645b033c2a9 100644
--- a/xml/System.Windows/TemplateBindingExtension.xml
+++ b/xml/System.Windows/TemplateBindingExtension.xml
@@ -143,7 +143,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This value is not the <xref:System.Windows.TemplateBindingExtensionConverter>. It is a specific converter pattern supported by [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] data binding.  
+ This value is not the <xref:System.Windows.TemplateBindingExtensionConverter>. It is a specific converter pattern supported by WPF data binding.  
   
 <a name="xamlTextUsage_Converter"></a>   
 ## XAML Text Usage  
diff --git a/xml/System.Windows/ThemeDictionaryExtension.xml b/xml/System.Windows/ThemeDictionaryExtension.xml
index a8a66dbd31e..046cc37183c 100644
--- a/xml/System.Windows/ThemeDictionaryExtension.xml
+++ b/xml/System.Windows/ThemeDictionaryExtension.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
   
 <a name="xamlTextUsage_ThemeDictionaryExtension"></a>   
 ## XAML Text Usage  
@@ -165,7 +165,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of `ThemeResourceDictionary` extension values during object creation.  
+ This method supports WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of `ThemeResourceDictionary` extension values during object creation.  
   
  This implementation relies on services based on the passed `serviceProvider`. It must not be `null`. The `serviceProvider` object is expected to implement <xref:System.Windows.Markup.IXamlTypeResolver>.  
   
diff --git a/xml/System.Windows/Trigger.xml b/xml/System.Windows/Trigger.xml
index 59b5946b71e..197eb0b2530 100644
--- a/xml/System.Windows/Trigger.xml
+++ b/xml/System.Windows/Trigger.xml
@@ -44,7 +44,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] defines properties that correspond to end-user actions, such as the <xref:System.Windows.UIElement.IsMouseOver%2A> property that is set to `true` when the user hovers the cursor over a <xref:System.Windows.UIElement> or the corresponding <xref:System.Windows.ContentElement.IsMouseOver%2A> property of a <xref:System.Windows.ContentElement>. Representing end-user actions in property values, along with the <xref:System.Windows.Trigger> element, allows [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] styles to change property values based on those end-user actions, all from within markup.  
+ WPF defines properties that correspond to end-user actions, such as the <xref:System.Windows.UIElement.IsMouseOver%2A> property that is set to `true` when the user hovers the cursor over a <xref:System.Windows.UIElement> or the corresponding <xref:System.Windows.ContentElement.IsMouseOver%2A> property of a <xref:System.Windows.ContentElement>. Representing end-user actions in property values, along with the <xref:System.Windows.Trigger> element, allows WPF styles to change property values based on those end-user actions, all from within markup.  
   
  The properties changed by triggers are automatically reset to their previous value when the triggered condition is no longer satisfied. Triggers are optimized for transient states which are expected to change and return to original state, such as <xref:System.Windows.Controls.Primitives.ButtonBase.IsPressed%2A> on <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.ListBoxItem.IsSelected%2A> on <xref:System.Windows.Controls.ListBoxItem>. The <xref:System.Windows.Trigger.Property%2A> of interest must be a dependency property.  
   
diff --git a/xml/System.Windows/TriggerBase.xml b/xml/System.Windows/TriggerBase.xml
index d580cfe7661..5cfdd7a0e45 100644
--- a/xml/System.Windows/TriggerBase.xml
+++ b/xml/System.Windows/TriggerBase.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] styling and templating model allows you to specify triggers within your <xref:System.Windows.Style>, <xref:System.Windows.Controls.ControlTemplate>, and <xref:System.Windows.DataTemplate>. Essentially, <xref:System.Windows.TriggerBase> is the base class for objects that allow you to apply changes when certain conditions (such as when a certain property value becomes `true`, or when an event occurs) are satisfied.  
+ The WPF styling and templating model allows you to specify triggers within your <xref:System.Windows.Style>, <xref:System.Windows.Controls.ControlTemplate>, and <xref:System.Windows.DataTemplate>. Essentially, <xref:System.Windows.TriggerBase> is the base class for objects that allow you to apply changes when certain conditions (such as when a certain property value becomes `true`, or when an event occurs) are satisfied.  
   
    
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 439d4a0c73a..7c316e9f264 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -41,7 +41,7 @@
   
  Much of the input and focusing behavior for elements in general is also defined in the <xref:System.Windows.UIElement> class. This includes the events for keyboard, mouse and stylus input, and related status properties. Many of these events are routed events, and many of the input-related events have both a bubbling routing version as well as a tunneling version of the event. These paired events are typically the events of greatest interest to control authors.  
   
- <xref:System.Windows.UIElement> also includes APIs that relate to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] event model, including methods that can raise specified routed events that are sourced from an element instance.  
+ <xref:System.Windows.UIElement> also includes APIs that relate to the WPF event model, including methods that can raise specified routed events that are sourced from an element instance.  
   
  In terms of architecture, <xref:System.Windows.UIElement> can be considered roughly equivalent to a window handle in [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] programming, or an Element in [!INCLUDE[TLA#tla_dhtml](~/includes/tlasharptla-dhtml-md.md)] programming. <xref:System.Windows.UIElement> is a base element at the WPF core level.  
   
@@ -5470,7 +5470,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- It is more common to derive an element from <xref:System.Windows.FrameworkElement> rather than <xref:System.Windows.UIElement>. If you are deriving from <xref:System.Windows.FrameworkElement>, note that an override of <xref:System.Windows.UIElement.MeasureCore%2A> on <xref:System.Windows.FrameworkElement> seals the <xref:System.Windows.UIElement.MeasureCore%2A> method. Therefore, you only override <xref:System.Windows.UIElement.MeasureCore%2A> as a means to alter layout measure characteristics if you derive from <xref:System.Windows.UIElement> through an inheritance that does not include <xref:System.Windows.FrameworkElement>. This might be the case if you are attempting to build your own implementation on the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] core-level. Otherwise, if you are deriving from <xref:System.Windows.FrameworkElement>, then the implementation template for Measure behavior is the <xref:System.Windows.FrameworkElement> implementation of .<xref:System.Windows.FrameworkElement.MeasureOverride%2A>.  
+ It is more common to derive an element from <xref:System.Windows.FrameworkElement> rather than <xref:System.Windows.UIElement>. If you are deriving from <xref:System.Windows.FrameworkElement>, note that an override of <xref:System.Windows.UIElement.MeasureCore%2A> on <xref:System.Windows.FrameworkElement> seals the <xref:System.Windows.UIElement.MeasureCore%2A> method. Therefore, you only override <xref:System.Windows.UIElement.MeasureCore%2A> as a means to alter layout measure characteristics if you derive from <xref:System.Windows.UIElement> through an inheritance that does not include <xref:System.Windows.FrameworkElement>. This might be the case if you are attempting to build your own implementation on the WPF core-level. Otherwise, if you are deriving from <xref:System.Windows.FrameworkElement>, then the implementation template for Measure behavior is the <xref:System.Windows.FrameworkElement> implementation of .<xref:System.Windows.FrameworkElement.MeasureOverride%2A>.  
   
  A parent element with child elements must call <xref:System.Windows.UIElement.Measure%2A> on each child, otherwise these child elements are not sized or arranged and will effectively disappear from layout.  
   
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 51dcff916ac..95ac184384c 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -31,7 +31,7 @@
   
  Much of the input, focusing, and eventing behavior for 3D elements in general is defined in the <xref:System.Windows.UIElement3D> class. This includes the events for keyboard, mouse, and stylus input, and related status properties. Many of these events are routed events, and many of the input-related events have both a bubbling routing version as well as a tunneling version of the event. These paired events are typically the events of greatest interest to control authors.  
   
- <xref:System.Windows.UIElement3D> also includes APIs that relate to the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] event model, including methods that can raise specified routed events that are sourced from an element instance.  
+ <xref:System.Windows.UIElement3D> also includes APIs that relate to the WPF event model, including methods that can raise specified routed events that are sourced from an element instance.  
   
  A <xref:System.Windows.UIElement3D> has the following capabilities that are specifically defined by the <xref:System.Windows.UIElement3D> class:  
   
diff --git a/xml/System.Windows/ValueSource.xml b/xml/System.Windows/ValueSource.xml
index f1a950688f4..a7123e9f128 100644
--- a/xml/System.Windows/ValueSource.xml
+++ b/xml/System.Windows/ValueSource.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Most of the information that <xref:System.Windows.ValueSource> transmits is contained in the <xref:System.Windows.ValueSource.BaseValueSource%2A> property. This property contains an enumeration value that specifies exactly one aspect of the overall [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] property system that is responsible for the effective value of a dependency property.  
+ Most of the information that <xref:System.Windows.ValueSource> transmits is contained in the <xref:System.Windows.ValueSource.BaseValueSource%2A> property. This property contains an enumeration value that specifies exactly one aspect of the overall WPF property system that is responsible for the effective value of a dependency property.  
   
  Besides the base value, the other information that might be interesting about a dependency property value is whether the value is being animated, and whether the value involves an expression (such as a binding, or a dynamic resource reference). This information is reported by <xref:System.Windows.ValueSource.IsAnimated%2A> and <xref:System.Windows.ValueSource.IsExpression%2A> respectively. Also, if coercion is acting on a property value, the property retains a desired value, and the property value will attempt to reach that desired value if the constraints of the specific coercion are changed or lifted. A coerced property that is not at its desired value will report that <xref:System.Windows.ValueSource.IsCoerced%2A> is `true`.  
   
diff --git a/xml/System.Windows/VisualState.xml b/xml/System.Windows/VisualState.xml
index 9bc52c7f0ff..1df574721c4 100644
--- a/xml/System.Windows/VisualState.xml
+++ b/xml/System.Windows/VisualState.xml
@@ -106,7 +106,7 @@
   
  When a <xref:System.Windows.Controls.Control> uses the <xref:System.Windows.VisualStateManager> in a <xref:System.Windows.Controls.ControlTemplate>, the control author should specify which <xref:System.Windows.VisualState> objects the control expects to find in its <xref:System.Windows.Controls.ControlTemplate> by putting the <xref:System.Windows.TemplateVisualStateAttribute> on its class signature. <xref:System.Windows.Controls.ControlTemplate> authors define new <xref:System.Windows.VisualState> objects and set the <xref:System.Windows.VisualState.Name%2A> property to the value specified by the <xref:System.Windows.TemplateVisualStateAttribute.Name%2A?displayProperty=nameWithType> property.  
   
- To find the names of the visual states for the controls that are included with [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). For information about how to create a <xref:System.Windows.Controls.ControlTemplate> and <xref:System.Windows.VisualState> objects for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
+ To find the names of the visual states for the controls that are included with WPF, see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). For information about how to create a <xref:System.Windows.Controls.ControlTemplate> and <xref:System.Windows.VisualState> objects for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
   
    
   
diff --git a/xml/System.Windows/VisualStateManager.xml b/xml/System.Windows/VisualStateManager.xml
index 64ea262d0ef..5fa327b1547 100644
--- a/xml/System.Windows/VisualStateManager.xml
+++ b/xml/System.Windows/VisualStateManager.xml
@@ -24,7 +24,7 @@
   
  The <xref:System.Windows.VisualStateManager> also enables you to specify when a control enters a specific state. The method that you should call to change states depends on your scenario. If you create a control that uses the <xref:System.Windows.VisualStateManager> in its <xref:System.Windows.Controls.ControlTemplate>, call the <xref:System.Windows.VisualStateManager.GoToState%2A> method. For more information about how to create controls that use the <xref:System.Windows.VisualStateManager>, see [Creating a Control That Has a Customizable Appearance](/dotnet/framework/wpf/controls/creating-a-control-that-has-a-customizable-appearance). If you use the <xref:System.Windows.VisualStateManager> outside of a <xref:System.Windows.Controls.ControlTemplate> (for example, if you use a <xref:System.Windows.VisualStateManager> in a <xref:System.Windows.Controls.UserControl> or in a single element), call the <xref:System.Windows.VisualStateManager.GoToElementState%2A> method. In either case, the <xref:System.Windows.VisualStateManager> performs the logic that is required to appropriately start and stop the storyboards that are associated with the involved state. For example, suppose that a control defines the states, `State1` and `State2`, each of which has a storyboard associated with it. If the control is in `State1` and you pass `State2` to <xref:System.Windows.VisualStateManager.GoToState%2A> or <xref:System.Windows.VisualStateManager.GoToElementState%2A>, the <xref:System.Windows.VisualStateManager> starts the storyboard in `State2` and stops the storyboard in `State1`.  
   
- Controls that are included with [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] use the <xref:System.Windows.VisualStateManager> to change visual states. When you create a <xref:System.Windows.Controls.ControlTemplate> for a control that is included with [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], you can add <xref:System.Windows.VisualState> objects to the control's <xref:System.Windows.Controls.ControlTemplate> to specify the control's appearance in a certain state. To find the names of the visual states for the controls that are included with [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)], see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). The control's logic handles transitioning between states, so you do not need to do anything other than define the <xref:System.Windows.VisualState> objects in the new <xref:System.Windows.Controls.ControlTemplate>. For more information about how to create control templates for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
+ Controls that are included with [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] use the <xref:System.Windows.VisualStateManager> to change visual states. When you create a <xref:System.Windows.Controls.ControlTemplate> for a control that is included with WPF, you can add <xref:System.Windows.VisualState> objects to the control's <xref:System.Windows.Controls.ControlTemplate> to specify the control's appearance in a certain state. To find the names of the visual states for the controls that are included with WPF, see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). The control's logic handles transitioning between states, so you do not need to do anything other than define the <xref:System.Windows.VisualState> objects in the new <xref:System.Windows.Controls.ControlTemplate>. For more information about how to create control templates for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
   
  If you want to implement your own logic for transitioning between states, you must inherit from <xref:System.Windows.VisualStateManager>, override the <xref:System.Windows.VisualStateManager.GoToStateCore%2A> method, and set the <xref:System.Windows.VisualStateManager.CustomVisualStateManager%2A?displayProperty=nameWithType> attached property on the control that uses the custom logic.  
   
diff --git a/xml/System.Xaml/AmbientPropertyValue.xml b/xml/System.Xaml/AmbientPropertyValue.xml
index a755c970ce8..736301daf7f 100644
--- a/xml/System.Xaml/AmbientPropertyValue.xml
+++ b/xml/System.Xaml/AmbientPropertyValue.xml
@@ -34,7 +34,7 @@
  <xref:System.Xaml.XamlMember.DependsOn%2A> is a similar concept that also influences XAML node-processing order. However, <xref:System.Xaml.XamlMember.DependsOn%2A> can only be used for peer member and node relationships; it cannot influence all descendants. Also, <xref:System.Xaml.XamlMember.DependsOn%2A> directly influences object graph property setting, whereas the ambient technique relies on type converters or markup extensions. In the ambient technique, there must also be a specific type converter or markup extension definition. It is up to each type converter or markup extension to determine how the ambient property value should be interpreted and applied to the object graph location where the type converter or markup extension is used.  
   
 ## WPF Usage Notes  
- An ambient property scenario that is illustrated in the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] feature set is <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType>, which can qualify the necessary property name lookups for other values. In this case, the <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value qualifies the <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> values in the XAML nodes underneath it. <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> uses the type converter behavior for a <xref:System.Windows.DependencyProperty>. This behavior accesses the ambient <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value by querying <xref:System.Xaml.IAmbientProvider.GetFirstAmbientValue%2A> from a service context that is available to type converters and markup extensions.  
+ An ambient property scenario that is illustrated in the WPF feature set is <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType>, which can qualify the necessary property name lookups for other values. In this case, the <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value qualifies the <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> values in the XAML nodes underneath it. <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> uses the type converter behavior for a <xref:System.Windows.DependencyProperty>. This behavior accesses the ambient <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value by querying <xref:System.Xaml.IAmbientProvider.GetFirstAmbientValue%2A> from a service context that is available to type converters and markup extensions.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Xaml/IAmbientProvider.xml b/xml/System.Xaml/IAmbientProvider.xml
index b4ab4c0c098..36a9afd5f55 100644
--- a/xml/System.Xaml/IAmbientProvider.xml
+++ b/xml/System.Xaml/IAmbientProvider.xml
@@ -31,7 +31,7 @@
  <xref:System.Xaml.XamlMember.DependsOn%2A> is a similar concept that also influences XAML node-processing order. However, <xref:System.Xaml.XamlMember.DependsOn%2A> can only be used for peer member and node relationships; it cannot influence all descendants. Also, <xref:System.Xaml.XamlMember.DependsOn%2A> directly influences object graph property setting; whereas the ambient technique relies on type converters or markup extensions. In the ambient technique, there must also be a specific type converter or markup extension definition that specifies how the ambient property value should be interpreted and applied to the object.  
   
 ## WPF Usage Notes  
- An ambient property scenario that is illustrated in the [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] feature set is <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType>, which can qualify the necessary property name lookups for other values. In this case, the <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value qualifies the <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> values that are located in the XAML nodes underneath it. <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> uses the type converter behavior for a <xref:System.Windows.DependencyProperty>. This behavior accesses the ambient <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value by querying <xref:System.Xaml.IAmbientProvider.GetFirstAmbientValue%2A> from a service context that is available to type converters and markup extensions.  
+ An ambient property scenario that is illustrated in the WPF feature set is <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType>, which can qualify the necessary property name lookups for other values. In this case, the <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value qualifies the <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> values that are located in the XAML nodes underneath it. <xref:System.Windows.Setter.Property%2A?displayProperty=nameWithType> uses the type converter behavior for a <xref:System.Windows.DependencyProperty>. This behavior accesses the ambient <xref:System.Windows.Style.TargetType%2A?displayProperty=nameWithType> value by querying <xref:System.Xaml.IAmbientProvider.GetFirstAmbientValue%2A> from a service context that is available to type converters and markup extensions.  
   
  An ambient type scenario that is illustrated in the WPF feature set is <xref:System.Windows.ResourceDictionary>. <xref:System.Windows.ResourceDictionary> has a <xref:System.Windows.ResourceDictionary.MergedDictionaries%2A> property that can contain other <xref:System.Windows.ResourceDictionary> objects to merge, and the intended order of resource resolution for the merged scenario clashes with the order that types are loaded. <xref:System.Windows.ResourceDictionary> applies <xref:System.Windows.Markup.AmbientAttribute> so that a XAML processor can correctly process the references in a merged dictionary with `StaticResource` usages. Specifically, `StaticResource` is a markup extension, which calls <xref:System.Xaml.IAmbientProvider.GetAllAmbientValues%2A>.  
   
diff --git a/xml/System.Xaml/XamlServices.xml b/xml/System.Xaml/XamlServices.xml
index 3c243efe22b..c74da051173 100644
--- a/xml/System.Xaml/XamlServices.xml
+++ b/xml/System.Xaml/XamlServices.xml
@@ -23,7 +23,7 @@
  The modes of the <xref:System.Xaml.XamlServices> class that are used in the most common XAML reading and writing scenarios rely on creating instances of XAML readers and XAML writers. These readers and writers are specialized but internal implementations of public classes, such as <xref:System.Xml.XmlReader>, <xref:System.Xaml.XamlXmlReader>, and <xref:System.Xaml.XamlObjectWriter>. To use <xref:System.Xaml.XamlServices> for most scenarios, you can rely on the default internal implementations to obtain the results that you want. For more specialized scenarios, you might define readers and writers yourself, and then pass them as arguments for overloads of the <xref:System.Xaml.XamlServices> methods.  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing WPF-defined types, or types based on WPF. For [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML (or BAML); and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use .NET Framework XAML Services APIs and the XAML readers and XAML writers internally in their implementation; however, they also provide support and specialized XAML schema context for WPF-specific concepts, such as optimizations for dependency properties and WPF known types.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing WPF-defined types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML (or BAML); and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use .NET Framework XAML Services APIs and the XAML readers and XAML writers internally in their implementation; however, they also provide support and specialized XAML schema context for WPF-specific concepts, such as optimizations for dependency properties and WPF known types.  
   
  ]]></format>
     </remarks>
@@ -76,7 +76,7 @@
 -   The XAML types that are specified in the source XAML must resolve to backing types in the relevant XAML namespaces. For example, XAML types for WPF namespaces can resolve to a WPF XAML namespace as specified in the XAML; the assemblies for WPF must be included in the project or available in the run time; and so on.  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>
@@ -272,7 +272,7 @@
 -   The XAML types that are specified in the `xaml` input must resolve to backing types in the relevant XAML namespaces. For example, XAML types for a WPF namespace can resolve to a WPF XAML namespace as specified in the XAML; the assemblies for WPF must be included in the project or be available in the run time; and so on.  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML, and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML, and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>
@@ -354,7 +354,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)]. For [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>
diff --git a/xml/ns-System.Windows.Forms.Integration.xml b/xml/ns-System.Windows.Forms.Integration.xml
index 35586f2e36f..63b7c31d405 100644
--- a/xml/ns-System.Windows.Forms.Integration.xml
+++ b/xml/ns-System.Windows.Forms.Integration.xml
@@ -5,13 +5,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Forms.Integration> namespace contains classes that enable interoperation between the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] technologies. When you use <xref:System.Windows.Forms.Integration> classes, you can host [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] controls on [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] pages, and [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] elements in [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based applications.  
+ The <xref:System.Windows.Forms.Integration> namespace contains classes that enable interoperation between the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF technologies. When you use <xref:System.Windows.Forms.Integration> classes, you can host [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] controls on WPF pages, and WPF elements in [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based applications.  
   
  The two key classes that implement interoperation capabilities are <xref:System.Windows.Forms.Integration.WindowsFormsHost> and <xref:System.Windows.Forms.Integration.ElementHost>. Which class you use depends on your control implementation:  
   
--   Use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> class when you must use a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control on a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] page.  
+-   Use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> class when you must use a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control on a WPF page.  
   
--   Use the <xref:System.Windows.Forms.Integration.ElementHost> class when you must use a [!INCLUDE[TLA2#tla_winclient](~/includes/tla2sharptla-winclient-md.md)] element in a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application.  
+-   Use the <xref:System.Windows.Forms.Integration.ElementHost> class when you must use a WPF element in a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application.  
   
  ]]></format>
     </remarks>

From f7eec8919ba7975c60871b1ed9c24a5d90c9b66d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:40:51 -0800
Subject: [PATCH 092/236] tla2sharptla-winvista

---
 xml/Microsoft.Win32/FileDialog.xml             | 2 +-
 xml/Microsoft.Win32/FileDialogCustomPlaces.xml | 2 +-
 xml/Microsoft.Win32/OpenFileDialog.xml         | 2 +-
 xml/Microsoft.Win32/SaveFileDialog.xml         | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/Microsoft.Win32/FileDialog.xml b/xml/Microsoft.Win32/FileDialog.xml
index 097d1bb5079..3e529341f93 100644
--- a/xml/Microsoft.Win32/FileDialog.xml
+++ b/xml/Microsoft.Win32/FileDialog.xml
@@ -191,7 +191,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting in [!INCLUDE[TLA2#tla_winvista](~/includes/tla2sharptla-winvista-md.md)], open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. This property allows you to modify the list that appears when your application uses a file dialog box.  
+ Starting in Windows Vista, open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. This property allows you to modify the list that appears when your application uses a file dialog box.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Win32/FileDialogCustomPlaces.xml b/xml/Microsoft.Win32/FileDialogCustomPlaces.xml
index 9b7db7fdf1b..065860bd5e7 100644
--- a/xml/Microsoft.Win32/FileDialogCustomPlaces.xml
+++ b/xml/Microsoft.Win32/FileDialogCustomPlaces.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Custom places are available starting in[!INCLUDE[TLA2#tla_winvista](~/includes/tla2sharptla-winvista-md.md)].  
+ Custom places are available starting in Windows Vista.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.Win32/OpenFileDialog.xml b/xml/Microsoft.Win32/OpenFileDialog.xml
index 5fb4233555b..3a61933ba68 100644
--- a/xml/Microsoft.Win32/OpenFileDialog.xml
+++ b/xml/Microsoft.Win32/OpenFileDialog.xml
@@ -25,7 +25,7 @@
   
  ![Open dialog box](~/add/media/dialogboxesoverviewfigure2.png "Open dialog box")  
   
- Starting in [!INCLUDE[TLA2#tla_winvista](~/includes/tla2sharptla-winvista-md.md)], open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. Use the <xref:Microsoft.Win32.FileDialog.CustomPlaces%2A> property to set this list of links.  
+ Starting in Windows Vista, open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. Use the <xref:Microsoft.Win32.FileDialog.CustomPlaces%2A> property to set this list of links.  
   
 <a name="xamlTextUsage_OpenFileDialog"></a>   
 ## XAML Text Usage  
diff --git a/xml/Microsoft.Win32/SaveFileDialog.xml b/xml/Microsoft.Win32/SaveFileDialog.xml
index 25dc48aec44..9fe744caac4 100644
--- a/xml/Microsoft.Win32/SaveFileDialog.xml
+++ b/xml/Microsoft.Win32/SaveFileDialog.xml
@@ -25,7 +25,7 @@
   
  ![Save As dialog box](~/add/media/dialogboxesoverviewfigure3.png "Save As dialog box")  
   
- Starting in [!INCLUDE[TLA2#tla_winvista](~/includes/tla2sharptla-winvista-md.md)], open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. Use the <xref:Microsoft.Win32.FileDialog.CustomPlaces%2A> property to set this list of links.  
+ Starting in Windows Vista, open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. Use the <xref:Microsoft.Win32.FileDialog.CustomPlaces%2A> property to set this list of links.  
   
 <a name="xamlTextUsage_SaveFileDialog"></a>   
 ## XAML Text Usage  

From 721c43ddd5bd67f090d16a786d7ae24a31a4b7d6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:42:23 -0800
Subject: [PATCH 093/236] tla2sharptla-wpf

---
 xml/Microsoft.Windows.Themes/BulletChrome.xml |  2 +-
 xml/System.Windows.Controls/Page.xml          |  4 +--
 xml/System.Windows.Controls/WebBrowser.xml    | 16 +++++-----
 xml/System.Windows.Input/KeyInterop.xml       |  8 ++---
 .../NavigationCommands.xml                    |  8 ++---
 .../NotifyInputEventArgs.xml                  |  4 +--
 .../NotifyInputEventHandler.xml               |  2 +-
 .../PreProcessInputEventArgs.xml              |  2 +-
 .../ProcessInputEventArgs.xml                 |  2 +-
 .../ProcessInputEventHandler.xml              |  2 +-
 .../StagingAreaInputItem.xml                  |  2 +-
 xml/System.Windows.Interop/InteropBitmap.xml  |  6 ++--
 xml/System.Windows.Interop/RenderMode.xml     |  4 +--
 xml/System.Windows.Media.Animation/Clock.xml  |  4 +--
 .../BevelBitmapEffect.xml                     |  2 +-
 .../BitmapEffect.xml                          |  2 +-
 .../BlurBitmapEffect.xml                      |  2 +-
 .../DropShadowBitmapEffect.xml                |  2 +-
 .../EmbossBitmapEffect.xml                    |  2 +-
 .../OuterGlowBitmapEffect.xml                 |  2 +-
 .../CustomContentState.xml                    |  6 ++--
 .../IProvideCustomContentState.xml            |  2 +-
 .../NavigationFailedEventArgs.xml             |  2 +-
 .../PageFunction`1.xml                        |  2 +-
 .../DispatcherTimer.xml                       |  2 +-
 xml/System.Windows/Application.xml            | 32 +++++++++----------
 xml/System.Windows/Window.xml                 |  2 +-
 xml/ns-System.Windows.Annotations.xml         |  2 +-
 28 files changed, 64 insertions(+), 64 deletions(-)

diff --git a/xml/Microsoft.Windows.Themes/BulletChrome.xml b/xml/Microsoft.Windows.Themes/BulletChrome.xml
index 49da59a13b5..b0a3d53b29b 100644
--- a/xml/Microsoft.Windows.Themes/BulletChrome.xml
+++ b/xml/Microsoft.Windows.Themes/BulletChrome.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The actual appearance of the <xref:System.Windows.Controls.Primitives.BulletDecorator.Bullet%2A> is dependent on which theme is active on the user's system. The properties of this class allow [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to set the appearance based on the current theme.  
+ The actual appearance of the <xref:System.Windows.Controls.Primitives.BulletDecorator.Bullet%2A> is dependent on which theme is active on the user's system. The properties of this class allow WPF to set the appearance based on the current theme.  
   
  In XAML usage, a <xref:Microsoft.Windows.Themes.BulletChrome> object element can also have child content, which can be a single <xref:System.Windows.UIElement> that sets the <xref:System.Windows.Controls.Decorator.Child%2A> property.  
   
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index f8d5949fec0..a2180c4bc22 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -120,7 +120,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a <xref:System.Windows.Controls.Page> is not being kept alive (see <xref:System.Windows.Controls.Page.KeepAlive%2A>), it needs to implement a parameterless constructor to allow [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to create a new instance of it when navigated to in back or forward navigation history.  
+ If a <xref:System.Windows.Controls.Page> is not being kept alive (see <xref:System.Windows.Controls.Page.KeepAlive%2A>), it needs to implement a parameterless constructor to allow WPF to create a new instance of it when navigated to in back or forward navigation history.  
   
  ]]></format>
         </remarks>
@@ -1009,7 +1009,7 @@
  <xref:System.Windows.Navigation.NavigationWindow> displays navigation UI by default to enable browser-style forwards and backwards navigation. If a page is set as the <xref:System.Windows.Application.StartupUri%2A>, <xref:System.Windows.Application> automatically opens a <xref:System.Windows.Navigation.NavigationWindow> to host the page in. If the page does not want to use the default <xref:System.Windows.Navigation.NavigationWindow> navigation UI, it can set <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> to `false`.  
   
 > [!NOTE]
->  Because [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does not integrate with the navigation UI for [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)], it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
+>  Because WPF does not integrate with the navigation UI for [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)], it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. WPF does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
   
    
   
diff --git a/xml/System.Windows.Controls/WebBrowser.xml b/xml/System.Windows.Controls/WebBrowser.xml
index d1c015e3ea0..75b32ea3736 100644
--- a/xml/System.Windows.Controls/WebBrowser.xml
+++ b/xml/System.Windows.Controls/WebBrowser.xml
@@ -41,11 +41,11 @@
   
  **WPF/HTML Interoperability**: <xref:System.Windows.Controls.WebBrowser.InvokeScript%2A> and <xref:System.Windows.Controls.WebBrowser.ObjectForScripting%2A>, and <xref:System.Windows.Controls.WebBrowser.Document%2A>.  
   
- <xref:System.Windows.Controls.WebBrowser> is bound by the security constraints of the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application that is hosting the <xref:System.Windows.Controls.WebBrowser>:  
+ <xref:System.Windows.Controls.WebBrowser> is bound by the security constraints of the WPF application that is hosting the <xref:System.Windows.Controls.WebBrowser>:  
   
--   When <xref:System.Windows.Controls.WebBrowser> is hosted by a full-trust [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application (a stand-alone application, for example), <xref:System.Windows.Controls.WebBrowser> can host HTML documents from any location.  
+-   When <xref:System.Windows.Controls.WebBrowser> is hosted by a full-trust WPF application (a stand-alone application, for example), <xref:System.Windows.Controls.WebBrowser> can host HTML documents from any location.  
   
--   When <xref:System.Windows.Controls.WebBrowser> is hosted by a partial-trust [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application (an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], for example), <xref:System.Windows.Controls.WebBrowser> can only host documents that are **Site Of Origin** application data files. For more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files).  
+-   When <xref:System.Windows.Controls.WebBrowser> is hosted by a partial-trust WPF application (an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], for example), <xref:System.Windows.Controls.WebBrowser> can only host documents that are **Site Of Origin** application data files. For more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files).  
   
 > [!CAUTION]
 >  The <xref:System.Windows.Controls.WebBrowser> control internally instantiates the native WebBrowser ActiveX control. WPF enables security features by applying feature controls to the WebBrowser ActiveX control. The feature controls that are applied differ for XBAPs and stand-alone applications. Some applications should apply additional feature controls to prevent malicious content from running. For more information, see the "WebBrowser Control and Feature Controls" section in [Security (WPF)](/dotnet/framework/wpf/security-wpf) and [WebBrowser Control Overviews and Tutorials](https://go.microsoft.com/fwlink/?LinkId=179388).  
@@ -442,9 +442,9 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
    
   
 ## Examples  
- The following example shows how to call a script function in a document from a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application by using <xref:System.Windows.Controls.WebBrowser.InvokeScript%28System.String%29>. In this example, the script function has no parameters.  
+ The following example shows how to call a script function in a document from a WPF application by using <xref:System.Windows.Controls.WebBrowser.InvokeScript%28System.String%29>. In this example, the script function has no parameters.  
   
- The following is the HTML document that implements the script function that will be called from [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)].  
+ The following is the HTML document that implements the script function that will be called from WPF.  
   
 ```html  
 <html>  
@@ -465,7 +465,7 @@ private void forwardButton_Click(object sender, RoutedEventArgs e)
 </html>  
 ```  
   
- The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script function in the HTML document.  
+ The following shows the WPF implementation to call the script function in the HTML document.  
   
 ```csharp  
 private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArgs e)  
@@ -549,7 +549,7 @@ private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArg
 ## Examples  
  The following example shows how to call script functions in a document from an application by using <xref:System.Windows.Controls.WebBrowser.InvokeScript%28System.String%2CSystem.Object%5B%5D%29>. In this example, the script functions require parameters.  
   
- The following is the document that implements the script functions that will be called from [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)].  
+ The following is the document that implements the script functions that will be called from WPF.  
   
 ```html  
 <html>  
@@ -570,7 +570,7 @@ private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArg
 </html>  
 ```  
   
- The following shows the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] implementation to call the script functions in the HTML document.  
+ The following shows the WPF implementation to call the script functions in the HTML document.  
   
 ```csharp  
 private void callScriptFunctionNoParamButton_Click(object sender, RoutedEventArgs e)  
diff --git a/xml/System.Windows.Input/KeyInterop.xml b/xml/System.Windows.Input/KeyInterop.xml
index 62d8e57ad84..437aa7fa7b1 100644
--- a/xml/System.Windows.Input/KeyInterop.xml
+++ b/xml/System.Windows.Input/KeyInterop.xml
@@ -42,8 +42,8 @@
       </Parameters>
       <Docs>
         <param name="virtualKey">The virtual key to convert.</param>
-        <summary>Converts a Win32 Virtual-Key into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" />.</summary>
-        <returns>The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] key.</returns>
+        <summary>Converts a Win32 Virtual-Key into WPF <see cref="T:System.Windows.Input.Key" />.</summary>
+        <returns>The WPF key.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -68,8 +68,8 @@
         <Parameter Name="key" Type="System.Windows.Input.Key" />
       </Parameters>
       <Docs>
-        <param name="key">The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to convert.</param>
-        <summary>Converts a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] <see cref="T:System.Windows.Input.Key" /> into a Win32 Virtual-Key.</summary>
+        <param name="key">The WPF to convert.</param>
+        <summary>Converts a WPF <see cref="T:System.Windows.Input.Key" /> into a Win32 Virtual-Key.</summary>
         <returns>The Win32 Virtual-Key.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Input/NavigationCommands.xml b/xml/System.Windows.Input/NavigationCommands.xml
index 740871bb942..54a251ccc49 100644
--- a/xml/System.Windows.Input/NavigationCommands.xml
+++ b/xml/System.Windows.Input/NavigationCommands.xml
@@ -231,7 +231,7 @@
 ## Remarks  
  This command indicates the intention to navigate home.  
   
- There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.BrowseHome%2A> command on any given [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] class. As such, you need to provide an appropriate implementation, which is shown in the example.  
+ There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.BrowseHome%2A> command on any given WPF class. As such, you need to provide an appropriate implementation, which is shown in the example.  
   
 <a name="xamlAttributeUsage_BrowseHome"></a>   
 ## XAML Attribute Usage  
@@ -460,7 +460,7 @@
 ## Remarks  
  This command indicates the intention to manage and navigate to favorites.  
   
- There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Favorites%2A> command on any given [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] class. As such, you need to provide an appropriate implementation, which is shown in the example.  
+ There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Favorites%2A> command on any given WPF class. As such, you need to provide an appropriate implementation, which is shown in the example.  
   
 <a name="xamlAttributeUsage_Favorites"></a>   
 ## XAML Attribute Usage  
@@ -1143,7 +1143,7 @@
 ## Remarks  
  This command indicates the intention to search.  
   
- There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Search%2A> command on any given [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] class. As such, you need to provide an appropriate implementation, which is shown in the example.  
+ There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Search%2A> command on any given WPF class. As such, you need to provide an appropriate implementation, which is shown in the example.  
   
 <a name="xamlAttributeUsage_Search"></a>   
 ## XAML Attribute Usage  
@@ -1222,7 +1222,7 @@
 ## Remarks  
  This command indicates the intention to set the zoom level.  
   
- There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Zoom%2A> command on any given [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] class. As such, you need to provide an appropriate implementation, which is shown in the example.  
+ There is no implementation for responding to the <xref:System.Windows.Input.NavigationCommands.Zoom%2A> command on any given WPF class. As such, you need to provide an appropriate implementation, which is shown in the example.  
   
 <a name="xamlAttributeUsage_Zoom"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Input/NotifyInputEventArgs.xml b/xml/System.Windows.Input/NotifyInputEventArgs.xml
index 150243411cb..b25328d429e 100644
--- a/xml/System.Windows.Input/NotifyInputEventArgs.xml
+++ b/xml/System.Windows.Input/NotifyInputEventArgs.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The input staging area processes input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes input into WPF events.  
   
  <xref:System.Windows.Input.NotifyInputEventArgs> is used with the <xref:System.Windows.Input.InputManager.PreNotifyInput> and <xref:System.Windows.Input.InputManager.PostNotifyInput> events.  
   
@@ -111,7 +111,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The input staging area processes raw input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes raw input into WPF events.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/NotifyInputEventHandler.xml b/xml/System.Windows.Input/NotifyInputEventHandler.xml
index e92ffb59ac4..f74cdd5abfe 100644
--- a/xml/System.Windows.Input/NotifyInputEventHandler.xml
+++ b/xml/System.Windows.Input/NotifyInputEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The input staging area processes input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes input into WPF events.  
   
  The <xref:System.Windows.Input.NotifyInputEventHandler> is used with the <xref:System.Windows.Input.InputManager.PreNotifyInput> and <xref:System.Windows.Input.InputManager.PostNotifyInput> events.  
   
diff --git a/xml/System.Windows.Input/PreProcessInputEventArgs.xml b/xml/System.Windows.Input/PreProcessInputEventArgs.xml
index 41ff2a91693..0c55f2228dd 100644
--- a/xml/System.Windows.Input/PreProcessInputEventArgs.xml
+++ b/xml/System.Windows.Input/PreProcessInputEventArgs.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Canceling a pre-process input stops the input from being processed further.  Listen for the <xref:System.Windows.Input.InputManager.PreNotifyInput> to determine if another handler canceled a pre-process input.  
   
- The input staging area processes input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes input into WPF events.  
   
  All <xref:System.Windows.Input.InputManager.PreProcessInput> event handlers are called, even if one of the handlers cancels the input.  To verify if a handler further up the tree canceled the input, listen for the <xref:System.Windows.Input.InputManager.PreNotifyInput> event.  
   
diff --git a/xml/System.Windows.Input/ProcessInputEventArgs.xml b/xml/System.Windows.Input/ProcessInputEventArgs.xml
index ce125468603..2d49e1006fc 100644
--- a/xml/System.Windows.Input/ProcessInputEventArgs.xml
+++ b/xml/System.Windows.Input/ProcessInputEventArgs.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Process input events enable access to the <xref:System.Windows.Input.InputManager> staging area.  
   
- The input staging area processes raw input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes raw input into WPF events.  
   
  <xref:System.Windows.Input.ProcessInputEventArgs> is used with the <xref:System.Windows.Input.InputManager.PostProcessInput> event.  
   
diff --git a/xml/System.Windows.Input/ProcessInputEventHandler.xml b/xml/System.Windows.Input/ProcessInputEventHandler.xml
index 5fd412452e6..b6405df4fae 100644
--- a/xml/System.Windows.Input/ProcessInputEventHandler.xml
+++ b/xml/System.Windows.Input/ProcessInputEventHandler.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  The <xref:System.Windows.Input.ProcessInputEventHandler> is used with the <xref:System.Windows.Input.InputManager.PostProcessInput> event.  
   
- Process input events enable access to the <xref:System.Windows.Input.InputManager> staging area, which processes input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ Process input events enable access to the <xref:System.Windows.Input.InputManager> staging area, which processes input into WPF events.  
   
  Input is processed in WPF in the follow stages:  
   
diff --git a/xml/System.Windows.Input/StagingAreaInputItem.xml b/xml/System.Windows.Input/StagingAreaInputItem.xml
index 597daaed6ed..b98ba1b3eff 100644
--- a/xml/System.Windows.Input/StagingAreaInputItem.xml
+++ b/xml/System.Windows.Input/StagingAreaInputItem.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The <xref:System.Windows.Input.StagingAreaInputItem> class provides a dictionary-based storage of the listeners of the input manager events.  
   
- The input staging area processes raw input into [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] events.  
+ The input staging area processes raw input into WPF events.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Interop/InteropBitmap.xml b/xml/System.Windows.Interop/InteropBitmap.xml
index 49785d3bdb8..d8b63a294d4 100644
--- a/xml/System.Windows.Interop/InteropBitmap.xml
+++ b/xml/System.Windows.Interop/InteropBitmap.xml
@@ -233,7 +233,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Forces the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered.</summary>
+        <summary>Forces the hosted non-WPF UI to be rendered.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">The <see cref="T:System.Windows.Interop.InteropBitmap" /> instance is frozen and cannot have its members written to.</exception>
       </Docs>
@@ -264,8 +264,8 @@
         <Parameter Name="dirtyRect" Type="System.Nullable&lt;System.Windows.Int32Rect&gt;" Index="0" FrameworkAlternate="net-5.0;netcore-3.0;netcore-3.1;netframework-4.5;netframework-4.5.1;netframework-4.5.2;netframework-4.6;netframework-4.6.1;netframework-4.6.2;netframework-4.7;netframework-4.7.1;netframework-4.7.2;netframework-4.8" />
       </Parameters>
       <Docs>
-        <param name="dirtyRect">The area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered. If this parameter is null, the entire non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI is rendered.</param>
-        <summary>Forces the specified area of the hosted non-[!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] UI to be rendered.</summary>
+        <param name="dirtyRect">The area of the hosted non-WPF UI to be rendered. If this parameter is null, the entire non-WPF UI is rendered.</param>
+        <summary>Forces the specified area of the hosted non-WPF UI to be rendered.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.InvalidOperationException">The <see cref="T:System.Windows.Interop.InteropBitmap" /> instance is frozen and cannot have its members written to.</exception>
       </Docs>
diff --git a/xml/System.Windows.Interop/RenderMode.xml b/xml/System.Windows.Interop/RenderMode.xml
index 2ce4db92735..91e300df4f8 100644
--- a/xml/System.Windows.Interop/RenderMode.xml
+++ b/xml/System.Windows.Interop/RenderMode.xml
@@ -45,7 +45,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] rendering is in hardware, if possible; software otherwise.</summary>
+        <summary>The WPF rendering is in hardware, if possible; software otherwise.</summary>
       </Docs>
     </Member>
     <Member MemberName="SoftwareOnly">
@@ -67,7 +67,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] rendering is in software only.</summary>
+        <summary>The WPF rendering is in software only.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Animation/Clock.xml b/xml/System.Windows.Media.Animation/Clock.xml
index 75658e53ab4..83f01abd847 100644
--- a/xml/System.Windows.Media.Animation/Clock.xml
+++ b/xml/System.Windows.Media.Animation/Clock.xml
@@ -216,8 +216,8 @@
         <ReturnType>System.TimeSpan</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current global time, as established by the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] timing system.</summary>
-        <value>The current global time for the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] timing system.</value>
+        <summary>Gets the current global time, as established by the WPF timing system.</summary>
+        <value>The current global time for the WPF timing system.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Effects/BevelBitmapEffect.xml b/xml/System.Windows.Media.Effects/BevelBitmapEffect.xml
index 9849f824baa..9f9fa9c9534 100644
--- a/xml/System.Windows.Media.Effects/BevelBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/BevelBitmapEffect.xml
@@ -24,7 +24,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
   
  The type of bevel (bevel curve) is determined by the <xref:System.Windows.Media.Effects.BevelBitmapEffect.EdgeProfile%2A> property.  
   
diff --git a/xml/System.Windows.Media.Effects/BitmapEffect.xml b/xml/System.Windows.Media.Effects/BitmapEffect.xml
index 8a23f7dc5a1..6101d2fb84a 100644
--- a/xml/System.Windows.Media.Effects/BitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/BitmapEffect.xml
@@ -25,7 +25,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations, because this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations, because this can degrade performance.  
   
 > [!CAUTION]
 >  Bitmap effects do not support partial trust execution. An application must have full trust permissions to use bitmap effects.  
diff --git a/xml/System.Windows.Media.Effects/BlurBitmapEffect.xml b/xml/System.Windows.Media.Effects/BlurBitmapEffect.xml
index 8e0e7bbbe45..3e7b6c21a39 100644
--- a/xml/System.Windows.Media.Effects/BlurBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/BlurBitmapEffect.xml
@@ -24,7 +24,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
   
  <xref:System.Windows.Media.Effects.BlurBitmapEffect> is one of several effects that are shipped with the SDK. Other effects include:  
   
diff --git a/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml b/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
index c2947048bf3..1d2f14f7a0e 100644
--- a/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
@@ -24,7 +24,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations because this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations because this can degrade performance.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Effects/EmbossBitmapEffect.xml b/xml/System.Windows.Media.Effects/EmbossBitmapEffect.xml
index bbb7da8013a..0947bfafe84 100644
--- a/xml/System.Windows.Media.Effects/EmbossBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/EmbossBitmapEffect.xml
@@ -24,7 +24,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations as this can degrade performance.  
   
  <xref:System.Windows.Media.Effects.EmbossBitmapEffect> is one of several effects that are shipped with the SDK. Other effects include:  
   
diff --git a/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml b/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
index 27ab23a32c0..a0fe67c078d 100644
--- a/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
@@ -24,7 +24,7 @@
 ## Remarks  
   
 > [!NOTE]
->  [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations because this can degrade performance.  
+>  WPF bitmap effects are software rendered. Any object that applies an effect will also be rendered in software. Bitmap effects should not be applied to large visuals or animations because this can degrade performance.  
   
  <xref:System.Windows.Media.Effects.OuterGlowBitmapEffect> is one of several effects that are shipped with the Windows SDK. Other effects include:  
   
diff --git a/xml/System.Windows.Navigation/CustomContentState.xml b/xml/System.Windows.Navigation/CustomContentState.xml
index 29f618d4d90..aa9b7bb14b9 100644
--- a/xml/System.Windows.Navigation/CustomContentState.xml
+++ b/xml/System.Windows.Navigation/CustomContentState.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, <xref:System.Windows.Navigation.NavigationService> does not store an instance of a content object in navigation history. Instead, <xref:System.Windows.Navigation.NavigationService> creates a new instance of the content object each time it is navigated to by using navigation history. This behavior is designed to avoid excessive memory consumption when large numbers and large pieces of content are being navigated to. Consequently, the state of the content is not remembered from one navigation to the next. However, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] provides the ability to associate a piece of custom state with the navigation history entry for a piece of content.  
+ By default, <xref:System.Windows.Navigation.NavigationService> does not store an instance of a content object in navigation history. Instead, <xref:System.Windows.Navigation.NavigationService> creates a new instance of the content object each time it is navigated to by using navigation history. This behavior is designed to avoid excessive memory consumption when large numbers and large pieces of content are being navigated to. Consequently, the state of the content is not remembered from one navigation to the next. However, WPF provides the ability to associate a piece of custom state with the navigation history entry for a piece of content.  
   
  Custom state that is associated with a navigation history entry must be a class that derives from <xref:System.Windows.Navigation.CustomContentState>. You associate a <xref:System.Windows.Navigation.CustomContentState> object with a navigation history entry by using one of the following techniques:  
   
@@ -56,14 +56,14 @@
 > [!NOTE]
 >  If you call the **AddBackEntry** method, you must handle the **Navigating** event or implement <xref:System.Windows.Navigation.IProvideCustomContentState>.  
   
- When the navigation history entry is navigated to, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] checks to see if a custom <xref:System.Windows.Navigation.CustomContentState> object is associated with it. If so, it calls <xref:System.Windows.Navigation.CustomContentState.Replay%2A> to allow the custom <xref:System.Windows.Navigation.CustomContentState> object to apply the state it remembered from the previous navigation.  
+ When the navigation history entry is navigated to, WPF checks to see if a custom <xref:System.Windows.Navigation.CustomContentState> object is associated with it. If so, it calls <xref:System.Windows.Navigation.CustomContentState.Replay%2A> to allow the custom <xref:System.Windows.Navigation.CustomContentState> object to apply the state it remembered from the previous navigation.  
   
  A custom <xref:System.Windows.Navigation.CustomContentState> class can override <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> to change the name that appears for the navigation history entry to which the <xref:System.Windows.Navigation.CustomContentState> object is associated. The value that <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> returns is visible from the navigation UI of the various navigators (Internet Explorer 7, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
  A class that derives from <xref:System.Windows.Navigation.CustomContentState> must be serializable, which means it must at least be augmented with <xref:System.SerializableAttribute>, and optionally implement <xref:System.Runtime.Serialization.ISerializable>.  
   
 > [!IMPORTANT]
->  When you store information in custom content state, you cannot store any references to the instance of the page for which you are remembering state if don't want the content to be retained in memory. This prevents [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] from releasing the page instance, and defeats the purpose of the default navigation history behavior. If you must do this, consider using <xref:System.Windows.Controls.Page.KeepAlive%2A> instead.  
+>  When you store information in custom content state, you cannot store any references to the instance of the page for which you are remembering state if don't want the content to be retained in memory. This prevents WPF from releasing the page instance, and defeats the purpose of the default navigation history behavior. If you must do this, consider using <xref:System.Windows.Controls.Page.KeepAlive%2A> instead.  
   
    
   
diff --git a/xml/System.Windows.Navigation/IProvideCustomContentState.xml b/xml/System.Windows.Navigation/IProvideCustomContentState.xml
index 15728ffe8c1..1fb8a766a46 100644
--- a/xml/System.Windows.Navigation/IProvideCustomContentState.xml
+++ b/xml/System.Windows.Navigation/IProvideCustomContentState.xml
@@ -53,7 +53,7 @@
  This is the default behavior because the state that is initially recorded in custom state may change after it was added to navigation history. If the custom state object is navigated back to and its state is applied, before some aspect about the state changes before the entry in navigation history is navigated to, the change in state cannot be reflected in the custom state object. Furthermore, <xref:System.Windows.Navigation.NavigationService.AddBackEntry%2A> can't be explicitly called to add a new custom state object that reflects the state changes. Consequently, to ensure the current state for a particular navigation is always stored in navigation history, <xref:System.Windows.Navigation.IProvideCustomContentState.GetContentState%2A> is called.  
   
 > [!IMPORTANT]
->  When you store information in custom content state, you cannot store any references to the instance of the page for which you are remembering state. This prevents [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] from releasing the page instance, and defeats the purpose of the default navigation history behavior. If you must do this, you might consider using <xref:System.Windows.Controls.Page.KeepAlive%2A> instead.  
+>  When you store information in custom content state, you cannot store any references to the instance of the page for which you are remembering state. This prevents WPF from releasing the page instance, and defeats the purpose of the default navigation history behavior. If you must do this, you might consider using <xref:System.Windows.Controls.Page.KeepAlive%2A> instead.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Navigation/NavigationFailedEventArgs.xml b/xml/System.Windows.Navigation/NavigationFailedEventArgs.xml
index b24a3d0fba3..26db534efb4 100644
--- a/xml/System.Windows.Navigation/NavigationFailedEventArgs.xml
+++ b/xml/System.Windows.Navigation/NavigationFailedEventArgs.xml
@@ -155,7 +155,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you handle <xref:System.Windows.Navigation.NavigationService.NavigationFailed> to process an exception that is thrown as a result of a failed navigation, and you don't want [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to continue processing the exception, you should set the <xref:System.Windows.Navigation.NavigationFailedEventArgs.Handled%2A> property to `true`.  
+ When you handle <xref:System.Windows.Navigation.NavigationService.NavigationFailed> to process an exception that is thrown as a result of a failed navigation, and you don't want WPF to continue processing the exception, you should set the <xref:System.Windows.Navigation.NavigationFailedEventArgs.Handled%2A> property to `true`.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Navigation/PageFunction`1.xml b/xml/System.Windows.Navigation/PageFunction`1.xml
index 92e823bbb05..8a4ee03b4bf 100644
--- a/xml/System.Windows.Navigation/PageFunction`1.xml
+++ b/xml/System.Windows.Navigation/PageFunction`1.xml
@@ -71,7 +71,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a <xref:System.Windows.Navigation.PageFunction%601> is not being kept alive (see <xref:System.Windows.Controls.Page.KeepAlive%2A>), it needs to implement a parameterless constructor to allow [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to create a new instance of it when navigated to in back or forward navigation history.  
+ If a <xref:System.Windows.Navigation.PageFunction%601> is not being kept alive (see <xref:System.Windows.Controls.Page.KeepAlive%2A>), it needs to implement a parameterless constructor to allow WPF to create a new instance of it when navigated to in back or forward navigation history.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Threading/DispatcherTimer.xml b/xml/System.Windows.Threading/DispatcherTimer.xml
index e5ea1912139..13df62c1e94 100644
--- a/xml/System.Windows.Threading/DispatcherTimer.xml
+++ b/xml/System.Windows.Threading/DispatcherTimer.xml
@@ -25,7 +25,7 @@
   
  Timers are not guaranteed to execute exactly when the time interval occurs, but they are guaranteed to not execute before the time interval occurs.  This is because <xref:System.Windows.Threading.DispatcherTimer> operations are placed on the <xref:System.Windows.Threading.Dispatcher> queue like other operations.  When the <xref:System.Windows.Threading.DispatcherTimer> operation executes is dependent on the other jobs in the queue and their priorities.  
   
- If a <xref:System.Timers.Timer?displayProperty=nameWithType> is used in a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application, it is worth noting that the <xref:System.Timers.Timer?displayProperty=nameWithType> runs on a different thread than the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread.  In order to access objects on the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread, it is necessary to post the operation onto the <xref:System.Windows.Threading.Dispatcher> of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread using <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. Reasons for using a <xref:System.Windows.Threading.DispatcherTimer> as opposed to a <xref:System.Timers.Timer?displayProperty=nameWithType> are that the <xref:System.Windows.Threading.DispatcherTimer> runs on the same thread as the <xref:System.Windows.Threading.Dispatcher> and a <xref:System.Windows.Threading.DispatcherPriority> can be set on the <xref:System.Windows.Threading.DispatcherTimer>.  
+ If a <xref:System.Timers.Timer?displayProperty=nameWithType> is used in a WPF application, it is worth noting that the <xref:System.Timers.Timer?displayProperty=nameWithType> runs on a different thread than the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread.  In order to access objects on the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread, it is necessary to post the operation onto the <xref:System.Windows.Threading.Dispatcher> of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread using <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. Reasons for using a <xref:System.Windows.Threading.DispatcherTimer> as opposed to a <xref:System.Timers.Timer?displayProperty=nameWithType> are that the <xref:System.Windows.Threading.DispatcherTimer> runs on the same thread as the <xref:System.Windows.Threading.Dispatcher> and a <xref:System.Windows.Threading.DispatcherPriority> can be set on the <xref:System.Windows.Threading.DispatcherTimer>.  
   
  A <xref:System.Windows.Threading.DispatcherTimer> will keep an object alive whenever the object's methods are bound to the timer.  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 04d771eed12..92068d17303 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Application> is a class that encapsulates [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application-specific functionality, including the following:  
+ <xref:System.Windows.Application> is a class that encapsulates WPF application-specific functionality, including the following:  
   
 -   **Application Lifetime**: <xref:System.Windows.Application.Activated>, <xref:System.Windows.Application.Current%2A>, <xref:System.Windows.Application.Deactivated>, <xref:System.Windows.Application.DispatcherUnhandledException>, <xref:System.Windows.Application.Exit>, <xref:System.Windows.Application.Run%2A>, <xref:System.Windows.Application.SessionEnding>, <xref:System.Windows.Application.Shutdown%2A>, <xref:System.Windows.Application.ShutdownMode%2A>, <xref:System.Windows.Application.Startup>.  
   
@@ -301,7 +301,7 @@
   
  You can use this information to determine whether an exception is recoverable or not. A recoverable exception might be a <xref:System.IO.FileNotFoundException>, for example, while an unrecoverable exception might be a <xref:System.StackOverflowException>, for example.  
   
- When you process an unhandled exception from <xref:System.Windows.Application.DispatcherUnhandledException>, and you don't want [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] to continue processing it, you need to set the <xref:System.Windows.Threading.DispatcherUnhandledExceptionEventArgs.Handled%2A> property to `true`.  
+ When you process an unhandled exception from <xref:System.Windows.Application.DispatcherUnhandledException>, and you don't want WPF to continue processing it, you need to set the <xref:System.Windows.Threading.DispatcherUnhandledExceptionEventArgs.Handled%2A> property to `true`.  
   
  Unlike the other events that <xref:System.Windows.Application> raises, <xref:System.Windows.Application.DispatcherUnhandledException> does not have a matching protected virtual implementation (OnDispatcherUnhandledException). Consequently, classes that derive from <xref:System.Windows.Application> must always register an event handler with <xref:System.Windows.Application.DispatcherUnhandledException> to process unhandled exceptions.  
   
@@ -553,7 +553,7 @@
 ## Remarks  
  <xref:System.Windows.Application.GetCookie%2A> retrieves a cookie for the specified <xref:System.Uri>. If the cookie can't be retrieved, a <xref:System.ComponentModel.Win32Exception> is thrown. You need to write the code to parse the cookie string into a list of name/value pairs.  
   
- For an overview of cookies in [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)], see [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
+ For an overview of cookies in WPF, see [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
   
  ]]></format>
         </remarks>
@@ -1619,13 +1619,13 @@
         <ReturnType>System.Reflection.Assembly</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the <see cref="T:System.Reflection.Assembly" /> that provides the pack uniform resource identifiers (URIs) for resources in a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application.</summary>
-        <value>A reference to the <see cref="T:System.Reflection.Assembly" /> that provides the pack uniform resource identifiers (URIs) for resources in a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application.</value>
+        <summary>Gets or sets the <see cref="T:System.Reflection.Assembly" /> that provides the pack uniform resource identifiers (URIs) for resources in a WPF application.</summary>
+        <value>A reference to the <see cref="T:System.Reflection.Assembly" /> that provides the pack uniform resource identifiers (URIs) for resources in a WPF application.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] resources are resolved at run time with respect to the entry assembly, which is identified by the value returned from the <xref:System.Reflection.Assembly.GetEntryAssembly%2A> method.  
+ By default, WPF resources are resolved at run time with respect to the entry assembly, which is identified by the value returned from the <xref:System.Reflection.Assembly.GetEntryAssembly%2A> method.  
   
  The entry assembly is the assembly that is returned by <xref:System.Reflection.Assembly.GetEntryAssembly%2A> and could be the following:  
   
@@ -1633,18 +1633,18 @@
   
 -   The first assembly to be executed by calling <xref:System.AppDomain.ExecuteAssembly%2A>.  
   
- In the following cases, however, a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly cannot get a reference to the entry assembly:  
+ In the following cases, however, a WPF assembly cannot get a reference to the entry assembly:  
   
--   An unmanaged (native) application hosts the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly.  
+-   An unmanaged (native) application hosts the WPF assembly.  
   
--   A managed application hosts the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly by loading it into a new application domain using a method other than <xref:System.AppDomain.ExecuteAssembly%2A>.  
+-   A managed application hosts the WPF assembly by loading it into a new application domain using a method other than <xref:System.AppDomain.ExecuteAssembly%2A>.  
   
- In both of these cases, <xref:System.Reflection.Assembly.GetEntryAssembly%2A> returns `null`, and the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly's resources cannot be resolved. In these cases, <xref:System.Windows.Application.ResourceAssembly%2A> can be set, once only, with a reference to the assembly that should be used to resolve resources.  
+ In both of these cases, <xref:System.Reflection.Assembly.GetEntryAssembly%2A> returns `null`, and the WPF assembly's resources cannot be resolved. In these cases, <xref:System.Windows.Application.ResourceAssembly%2A> can be set, once only, with a reference to the assembly that should be used to resolve resources.  
   
- <xref:System.Windows.Application.ResourceAssembly%2A> can only be set once because it is unlikely that the resource assembly will change after the [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly is loaded.  
+ <xref:System.Windows.Application.ResourceAssembly%2A> can only be set once because it is unlikely that the resource assembly will change after the WPF assembly is loaded.  
   
 > [!NOTE]
->  <xref:System.Windows.Application.ResourceAssembly%2A> cannot be set when a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] assembly can discover the entry assembly - that is, when <xref:System.Reflection.Assembly.GetEntryAssembly%2A> returns a reference to an assembly rather than `null`.  
+>  <xref:System.Windows.Application.ResourceAssembly%2A> cannot be set when a WPF assembly can discover the entry assembly - that is, when <xref:System.Reflection.Assembly.GetEntryAssembly%2A> returns a reference to an assembly rather than `null`.  
   
  This property is thread safe and is available from any thread.  
   
@@ -1652,7 +1652,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.InvalidOperationException">A [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application has an entry assembly, or <see cref="P:System.Windows.Application.ResourceAssembly" /> has already been set.</exception>
+        <exception cref="T:System.InvalidOperationException">A WPF application has an entry assembly, or <see cref="P:System.Windows.Application.ResourceAssembly" /> has already been set.</exception>
       </Docs>
     </Member>
     <Member MemberName="Resources">
@@ -1762,7 +1762,7 @@ This example illustrates how to use XAML together with application-scope resourc
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Application.Run%2A> is called to start a [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] application. If you define your <xref:System.Windows.Application> using markup, or markup and code-behind, <xref:System.Windows.Application.Run%2A> will be called implicitly. However, if you define your <xref:System.Windows.Application> using code, you will need to explicitly call <xref:System.Windows.Application.Run%2A>.  
+ <xref:System.Windows.Application.Run%2A> is called to start a WPF application. If you define your <xref:System.Windows.Application> using markup, or markup and code-behind, <xref:System.Windows.Application.Run%2A> will be called implicitly. However, if you define your <xref:System.Windows.Application> using code, you will need to explicitly call <xref:System.Windows.Application.Run%2A>.  
   
  When <xref:System.Windows.Application.Run%2A> is called, <xref:System.Windows.Application> attaches a new <xref:System.Windows.Threading.Dispatcher> instance to the UI thread. Next, the <xref:System.Windows.Threading.Dispatcher> object's <xref:System.Windows.Threading.Dispatcher.Run%2A> method is called, which starts a message pump to process windows messages. Finally, the <xref:System.Windows.Threading.Dispatcher> object calls the <xref:System.Windows.Application> object's the <xref:System.Windows.Application.OnStartup%2A> method to raise the <xref:System.Windows.Application.Startup> event. Consequently, the application execution model has been established by the time you handle <xref:System.Windows.Application.Startup>, at which point the application is considered to be running.  
   
@@ -1943,7 +1943,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
  Persistent cookies are stored in the current [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] installation's Temporary Internet Files folder until they expire, in which case they are deleted. You can delete a persistent cookie from your application by setting its expiry date to a date/time value that is in the past.  
   
- For an overview of cookies in [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)], see [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
+ For an overview of cookies in WPF, see [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
   
  ]]></format>
         </remarks>
@@ -2157,7 +2157,7 @@ This example illustrates how to use XAML together with application-scope resourc
  If you set <xref:System.Windows.Application.StartupUri%2A> using XAML, the main window that is created is not available from either the <xref:System.Windows.Application.MainWindow%2A> property or the <xref:System.Windows.Application.Windows%2A> property of the <xref:System.Windows.Application> object until after the <xref:System.Windows.Application.Startup> event is processed. If you need access to the main window during startup, you need to manually create a new window object from your <xref:System.Windows.Application.Startup> event handler.  
   
 > [!NOTE]
->  If your application uses <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> to specify a credential policy, you need to set <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> after <xref:System.Windows.Application.Startup> is raised; otherwise, [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] sets it to a default internal policy directly after the <xref:System.Windows.Application.Startup> event has been raised.  
+>  If your application uses <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> to specify a credential policy, you need to set <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> after <xref:System.Windows.Application.Startup> is raised; otherwise, WPF sets it to a default internal policy directly after the <xref:System.Windows.Application.Startup> event has been raised.  
   
  The command-line arguments that are passed to the <xref:System.Windows.Application.Startup> event handler are not the same as the [!INCLUDE[TLA#tla_url](~/includes/tlasharptla-url-md.md)] query string parameters that are passed to an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)].  
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index e5567ed9f42..c93ab949af5 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2073,7 +2073,7 @@
   
  A window that is opened by calling the <xref:System.Windows.Window.ShowDialog%2A> method does not automatically have a relationship with the window that opened it; specifically, the opened window does not know which window opened it. This relationship can be established using the <xref:System.Windows.Window.Owner%2A> property and managed using the <xref:System.Windows.Window.OwnedWindows%2A> property. To support UI automation (see [UI Automation Overview](/dotnet/framework/ui-automation/ui-automation-overview)), <xref:System.Windows.Window.Owner%2A> must be set for a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>.  
   
- When a modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window (a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>) is closed, the previously activated window is reactivated. If a modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window has an owner window (see <xref:System.Windows.Window.Owner%2A>), the owner window is not reactivated when the modal [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] window is closed unless it was the previously activated window.  
+ When a modal WPF window (a window opened by calling <xref:System.Windows.Window.ShowDialog%2A>) is closed, the previously activated window is reactivated. If a modal WPF window has an owner window (see <xref:System.Windows.Window.Owner%2A>), the owner window is not reactivated when the modal WPF window is closed unless it was the previously activated window.  
   
 > [!NOTE]
 >  This method cannot be called when a window is hosted in a browser.  
diff --git a/xml/ns-System.Windows.Annotations.xml b/xml/ns-System.Windows.Annotations.xml
index 911ee5ce558..232425c12f0 100644
--- a/xml/ns-System.Windows.Annotations.xml
+++ b/xml/ns-System.Windows.Annotations.xml
@@ -7,7 +7,7 @@
 ## Remarks  
  Types in the <xref:System.Windows.Annotations> namespace are provided to support the management of user-created annotations on application data displayed in Windows Presentation Foundation document viewing controls.  Using the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)] applications can add support for user-created notes and highlights that are stored separate from the application document itself.  Since the user annotation information is stored separately from the document content, users can even add notes and highlights to read-only or rights-managed documents that cannot be physically changed.  
   
- The [!INCLUDE[TLA2#tla_wpf](~/includes/tla2sharptla-wpf-md.md)] document viewing controls that support user-annotation capabilities are based on <xref:System.Windows.Controls.Primitives.DocumentViewerBase> derived subclasses such as <xref:System.Windows.Controls.DocumentViewer>, <xref:System.Windows.Controls.FlowDocumentPageViewer>, and <xref:System.Windows.Controls.FlowDocumentScrollViewer> as well as <xref:System.Windows.Controls.FlowDocumentReader>.  
+ The WPF document viewing controls that support user-annotation capabilities are based on <xref:System.Windows.Controls.Primitives.DocumentViewerBase> derived subclasses such as <xref:System.Windows.Controls.DocumentViewer>, <xref:System.Windows.Controls.FlowDocumentPageViewer>, and <xref:System.Windows.Controls.FlowDocumentScrollViewer> as well as <xref:System.Windows.Controls.FlowDocumentReader>.  
   
  ]]></format>
     </remarks>

From 20b195fb0b96aa512fc0398f7267370085d2c101 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:42:50 -0800
Subject: [PATCH 094/236] tla2sharptla-xaml

---
 .../MarkupCompilePass1.xml                    | 24 ++---
 .../MarkupCompilePass2.xml                    |  4 +-
 .../MergeLocalizationDirectives.xml           |  4 +-
 .../UidManager.xml                            |  8 +-
 xml/Microsoft.Win32/OpenFileDialog.xml        |  2 +-
 xml/Microsoft.Win32/SaveFileDialog.xml        |  2 +-
 .../PropertyFilterOptions.xml                 |  2 +-
 .../PresentationTraceLevel.xml                |  2 +-
 xml/System.IO.Packaging/PackageStore.xml      |  2 +-
 .../WebBrowserPermission.xml                  |  2 +-
 .../WebBrowserPermissionAttribute.xml         |  6 +-
 .../UnsignedPublishLicense.xml                |  6 +-
 .../ButtonBase.xml                            |  2 +-
 xml/System.Windows.Controls/AccessText.xml    |  2 +-
 .../ContentPresenter.xml                      |  6 +-
 .../ControlTemplate.xml                       |  2 +-
 .../DocumentViewer.xml                        |  8 +-
 .../FlowDocumentReader.xml                    |  2 +-
 xml/System.Windows.Controls/Frame.xml         |  6 +-
 xml/System.Windows.Controls/GridView.xml      |  2 +-
 .../GridViewHeaderRowPresenter.xml            |  2 +-
 xml/System.Windows.Controls/Image.xml         |  2 +-
 xml/System.Windows.Controls/InkCanvas.xml     |  4 +-
 .../ItemCollection.xml                        |  2 +-
 xml/System.Windows.Controls/ItemsControl.xml  |  2 +-
 xml/System.Windows.Controls/SpellCheck.xml    |  8 +-
 xml/System.Windows.Controls/TextBlock.xml     | 20 ++--
 xml/System.Windows.Controls/TextSearch.xml    |  2 +-
 xml/System.Windows.Controls/ToolBar.xml       |  2 +-
 .../ToolTipService.xml                        |  4 +-
 xml/System.Windows.Controls/TreeViewItem.xml  |  2 +-
 xml/System.Windows.Data/Binding.xml           | 12 +--
 xml/System.Windows.Data/BindingBase.xml       |  4 +-
 xml/System.Windows.Data/BindingStatus.xml     |  2 +-
 .../CollectionContainer.xml                   |  2 +-
 xml/System.Windows.Data/CollectionView.xml    |  4 +-
 .../CollectionViewGroup.xml                   |  2 +-
 .../CollectionViewSource.xml                  |  4 +-
 .../ObjectDataProvider.xml                    |  4 +-
 xml/System.Windows.Data/RelativeSource.xml    | 14 +--
 .../RelativeSourceMode.xml                    |  2 +-
 xml/System.Windows.Data/XmlDataProvider.xml   |  2 +-
 xml/System.Windows.Documents/Block.xml        |  2 +-
 xml/System.Windows.Documents/Glyphs.xml       |  2 +-
 xml/System.Windows.Documents/PageContent.xml  |  2 +-
 xml/System.Windows.Documents/TextElement.xml  | 12 +--
 xml/System.Windows.Documents/Typography.xml   | 92 +++++++++----------
 xml/System.Windows.Ink/GestureRecognizer.xml  |  2 +-
 .../DynamicRenderer.xml                       |  2 +-
 xml/System.Windows.Input/Cursors.xml          |  4 +-
 .../InputBindingCollection.xml                |  4 +-
 xml/System.Windows.Input/KeyBinding.xml       | 10 +-
 xml/System.Windows.Input/KeyGesture.xml       |  4 +-
 xml/System.Windows.Input/Keyboard.xml         | 40 ++++----
 xml/System.Windows.Input/Mouse.xml            | 30 +++---
 xml/System.Windows.Input/MouseBinding.xml     |  4 +-
 xml/System.Windows.Input/MouseGesture.xml     |  4 +-
 xml/System.Windows.Input/Stylus.xml           | 44 ++++-----
 xml/System.Windows.Interop/DocObjHost.xml     |  2 +-
 .../BamlLocalizabilityResolver.xml            |  2 +-
 .../MarkupObject.xml                          |  2 +-
 xml/System.Windows.Markup/TypeExtension.xml   |  2 +-
 .../Storyboard.xml                            |  2 +-
 .../MatrixValueSerializer.xml                 |  2 +-
 xml/System.Windows.Media/Brush.xml            |  4 +-
 xml/System.Windows.Media/Brushes.xml          |  2 +-
 xml/System.Windows.Media/Colors.xml           |  2 +-
 xml/System.Windows.Media/DashStyles.xml       |  2 +-
 xml/System.Windows.Media/ImageBrush.xml       |  2 +-
 xml/System.Windows.Media/ImageDrawing.xml     |  2 +-
 xml/System.Windows.Media/MatrixConverter.xml  |  2 +-
 xml/System.Windows.Media/MediaPlayer.xml      |  8 +-
 .../NumberSubstitution.xml                    |  8 +-
 xml/System.Windows.Media/VideoDrawing.xml     |  2 +-
 .../JournalEntry.xml                          |  2 +-
 .../JournalEntryUnifiedViewConverter.xml      | 10 +-
 .../NavigationService.xml                     | 10 +-
 .../NavigationWindow.xml                      |  8 +-
 .../DispatcherFrame.xml                       |  4 +-
 .../XpsSerializationManager.xml               |  4 +-
 xml/System.Windows/Application.xml            |  8 +-
 .../AttachedPropertyBrowsableAttribute.xml    |  2 +-
 ...dPropertyBrowsableForChildrenAttribute.xml |  8 +-
 ...achedPropertyBrowsableForTypeAttribute.xml |  4 +-
 ...BrowsableWhenAttributePresentAttribute.xml |  4 +-
 .../ColorConvertedBitmapExtension.xml         |  4 +-
 xml/System.Windows/ComponentResourceKey.xml   |  8 +-
 xml/System.Windows/ContentElement.xml         |  2 +-
 xml/System.Windows/CornerRadius.xml           |  2 +-
 xml/System.Windows/DataFormats.xml            |  2 +-
 xml/System.Windows/DependencyProperty.xml     |  8 +-
 .../DynamicResourceExtension.xml              | 10 +-
 xml/System.Windows/EventSetter.xml            |  6 +-
 .../FrameworkContentElement.xml               | 22 ++---
 xml/System.Windows/FrameworkElement.xml       | 46 +++++-----
 .../FrameworkElementFactory.xml               |  2 +-
 .../FrameworkPropertyMetadata.xml             | 32 +++----
 xml/System.Windows/FreezableCollection`1.xml  |  6 +-
 .../HierarchicalDataTemplate.xml              |  2 +-
 xml/System.Windows/PropertyMetadata.xml       |  4 +-
 xml/System.Windows/PropertyPath.xml           | 10 +-
 xml/System.Windows/ResourceDictionary.xml     | 12 +--
 .../StaticResourceExtension.xml               |  2 +-
 xml/System.Windows/Style.xml                  |  4 +-
 .../StyleTypedPropertyAttribute.xml           |  6 +-
 xml/System.Windows/SystemColors.xml           |  2 +-
 .../TemplateBindingExpression.xml             |  2 +-
 .../TemplateBindingExtension.xml              |  8 +-
 xml/System.Windows/TemplatePartAttribute.xml  |  6 +-
 .../ThemeDictionaryExtension.xml              |  8 +-
 xml/System.Windows/Thickness.xml              |  2 +-
 xml/System.Windows/UIElement.xml              | 12 +--
 xml/System.Windows/VisualStateManager.xml     |  2 +-
 .../WeakEventManager+ListenerList.xml         |  2 +-
 114 files changed, 399 insertions(+), 399 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
index cb9407c3312..5bd3cc0005a 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
@@ -144,8 +144,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the name of the application definition [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</summary>
-        <value>The name of the application definition [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</value>
+        <summary>Gets or sets the name of the application definition XAML file.</summary>
+        <value>The name of the application definition XAML file.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -503,8 +503,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the generated localization file for each localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</summary>
-        <value>The generated localization file for each localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</value>
+        <summary>Gets or sets the generated localization file for each localizable XAML file.</summary>
+        <value>The generated localization file for each localizable XAML file.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -781,8 +781,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a list of [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files to process.</summary>
-        <value>A list of [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files to process.</value>
+        <summary>Gets or sets a list of XAML files to process.</summary>
+        <value>A list of XAML files to process.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -851,9 +851,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the project contains non-localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that reference local types that are embedded into the main assembly.</summary>
+        <summary>Gets or sets a value that indicates whether the project contains non-localizable XAML files that reference local types that are embedded into the main assembly.</summary>
         <value>
-          <see langword="true" /> if project contains non-localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that reference local types that are embedded into the main assembly.; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if project contains non-localizable XAML files that reference local types that are embedded into the main assembly.; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -889,9 +889,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the project contains localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that reference local types that are embedded in the satellite assembly.</summary>
+        <summary>Gets or sets a value that indicates whether the project contains localizable XAML files that reference local types that are embedded in the satellite assembly.</summary>
         <value>
-          <see langword="true" /> if the p project contains localizable [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that reference local types that are embedded in the satellite assembly; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the p project contains localizable XAML files that reference local types that are embedded in the satellite assembly; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -1055,9 +1055,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether diagnostic information is generated and included in the compiled [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] in order to aid debugging.</summary>
+        <summary>Gets or sets a value that indicates whether diagnostic information is generated and included in the compiled XAML in order to aid debugging.</summary>
         <value>
-          <see langword="true" /> if diagnostic information is generated and included in the compiled [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] in order to aid debugging; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if diagnostic information is generated and included in the compiled XAML in order to aid debugging; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
index 145dea14a25..d001ba85260 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
@@ -453,9 +453,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether diagnostic information is generated and included in the compiled [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] in order to aid debugging.</summary>
+        <summary>Gets or sets a value that indicates whether diagnostic information is generated and included in the compiled XAML in order to aid debugging.</summary>
         <value>
-          <see langword="true" /> if diagnostic information is generated and included in the compiled [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] in order to aid debugging; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if diagnostic information is generated and included in the compiled XAML in order to aid debugging; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks.Windows/MergeLocalizationDirectives.xml b/xml/Microsoft.Build.Tasks.Windows/MergeLocalizationDirectives.xml
index 22b9412bbdd..b1254e265ab 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MergeLocalizationDirectives.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MergeLocalizationDirectives.xml
@@ -95,8 +95,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the list of localization directives files for individual files in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] binary format.</summary>
-        <value>The list of localization directives files for individual files in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] binary format.</value>
+        <summary>Gets or sets the list of localization directives files for individual files in XAML binary format.</summary>
+        <value>The list of localization directives files for individual files in XAML binary format.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks.Windows/UidManager.xml b/xml/Microsoft.Build.Tasks.Windows/UidManager.xml
index 1d97a65b7a4..3df171a3918 100644
--- a/xml/Microsoft.Build.Tasks.Windows/UidManager.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/UidManager.xml
@@ -87,8 +87,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the directory that is used to back up the source [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that are specified by the <see cref="P:Microsoft.Build.Tasks.Windows.UidManager.MarkupFiles" /> property.</summary>
-        <value>The directory that is used to back up the source [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files that are specified by the <see cref="P:Microsoft.Build.Tasks.Windows.UidManager.MarkupFiles" /> property.</value>
+        <summary>Gets or sets the directory that is used to back up the source XAML files that are specified by the <see cref="P:Microsoft.Build.Tasks.Windows.UidManager.MarkupFiles" /> property.</summary>
+        <value>The directory that is used to back up the source XAML files that are specified by the <see cref="P:Microsoft.Build.Tasks.Windows.UidManager.MarkupFiles" /> property.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -124,8 +124,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the source [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files to include for UID checking, updating, or removing.</summary>
-        <value>The source [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files to include for UID checking, updating, or removing.</value>
+        <summary>Gets or sets the source XAML files to include for UID checking, updating, or removing.</summary>
+        <value>The source XAML files to include for UID checking, updating, or removing.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Win32/OpenFileDialog.xml b/xml/Microsoft.Win32/OpenFileDialog.xml
index 3a61933ba68..ac70989c902 100644
--- a/xml/Microsoft.Win32/OpenFileDialog.xml
+++ b/xml/Microsoft.Win32/OpenFileDialog.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_OpenFileDialog"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML.  
   
    
   
diff --git a/xml/Microsoft.Win32/SaveFileDialog.xml b/xml/Microsoft.Win32/SaveFileDialog.xml
index 9fe744caac4..709a7b7e241 100644
--- a/xml/Microsoft.Win32/SaveFileDialog.xml
+++ b/xml/Microsoft.Win32/SaveFileDialog.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_SaveFileDialog"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML.  
   
    
   
diff --git a/xml/System.ComponentModel/PropertyFilterOptions.xml b/xml/System.ComponentModel/PropertyFilterOptions.xml
index fb53f334902..75ceed408dc 100644
--- a/xml/System.ComponentModel/PropertyFilterOptions.xml
+++ b/xml/System.ComponentModel/PropertyFilterOptions.xml
@@ -28,7 +28,7 @@
 ## Remarks  
  This filter mechanism is only implemented by the custom <xref:System.ComponentModel.DependencyPropertyDescriptor> for <xref:System.Windows.DependencyObject>.  
   
- Invalid and Valid are relevant only for attached properties. The validity of a property is determined by working with the following attributes: <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> , <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute>, <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute> which define the intended scope of the attached property in the object tree once the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is loaded. Designer applications that populate property grids and include attached properties in the grid must examine the value or presence of these attributes and the relative position of the current element versus either a parent or child element that "owns" the attached property. The owner-setter relationship together with the attribute values and <xref:System.ComponentModel.PropertyFilterOptions> will define whether a given attached property that is set on an element is valid or invalid.  
+ Invalid and Valid are relevant only for attached properties. The validity of a property is determined by working with the following attributes: <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> , <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute>, <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute> which define the intended scope of the attached property in the object tree once the XAML is loaded. Designer applications that populate property grids and include attached properties in the grid must examine the value or presence of these attributes and the relative position of the current element versus either a parent or child element that "owns" the attached property. The owner-setter relationship together with the attribute values and <xref:System.ComponentModel.PropertyFilterOptions> will define whether a given attached property that is set on an element is valid or invalid.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Diagnostics/PresentationTraceLevel.xml b/xml/System.Diagnostics/PresentationTraceLevel.xml
index d46e60d0066..180253afe0e 100644
--- a/xml/System.Diagnostics/PresentationTraceLevel.xml
+++ b/xml/System.Diagnostics/PresentationTraceLevel.xml
@@ -25,7 +25,7 @@
    
   
 ## Examples  
- If you run the application that contains the following [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] under a debugger, the output window provides lines of information describing the status and evaluation of the binding:  
+ If you run the application that contains the following XAML under a debugger, the output window provides lines of information describing the status and evaluation of the binding:  
   
  [!code-xaml[Debugging#1](~/samples/snippets/csharp/VS_Snippets_Wpf/Debugging/CSharp/Page1.xaml#1)]  
 [!code-xaml[Debugging#2](~/samples/snippets/csharp/VS_Snippets_Wpf/Debugging/CSharp/Page1.xaml#2)]  
diff --git a/xml/System.IO.Packaging/PackageStore.xml b/xml/System.IO.Packaging/PackageStore.xml
index e0ac6c0b0b2..66946baa43c 100644
--- a/xml/System.IO.Packaging/PackageStore.xml
+++ b/xml/System.IO.Packaging/PackageStore.xml
@@ -44,7 +44,7 @@
   
  The file I/O permissions of a package accessed through the <xref:System.IO.Packaging.PackageStore> remains the same as the I/O permissions set on the package when it is opened.  The <xref:System.IO.Packaging.PackageStore> only provides references to the packages that have been added the store.  It is up to the application to correctly open, update, and close each package.  
   
- Packages added to the <xref:System.IO.Packaging.PackageStore> can be accessed in multithreaded environments when they are used in combination with a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] parser such as <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>.  When operating in a multithreaded environment, the application must lock the package before access.  
+ Packages added to the <xref:System.IO.Packaging.PackageStore> can be accessed in multithreaded environments when they are used in combination with a XAML parser such as <xref:System.Windows.Markup.XamlReader.Load%2A?displayProperty=nameWithType>.  When operating in a multithreaded environment, the application must lock the package before access.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Security.Permissions/WebBrowserPermission.xml b/xml/System.Security.Permissions/WebBrowserPermission.xml
index 7dca91e89a1..7334b254e54 100644
--- a/xml/System.Security.Permissions/WebBrowserPermission.xml
+++ b/xml/System.Security.Permissions/WebBrowserPermission.xml
@@ -429,7 +429,7 @@
 ## Remarks  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
    
   
diff --git a/xml/System.Security.Permissions/WebBrowserPermissionAttribute.xml b/xml/System.Security.Permissions/WebBrowserPermissionAttribute.xml
index 0ff9e044cde..46ad3a02020 100644
--- a/xml/System.Security.Permissions/WebBrowserPermissionAttribute.xml
+++ b/xml/System.Security.Permissions/WebBrowserPermissionAttribute.xml
@@ -102,7 +102,7 @@
  The default value of the <xref:System.Security.Permissions.WebBrowserPermissionAttribute.Level%2A> property is <xref:System.Security.Permissions.WebBrowserPermissionLevel.None>.  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
    
   
@@ -151,7 +151,7 @@
  The security information described by <xref:System.Security.Permissions.WebBrowserPermissionAttribute> is stored in the metadata of the attribute target, which is the class to which <xref:System.Security.Permissions.WebBrowserPermissionAttribute> is applied. The system accesses the information at run time. The system uses the <xref:System.Security.Permissions.WebBrowserPermission> returned by <xref:System.Security.Permissions.WebBrowserPermissionAttribute.CreatePermission%2A> to convert the security information of the attribute target to a serializable form stored in metadata.  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
  ]]></format>
         </remarks>
@@ -195,7 +195,7 @@
  The default value is <xref:System.Security.Permissions.WebBrowserPermissionLevel.None>.  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
    
   
diff --git a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
index dd9094e06d9..02e84bc5cc2 100644
--- a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
+++ b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
@@ -37,7 +37,7 @@
   
 <a name="xamlTextUsage_UnsignedPublishLicense"></a>   
 ## XAML Text Usage  
- This type is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This type is not typically used in XAML.  
   
  ]]></format>
     </remarks>
@@ -264,7 +264,7 @@
   
 <a name="xamlTextUsage_ReferralInfoName"></a>   
 ## XAML Text Usage  
- Members of this type are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this type are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -299,7 +299,7 @@
   
 <a name="xamlTextUsage_ReferralInfoUri"></a>   
 ## XAML Text Usage  
- Members of this type are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this type are not typically used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls.Primitives/ButtonBase.xml b/xml/System.Windows.Controls.Primitives/ButtonBase.xml
index 6a188efcf25..cd773c8419b 100644
--- a/xml/System.Windows.Controls.Primitives/ButtonBase.xml
+++ b/xml/System.Windows.Controls.Primitives/ButtonBase.xml
@@ -349,7 +349,7 @@
 <a name="xamlValues_CommandParameter"></a>   
 ## XAML Values  
  *commandParameter*  
- A value of the same type as the particular command specified in the <xref:System.Windows.Controls.Primitives.ButtonBase.Command%2A> property expects. If you use an existing command library command, see that command library's documentation for [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage information, including which type of <xref:System.Windows.Controls.Primitives.ButtonBase.CommandParameter%2A> the command expects. If you use a custom command, see Remarks.  
+ A value of the same type as the particular command specified in the <xref:System.Windows.Controls.Primitives.ButtonBase.Command%2A> property expects. If you use an existing command library command, see that command library's documentation for XAML usage information, including which type of <xref:System.Windows.Controls.Primitives.ButtonBase.CommandParameter%2A> the command expects. If you use a custom command, see Remarks.  
   
 <a name="dependencyPropertyInfo_CommandParameter"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/AccessText.xml b/xml/System.Windows.Controls/AccessText.xml
index ee60aa3834e..4fd6f178335 100644
--- a/xml/System.Windows.Controls/AccessText.xml
+++ b/xml/System.Windows.Controls/AccessText.xml
@@ -231,7 +231,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], this value is a true double. You cannot qualify this value by using measurement units such as picas or points.  
+ In XAML, this value is a true double. You cannot qualify this value by using measurement units such as picas or points.  
   
 <a name="dependencyPropertyInfo_BaselineOffset"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/ContentPresenter.xml b/xml/System.Windows.Controls/ContentPresenter.xml
index 2b243679c09..520966424a6 100644
--- a/xml/System.Windows.Controls/ContentPresenter.xml
+++ b/xml/System.Windows.Controls/ContentPresenter.xml
@@ -188,7 +188,7 @@
   
 <a name="xamlTextUsage_Content"></a>   
 ## XAML Text Usage  
- Typically, you use `TemplateBinding` to bind this property value to a value on templated control. For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ Typically, you use `TemplateBinding` to bind this property value to a value on templated control. For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
 <a name="dependencyPropertyInfo_Content"></a>   
 ## Dependency Property Information  
@@ -386,7 +386,7 @@
   
 <a name="xamlTextUsage_ContentTemplate"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
 <a name="dependencyPropertyInfo_ContentTemplate"></a>   
 ## Dependency Property Information  
@@ -457,7 +457,7 @@
   
 <a name="xamlTextUsage_ContentTemplateSelector"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
 <a name="dependencyPropertyInfo_ContentTemplateSelector"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/ControlTemplate.xml b/xml/System.Windows.Controls/ControlTemplate.xml
index 9181646b8af..2ef855298ea 100644
--- a/xml/System.Windows.Controls/ControlTemplate.xml
+++ b/xml/System.Windows.Controls/ControlTemplate.xml
@@ -56,7 +56,7 @@
  Object element for <xref:System.Windows.Controls.ControlTemplate> or a derived class.  
   
  *VisualTreeRootNode*  
- A single [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element as the immediate child of the <xref:System.Windows.Controls.ControlTemplate> (or a derived class). Templates must have a single root node. In order to generate a useful template, the element chosen as *VisualTreeRootNode* is expected to support a content model of its own, often a model that supports multiple child elements.  
+ A single XAML element as the immediate child of the <xref:System.Windows.Controls.ControlTemplate> (or a derived class). Templates must have a single root node. In order to generate a useful template, the element chosen as *VisualTreeRootNode* is expected to support a content model of its own, often a model that supports multiple child elements.  
   
  *VisualTreeNodeContents*  
  One or more elements that complete the intended template. If the element chosen as *VisualTreeRootNode* only supports a single child, then there can only be one element declared as *VisualTreeNodeContents*. It is also possible (though uncommon) to provide text content if the chosen *VisualTreeRootNode* supports a text content property.  
diff --git a/xml/System.Windows.Controls/DocumentViewer.xml b/xml/System.Windows.Controls/DocumentViewer.xml
index 919f3783bba..e182e5d3d15 100644
--- a/xml/System.Windows.Controls/DocumentViewer.xml
+++ b/xml/System.Windows.Controls/DocumentViewer.xml
@@ -982,7 +982,7 @@
   
  The horizontal offset is measured from the left edge of the visible content area.  
   
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Width" or "Horizontal" properties.  
+ When setting this property in XAML, you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Width" or "Horizontal" properties.  
   
 <a name="dependencyPropertyInfo_HorizontalOffset"></a>   
 ## Dependency Property Information  
@@ -1051,7 +1051,7 @@
 ## Remarks  
  Setting the <xref:System.Windows.Controls.DocumentViewer.HorizontalPageSpacing%2A> property adjusts the horizontal spacing between pages.  
   
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Width" or "Horizontal" properties.  
+ When setting this property in XAML, you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Width" or "Horizontal" properties.  
   
 <a name="dependencyPropertyInfo_HorizontalPageSpacing"></a>   
 ## Dependency Property Information  
@@ -2331,7 +2331,7 @@
   
  The vertical offset is measured from the top of the visible content area.  
   
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Height" or "Vertical" properties.  
+ When setting this property in XAML, you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Height" or "Vertical" properties.  
   
 <a name="dependencyPropertyInfo_VerticalOffset"></a>   
 ## Dependency Property Information  
@@ -2401,7 +2401,7 @@
   
  The <xref:System.Windows.Controls.DocumentViewer.VerticalPageSpacing%2A> value must be non-negative.  Setting this property to a negative value will raise an <xref:System.ArgumentException> exception.  
   
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Height" or "Vertical" properties.  
+ When setting this property in XAML, you cannot use the unit qualifiers (such as `in` or `cm`) that are enabled for many other "Height" or "Vertical" properties.  
   
 <a name="dependencyPropertyInfo_VerticalPageSpacing"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/FlowDocumentReader.xml b/xml/System.Windows.Controls/FlowDocumentReader.xml
index 1e416da2d5d..fac84faf87d 100644
--- a/xml/System.Windows.Controls/FlowDocumentReader.xml
+++ b/xml/System.Windows.Controls/FlowDocumentReader.xml
@@ -2078,7 +2078,7 @@
   
  Rather than initiate this command, you can instead call <xref:System.Windows.Controls.FlowDocumentReader.SwitchViewingMode%2A> on the relevant <xref:System.Windows.Controls.FlowDocumentReader>. The result is the same.  
   
- The **Switch Viewing Mode** command can either be parameterless, in which case the viewing mode advances to the next available viewing mode in the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> enumeration sequence, or it can specify a viewing mode by naming the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> in the <xref:System.Windows.Input.RoutedUICommand> command parameters. If used to set a command property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the command must be parameterless.  
+ The **Switch Viewing Mode** command can either be parameterless, in which case the viewing mode advances to the next available viewing mode in the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> enumeration sequence, or it can specify a viewing mode by naming the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> in the <xref:System.Windows.Input.RoutedUICommand> command parameters. If used to set a command property in XAML, the command must be parameterless.  
   
  You could also use or respond to this command in a derived class, using either the built-in handling or replacing it with handling of your own. <xref:System.Windows.Controls.FlowDocumentReader.OnSwitchViewingModeCommand%2A> is a callback that you can use to change the class handling, without requiring changes to command bindings in the template or in instances.  
   
diff --git a/xml/System.Windows.Controls/Frame.xml b/xml/System.Windows.Controls/Frame.xml
index e7c163ff798..e70056a1baf 100644
--- a/xml/System.Windows.Controls/Frame.xml
+++ b/xml/System.Windows.Controls/Frame.xml
@@ -1539,12 +1539,12 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- External content is [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] content that is not included with an application as either a resource file or a content file (see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ External content is XAML content that is not included with an application as either a resource file or a content file (see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
- When <xref:System.Windows.Controls.Frame.SandboxExternalContent%2A> is `true`, and the source for the content of the <xref:System.Windows.Controls.Frame> is an external [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, the content is loaded into a partial trust security sandbox that is limited to the default `Internet` permission set. The external content is subsequently loaded into a separate process. As a result, the external content becomes isolated and does not have access to application-scope resources, such as resource dictionaries (see <xref:System.Windows.ResourceDictionary>).  
+ When <xref:System.Windows.Controls.Frame.SandboxExternalContent%2A> is `true`, and the source for the content of the <xref:System.Windows.Controls.Frame> is an external XAML file, the content is loaded into a partial trust security sandbox that is limited to the default `Internet` permission set. The external content is subsequently loaded into a separate process. As a result, the external content becomes isolated and does not have access to application-scope resources, such as resource dictionaries (see <xref:System.Windows.ResourceDictionary>).  
   
 > [!NOTE]
->  <xref:System.Windows.Controls.Frame> will only contain external content when the <xref:System.Windows.Controls.Frame.Source%2A> property is set to the uniform resource identifier (URI) for an external [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file. <xref:System.Windows.Controls.Frame> content that is provided using the <xref:System.Windows.Controls.ContentControl.Content%2A> property is considered internal content and, subsequently, is not isolated.  
+>  <xref:System.Windows.Controls.Frame> will only contain external content when the <xref:System.Windows.Controls.Frame.Source%2A> property is set to the uniform resource identifier (URI) for an external XAML file. <xref:System.Windows.Controls.Frame> content that is provided using the <xref:System.Windows.Controls.ContentControl.Content%2A> property is considered internal content and, subsequently, is not isolated.  
   
 <a name="dependencyPropertyInfo_FrameSandboxExternalContent"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/GridView.xml b/xml/System.Windows.Controls/GridView.xml
index f2fd491e396..189f36df908 100644
--- a/xml/System.Windows.Controls/GridView.xml
+++ b/xml/System.Windows.Controls/GridView.xml
@@ -833,7 +833,7 @@
  A string that becomes the display text for the <xref:System.Windows.Controls.GridView.ColumnHeaderToolTip%2A>.  
   
  `toolTipObjectContent`  
- An object to use as the content for the tooltip. Typically, this object is a <xref:System.Windows.FrameworkElement> or some other element that defines a layout for the <xref:System.Windows.Controls.GridViewHeaderRowPresenter.ColumnHeaderToolTip%2A>, such as a text element. In this usage, a <xref:System.Windows.Controls.ToolTip> element is implicitly created from the parsed [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], and the `toolTipObjectContent` content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
+ An object to use as the content for the tooltip. Typically, this object is a <xref:System.Windows.FrameworkElement> or some other element that defines a layout for the <xref:System.Windows.Controls.GridViewHeaderRowPresenter.ColumnHeaderToolTip%2A>, such as a text element. In this usage, a <xref:System.Windows.Controls.ToolTip> element is implicitly created from the parsed XAML, and the `toolTipObjectContent` content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
   
  <`ToolTip` .../>  
  See <xref:System.Windows.Controls.ToolTip>.  
diff --git a/xml/System.Windows.Controls/GridViewHeaderRowPresenter.xml b/xml/System.Windows.Controls/GridViewHeaderRowPresenter.xml
index 92053c7ea3a..8023f7d0ae3 100644
--- a/xml/System.Windows.Controls/GridViewHeaderRowPresenter.xml
+++ b/xml/System.Windows.Controls/GridViewHeaderRowPresenter.xml
@@ -638,7 +638,7 @@
  A string that becomes the display text for the <xref:System.Windows.Controls.GridViewHeaderRowPresenter.ColumnHeaderToolTip%2A>.  
   
  `toolTipObjectContent`  
- An object to use as the content for the tooltip. Typically, this object is a <xref:System.Windows.FrameworkElement> or some other element that defines a layout for the <xref:System.Windows.Controls.GridViewHeaderRowPresenter.ColumnHeaderToolTip%2A>, such as a text element. In this usage, a <xref:System.Windows.Controls.ToolTip> element is implicitly created from the parsed [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], and the `toolTipObjectContent` content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
+ An object to use as the content for the tooltip. Typically, this object is a <xref:System.Windows.FrameworkElement> or some other element that defines a layout for the <xref:System.Windows.Controls.GridViewHeaderRowPresenter.ColumnHeaderToolTip%2A>, such as a text element. In this usage, a <xref:System.Windows.Controls.ToolTip> element is implicitly created from the parsed XAML, and the `toolTipObjectContent` content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
   
  <`ToolTip` .../>  
  See <xref:System.Windows.Controls.ToolTip>.  
diff --git a/xml/System.Windows.Controls/Image.xml b/xml/System.Windows.Controls/Image.xml
index e0f11f1b08e..78a5215b504 100644
--- a/xml/System.Windows.Controls/Image.xml
+++ b/xml/System.Windows.Controls/Image.xml
@@ -391,7 +391,7 @@
   
 <a name="xamlTextUsage_Source"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see the <xref:System.Windows.Media.ImageSource> type.  
+ For XAML information, see the <xref:System.Windows.Media.ImageSource> type.  
   
 <a name="xamlValues_Source"></a>   
 ## XAML Values  
diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index 7220bf2102d..14d18c3d5af 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -723,7 +723,7 @@
   
 <a name="xamlTextUsage_DefaultStylusPointDescription"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this property in XAML.  
   
    
   
@@ -1103,7 +1103,7 @@
   
 <a name="xamlTextUsage_EraserShape"></a>   
 ## XAML Text Usage  
- This property is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property is not typically used in XAML.  
   
    
   
diff --git a/xml/System.Windows.Controls/ItemCollection.xml b/xml/System.Windows.Controls/ItemCollection.xml
index b855ae46a38..1608f60f547 100644
--- a/xml/System.Windows.Controls/ItemCollection.xml
+++ b/xml/System.Windows.Controls/ItemCollection.xml
@@ -90,7 +90,7 @@
 [!code-csharp[GroupingSample#GetView](~/samples/snippets/csharp/VS_Snippets_Wpf/GroupingSample/CSharp/Window1.xaml.cs#getview)]
 [!code-vb[GroupingSample#GetView](~/samples/snippets/visualbasic/VS_Snippets_Wpf/GroupingSample/visualbasic/window1.xaml.vb#getview)]  
   
- Alternately, you can specify filtering, sorting, and grouping criteria in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] using <xref:System.Windows.Data.CollectionViewSource>.  
+ Alternately, you can specify filtering, sorting, and grouping criteria in XAML using <xref:System.Windows.Data.CollectionViewSource>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Controls/ItemsControl.xml b/xml/System.Windows.Controls/ItemsControl.xml
index fc3417f7dc8..cc34bc08fde 100644
--- a/xml/System.Windows.Controls/ItemsControl.xml
+++ b/xml/System.Windows.Controls/ItemsControl.xml
@@ -1578,7 +1578,7 @@ ListBox that contains multiple types of objects
 [!code-csharp[GroupingSample#GetView](~/samples/snippets/csharp/VS_Snippets_Wpf/GroupingSample/CSharp/Window1.xaml.cs#getview)]
 [!code-vb[GroupingSample#GetView](~/samples/snippets/visualbasic/VS_Snippets_Wpf/GroupingSample/visualbasic/window1.xaml.vb#getview)]  
   
- Alternately, you can specify filtering, sorting, and grouping criteria in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] or code by using a <xref:System.Windows.Data.CollectionViewSource>.  
+ Alternately, you can specify filtering, sorting, and grouping criteria in XAML or code by using a <xref:System.Windows.Data.CollectionViewSource>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/SpellCheck.xml b/xml/System.Windows.Controls/SpellCheck.xml
index 0536d6fb898..3f096e8f5f9 100644
--- a/xml/System.Windows.Controls/SpellCheck.xml
+++ b/xml/System.Windows.Controls/SpellCheck.xml
@@ -217,7 +217,7 @@ ListBox
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has a specialized write-only attached property usage. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax for setting the property is `<`*textBoxBaseClass* **SpellCheck.IsEnabled**`="`*boolValue*`" .../>`, where *textBoxBaseClass* is an object element for a class that derives from <xref:System.Windows.Controls.Primitives.TextBoxBase>, and *boolValue* is either `true` or `false` (case insensitive). To set the property as an attached property in code, see the <xref:System.Windows.Controls.SpellCheck.SetIsEnabled%2A> method. There is no matching `GetIsEnabled` accessor. To get the value, get the current <xref:System.Windows.Controls.SpellCheck> object from the <xref:System.Windows.Controls.Primitives.TextBoxBase.SpellCheck%2A?displayProperty=nameWithType> property, and then get the value of the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A> property from that <xref:System.Windows.Controls.SpellCheck>.  
+ This dependency property also has a specialized write-only attached property usage. The XAML syntax for setting the property is `<`*textBoxBaseClass* **SpellCheck.IsEnabled**`="`*boolValue*`" .../>`, where *textBoxBaseClass* is an object element for a class that derives from <xref:System.Windows.Controls.Primitives.TextBoxBase>, and *boolValue* is either `true` or `false` (case insensitive). To set the property as an attached property in code, see the <xref:System.Windows.Controls.SpellCheck.SetIsEnabled%2A> method. There is no matching `GetIsEnabled` accessor. To get the value, get the current <xref:System.Windows.Controls.SpellCheck> object from the <xref:System.Windows.Controls.Primitives.TextBoxBase.SpellCheck%2A?displayProperty=nameWithType> property, and then get the value of the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A> property from that <xref:System.Windows.Controls.SpellCheck>.  
   
 <a name="dependencyPropertyInfo_IsEnabled"></a>   
 ## Dependency Property Information  
@@ -282,7 +282,7 @@ ListBox
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method enables an attached property usage for the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A> property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. The following example shows the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage.  
+ This method enables an attached property usage for the <xref:System.Windows.Controls.SpellCheck.IsEnabled%2A> property in XAML. The following example shows the XAML usage.  
   
  ]]></format>
         </remarks>
@@ -319,7 +319,7 @@ ListBox
 ## Remarks  
  The spelling reform rules that are accessed by this method refer to the French and German spelling reforms of the 1990's. This method has no effect when it is used with any other language.  
   
- This method enables an attached property usage for the <xref:System.Windows.Controls.SpellCheck.SpellingReform%2A> property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This method enables an attached property usage for the <xref:System.Windows.Controls.SpellCheck.SpellingReform%2A> property in XAML.  
   
  ]]></format>
         </remarks>
@@ -351,7 +351,7 @@ ListBox
 ## Remarks  
  The spelling reform rules that are determined by this property refer to the French and German spelling reforms. This property has no effect when it is used with any other language.  
   
- This dependency property also has a specialized write-only attached property usage. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax for setting the property is `<`*textBoxBaseClass* **SpellCheck.SpellingReform**`="`*enumValue*`" .../>`, where *textBoxBaseClass* is an object element for a class that derives from <xref:System.Windows.Controls.Primitives.TextBoxBase>, and *enumValue* is a string name for a value of the <xref:System.Windows.Controls.SpellingReform> enumeration. To set the property as an attached property in code, see the <xref:System.Windows.Controls.SpellCheck.SetSpellingReform%2A> method. There is no matching `GetSpellingReform` accessor. To get the value, get the current <xref:System.Windows.Controls.SpellCheck> object from the <xref:System.Windows.Controls.Primitives.TextBoxBase.SpellCheck%2A?displayProperty=nameWithType> property, and then get the value of the <xref:System.Windows.Controls.SpellCheck.SpellingReform%2A> property from that <xref:System.Windows.Controls.SpellCheck>.  
+ This dependency property also has a specialized write-only attached property usage. The XAML syntax for setting the property is `<`*textBoxBaseClass* **SpellCheck.SpellingReform**`="`*enumValue*`" .../>`, where *textBoxBaseClass* is an object element for a class that derives from <xref:System.Windows.Controls.Primitives.TextBoxBase>, and *enumValue* is a string name for a value of the <xref:System.Windows.Controls.SpellingReform> enumeration. To set the property as an attached property in code, see the <xref:System.Windows.Controls.SpellCheck.SetSpellingReform%2A> method. There is no matching `GetSpellingReform` accessor. To get the value, get the current <xref:System.Windows.Controls.SpellCheck> object from the <xref:System.Windows.Controls.Primitives.TextBoxBase.SpellCheck%2A?displayProperty=nameWithType> property, and then get the value of the <xref:System.Windows.Controls.SpellCheck.SpellingReform%2A> property from that <xref:System.Windows.Controls.SpellCheck>.  
   
 <a name="dependencyPropertyInfo_SpellingReform"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index 7732f5436aa..38e82822222 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -275,7 +275,7 @@
 ## Remarks  
  The baseline is the imaginary horizontal line with which the base of each character in a line of text is aligned.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.BaselineOffset="double".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetBaselineOffset%2A> and <xref:System.Windows.Controls.TextBlock.SetBaselineOffset%2A>.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.BaselineOffset="double".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetBaselineOffset%2A> and <xref:System.Windows.Controls.TextBlock.SetBaselineOffset%2A>.  
   
  ]]></format>
         </remarks>
@@ -467,7 +467,7 @@
   
  This property specifies a preference only.  If the specified font family is not available, the <xref:System.Windows.Controls.TextBlock> silently falls back to the font determined by the <xref:System.Windows.SystemFonts.MessageFontFamily%2A> value.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.FontFamily="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontFamily%2A> and <xref:System.Windows.Controls.TextBlock.SetFontFamily%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontFamily` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.FontFamily="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontFamily%2A> and <xref:System.Windows.Controls.TextBlock.SetFontFamily%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontFamily` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="xamlAttributeUsage_FontFamily"></a>   
 ## XAML Attribute Usage  
@@ -578,7 +578,7 @@
 ## Remarks  
  Any <xref:System.Windows.Controls.TextBlock.FontSize%2A> settings on child elements override this top-level setting.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.FontSize="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontSize%2A> and <xref:System.Windows.Controls.TextBlock.SetFontSize%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontSize` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.FontSize="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontSize%2A> and <xref:System.Windows.Controls.TextBlock.SetFontSize%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontSize` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="xamlAttributeUsage_FontSize"></a>   
 ## XAML Attribute Usage  
@@ -679,7 +679,7 @@
 ## Remarks  
  Any <xref:System.Windows.Controls.TextBlock.FontStretch%2A> settings on child elements override this top-level setting.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.FontStretch="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format property names of the <xref:System.Windows.FontStretch> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontStretch%2A> and <xref:System.Windows.Controls.TextBlock.SetFontStretch%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontStretch` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.FontStretch="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format property names of the <xref:System.Windows.FontStretch> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontStretch%2A> and <xref:System.Windows.Controls.TextBlock.SetFontStretch%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontStretch` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontStretch"></a>   
 ## Dependency Property Information  
@@ -753,7 +753,7 @@
 ## Remarks  
  Any <xref:System.Windows.Controls.TextBlock.FontStyle%2A> settings on child elements override this top-level setting.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.FontStyle="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format property names in the <xref:System.Windows.FontStyles> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontStyle%2A> and <xref:System.Windows.Controls.TextBlock.SetFontStyle%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontStyle` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.FontStyle="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format property names in the <xref:System.Windows.FontStyles> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontStyle%2A> and <xref:System.Windows.Controls.TextBlock.SetFontStyle%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontStyle` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontStyle"></a>   
 ## Dependency Property Information  
@@ -829,7 +829,7 @@
   
  For a list of valid values of font weights, see the <xref:System.Windows.FontWeights> class.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.FontWeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values of a property of the <xref:System.Windows.FontWeights> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontWeight%2A> and <xref:System.Windows.Controls.TextBlock.SetFontWeight%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontWeight` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.FontWeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values of a property of the <xref:System.Windows.FontWeights> class. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetFontWeight%2A> and <xref:System.Windows.Controls.TextBlock.SetFontWeight%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `FontWeight` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontWeight"></a>   
 ## Dependency Property Information  
@@ -905,7 +905,7 @@
   
  Any <xref:System.Windows.Controls.TextBlock.Foreground%2A> settings on child elements override this top-level setting.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.Foreground="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string that resolves to a <xref:System.Windows.Media.Brush> implementation value. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetForeground%2A> and <xref:System.Windows.Controls.TextBlock.SetForeground%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `Foreground` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.Foreground="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string that resolves to a <xref:System.Windows.Media.Brush> implementation value. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetForeground%2A> and <xref:System.Windows.Controls.TextBlock.SetForeground%2A>. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Controls.TextBlock> support an analogous nonattached `Foreground` property, which the <xref:System.Windows.Controls.TextBlock> uses for rendering.  
   
 <a name="dependencyPropertyInfo_Foreground"></a>   
 ## Dependency Property Information  
@@ -1595,7 +1595,7 @@
   
  In addition to this property, the layout of lines in a <xref:System.Windows.Controls.TextBlock> is affected by its <xref:System.Windows.Controls.TextBlock.LineStackingStrategy%2A> property.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.LineHeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetLineHeight%2A> and <xref:System.Windows.Controls.TextBlock.SetLineHeight%2A>. The attached property usage is not common.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.LineHeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetLineHeight%2A> and <xref:System.Windows.Controls.TextBlock.SetLineHeight%2A>. The attached property usage is not common.  
   
 <a name="xamlAttributeUsage_LineHeight"></a>   
 ## XAML Attribute Usage  
@@ -1702,7 +1702,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.LineStackingStrategy="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string value of the <xref:System.Windows.LineStackingStrategy> enumeration. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetLineStackingStrategy%2A> and <xref:System.Windows.Controls.TextBlock.SetLineStackingStrategy%2A>. The attached property usage is not common.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.LineStackingStrategy="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string value of the <xref:System.Windows.LineStackingStrategy> enumeration. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetLineStackingStrategy%2A> and <xref:System.Windows.Controls.TextBlock.SetLineStackingStrategy%2A>. The attached property usage is not common.  
   
 <a name="dependencyPropertyInfo_LineStackingStrategy"></a>   
 ## Dependency Property Information  
@@ -2766,7 +2766,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextBlock.TextAlignment="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string value of the <xref:System.Windows.TextAlignment> enumeration. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetTextAlignment%2A> and <xref:System.Windows.Controls.TextBlock.SetTextAlignment%2A>. The attached property usage is not common.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextBlock.TextAlignment="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is a string value of the <xref:System.Windows.TextAlignment> enumeration. In code, the attached property usage is supported by <xref:System.Windows.Controls.TextBlock.GetTextAlignment%2A> and <xref:System.Windows.Controls.TextBlock.SetTextAlignment%2A>. The attached property usage is not common.  
   
 <a name="dependencyPropertyInfo_TextAlignment"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/TextSearch.xml b/xml/System.Windows.Controls/TextSearch.xml
index 5494b1f60b4..0cd6e9ceeb1 100644
--- a/xml/System.Windows.Controls/TextSearch.xml
+++ b/xml/System.Windows.Controls/TextSearch.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_TextSearch"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but you can use its static properties to assign values in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML, but you can use its static properties to assign values in XAML.  
   
    
   
diff --git a/xml/System.Windows.Controls/ToolBar.xml b/xml/System.Windows.Controls/ToolBar.xml
index fe365f9d214..eed4224920f 100644
--- a/xml/System.Windows.Controls/ToolBar.xml
+++ b/xml/System.Windows.Controls/ToolBar.xml
@@ -503,7 +503,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is a read-only attached property. Read-only attached properties are uncommon, and have no direct [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage. However, you can use the attached property reference as a property trigger in a style, to apply different style values to an item within a toolbar that is in the overflow panel.  
+ This property is a read-only attached property. Read-only attached properties are uncommon, and have no direct XAML usage. However, you can use the attached property reference as a property trigger in a style, to apply different style values to an item within a toolbar that is in the overflow panel.  
   
 <a name="dependencyPropertyInfo_IsOverflowItem"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/ToolTipService.xml b/xml/System.Windows.Controls/ToolTipService.xml
index bb8a8d0287d..358d76c4cd0 100644
--- a/xml/System.Windows.Controls/ToolTipService.xml
+++ b/xml/System.Windows.Controls/ToolTipService.xml
@@ -1997,7 +1997,7 @@ This is an attached property. For information about how to get the value of this
   
  This property is an attached property. For information about how to get or set the value of this property in code, see the <xref:System.Windows.Controls.ToolTipService.GetToolTip%2A> and <xref:System.Windows.Controls.ToolTipService.SetToolTip%2A> methods.  
   
- The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax shown here is appropriate if the object that fills the tooltip is a primitive with native type conversion, such as a string. If the object does not support native type conversion or support its own type converter, you might need to specify a verbose form of attached property syntax as follows:  
+ The XAML syntax shown here is appropriate if the object that fills the tooltip is a primitive with native type conversion, such as a string. If the object does not support native type conversion or support its own type converter, you might need to specify a verbose form of attached property syntax as follows:  
   
 ```  
 <object>  
@@ -2007,7 +2007,7 @@ This is an attached property. For information about how to get the value of this
 </object>  
 ```  
   
- The placeholder element *objectThatFillsTheToolTip* could also have child elements, if that object permits them. However, the need for this usage should be relatively rare, because most [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usages will instead use practical control implementations of the service that are exposed by <xref:System.Windows.Controls.ToolTip>.  
+ The placeholder element *objectThatFillsTheToolTip* could also have child elements, if that object permits them. However, the need for this usage should be relatively rare, because most XAML usages will instead use practical control implementations of the service that are exposed by <xref:System.Windows.Controls.ToolTip>.  
   
 <a name="dependencyPropertyInfo_ToolTip"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/TreeViewItem.xml b/xml/System.Windows.Controls/TreeViewItem.xml
index 6d95b49d00e..ef057795f2a 100644
--- a/xml/System.Windows.Controls/TreeViewItem.xml
+++ b/xml/System.Windows.Controls/TreeViewItem.xml
@@ -324,7 +324,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following examples show how to find the selected <xref:System.Windows.Controls.TreeViewItem> and expand it and all of it child items.  The following [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] creates a <xref:System.Windows.Controls.TreeView> and populates it with some data.  
+ The following examples show how to find the selected <xref:System.Windows.Controls.TreeViewItem> and expand it and all of it child items.  The following XAML creates a <xref:System.Windows.Controls.TreeView> and populates it with some data.  
   
  [!code-xaml[TreeViewExpand#1](~/samples/snippets/csharp/VS_Snippets_Wpf/treeviewexpand/csharp/mainwindow.xaml#1)]  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index d825f706000..2bb518b1b31 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -135,7 +135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports attached event usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This method supports attached event usage in XAML.  
   
  ]]></format>
         </remarks>
@@ -170,7 +170,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports attached event usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This method supports attached event usage in XAML.  
   
  ]]></format>
         </remarks>
@@ -347,7 +347,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If you do not set this property, the binding engine uses the `Language` property of the binding target object. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] this defaults to "en-US" or inherits the value from the root element (or any element) of the page, if one has been explicitly set.  
+ If you do not set this property, the binding engine uses the `Language` property of the binding target object. In XAML this defaults to "en-US" or inherits the value from the root element (or any element) of the page, if one has been explicitly set.  
   
  For information about data conversion, see the Data Conversion section in the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -835,7 +835,7 @@
   
  The <xref:System.Windows.Data.Binding.ElementName%2A?displayProperty=nameWithType> and <xref:System.Windows.Data.Binding.Source%2A?displayProperty=nameWithType> properties also enable you to set the source of the binding explicitly. However, only one of the three properties, <xref:System.Windows.Data.Binding.ElementName%2A>, <xref:System.Windows.Data.Binding.Source%2A>, and <xref:System.Windows.Data.Binding.RelativeSource%2A>, should be set for each binding, or a conflict can occur. This property throws an exception if there is a binding source conflict.  
   
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
     
 ## Examples  
  The following example shows a style trigger that creates a <xref:System.Windows.Controls.ToolTip> that reports a validation error message. The value of the setter binds to the error content of the current <xref:System.Windows.Controls.TextBox> (the <xref:System.Windows.Controls.TextBox> using the style) using the <xref:System.Windows.Data.Binding.RelativeSource%2A> property. For more information on this example, see [How to: Implement Binding Validation](/dotnet/framework/wpf/data/how-to-implement-binding-validation).  
@@ -878,7 +878,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports attached event usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This method supports attached event usage in XAML.  
   
  ]]></format>
         </remarks>
@@ -913,7 +913,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports attached event usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This method supports attached event usage in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/BindingBase.xml b/xml/System.Windows.Data/BindingBase.xml
index 2ddb507148d..9c0bd732487 100644
--- a/xml/System.Windows.Data/BindingBase.xml
+++ b/xml/System.Windows.Data/BindingBase.xml
@@ -237,10 +237,10 @@
 ## Remarks  
  This implementation provides the base syntax support for binding through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] for all provided practical derived classes (<xref:System.Windows.Data.Binding>, <xref:System.Windows.Data.PriorityBinding>, and <xref:System.Windows.Data.MultiBinding>).  
   
- The <xref:System.Windows.Data.BindingBase> class implementation of this method is expected to return an expression object that is the result of a binding. Binding a property works by targeting a given <xref:System.Windows.DependencyProperty> on a given <xref:System.Windows.DependencyObject>. These two pieces of information are transmitted by querying for an <xref:System.Windows.Markup.IProvideValueTarget> implementation on the `serviceProvider`, which the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] reader makes available during parsing of a binding. This base class implementation is responsible for checking for a valid <xref:System.Windows.DependencyProperty> and <xref:System.Windows.DependencyObject>. If these are found, the actual implementation of returning a binding expression falls to various derived classes, as implemented by having the base class call an internal abstract method. Otherwise, the extension returns the binding object itself. Returning the binding itself results in a type mismatch error, but this should not occur under normal circumstances.  
+ The <xref:System.Windows.Data.BindingBase> class implementation of this method is expected to return an expression object that is the result of a binding. Binding a property works by targeting a given <xref:System.Windows.DependencyProperty> on a given <xref:System.Windows.DependencyObject>. These two pieces of information are transmitted by querying for an <xref:System.Windows.Markup.IProvideValueTarget> implementation on the `serviceProvider`, which the WPF XAML reader makes available during parsing of a binding. This base class implementation is responsible for checking for a valid <xref:System.Windows.DependencyProperty> and <xref:System.Windows.DependencyObject>. If these are found, the actual implementation of returning a binding expression falls to various derived classes, as implemented by having the base class call an internal abstract method. Otherwise, the extension returns the binding object itself. Returning the binding itself results in a type mismatch error, but this should not occur under normal circumstances.  
   
 > [!IMPORTANT]
->  Because the syntax for binding through [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] as implemented in this method relies on implementing an internal override, and because <xref:System.Windows.Data.BindingBase.ProvideValue%2A?displayProperty=nameWithType> itself is sealed, a custom binding class that derives from <xref:System.Windows.Data.BindingBase> will not function correctly as a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] markup extension.  
+>  Because the syntax for binding through XAML as implemented in this method relies on implementing an internal override, and because <xref:System.Windows.Data.BindingBase.ProvideValue%2A?displayProperty=nameWithType> itself is sealed, a custom binding class that derives from <xref:System.Windows.Data.BindingBase> will not function correctly as a XAML markup extension.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/BindingStatus.xml b/xml/System.Windows.Data/BindingStatus.xml
index 284b4030cdd..82843f0fb87 100644
--- a/xml/System.Windows.Data/BindingStatus.xml
+++ b/xml/System.Windows.Data/BindingStatus.xml
@@ -23,7 +23,7 @@
   
 <a name="xamlTextUsage_BindingStatus"></a>   
 ## XAML Text Usage  
- You do not typically use this enumeration in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You do not typically use this enumeration in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Data/CollectionContainer.xml b/xml/System.Windows.Data/CollectionContainer.xml
index 10b5d55e4f3..71df648ac70 100644
--- a/xml/System.Windows.Data/CollectionContainer.xml
+++ b/xml/System.Windows.Data/CollectionContainer.xml
@@ -91,7 +91,7 @@
   
 <a name="xamlTextUsage_Collection"></a>   
 ## XAML Text Usage  
- In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you can use the <xref:System.Windows.Data.Binding> syntax to bind to a collection. For more information, see the <xref:System.Windows.Data.Binding> type.  
+ In XAML, you can use the <xref:System.Windows.Data.Binding> syntax to bind to a collection. For more information, see the <xref:System.Windows.Data.Binding> type.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/CollectionView.xml b/xml/System.Windows.Data/CollectionView.xml
index 4f243cc369d..05b2d51acd5 100644
--- a/xml/System.Windows.Data/CollectionView.xml
+++ b/xml/System.Windows.Data/CollectionView.xml
@@ -46,11 +46,11 @@
   
  In WPF applications, all collections have an associated default collection view. Rather than working with the collection directly, the binding engine always accesses the collection through the associated view. To get the default view, use the <xref:System.Windows.Data.CollectionViewSource.GetDefaultView%2A?displayProperty=nameWithType> method. An internal class based on <xref:System.Windows.Data.CollectionView> is the default view for collections that implement only <xref:System.Collections.IEnumerable>. <xref:System.Windows.Data.ListCollectionView> is the default view for collections that implement <xref:System.Collections.IList>. <xref:System.Windows.Data.BindingListCollectionView> is the default view for collections that implement <xref:System.ComponentModel.IBindingListView> or <xref:System.ComponentModel.IBindingList>.  
   
- Alternatively, you can create a view of your collection in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by using the <xref:System.Windows.Data.CollectionViewSource> class and then bind your control to that view. The <xref:System.Windows.Data.CollectionViewSource> class is the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representation of the <xref:System.Windows.Data.CollectionView> class. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
+ Alternatively, you can create a view of your collection in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by using the <xref:System.Windows.Data.CollectionViewSource> class and then bind your control to that view. The <xref:System.Windows.Data.CollectionViewSource> class is the XAML representation of the <xref:System.Windows.Data.CollectionView> class. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
   
  For more information, see "Binding to Collections" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
- To set a view in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], use the <xref:System.Windows.Data.CollectionViewSource> class. <xref:System.Windows.Data.CollectionViewSource> is the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representation of the <xref:System.Windows.Data.CollectionView> class, and it exposes the most commonly used members of the <xref:System.Windows.Data.CollectionView> class.  
+ To set a view in XAML, use the <xref:System.Windows.Data.CollectionViewSource> class. <xref:System.Windows.Data.CollectionViewSource> is the XAML representation of the <xref:System.Windows.Data.CollectionView> class, and it exposes the most commonly used members of the <xref:System.Windows.Data.CollectionView> class.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Data/CollectionViewGroup.xml b/xml/System.Windows.Data/CollectionViewGroup.xml
index 95832aff473..69cb7fa305b 100644
--- a/xml/System.Windows.Data/CollectionViewGroup.xml
+++ b/xml/System.Windows.Data/CollectionViewGroup.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_CollectionViewGroup"></a>   
 ## XAML Text Usage  
- You cannot use this class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this class in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Data/CollectionViewSource.xml b/xml/System.Windows.Data/CollectionViewSource.xml
index 6800255c1c5..cb20c8fad26 100644
--- a/xml/System.Windows.Data/CollectionViewSource.xml
+++ b/xml/System.Windows.Data/CollectionViewSource.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Data.CollectionViewSource> is a proxy for a <xref:System.Windows.Data.CollectionView> class, or a class derived from <xref:System.Windows.Data.CollectionView>. <xref:System.Windows.Data.CollectionViewSource> enables [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] code to set the commonly used <xref:System.Windows.Data.CollectionView> properties, passing these settings to the underlying view. <xref:System.Windows.Data.CollectionViewSource> has a <xref:System.Windows.Data.CollectionViewSource.View%2A> property that holds the actual view and a <xref:System.Windows.Data.CollectionViewSource.Source%2A> property that holds the source collection.  
+ <xref:System.Windows.Data.CollectionViewSource> is a proxy for a <xref:System.Windows.Data.CollectionView> class, or a class derived from <xref:System.Windows.Data.CollectionView>. <xref:System.Windows.Data.CollectionViewSource> enables XAML code to set the commonly used <xref:System.Windows.Data.CollectionView> properties, passing these settings to the underlying view. <xref:System.Windows.Data.CollectionViewSource> has a <xref:System.Windows.Data.CollectionViewSource.View%2A> property that holds the actual view and a <xref:System.Windows.Data.CollectionViewSource.Source%2A> property that holds the source collection.  
   
  You can think of a collection view as the layer on top of the binding source collection that allows you to navigate and display the collection based on sort, filter, and group queries, all without having to manipulate the underlying source collection itself. If the source collection implements the <xref:System.Collections.Specialized.INotifyCollectionChanged> interface, the changes raised by the <xref:System.Collections.Specialized.INotifyCollectionChanged.CollectionChanged> event are propagated to the views.  
   
@@ -297,7 +297,7 @@
 <a name="xamlValues_CollectionViewType"></a>   
 ## XAML Values  
  *typeName*  
- The name of the <xref:System.Type> that is contained by this view. Note the use of the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension) to specify a type in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ The name of the <xref:System.Type> that is contained by this view. Note the use of the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension) to specify a type in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/ObjectDataProvider.xml b/xml/System.Windows.Data/ObjectDataProvider.xml
index a9795d36546..5802f3bde2a 100644
--- a/xml/System.Windows.Data/ObjectDataProvider.xml
+++ b/xml/System.Windows.Data/ObjectDataProvider.xml
@@ -33,7 +33,7 @@
   
  There are many ways to create an object to use as a binding source. For example, you can create your object in the resources section of your [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] page, or you can create your object in code and set it as the `DataContext` of your window.  
   
- <xref:System.Windows.Data.ObjectDataProvider> enables you to create your object in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] and make it available as a binding source. It provides the following properties that enable you to execute a query on your object and bind to the results.  
+ <xref:System.Windows.Data.ObjectDataProvider> enables you to create your object in XAML and make it available as a binding source. It provides the following properties that enable you to execute a query on your object and bind to the results.  
   
 -   Use the <xref:System.Windows.Data.ObjectDataProvider.ConstructorParameters%2A> property to pass parameters to the constructor of your object.  
   
@@ -43,7 +43,7 @@
   
  This class is also useful when you want to replace your current binding source object with another object and have all the associated bindings updated.  
   
- <xref:System.Windows.Data.ObjectDataProvider> provides a convenient way to create and use objects as binding source objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but it does not replace existing data models.  
+ <xref:System.Windows.Data.ObjectDataProvider> provides a convenient way to create and use objects as binding source objects in XAML, but it does not replace existing data models.  
   
  If you are implementing your own objects for data binding, see [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview) for information and recommendations.  
   
diff --git a/xml/System.Windows.Data/RelativeSource.xml b/xml/System.Windows.Data/RelativeSource.xml
index dbb246b57dc..0aa0ee5a807 100644
--- a/xml/System.Windows.Data/RelativeSource.xml
+++ b/xml/System.Windows.Data/RelativeSource.xml
@@ -33,7 +33,7 @@
 ## Remarks  
  One of the ways to specify a binding source is to use the <xref:System.Windows.Data.Binding.RelativeSource%2A?displayProperty=nameWithType> property. This is the property type of that property. <xref:System.Windows.Data.RelativeSource> is simultaneously a markup extension implementation and a data object. When the extension returns itself (see <xref:System.Windows.Data.RelativeSource.ProvideValue%2A>), the relevant information is contained in the data. The main purpose of the markup extension is to allow a variable-argument constructor syntax in attribute form, so that the <xref:System.Windows.Data.RelativeSourceMode.FindAncestor> mode can be defined inline with the two extra arguments for ancestor type and level that the other modes do not require.  
   
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
 ## Examples  
  The following example shows a style trigger that creates a <xref:System.Windows.Controls.ToolTip> that reports a validation error message. Using the <xref:System.Windows.Data.Binding.RelativeSource%2A> property, the value of the setter binds to the error content of the current <xref:System.Windows.Controls.TextBox> (the <xref:System.Windows.Controls.TextBox> using the style). For more information on this example, see [How to: Implement Binding Validation](/dotnet/framework/wpf/data/how-to-implement-binding-validation).  
@@ -183,7 +183,7 @@
   
 <a name="xamlTextUsage_AncestorLevel"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
    
   
@@ -233,7 +233,7 @@
   
 <a name="xamlTextUsage_AncestorType"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
    
   
@@ -290,7 +290,7 @@
   
 <a name="xamlTextUsage_Mode"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
  ]]></format>
         </remarks>
@@ -327,7 +327,7 @@
   
 <a name="xamlTextUsage_PreviousData"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
  ]]></format>
         </remarks>
@@ -397,7 +397,7 @@
   
 <a name="xamlTextUsage_Self"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
    
   
@@ -570,7 +570,7 @@
   
 <a name="xamlTextUsage_TemplatedParent"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
    
   
diff --git a/xml/System.Windows.Data/RelativeSourceMode.xml b/xml/System.Windows.Data/RelativeSourceMode.xml
index 48c4ab92ff8..95496a657c5 100644
--- a/xml/System.Windows.Data/RelativeSourceMode.xml
+++ b/xml/System.Windows.Data/RelativeSourceMode.xml
@@ -23,7 +23,7 @@
   
 <a name="xamlTextUsage_RelativeSource"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
+ For XAML information, see [RelativeSource MarkupExtension](/dotnet/framework/wpf/advanced/relativesource-markupextension).  
   
    
   
diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index 9b677633b21..a07d3cfecf2 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -415,7 +415,7 @@
    
   
 ## Examples  
- In some applications, embedding the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] inline within the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page can be inconvenient because the exact content of the data must be known at compile time. Therefore, you can obtain the data from an external [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, as in the following example.  
+ In some applications, embedding the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] inline within the XAML page can be inconvenient because the exact content of the data must be known at compile time. Therefore, you can obtain the data from an external [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, as in the following example.  
   
  [!code-xaml[XMLDataSource2#XmlFileExample](~/samples/snippets/csharp/VS_Snippets_Wpf/XmlDataSource2/CS/Window1.xaml#xmlfileexample)]  
   
diff --git a/xml/System.Windows.Documents/Block.xml b/xml/System.Windows.Documents/Block.xml
index 9cfed2c430f..81345c615b5 100644
--- a/xml/System.Windows.Documents/Block.xml
+++ b/xml/System.Windows.Documents/Block.xml
@@ -865,7 +865,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object Block.LineStackingStrategy="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.Block> derived class, and *value* is a string value of the <xref:System.Windows.LineStackingStrategy> enumeration. In code, the attached property usage is supported by the <xref:System.Windows.Documents.Block.GetLineStackingStrategy%2A> and <xref:System.Windows.Documents.Block.SetLineStackingStrategy%2A> methods. The attached property usage is not common.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object Block.LineStackingStrategy="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.Block> derived class, and *value* is a string value of the <xref:System.Windows.LineStackingStrategy> enumeration. In code, the attached property usage is supported by the <xref:System.Windows.Documents.Block.GetLineStackingStrategy%2A> and <xref:System.Windows.Documents.Block.SetLineStackingStrategy%2A> methods. The attached property usage is not common.  
   
 <a name="dependencyPropertyInfo_LineStackingStrategy"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Documents/Glyphs.xml b/xml/System.Windows.Documents/Glyphs.xml
index 17a20d31eac..e6f7871557f 100644
--- a/xml/System.Windows.Documents/Glyphs.xml
+++ b/xml/System.Windows.Documents/Glyphs.xml
@@ -25,7 +25,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Documents.Glyphs> element represents the output of a <xref:System.Windows.Media.GlyphRun> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. The following markup syntax is used to describe the <xref:System.Windows.Documents.Glyphs> element.  
+ The <xref:System.Windows.Documents.Glyphs> element represents the output of a <xref:System.Windows.Media.GlyphRun> in XAML. The following markup syntax is used to describe the <xref:System.Windows.Documents.Glyphs> element.  
   
 [!code-xaml[GlyphsOvwSample1#1](~/samples/snippets/csharp/VS_Snippets_Wpf/GlyphsOvwSample1/CS/default.xaml#1)]   
   
diff --git a/xml/System.Windows.Documents/PageContent.xml b/xml/System.Windows.Documents/PageContent.xml
index da33e81ad40..77917b73041 100644
--- a/xml/System.Windows.Documents/PageContent.xml
+++ b/xml/System.Windows.Documents/PageContent.xml
@@ -127,7 +127,7 @@
 ## Remarks  
  The <xref:System.Windows.Documents.PageContent.Child%2A> property returns a <xref:System.Windows.Documents.FixedPage> when:  
   
-1.  <xref:System.Windows.Documents.PageContent> has an immediate <xref:System.Windows.Documents.FixedPage> child defined in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] markup.  
+1.  <xref:System.Windows.Documents.PageContent> has an immediate <xref:System.Windows.Documents.FixedPage> child defined in XAML markup.  
   
 2.  The <xref:System.Windows.Documents.PageContent.System%23Windows%23Markup%23IAddChild%23AddChild%2A> has been called to set the <xref:System.Windows.Documents.FixedPage> as the child of the <xref:System.Windows.Documents.PageContent>.  
   
diff --git a/xml/System.Windows.Documents/TextElement.xml b/xml/System.Windows.Documents/TextElement.xml
index 22ffb7f3c53..8e04cff57f8 100644
--- a/xml/System.Windows.Documents/TextElement.xml
+++ b/xml/System.Windows.Documents/TextElement.xml
@@ -270,7 +270,7 @@
   
  This property specifies a preference only.  If the specified font family is not available, the <xref:System.Windows.Documents.FlowDocument> silently falls back to the font determined by the <xref:System.Windows.SystemFonts.MessageFontFamily%2A> value.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.FontFamily="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontFamily%2A> and <xref:System.Windows.Documents.TextElement.SetFontFamily%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontFamily` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.FontFamily="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Controls.TextBlock>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontFamily%2A> and <xref:System.Windows.Documents.TextElement.SetFontFamily%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontFamily` property, which the content host uses for rendering.  
   
 <a name="xamlAttributeUsage_FontFamily"></a>   
 ## XAML Attribute Usage  
@@ -381,7 +381,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.FontSize="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontSize%2A> and <xref:System.Windows.Documents.TextElement.SetFontSize%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontSize` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.FontSize="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontSize%2A> and <xref:System.Windows.Documents.TextElement.SetFontSize%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontSize` property, which the content host uses for rendering.  
   
 <a name="xamlAttributeUsage_FontSize"></a>   
 ## XAML Attribute Usage  
@@ -484,7 +484,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.FontStretch="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format property names of the <xref:System.Windows.FontStretch> class. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontStretch%2A> and <xref:System.Windows.Documents.TextElement.SetFontStretch%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontStretch` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.FontStretch="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format property names of the <xref:System.Windows.FontStretch> class. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontStretch%2A> and <xref:System.Windows.Documents.TextElement.SetFontStretch%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontStretch` property, which the content host uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontStretch"></a>   
 ## Dependency Property Information  
@@ -558,7 +558,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.FontStyle="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format property names in the <xref:System.Windows.FontStyles> class. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontStyle%2A> and <xref:System.Windows.Documents.TextElement.SetFontStyle%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontStyle` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.FontStyle="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format property names in the <xref:System.Windows.FontStyles> class. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontStyle%2A> and <xref:System.Windows.Documents.TextElement.SetFontStyle%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontStyle` property, which the content host uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontStyle"></a>   
 ## Dependency Property Information  
@@ -632,7 +632,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.FontWeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format values of the <xref:System.Windows.FontWeight> enumeration. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontWeight%2A> and <xref:System.Windows.Documents.TextElement.SetFontWeight%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontWeight` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.FontWeight="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is one of the string-format values of the <xref:System.Windows.FontWeight> enumeration. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetFontWeight%2A> and <xref:System.Windows.Documents.TextElement.SetFontWeight%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `FontWeight` property, which the content host uses for rendering.  
   
 <a name="dependencyPropertyInfo_FontWeight"></a>   
 ## Dependency Property Information  
@@ -708,7 +708,7 @@
 ## Remarks  
  For a table of swatches that shows the available predefined brush colors, see <xref:System.Windows.Media.Brushes>.  
   
- This dependency property also has an attached property usage. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<object TextElement.Foreground="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is a string that resolves to a <xref:System.Windows.Media.Brush> implementation value. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetForeground%2A> and <xref:System.Windows.Documents.TextElement.SetForeground%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `Foreground` property, which the content host uses for rendering.  
+ This dependency property also has an attached property usage. In XAML, the usage is `<object TextElement.Foreground="value".../>`, where *object* is an object element (typically a flow element) contained within a <xref:System.Windows.Documents.TextElement>, and *value* is a string that resolves to a <xref:System.Windows.Media.Brush> implementation value. In code, the attached property usage is supported by the <xref:System.Windows.Documents.TextElement.GetForeground%2A> and <xref:System.Windows.Documents.TextElement.SetForeground%2A> methods. The attached property usage is not common, because most elements that can be contained in a <xref:System.Windows.Documents.TextElement> support an analogous nonattached `Foreground` property, which the content host uses for rendering.  
   
 <a name="dependencyPropertyInfo_Foreground"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Documents/Typography.xml b/xml/System.Windows.Documents/Typography.xml
index 3dde58ffa1c..7956a89241e 100644
--- a/xml/System.Windows.Documents/Typography.xml
+++ b/xml/System.Windows.Documents/Typography.xml
@@ -87,7 +87,7 @@ Text using OpenType capitals
 |<xref:System.Windows.Documents.Typography.StylisticSet20%2A>|<xref:System.Boolean>|`false`|  
 |<xref:System.Windows.Documents.Typography.Variants%2A>|<xref:System.Windows.FontVariants.Inferior> &#124; <xref:System.Windows.FontVariants.Normal> &#124; <xref:System.Windows.FontVariants.Ordinal> &#124; <xref:System.Windows.FontVariants.Ruby> &#124; <xref:System.Windows.FontVariants.Subscript> &#124; <xref:System.Windows.FontVariants.Superscript>|<xref:System.Windows.FontVariants>.<xref:System.Windows.FontVariants.Normal>|  
   
- All dependency properties of this class also have an attached property usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. 
+ All dependency properties of this class also have an attached property usage in XAML. 
  For instance, you can set the <xref:System.Windows.Documents.Typography.AnnotationAlternates%2A> property through this syntax: 
 
  <*object* **Typography.AnnotationAlternates**="*`value`*" .../>
@@ -95,11 +95,11 @@ Text using OpenType capitals
    
   
 ## Examples  
- The following code sample shows the use typographic <xref:System.Windows.Documents.Typography.Capitals%2A> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Notice that the variant feature is applied to all text contained with the <xref:System.Windows.Documents.Paragraph> element.  
+ The following code sample shows the use typographic <xref:System.Windows.Documents.Typography.Capitals%2A> in XAML. Notice that the variant feature is applied to all text contained with the <xref:System.Windows.Documents.Paragraph> element.  
   
  [!code-xaml[TypographySnippets#TypographySnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/TypographySnippets/CS/PageTwo.xaml#typographysnippet2)]  
   
- The following code sample shows the use typographic <xref:System.Windows.Documents.Typography.Capitals%2A> and <xref:System.Windows.Documents.Typography.NumeralStyle%2A> features in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Notice that both typographic properties are applied to the entire paragraph.  
+ The following code sample shows the use typographic <xref:System.Windows.Documents.Typography.Capitals%2A> and <xref:System.Windows.Documents.Typography.NumeralStyle%2A> features in XAML. Notice that both typographic properties are applied to the entire paragraph.  
   
  [!code-xaml[TypographySnippets#TypographySnippet3](~/samples/snippets/csharp/VS_Snippets_Wpf/TypographySnippets/CS/PageThree.xaml#typographysnippet3)]  
   
@@ -135,7 +135,7 @@ Text using OpenType capitals
   
  If the value of <xref:System.Windows.Documents.Typography.AnnotationAlternates%2A> is greater than zero and the selected font does not support annotation alternates, the default form of the letter is displayed.  
   
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
 <a name="xamlAttributeUsage_AnnotationAlternates"></a>   
 ## XAML Attribute Usage  
@@ -199,7 +199,7 @@ Text using OpenType capitals
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Capitals are a set of typographical forms that render text in capital-styled glyphs. Typically, when text is rendered as all capitals, the spacing between letters can appear too tight, and the weight and proportion of the letters too heavy. OpenType supports a number of styling formats for capitals, including small capitals, petite capitals, titling, and capital spacing. These styling formats allow you to control the appearance of capitals.  
   
@@ -259,7 +259,7 @@ Example of capitals
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Capital spacing is a feature that allows you to provide more spacing when using all capitals in text. Capital letters are typically designed to blend with lowercase letters. Spacing that appears attractive between and a capital letter and a lowercase letter may look too tight when all capital letters are used. The following text displays normal and capital spacing for the Pescadero font.  
   
@@ -356,7 +356,7 @@ Example of normal and capital spacing
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
 <a name="xamlAttributeUsage_CaseSensitiveForms"></a>   
 ## XAML Attribute Usage  
@@ -421,7 +421,7 @@ Example of normal and capital spacing
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Random contextual alternates provide multiple substitute glyphs for a single character. When implemented with script-type fonts, this feature can simulate handwriting by using of a set of randomly chosen glyphs with slight differences in appearance. The following text uses random contextual alternates for the Lindsey font. Notice that the letter "a" varies slightly in appearance  
   
@@ -496,7 +496,7 @@ Example of random contextual alternates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Contextual ligatures are designed to enhance readability by providing better joining behavior between the characters that make up the ligature.  
   
@@ -567,7 +567,7 @@ Example of random contextual alternates
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Certain combinations of swash glyphs can cause an unattractive appearance, such as overlapping descenders on adjacent letters. Using a contextual swash allows you to use a substitute swash glyph that produces a better appearance. The following text shows the same word before and after a contextual swash is applied.  
   
@@ -642,7 +642,7 @@ Example of a contextual swash
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Discretionary ligatures are designed to be ornamental, and not specifically designed for readability. The following text displays discretionary ligature glyphs for the Pericles font.  
   
@@ -719,7 +719,7 @@ Example of discretionary set of ligatures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
 <a name="xamlAttributeUsage_EastAsianExpertForms"></a>   
 ## XAML Attribute Usage  
@@ -785,7 +785,7 @@ Example of discretionary set of ligatures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
 <a name="xamlAttributeUsage_EastAsianLanguage"></a>   
 ## XAML Attribute Usage  
@@ -851,7 +851,7 @@ Example of discretionary set of ligatures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
 <a name="xamlAttributeUsage_EastAsianWidths"></a>   
 ## XAML Attribute Usage  
@@ -917,7 +917,7 @@ Example of discretionary set of ligatures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  OpenType fonts support styles for fractions, including slashed and stacked.  
   
@@ -2456,7 +2456,7 @@ Example of slashed and stacked fraction styles
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Historical forms are typographic conventions that were common in the past. The following text displays the phrase, "Boston, Massachusetts", using an historical form of glyphs for the Palatino Linotype font.  
   
@@ -2531,7 +2531,7 @@ Example of historical forms
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Historical ligatures are typographic forms used in historical typography that font designers may add to their fonts.  
   
@@ -2602,7 +2602,7 @@ Example of historical forms
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Kerning is a typographic function that adjusts the spacing between characters to enhance word shape.  
   
@@ -2669,7 +2669,7 @@ Example of historical forms
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  If the value of <xref:System.Windows.Documents.Typography.MathematicalGreek%2A> is `true` and the selected font does not support mathematical Greek forms, the default form of the letter is displayed.  
   
@@ -2735,7 +2735,7 @@ Example of historical forms
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  OpenType fonts support a proportional and tabular figure feature to control the alignment of widths when using numerals. Proportional figures treat each numeral as having a different width - "1" is narrower than "5". Tabular figures are treated as equal-width numerals so that they align vertically, which increases the readability of financial type information.  
   
@@ -2812,7 +2812,7 @@ Example of proportional and tabbed figures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  OpenType fonts support an old style numeral format. This format is useful for displaying numerals in styles that are no longer standard. The following text displays an 18th century date in standard and old style numeral formats for the Palatino Linotype font.  
   
@@ -4183,7 +4183,7 @@ Example of standard and old style numeral sets
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  OpenType fonts support a slashed zero numeral format to emphasize the difference between the letter "O" and the numeral "0". The slashed zero numeral is often used for identifiers in financial and business information.  
   
@@ -4263,7 +4263,7 @@ Example of slashed zero numerals
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  The following text displays standard ligature glyphs for the Pericles font.  
   
@@ -4355,7 +4355,7 @@ Example of disabled standard ligatures
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Swashes are decorative glyphs that use elaborate ornamentation often associated with calligraphy. The following text displays standard and swash glyphs for the Pescadero font.  
   
@@ -4436,7 +4436,7 @@ Example of swashes used for capital letters
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Alternates are glyphs that can be substituted for a standard glyph. OpenType fonts, such as the Pericles font used in the following examples, contain alternate glyphs that you can use to create different appearances for text. The following text displays standard glyphs for the Pericles font.  
   
@@ -4525,7 +4525,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4570,7 +4570,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4637,7 +4637,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4704,7 +4704,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4771,7 +4771,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4838,7 +4838,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4905,7 +4905,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -4972,7 +4972,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5039,7 +5039,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5106,7 +5106,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5173,7 +5173,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5262,7 +5262,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5307,7 +5307,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5396,7 +5396,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5463,7 +5463,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5530,7 +5530,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5597,7 +5597,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5664,7 +5664,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5729,7 +5729,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5796,7 +5796,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Some fonts contain stylistic variant glyphs that correspond to portions of a character set. Glyphs in stylistic sets may be designed to harmonize visually, interact in particular ways, or work together in other ways.  
   
@@ -5862,7 +5862,7 @@ Example of other stylistic alternate glyphs
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This property gets or sets a value on the object that owns a `Typography` property, which is the only way to access a <xref:System.Windows.Documents.Typography> class instance. In addition, this property supports an attached property usage so that it can be set on text-containing objects in XAML.  
   
  Variants are similar to superscript or subscript font forms. It is possible for a font form to contain differing glyph sets between superscript and the ordinal form, or between subscript and inferior forms. The <xref:System.Windows.Documents.Typography.Variants%2A> property allows you to set superscript and subscript values for an OpenType font.  
   
diff --git a/xml/System.Windows.Ink/GestureRecognizer.xml b/xml/System.Windows.Ink/GestureRecognizer.xml
index 922588a2dd9..119684fb00d 100644
--- a/xml/System.Windows.Ink/GestureRecognizer.xml
+++ b/xml/System.Windows.Ink/GestureRecognizer.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_GestureRecognizer"></a>   
 ## XAML Text Usage  
- You cannot use this class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this class in XAML.  
   
    
   
diff --git a/xml/System.Windows.Input.StylusPlugIns/DynamicRenderer.xml b/xml/System.Windows.Input.StylusPlugIns/DynamicRenderer.xml
index fc0963735c0..1003633d731 100644
--- a/xml/System.Windows.Input.StylusPlugIns/DynamicRenderer.xml
+++ b/xml/System.Windows.Input.StylusPlugIns/DynamicRenderer.xml
@@ -26,7 +26,7 @@
  Dynamic rendering is done on a thread separate from the application's user interface thread when the user inputs ink with a tablet pen. When a mouse is used, dynamic rendering is done on the UI thread.  
   
 > [!NOTE]
->  In order to reference this class as a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element, you must map the <xref:System.Windows.Input.StylusPlugIns?displayProperty=nameWithType> CLR namespace to a prefix, and use that prefix to qualify the <xref:System.Windows.Input.StylusPlugIns.DynamicRenderer> element. For details, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
+>  In order to reference this class as a XAML element, you must map the <xref:System.Windows.Input.StylusPlugIns?displayProperty=nameWithType> CLR namespace to a prefix, and use that prefix to qualify the <xref:System.Windows.Input.StylusPlugIns.DynamicRenderer> element. For details, see [XAML Namespaces and Namespace Mapping for WPF XAML](/dotnet/framework/wpf/advanced/xaml-namespaces-and-namespace-mapping-for-wpf-xaml).  
   
 <a name="xamlTextUsage_DynamicRenderer"></a>   
 ## XAML Text Usage  
diff --git a/xml/System.Windows.Input/Cursors.xml b/xml/System.Windows.Input/Cursors.xml
index e8f24c8cd3f..1d4ea4b1269 100644
--- a/xml/System.Windows.Input/Cursors.xml
+++ b/xml/System.Windows.Input/Cursors.xml
@@ -23,9 +23,9 @@
 ## Remarks  
  This static class defines a set of default cursors common to applications.  
   
- The various static properties defining cursors are not directly usable in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but are indirectly used through two possible mechanisms:  
+ The various static properties defining cursors are not directly usable in XAML, but are indirectly used through two possible mechanisms:  
   
--   The <xref:System.Windows.Input.Cursor> class performs type conversion on any [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute that takes type <xref:System.Windows.Input.Cursor>, such that a value of the <xref:System.Windows.Input.CursorType> enumeration specified as the attribute value will evaluate to one of the static <xref:System.Windows.Input.Cursors> properties.  
+-   The <xref:System.Windows.Input.Cursor> class performs type conversion on any XAML attribute that takes type <xref:System.Windows.Input.Cursor>, such that a value of the <xref:System.Windows.Input.CursorType> enumeration specified as the attribute value will evaluate to one of the static <xref:System.Windows.Input.Cursors> properties.  
   
 -   A static property value can be used through the [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension).  
   
diff --git a/xml/System.Windows.Input/InputBindingCollection.xml b/xml/System.Windows.Input/InputBindingCollection.xml
index 66716616ef9..a81f126119b 100644
--- a/xml/System.Windows.Input/InputBindingCollection.xml
+++ b/xml/System.Windows.Input/InputBindingCollection.xml
@@ -34,7 +34,7 @@
 ## Remarks  
  All objects that derive from <xref:System.Windows.UIElement> have an <xref:System.Windows.Input.InputBindingCollection> named <xref:System.Windows.UIElement.InputBindings%2A>. All objects that derive from <xref:System.Windows.ContentElement> have an <xref:System.Windows.Input.InputBindingCollection> named <xref:System.Windows.ContentElement.InputBindings%2A>.  
   
- However, if these collections are set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], then the items in the collection must be derived classes of <xref:System.Windows.Input.InputBinding> rather than direct <xref:System.Windows.Input.InputBinding> objects. This is because <xref:System.Windows.Input.InputBinding> does not support a default public constructor. Therefore, the items in a <xref:System.Windows.Input.InputBindingCollection> that was set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will typically be an <xref:System.Windows.Input.InputBinding> derived class that does support a default public constructor, such as <xref:System.Windows.Input.KeyBinding> or <xref:System.Windows.Input.MouseBinding>.  
+ However, if these collections are set in XAML, then the items in the collection must be derived classes of <xref:System.Windows.Input.InputBinding> rather than direct <xref:System.Windows.Input.InputBinding> objects. This is because <xref:System.Windows.Input.InputBinding> does not support a default public constructor. Therefore, the items in a <xref:System.Windows.Input.InputBindingCollection> that was set in XAML will typically be an <xref:System.Windows.Input.InputBinding> derived class that does support a default public constructor, such as <xref:System.Windows.Input.KeyBinding> or <xref:System.Windows.Input.MouseBinding>.  
   
    
   
@@ -170,7 +170,7 @@
  [!code-csharp[commandingoverviewsnippets#CommandingOverviewKeyBinding](~/samples/snippets/csharp/VS_Snippets_Wpf/CommandingOverviewSnippets/CSharp/Window1.xaml.cs#commandingoverviewkeybinding)]
  [!code-vb[commandingoverviewsnippets#CommandingOverviewKeyBinding](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CommandingOverviewSnippets/visualbasic/window1.xaml.vb#commandingoverviewkeybinding)]  
   
- The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] example does not literally use <xref:System.Windows.Input.InputBindingCollection.Add%2A>, but <xref:System.Windows.Input.InputBindingCollection.Add%2A> is called implicitly by the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processing support for collections. For details on [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] and collections, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+ The XAML example does not literally use <xref:System.Windows.Input.InputBindingCollection.Add%2A>, but <xref:System.Windows.Input.InputBindingCollection.Add%2A> is called implicitly by the XAML processing support for collections. For details on XAML and collections, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/KeyBinding.xml b/xml/System.Windows.Input/KeyBinding.xml
index 8ed8613b57b..d4dce7fa7fb 100644
--- a/xml/System.Windows.Input/KeyBinding.xml
+++ b/xml/System.Windows.Input/KeyBinding.xml
@@ -23,11 +23,11 @@
 ## Remarks  
  A <xref:System.Windows.Input.KeyBinding> associates a <xref:System.Windows.Input.KeyGesture> with a <xref:System.Windows.Input.ICommand>, such as a <xref:System.Windows.Input.RoutedCommand>. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the WPF commanding system .  In general, when the <xref:System.Windows.Input.KeyGesture> is executed the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
   
- With the exception of the function keys and the numeric keypad keys, a valid <xref:System.Windows.Input.KeyGesture> must contain exactly one <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  Function keys and numeric keypad keys do not require a modifier key in order to be a valid <xref:System.Windows.Input.KeyGesture>. It is possible to specify an invalid <xref:System.Windows.Input.KeyGesture> and a <xref:System.Windows.Input.KeyBinding> with an invalid associated gesture, either through [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] or code. For instance, there is no validation that prevents creating and binding a <xref:System.Windows.Input.KeyGesture> that contains only a nonfunction key, or only modifiers but no key. Such a <xref:System.Windows.Input.KeyBinding> will never attempt to invoke its associated command.  
+ With the exception of the function keys and the numeric keypad keys, a valid <xref:System.Windows.Input.KeyGesture> must contain exactly one <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  Function keys and numeric keypad keys do not require a modifier key in order to be a valid <xref:System.Windows.Input.KeyGesture>. It is possible to specify an invalid <xref:System.Windows.Input.KeyGesture> and a <xref:System.Windows.Input.KeyBinding> with an invalid associated gesture, either through XAML or code. For instance, there is no validation that prevents creating and binding a <xref:System.Windows.Input.KeyGesture> that contains only a nonfunction key, or only modifiers but no key. Such a <xref:System.Windows.Input.KeyBinding> will never attempt to invoke its associated command.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
- A <xref:System.Windows.Input.KeyBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.KeyBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
+ A <xref:System.Windows.Input.KeyBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.KeyBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in XAML by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
   
    
   
@@ -271,7 +271,7 @@
 ## Remarks  
  With the exception of the function keys and the numeric keypad keys, a <xref:System.Windows.Input.KeyGesture> must contain a <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
  ]]></format>
         </remarks>
@@ -332,7 +332,7 @@
 ## Remarks  
  With the exception of the function keys and the numeric keypad keys, a <xref:System.Windows.Input.KeyGesture> must contain a <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
 <a name="xamlAttributeUsage_Modifiers"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Input/KeyGesture.xml b/xml/System.Windows.Input/KeyGesture.xml
index 1b01e1d1556..5d4da392abc 100644
--- a/xml/System.Windows.Input/KeyGesture.xml
+++ b/xml/System.Windows.Input/KeyGesture.xml
@@ -37,7 +37,7 @@
   
  You can use a <xref:System.Windows.Input.KeyBinding> to bind a <xref:System.Windows.Input.KeyGesture> to an <xref:System.Windows.Input.ICommand>, so that the command is invoked when the <xref:System.Windows.Input.KeyGesture> occurs.  
   
- For <xref:System.Windows.Input.KeyGesture> [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usages, the property that is generally set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is <xref:System.Windows.Input.KeyBinding.Gesture%2A>, in cases where the gesture represents both a standard key and a modifier key. You can also set the <xref:System.Windows.Input.KeyBinding.Gesture%2A> property to be just a function key, or just a modifier key combination. However, it is more common to set the <xref:System.Windows.Input.KeyBinding.Key%2A> property if the intended command binding is a function key with no modifiers, or <xref:System.Windows.Input.KeyBinding.Modifiers%2A> if the intended command binding is for modifier keys only.  
+ For <xref:System.Windows.Input.KeyGesture> XAML usages, the property that is generally set in XAML is <xref:System.Windows.Input.KeyBinding.Gesture%2A>, in cases where the gesture represents both a standard key and a modifier key. You can also set the <xref:System.Windows.Input.KeyBinding.Gesture%2A> property to be just a function key, or just a modifier key combination. However, it is more common to set the <xref:System.Windows.Input.KeyBinding.Key%2A> property if the intended command binding is a function key with no modifiers, or <xref:System.Windows.Input.KeyBinding.Modifiers%2A> if the intended command binding is for modifier keys only.  
   
 <a name="xamlAttributeUsage_KeyGesture"></a>   
 ## XAML Attribute Usage  
@@ -71,7 +71,7 @@
  [!code-csharp[commandlibrarysnippets#KeyBindingWithKeyAndModifiers](~/samples/snippets/csharp/VS_Snippets_Wpf/CommandLibrarySnippets/CSharp/Window1.xaml.cs#keybindingwithkeyandmodifiers)]
  [!code-vb[commandlibrarysnippets#KeyBindingWithKeyAndModifiers](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CommandLibrarySnippets/visualbasic/window1.xaml.vb#keybindingwithkeyandmodifiers)]  
   
- The following example shows how to use <xref:System.Windows.Input.KeyGesture> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Note that the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage does not directly declare a `<KeyGesture>` element. That object element usage is not possible because <xref:System.Windows.Input.KeyGesture> does not expose a public parameterless constructor. Instead, the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage uses the typeconverter behavior to declare an entire <xref:System.Windows.Input.KeyGesture> inline as the `Gesture` attribute value.  
+ The following example shows how to use <xref:System.Windows.Input.KeyGesture> in XAML. Note that the XAML usage does not directly declare a `<KeyGesture>` element. That object element usage is not possible because <xref:System.Windows.Input.KeyGesture> does not expose a public parameterless constructor. Instead, the XAML usage uses the typeconverter behavior to declare an entire <xref:System.Windows.Input.KeyGesture> inline as the `Gesture` attribute value.  
   
  [!code-xaml[commandWithHandler#CommandHandlerKeyBinding](~/samples/snippets/csharp/VS_Snippets_Wpf/commandWithHandler/CSharp/Window1.xaml#commandhandlerkeybinding)]  
   
diff --git a/xml/System.Windows.Input/Keyboard.xml b/xml/System.Windows.Input/Keyboard.xml
index 0e483cd5770..071af963219 100644
--- a/xml/System.Windows.Input/Keyboard.xml
+++ b/xml/System.Windows.Input/Keyboard.xml
@@ -76,7 +76,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.GotKeyboardFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.GotKeyboardFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -110,7 +110,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.KeyboardInputProviderAcquireFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.KeyboardInputProviderAcquireFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -145,7 +145,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.KeyDown?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.KeyDown?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -180,7 +180,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.KeyUp?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.KeyUp?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -215,7 +215,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.LostKeyboardFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.LostKeyboardFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -250,7 +250,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -284,7 +284,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyboardInputProviderAcquireFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyboardInputProviderAcquireFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -319,7 +319,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyDown?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyDown?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -354,7 +354,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyUp?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewKeyUp?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -389,7 +389,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method provides attached property accessors for code access and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus?displayProperty=nameWithType> attached event.  
+ This method provides attached property accessors for code access and XAML attribute processing of the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus?displayProperty=nameWithType> attached event.  
   
  ]]></format>
         </remarks>
@@ -599,7 +599,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Keyboard focus refers to the object that is receiving keyboard input. The element with keyboard focus has <xref:System.Windows.IInputElement.IsKeyboardFocused%2A> set to `true`.  There can be only one element with keyboard focus on the entire desktop.  Logical focus refers to the object within a focus scope that has focus.  For more information on focus, keyboard focus, and logical focus, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview) and [Focus Overview](/dotnet/framework/wpf/advanced/focus-overview).  
   
@@ -815,7 +815,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyboardInputProviderAcquireFocus"></a>   
 ## Routed Event Information  
@@ -879,7 +879,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyDown"></a>   
 ## Routed Event Information  
@@ -955,7 +955,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_KeyUp"></a>   
 ## Routed Event Information  
@@ -1021,7 +1021,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Keyboard focus refers to the object that is receiving keyboard input. The element with keyboard focus has <xref:System.Windows.IInputElement.IsKeyboardFocused%2A> set to `true`.  There can be only one element with keyboard focus on the entire desktop.  Logical focus refers to the object within a focus scope that has focus.  For more information on focus, keyboard focus, and logical focus, see [Input Overview](/dotnet/framework/wpf/advanced/input-overview) and [Focus Overview](/dotnet/framework/wpf/advanced/focus-overview).  
   
@@ -1141,7 +1141,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  If the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus> event or the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus> event is handled, keyboard focus does not change.  
   
@@ -1209,7 +1209,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyboardInputProviderAcquireFocus"></a>   
 ## Routed Event Information  
@@ -1273,7 +1273,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyDown"></a>   
 ## Routed Event Information  
@@ -1338,7 +1338,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewKeyUp"></a>   
 ## Routed Event Information  
@@ -1403,7 +1403,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  If the <xref:System.Windows.Input.Keyboard.PreviewGotKeyboardFocus> event or the <xref:System.Windows.Input.Keyboard.PreviewLostKeyboardFocus> event is handled, keyboard focus does not change.  
   
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 253911b1519..1a422abea1a 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -751,7 +751,7 @@
 ## Remarks  
  When an element captures the mouse, it receives mouse input whether or not the cursor is within its borders.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Because of the bubbling routing, the actual element that has capture might be a child element, not necessarily the element where the event handler is actually attached. Check the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event arguments to determine the actual element that has mouse capture.  
   
@@ -854,7 +854,7 @@
 ## Remarks  
  When an element captures the mouse, it receives mouse input whether or not the cursor is within its borders. T  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  Because of the bubbling routing, the actual element that lost capture might be a child element, not necessarily the element where the event handler is actually attached. Check the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event arguments to determine the actual element that lost capture.  
   
@@ -957,7 +957,7 @@
 ## Remarks  
  To determine which mouse button was depressed, check the <xref:System.Windows.Input.MouseButtonEventArgs.ChangedButton%2A> property in the <xref:System.Windows.Input.MouseButtonEventArgs> passed to the handler.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
   
@@ -1035,7 +1035,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event uses the direct event handling routing strategy. Direct routed events are not raised along a route (they are only handled in the same element on which they are raised).  They do, however, enable other aspects of routed event behaviors, such as event triggers in styles.  
   
@@ -1102,7 +1102,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event uses the direct event handling routing strategy. Direct routed events do not follow a route (they are only handled in the same element on which they are raised).  They do, however, enable other aspects of routed event behaviors, such as event triggers in styles.  
   
@@ -1168,7 +1168,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 ## Routed Event Information  
   
@@ -1234,7 +1234,7 @@
 ## Remarks  
  Which mouse button was released is determined by checking the arguments of the event.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
   
@@ -1306,7 +1306,7 @@
 ## Remarks  
  Focus or mouse capture take precedence over where the mouse pointer is.  If you receive this event from a focused or captured element, the mouse pointer might in fact be over another element at the time.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_MouseWheel"></a>   
 ## Routed Event Information  
@@ -1446,7 +1446,7 @@
 ## Remarks  
  Which mouse button was depressed is determined by checking the arguments of the event. This is an attached event (using tunneling routing strategy) that is intended through attached event syntax to be referenced by existing [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements that take input.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
   
@@ -1515,7 +1515,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event is not resurfaced on base elements. It is mainly of concern to control authors that are attempting to reconcile mouse capture and mouse input within their control compositing.  
   
@@ -1582,7 +1582,7 @@
 ## Remarks  
  This event occurs both when the mouse pointer is newly moved in the element bounds, and also when the mouse pointer moves while still remaining in the element bounds.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewMouseMove"></a>   
 ## Routed Event Information  
@@ -1649,7 +1649,7 @@
 ## Remarks  
  Which mouse button was released is determined by checking the arguments of the event.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
   
@@ -1717,7 +1717,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
  This event is not resurfaced on base elements. It is mainly of concern to control authors that are attempting to reconcile mouse capture and mouse input within their control compositing.  
   
@@ -1786,7 +1786,7 @@
 ## Remarks  
  Focus or mouse capture take precedence over where the mouse pointer is; therefore, if you receive this event from a focused or captured element, the mouse pointer might in fact be over another element at the time.  
   
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewMouseWheel"></a>   
 ## Routed Event Information  
@@ -1888,7 +1888,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_Querycursor"></a>   
 ## Routed Event Information  
diff --git a/xml/System.Windows.Input/MouseBinding.xml b/xml/System.Windows.Input/MouseBinding.xml
index 33ebf1e348b..1732604f8a2 100644
--- a/xml/System.Windows.Input/MouseBinding.xml
+++ b/xml/System.Windows.Input/MouseBinding.xml
@@ -23,9 +23,9 @@
 ## Remarks  
  A <xref:System.Windows.Input.MouseBinding> associates a <xref:System.Windows.Input.MouseGesture> with an <xref:System.Windows.Input.ICommand> implementation. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the WPF commanding system. In general, when the <xref:System.Windows.Input.MouseGesture> is executed, the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
   
- When defining a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], there are two ways to specify the <xref:System.Windows.Input.MouseGesture>. The first way to establish a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is to define the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element, which enables a syntax to specify mouse actions and modifiers as a single string; for example, "CTRL+LeftClick". The second way is to define the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element. Both ways of setting the <xref:System.Windows.Input.MouseGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> and the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attributes are both set, the gesture is invalid. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], even if you do not specify modifiers; this avoids ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], there are two ways to specify the <xref:System.Windows.Input.MouseGesture>. The first way to establish a <xref:System.Windows.Input.MouseBinding> in XAML is to define the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element, which enables a syntax to specify mouse actions and modifiers as a single string; for example, "CTRL+LeftClick". The second way is to define the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element. Both ways of setting the <xref:System.Windows.Input.MouseGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> and the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attributes are both set, the gesture is invalid. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML, even if you do not specify modifiers; this avoids ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
- A <xref:System.Windows.Input.MouseBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.MouseBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
+ A <xref:System.Windows.Input.MouseBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.MouseBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in XAML by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
   
    
   
diff --git a/xml/System.Windows.Input/MouseGesture.xml b/xml/System.Windows.Input/MouseGesture.xml
index 8bb49f0f066..435a036823c 100644
--- a/xml/System.Windows.Input/MouseGesture.xml
+++ b/xml/System.Windows.Input/MouseGesture.xml
@@ -35,9 +35,9 @@
   
  A <xref:System.Windows.Input.MouseGesture> can be bound to a <xref:System.Windows.Input.RoutedCommand> (or other <xref:System.Windows.Input.ICommand> implementations) through a <xref:System.Windows.Input.MouseBinding> so that the command is invoked when the <xref:System.Windows.Input.MouseGesture> occurs.  
   
- For <xref:System.Windows.Input.MouseGesture> [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute usages, the property that is generally set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is <xref:System.Windows.Input.MouseBinding.Gesture%2A>, in cases where the gesture can represent both a mouse action and one or more modifier key. You can also set the <xref:System.Windows.Input.MouseBinding.Gesture%2A> property to be just a mouse action. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], rather than setting <xref:System.Windows.Input.MouseBinding.MouseAction%2A>, even if you do not specify modifiers. This will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ For <xref:System.Windows.Input.MouseGesture> XAML attribute usages, the property that is generally set in XAML is <xref:System.Windows.Input.MouseBinding.Gesture%2A>, in cases where the gesture can represent both a mouse action and one or more modifier key. You can also set the <xref:System.Windows.Input.MouseBinding.Gesture%2A> property to be just a mouse action. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML, rather than setting <xref:System.Windows.Input.MouseBinding.MouseAction%2A>, even if you do not specify modifiers. This will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
- <xref:System.Windows.Input.MouseGesture> [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] object element usages are possible but uncommon, because you can ordinarily set the <xref:System.Windows.Input.MouseBinding.Gesture%2A> property of <xref:System.Windows.Input.MouseBinding> inline without the use of property element syntax.  
+ <xref:System.Windows.Input.MouseGesture> XAML object element usages are possible but uncommon, because you can ordinarily set the <xref:System.Windows.Input.MouseBinding.Gesture%2A> property of <xref:System.Windows.Input.MouseBinding> inline without the use of property element syntax.  
   
 <a name="xamlAttributeUsage_MouseGesture"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Input/Stylus.xml b/xml/System.Windows.Input/Stylus.xml
index 26e278eb4dc..661116c1ed3 100644
--- a/xml/System.Windows.Input/Stylus.xml
+++ b/xml/System.Windows.Input/Stylus.xml
@@ -1057,7 +1057,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. Attached events are, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. The WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. Attached events are, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. The WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_GotStylusCapture"></a>   
 ## Routed Event Information  
@@ -1376,7 +1376,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_LostStylusCapture"></a>   
 ## Routed Event Information  
@@ -1441,7 +1441,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusButtonDown"></a>   
 ## Routed Event Information  
@@ -1506,7 +1506,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusButtonUp"></a>   
 ## Routed Event Information  
@@ -1571,7 +1571,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusDown"></a>   
 ## Routed Event Information  
@@ -1636,7 +1636,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusInAirMove"></a>   
 ## Routed Event Information  
@@ -1701,7 +1701,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusInRange"></a>   
 ## Routed Event Information  
@@ -1766,7 +1766,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusMove"></a>   
 ## Routed Event Information  
@@ -1831,7 +1831,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusOutOfRange"></a>   
 ## Routed Event Information  
@@ -1896,7 +1896,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusSystemGesture"></a>   
 ## Routed Event Information  
@@ -1961,7 +1961,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_PreviewStylusUp"></a>   
 ## Routed Event Information  
@@ -2813,7 +2813,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusButtonDown"></a>   
 ## Routed Event Information  
@@ -2878,7 +2878,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusButtonUp"></a>   
 ## Routed Event Information  
@@ -2943,7 +2943,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusDown"></a>   
 ## Routed Event Information  
@@ -3008,7 +3008,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusEnter"></a>   
 ## Routed Event Information  
@@ -3073,7 +3073,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusInAirMove"></a>   
 ## Routed Event Information  
@@ -3138,7 +3138,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusInRange"></a>   
 ## Routed Event Information  
@@ -3203,7 +3203,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusLeave"></a>   
 ## Routed Event Information  
@@ -3268,7 +3268,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusMove"></a>   
 ## Routed Event Information  
@@ -3333,7 +3333,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route.  Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route.  Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusOutOfRange"></a>   
 ## Routed Event Information  
@@ -3398,7 +3398,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusSystemGesture"></a>   
 ## Routed Event Information  
@@ -3463,7 +3463,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
+ This is an attached event. WPF implements attached events as routed events. An attached event is, fundamentally, a XAML language concept used to reference events that are handled on objects that do not, themselves, define events. WPF further expands an attached event's capabilities, allowing it to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
 <a name="routedEventInfo_StylusUp"></a>   
 ## Routed Event Information  
diff --git a/xml/System.Windows.Interop/DocObjHost.xml b/xml/System.Windows.Interop/DocObjHost.xml
index e145780c678..23636094d23 100644
--- a/xml/System.Windows.Interop/DocObjHost.xml
+++ b/xml/System.Windows.Interop/DocObjHost.xml
@@ -27,7 +27,7 @@
   
 <a name="xamlTextUsage_DocObjHost"></a>   
 ## XAML Text Usage  
- This managed class is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This managed class is not typically used in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
index 637bfbe83ae..a27557694e3 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizabilityResolver.xml
@@ -177,7 +177,7 @@
       </Parameters>
       <Docs>
         <param name="formattingTag">The name of the tag.</param>
-        <summary>Returns the full class name of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] tag that has not been encountered in BAML.</summary>
+        <summary>Returns the full class name of a XAML tag that has not been encountered in BAML.</summary>
         <returns>The full class name associated with the tag.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Markup.Primitives/MarkupObject.xml b/xml/System.Windows.Markup.Primitives/MarkupObject.xml
index 2571ff75a1b..a0f282da759 100644
--- a/xml/System.Windows.Markup.Primitives/MarkupObject.xml
+++ b/xml/System.Windows.Markup.Primitives/MarkupObject.xml
@@ -162,7 +162,7 @@
         <ReturnType>System.Collections.Generic.IEnumerable&lt;System.Windows.Markup.Primitives.MarkupProperty&gt;</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>When overridden in a derived class, gets the properties of this <see cref="T:System.Windows.Markup.Primitives.MarkupObject" /> instance that should be written to [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].</summary>
+        <summary>When overridden in a derived class, gets the properties of this <see cref="T:System.Windows.Markup.Primitives.MarkupObject" /> instance that should be written to XAML.</summary>
         <value>The properties.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Markup/TypeExtension.xml b/xml/System.Windows.Markup/TypeExtension.xml
index c38e8f70012..63dc3fd5c62 100644
--- a/xml/System.Windows.Markup/TypeExtension.xml
+++ b/xml/System.Windows.Markup/TypeExtension.xml
@@ -47,7 +47,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage information, see [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension).  
+ For XAML usage information, see [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension).  
   
 > [!NOTE]
 >  The `{x:Type}` functionality is generally for user code invocation from markup. For code that is implementing XAML support, type resolution services come from <xref:System.Windows.Markup.IXamlTypeResolver> and are related to the implementation of the acting XAML schema context. Do not attempt to reference <xref:System.Windows.Markup.TypeExtension.ProvideValue%2A> as a substitute for a <xref:System.Windows.Markup.IXamlTypeResolver> service provider; the context you pass in might not be valid for a type resolution, and attempts to call without valid services will fail.  
diff --git a/xml/System.Windows.Media.Animation/Storyboard.xml b/xml/System.Windows.Media.Animation/Storyboard.xml
index a605798f9f2..caaa0a025c0 100644
--- a/xml/System.Windows.Media.Animation/Storyboard.xml
+++ b/xml/System.Windows.Media.Animation/Storyboard.xml
@@ -3187,7 +3187,7 @@
  When this property is set on a timeline with children, those child timelines "inherit" the parent's <xref:System.Windows.Media.Animation.Storyboard.TargetName%2A> unless they specify their own.  
   
 ## Making an Object Targetable  
- When using [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you perform one of the following two actions to make an object targetable by a storyboard:  
+ When using XAML, you perform one of the following two actions to make an object targetable by a storyboard:  
   
 -   If the object is a <xref:System.Windows.FrameworkElement> or a <xref:System.Windows.FrameworkContentElement>, set its <xref:System.Windows.FrameworkElement.Name%2A> property.  
   
diff --git a/xml/System.Windows.Media.Converters/MatrixValueSerializer.xml b/xml/System.Windows.Media.Converters/MatrixValueSerializer.xml
index 33ede7d1e1f..cfa73627082 100644
--- a/xml/System.Windows.Media.Converters/MatrixValueSerializer.xml
+++ b/xml/System.Windows.Media.Converters/MatrixValueSerializer.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class is typically only utilized by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization purposes.  
   
- Use a <xref:System.Windows.Media.Converters.MatrixValueSerializer> to create a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representation of a <xref:System.Windows.Media.Matrix> structure. Use a <xref:System.Windows.Media.MatrixConverter> to create a <xref:System.Windows.Media.Matrix> from an attribute string.  
+ Use a <xref:System.Windows.Media.Converters.MatrixValueSerializer> to create a XAML representation of a <xref:System.Windows.Media.Matrix> structure. Use a <xref:System.Windows.Media.MatrixConverter> to create a <xref:System.Windows.Media.Matrix> from an attribute string.  
   
    
   
diff --git a/xml/System.Windows.Media/Brush.xml b/xml/System.Windows.Media/Brush.xml
index d8d0d291ae0..dcee8008951 100644
--- a/xml/System.Windows.Media/Brush.xml
+++ b/xml/System.Windows.Media/Brush.xml
@@ -59,7 +59,7 @@
  Use the <xref:System.Windows.Media.Brushes> class to paint an object using a predefined solid color, such as <xref:System.Windows.Media.Brushes.AliceBlue%2A> or <xref:System.Windows.Media.Brushes.Red%2A>.  
   
 ## Brushes in XAML  
- The following table lists the different <xref:System.Windows.Media.Brush> types that can be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] and the syntax they support. For detailed syntax information for a specific brush, see that brush's type page.  
+ The following table lists the different <xref:System.Windows.Media.Brush> types that can be used in XAML and the syntax they support. For detailed syntax information for a specific brush, see that brush's type page.  
   
 |Class|Attribute Syntax|Object Element Syntax|  
 |-----------|----------------------|---------------------------|  
@@ -77,7 +77,7 @@
   
 <a name="xamlTextUsage_Brush"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see the **Remarks** section.  
+ For XAML information, see the **Remarks** section.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/Brushes.xml b/xml/System.Windows.Media/Brushes.xml
index db11ef8bc6e..dace619fac8 100644
--- a/xml/System.Windows.Media/Brushes.xml
+++ b/xml/System.Windows.Media/Brushes.xml
@@ -32,7 +32,7 @@ Color table including a color swatch, the color name, and the hexadecimal value
   
 <a name="xamlTextUsage_Brushes"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but you can use its static properties to assign values in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML, but you can use its static properties to assign values in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/Colors.xml b/xml/System.Windows.Media/Colors.xml
index b176be0a45a..184e0b7776e 100644
--- a/xml/System.Windows.Media/Colors.xml
+++ b/xml/System.Windows.Media/Colors.xml
@@ -32,7 +32,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
   
 <a name="xamlTextUsage_Colors"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but you can use its static properties to assign values in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML, but you can use its static properties to assign values in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/DashStyles.xml b/xml/System.Windows.Media/DashStyles.xml
index 8c5320f1fc1..8df7fd28be1 100644
--- a/xml/System.Windows.Media/DashStyles.xml
+++ b/xml/System.Windows.Media/DashStyles.xml
@@ -27,7 +27,7 @@
   
 <a name="xamlTextUsage_DashStyles"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but you can use its static properties to assign values in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML, but you can use its static properties to assign values in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/ImageBrush.xml b/xml/System.Windows.Media/ImageBrush.xml
index b4401338cf2..9e102d7a3e8 100644
--- a/xml/System.Windows.Media/ImageBrush.xml
+++ b/xml/System.Windows.Media/ImageBrush.xml
@@ -247,7 +247,7 @@ An ImageBrush can paint shapes, controls, text, and more
   
 <a name="xamlTextUsage_ImageSource"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see <xref:System.Windows.Media.ImageSource>.  
+ For XAML information, see <xref:System.Windows.Media.ImageSource>.  
   
 <a name="xamlValues_ImageSource"></a>   
 ## XAML Values  
diff --git a/xml/System.Windows.Media/ImageDrawing.xml b/xml/System.Windows.Media/ImageDrawing.xml
index 8dda2212f04..f38c19e3a16 100644
--- a/xml/System.Windows.Media/ImageDrawing.xml
+++ b/xml/System.Windows.Media/ImageDrawing.xml
@@ -207,7 +207,7 @@
   
 <a name="xamlTextUsage_ImageSource"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see the <xref:System.Windows.Media.ImageSource> type.  
+ For XAML information, see the <xref:System.Windows.Media.ImageSource> type.  
   
 <a name="xamlValues_ImageSource"></a>   
 ## XAML Values  
diff --git a/xml/System.Windows.Media/MatrixConverter.xml b/xml/System.Windows.Media/MatrixConverter.xml
index 500ab87541f..d8ae5bb3a26 100644
--- a/xml/System.Windows.Media/MatrixConverter.xml
+++ b/xml/System.Windows.Media/MatrixConverter.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use a <xref:System.Windows.Media.MatrixConverter> to create a <xref:System.Windows.Media.Matrix> from an attribute string; use a <xref:System.Windows.Media.Converters.MatrixValueSerializer> to create a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representation of a <xref:System.Windows.Media.Matrix> structure.  
+ Use a <xref:System.Windows.Media.MatrixConverter> to create a <xref:System.Windows.Media.Matrix> from an attribute string; use a <xref:System.Windows.Media.Converters.MatrixValueSerializer> to create a XAML representation of a <xref:System.Windows.Media.Matrix> structure.  
   
    
   
diff --git a/xml/System.Windows.Media/MediaPlayer.xml b/xml/System.Windows.Media/MediaPlayer.xml
index 102859abf66..a95f8b5a792 100644
--- a/xml/System.Windows.Media/MediaPlayer.xml
+++ b/xml/System.Windows.Media/MediaPlayer.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Although you can declare an instance of this class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], you cannot load and play its media without using code. To play media in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] only, use a <xref:System.Windows.Controls.MediaElement>. Also, if you declare an instance in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the only practical use is to fill property element syntax for the <xref:System.Windows.Media.VideoDrawing.Player%2A> property.  
+ Although you can declare an instance of this class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], you cannot load and play its media without using code. To play media in XAML only, use a <xref:System.Windows.Controls.MediaElement>. Also, if you declare an instance in XAML, the only practical use is to fill property element syntax for the <xref:System.Windows.Media.VideoDrawing.Player%2A> property.  
   
  When distributing media with your application, you cannot use a media file as a project resource. In your project file, you must instead set the media type to `Content` and set `CopyToOutputDirectory` to `PreserveNewest` or `Always`.  
   
@@ -773,7 +773,7 @@
   
 <a name="xamlTextUsage_Position"></a>   
 ## XAML Text Usage  
- Not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -924,7 +924,7 @@
   
 <a name="xamlTextUsage_SpeedRatio"></a>   
 ## XAML Text Usage  
- Not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -987,7 +987,7 @@
   
 <a name="xamlTextUsage_Volume"></a>   
 ## XAML Text Usage  
- Not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Not typically used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/NumberSubstitution.xml b/xml/System.Windows.Media/NumberSubstitution.xml
index bb58873ca96..6bbddd99c0a 100644
--- a/xml/System.Windows.Media/NumberSubstitution.xml
+++ b/xml/System.Windows.Media/NumberSubstitution.xml
@@ -35,7 +35,7 @@ Example of the appearance of digits in different cultures
   
 <a name="xamlTextUsage_NumberSubstitution"></a>   
 ## XAML Text Usage  
- This type is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] as an object element. However, the type exposes several attached properties that can be set on other object elements that have text content.  
+ This type is not typically used in XAML as an object element. However, the type exposes several attached properties that can be set on other object elements that have text content.  
   
  ]]></format>
     </remarks>
@@ -138,7 +138,7 @@ Example of the appearance of digits in different cultures
   
 -   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
--   You can set this property as an attached property usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<`*object* **NumberSubstitution.CultureOverride**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureOverride%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureOverride%2A>.  
+-   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.CultureOverride**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureOverride%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureOverride%2A>.  
   
 <a name="xamlAttributeUsage_CultureOverride"></a>   
 ## XAML Attribute Usage  
@@ -222,7 +222,7 @@ Example of the appearance of digits in different cultures
   
 -   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
--   You can set this property as an attached property usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<`*object* **NumberSubstitution.CultureSource**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberCultureSource> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureSource%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureSource%2A>.  
+-   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.CultureSource**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberCultureSource> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureSource%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureSource%2A>.  
   
 <a name="xamlAttributeUsage_CultureSource"></a>   
 ## XAML Attribute Usage  
@@ -550,7 +550,7 @@ Example of the appearance of digits in different cultures
   
 -   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
--   You can set this property as an attached property usage in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the usage is `<`*object* **NumberSubstitution.Substitution**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberSubstitutionMethod> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetSubstitution%2A> and <xref:System.Windows.Media.NumberSubstitution.SetSubstitution%2A>.  
+-   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.Substitution**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberSubstitutionMethod> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetSubstitution%2A> and <xref:System.Windows.Media.NumberSubstitution.SetSubstitution%2A>.  
   
 <a name="xamlAttributeUsage_Substitution"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Media/VideoDrawing.xml b/xml/System.Windows.Media/VideoDrawing.xml
index bb75cf662d3..25d5c7132c1 100644
--- a/xml/System.Windows.Media/VideoDrawing.xml
+++ b/xml/System.Windows.Media/VideoDrawing.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Although you can declare an instance of this class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you cannot load and play its media without using code, because of the dependency on the <xref:System.Windows.Media.MediaPlayer> class and in particular the <xref:System.Windows.Media.MediaPlayer.Open%2A> and <xref:System.Windows.Media.MediaPlayer.Play%2A> methods. To play media in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] only, use a <xref:System.Windows.Controls.MediaElement>.  
+ Although you can declare an instance of this class in XAML, you cannot load and play its media without using code, because of the dependency on the <xref:System.Windows.Media.MediaPlayer> class and in particular the <xref:System.Windows.Media.MediaPlayer.Open%2A> and <xref:System.Windows.Media.MediaPlayer.Play%2A> methods. To play media in XAML only, use a <xref:System.Windows.Controls.MediaElement>.  
   
  Despite its name, a <xref:System.Windows.Media.VideoDrawing> can be used to play audio.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntry.xml b/xml/System.Windows.Navigation/JournalEntry.xml
index 762b1f1ec79..47bc66acbb4 100644
--- a/xml/System.Windows.Navigation/JournalEntry.xml
+++ b/xml/System.Windows.Navigation/JournalEntry.xml
@@ -333,7 +333,7 @@
    
   
 ## Examples  
- The following example shows how to set the <xref:System.Windows.Navigation.JournalEntry.Name%2A> property for a <xref:System.Windows.Controls.Page> from markup, with a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attached property usage.  
+ The following example shows how to set the <xref:System.Windows.Navigation.JournalEntry.Name%2A> property for a <xref:System.Windows.Controls.Page> from markup, with a XAML attached property usage.  
   
  [!code-xaml[JournalEntrySnippets#JENameMARKUP](~/samples/snippets/csharp/VS_Snippets_Wpf/JournalEntrySnippets/CSharp/JENamePage.xaml#jenamemarkup)]  
   
diff --git a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
index 7613aa60e5d..354b017ea78 100644
--- a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
+++ b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
@@ -49,7 +49,7 @@
  If you create custom navigation UI, and need to provide an [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, you can use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to similar effect.  
   
 ## XAML Attribute Usage  
- This class is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is not typically used in XAML.  
   
    
   
@@ -140,7 +140,7 @@
  The two passed navigation stacks are combined into a single navigation stack that contains up to nine items from each navigation stack plus the current item.  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
  ]]></format>
         </remarks>
@@ -185,7 +185,7 @@
 ## Remarks  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
  ]]></format>
         </remarks>
@@ -244,7 +244,7 @@
  To get all <xref:System.Windows.Navigation.JournalEntry> objects from a <xref:System.Windows.Controls.Frame>, enumerate the entries that are returned by <xref:System.Windows.Controls.Frame.BackStack%2A?displayProperty=nameWithType> and <xref:System.Windows.Controls.Frame.ForwardStack%2A?displayProperty=nameWithType>.  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
  ]]></format>
         </remarks>
@@ -303,7 +303,7 @@
 ## Remarks  
   
 ## XAML Attribute Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 35c97d03093..56c8f299eeb 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -289,7 +289,7 @@
 <TextBlock Name="FragmentName">...</TextBlock>  
 ```  
   
- You navigate to a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] fragment by providing a URI with a suffix in the following format:  
+ You navigate to a XAML fragment by providing a URI with a suffix in the following format:  
   
  \#*FragmentName*  
   
@@ -311,13 +311,13 @@
 >  When <xref:System.Windows.Navigation.NavigationService> raises <xref:System.Windows.Navigation.NavigationService.FragmentNavigation>, it also raises <xref:System.Windows.Application.FragmentNavigation?displayProperty=nameWithType> event on the <xref:System.Windows.Application> object.  
   
 > [!IMPORTANT]
->  Fragment navigation is not supported for loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] pages (markup-only [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files with `Page` as the root element) in the following cases:  
+>  Fragment navigation is not supported for loose XAML pages (markup-only XAML files with `Page` as the root element) in the following cases:  
 >   
->  • When navigating to a fragment in a loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page.  
+>  • When navigating to a fragment in a loose XAML page.  
 >   
->  • When navigating from a loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page to a fragment in another loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page.  
+>  • When navigating from a loose XAML page to a fragment in another loose XAML page.  
 >   
->  However, a loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page can navigate to its own fragments.  
+>  However, a loose XAML page can navigate to its own fragments.  
   
    
   
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index e82d588e084..997f16fbad3 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -197,7 +197,7 @@
         <param name="value">The child object to add.</param>
         <summary>Adds a child object.</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.InvalidOperationException">when this method is called. This prevents content from being added to <see cref="T:System.Windows.Navigation.NavigationWindow" /> using [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].</exception>
+        <exception cref="T:System.InvalidOperationException">when this method is called. This prevents content from being added to <see cref="T:System.Windows.Navigation.NavigationWindow" /> using XAML.</exception>
         <altmember cref="M:System.Windows.Markup.IAddChild.AddChild(System.Object)" />
       </Docs>
     </Member>
@@ -1248,12 +1248,12 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- External content is [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] content that is not included with an application as either a resource file or a content file (for more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ External content is XAML content that is not included with an application as either a resource file or a content file (for more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
- When <xref:System.Windows.Navigation.NavigationWindow.SandboxExternalContent%2A> is true, and the content of the <xref:System.Windows.Navigation.NavigationWindow> is an external [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, the content is loaded into a partial trust security sandbox that is limited to the default Internet zone permission set. Additionally, the external content is loaded into a separate process. Consequently, the external content becomes isolated and does not have access to application-scope resources, such as resource dictionaries (for more information, see <xref:System.Windows.ResourceDictionary>).  
+ When <xref:System.Windows.Navigation.NavigationWindow.SandboxExternalContent%2A> is true, and the content of the <xref:System.Windows.Navigation.NavigationWindow> is an external XAML file, the content is loaded into a partial trust security sandbox that is limited to the default Internet zone permission set. Additionally, the external content is loaded into a separate process. Consequently, the external content becomes isolated and does not have access to application-scope resources, such as resource dictionaries (for more information, see <xref:System.Windows.ResourceDictionary>).  
   
 > [!NOTE]
->  <xref:System.Windows.Navigation.NavigationWindow> contains external content only when the <xref:System.Windows.Navigation.NavigationWindow.Source%2A> property is set to the uniform resource identifier (URI) for an external [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file. <xref:System.Windows.Navigation.NavigationWindow> content that is provided using the <xref:System.Windows.Controls.ContentControl.Content%2A> property is considered internal content and, subsequently, is not isolated.  
+>  <xref:System.Windows.Navigation.NavigationWindow> contains external content only when the <xref:System.Windows.Navigation.NavigationWindow.Source%2A> property is set to the uniform resource identifier (URI) for an external XAML file. <xref:System.Windows.Navigation.NavigationWindow> content that is provided using the <xref:System.Windows.Controls.ContentControl.Content%2A> property is considered internal content and, subsequently, is not isolated.  
   
 <a name="dependencyPropertyInfo_NavigationWindowSandboxExternalContent"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Threading/DispatcherFrame.xml b/xml/System.Windows.Threading/DispatcherFrame.xml
index 2019419e103..8a091b2d078 100644
--- a/xml/System.Windows.Threading/DispatcherFrame.xml
+++ b/xml/System.Windows.Threading/DispatcherFrame.xml
@@ -30,7 +30,7 @@
   
 <a name="xamlTextUsage_DispatcherFrame"></a>   
 ## XAML Text Usage  
- You cannot use this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this managed class in XAML.  
   
    
   
@@ -155,7 +155,7 @@ At application shutdown, all frames are requested to exit.
   
 <a name="xamlTextUsage_Continue"></a>   
 ## XAML Text Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or cannot be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML, or cannot be used in XAML.  
   
    
   
diff --git a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
index 320fbe13a2e..e227722a27f 100644
--- a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
@@ -138,8 +138,8 @@
         <Parameter Name="serializedObject" Type="System.Object" />
       </Parameters>
       <Docs>
-        <param name="serializedObject">The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] serialized object to save.</param>
-        <summary>Saves a specified [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] serialized object to the document package.</summary>
+        <param name="serializedObject">The XAML serialized object to save.</param>
+        <summary>Saves a specified XAML serialized object to the document package.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 92068d17303..89bf76198c7 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -737,7 +737,7 @@
         <Parameter Name="resourceLocator" Type="System.Uri" />
       </Parameters>
       <Docs>
-        <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</param>
+        <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative XAML file.</param>
         <summary>Loads a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file that is located at the specified uniform resource identifier (URI), and converts it to an instance of the object that is specified by the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.</summary>
         <returns>An instance of the root element specified by the XAML file loaded.</returns>
         <remarks>
@@ -790,8 +790,8 @@
         <Parameter Name="resourceLocator" Type="System.Uri" />
       </Parameters>
       <Docs>
-        <param name="component">An object of the same type as the root element of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</param>
-        <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</param>
+        <param name="component">An object of the same type as the root element of the XAML file.</param>
+        <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative XAML file.</param>
         <summary>Loads a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file that is located at the specified uniform resource identifier (URI) and converts it to an instance of the object that is specified by the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -808,7 +808,7 @@
           <paramref name="resourceLocator" /> is null.</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="resourceLocator" /> is an absolute URI.</exception>
         <exception cref="T:System.Exception">
-          <paramref name="component" /> is of a type that does not match the root element of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file.</exception>
+          <paramref name="component" /> is of a type that does not match the root element of the XAML file.</exception>
         <altmember cref="M:System.Windows.Application.GetResourceStream(System.Uri)" />
         <altmember cref="M:System.Windows.Application.GetContentStream(System.Uri)" />
         <altmember cref="M:System.Windows.Application.GetRemoteStream(System.Uri)" />
diff --git a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
index e3649a8fa04..9307be00bee 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] concept.  
+ The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
index eba96de481f..49f308f708d 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] concept.  
+ The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
  When this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is applied to the get accessor for an attached property, this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] specifies that an attached property is browsable when the attached property owner is a parent element of other elements.  
   
@@ -37,7 +37,7 @@
   
  This  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] supports two types of tree detection modes for parent element positions:  a shallow mode, and a deep mode. The shallow mode, which is the default mode for an applied <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], requires that the immediate parent element be the owner type of the property in order for the attached property to be browsable. The deep mode is declared by applying the attribute with <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> as `true`. The deep mode is less restrictive because it only requires that the owner type be somewhere in the ancestor direction of the logical tree, and therefore the attached property is browsable on all child elements, not just immediate child elements. The deep mode is applied for attached property usages where intervening elements in the logical tree should not be reported as the true parent element. Implicit collections (for example, the <xref:System.Windows.Controls.UIElementCollection> that is implicit in the <xref:System.Windows.Controls.Panel.Children%2A> of a <xref:System.Windows.Controls.Panel>) are not considered to be parent elements for purposes of how this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] declares the tree detection mode.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] on child elements, it is the presence and characteristics of the get accessor on the parent element that controls the true behavior.  
+ This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on child elements, it is the presence and characteristics of the get accessor on the parent element that controls the true behavior.  
   
  Whether an attached property is browsable on a child element is not an absolute guarantee that the attached property value is really processed by the parent element in some manner. Also, the <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> value is not an absolute guarantee that the processing scope does or does not extend beyond the immediate parent element. All this is implementation specific. However, this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] for reporting the browsable state is the best available mechanism for reporting the usage information and functional information for an attached property. Therefore, you can generally assume that the browsable state of an attached property is analogous to the behavior of how an attached property value on a child element is processed or interpreted by the relevant parent element in your application code.  
   
@@ -45,7 +45,7 @@
   
 <a name="xamlTextUsage_AttachedPropertyBrowsableForChildrenAttribute"></a>   
 ## XAML Text Usage  
- Members of this type are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this type are not typically used in XAML.  
   
  ]]></format>
     </remarks>
@@ -189,7 +189,7 @@
   
 <a name="xamlTextUsage_IncludeDescendants"></a>   
 ## XAML Text Usage  
- Members of this type are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this type are not typically used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
index 2cd4c0e21eb..f13968b650e 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
@@ -27,13 +27,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] concept.  
+ The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
  If more than one type is specified for a <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], the property is browsable if any specified type matches (logical or).  The type can also be an interface.  
   
  This  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] specifies <xref:System.AttributeUsageAttribute.AllowMultiple%2A> `true`.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
+ This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
   
  For general information on declaring attached properties, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
diff --git a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
index 605084ea728..6135188eb29 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
@@ -27,9 +27,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] concept.  
+ The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
+ This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
   
  For general information on declaring attached properties, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
diff --git a/xml/System.Windows/ColorConvertedBitmapExtension.xml b/xml/System.Windows/ColorConvertedBitmapExtension.xml
index 721b3670334..9193bdbb123 100644
--- a/xml/System.Windows/ColorConvertedBitmapExtension.xml
+++ b/xml/System.Windows/ColorConvertedBitmapExtension.xml
@@ -27,11 +27,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF XAML processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension) usage from XAML.  
   
 <a name="xamlTextUsage_ColorConvertedBitmapExtension"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension).  
+ For XAML information, see [ColorConvertedBitmap Markup Extension](/dotnet/framework/wpf/advanced/colorconvertedbitmap-markup-extension).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/ComponentResourceKey.xml b/xml/System.Windows/ComponentResourceKey.xml
index 3e1aa064fe2..adc4dbf6c8b 100644
--- a/xml/System.Windows/ComponentResourceKey.xml
+++ b/xml/System.Windows/ComponentResourceKey.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
+ For XAML information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
   
  This class implements an object type that is useful for creating keys that are based on types in assemblies plus an identifier. Because you define or reference the type, you do not need to request a specific <xref:System.Windows.ResourceDictionary>, and more than one set of resources can exist in the assembly, each differentiated by the type of their <xref:System.Windows.ComponentResourceKey>.  
   
@@ -35,7 +35,7 @@
   
  If you want an easily accessible key, you can define a static property on your control class code that returns a <xref:System.Windows.ComponentResourceKey>, constructed with a <xref:System.Windows.ComponentResourceKey.TypeInTargetAssembly%2A> that exists in the external resource assembly, and a <xref:System.Windows.ComponentResourceKey.ResourceId%2A>. The key can be used for defining alternate default styles for controls in an assembly, by swapping the original external resource assembly for a custom one. You can also define a named resource part within a larger control style or template to expose a customization entry point. This is particularly useful if you are defining a theme resource dictionary for your control.  
   
- You can also use the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension) in verbose syntax directly to create a loose instance of the key. This is useful if you want to declare private resources from other assemblies that are less discoverable to customize.  
+ You can also use the XAML [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension) in verbose syntax directly to create a loose instance of the key. This is useful if you want to declare private resources from other assemblies that are less discoverable to customize.  
   
  ]]></format>
     </remarks>
@@ -238,7 +238,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
+ For XAML information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
   
  Typically, the string used for a <xref:System.Windows.ComponentResourceKey.ResourceId%2A> value conforms to the [XamlName Grammar](/dotnet/framework/xaml-services/xamlname-grammar).  
   
@@ -305,7 +305,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
+ For XAML information, see [ComponentResourceKey Markup Extension](/dotnet/framework/wpf/advanced/componentresourcekey-markup-extension).  
   
  The <xref:System.Windows.ComponentResourceKey> element is used by custom components to define keys for resources that are accessed from external assemblies, based on targeting an assembly that contains the type. Custom components often define new types which must be in the assembly where the resource is located. Generally these types have no other implementation, the types only exist in order to satisfy the lookup requirements of a <xref:System.Windows.ComponentResourceKey>.  
   
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index db309b3e6f9..995b4e19a5b 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -262,7 +262,7 @@
    
   
 ## Examples  
- The following example sets <xref:System.Windows.ContentElement.AllowDrop%2A> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ The following example sets <xref:System.Windows.ContentElement.AllowDrop%2A> in XAML.  
   
  [!code-xaml[ContentElementsSmorgasbord#AllowDrop](~/samples/snippets/csharp/VS_Snippets_Wpf/ContentElementsSmorgasbord/CSharp/page1.xaml#allowdrop)]  
   
diff --git a/xml/System.Windows/CornerRadius.xml b/xml/System.Windows/CornerRadius.xml
index 8f7221f301b..564527bbe0f 100644
--- a/xml/System.Windows/CornerRadius.xml
+++ b/xml/System.Windows/CornerRadius.xml
@@ -66,7 +66,7 @@
  If only a single <xref:System.Double> value is specified, that measure is applied to ALL of the *TopLeft*, *TopRight*, *BottomRight*, and *BottomLeft* corners of the <xref:System.Windows.CornerRadius>.  
   
 > [!NOTE]
->  Values need not include the decimal point explicitly when specified as a string. The string "1" provided in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] evaluates to a value of 1.0 when referenced in code.  
+>  Values need not include the decimal point explicitly when specified as a string. The string "1" provided in XAML evaluates to a value of 1.0 when referenced in code.  
   
    
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 8328251fa3a..23c513715f8 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -867,7 +867,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] programming language. In [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is typically used to describe user interfaces (UI), documents, and media experiences.  
+ XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] programming language. In [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], XAML is typically used to describe user interfaces (UI), documents, and media experiences.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index 1380b9ec996..63152d776e6 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -55,7 +55,7 @@
   
  To learn more about dependency properties, see [Dependency Properties Overview](/dotnet/framework/wpf/advanced/dependency-properties-overview). If you want properties on your custom types to support the capabilities in the preceding list, you should create a dependency property.  To learn how to create custom dependency properties, see [Custom Dependency Properties](/dotnet/framework/wpf/advanced/custom-dependency-properties).  
   
- An attached property is a property that enables any object to report information to the type that defines the attached property. In WPF, any type that inherits from <xref:System.Windows.DependencyObject> can use an attached property regardless of whether the type inherits from the type that defines the property. An attached property is a feature of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] language.  To set an attached property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], use the *ownerType*.*propertyName* syntax. An example of an attached property is the <xref:System.Windows.Controls.DockPanel.Dock%2A?displayProperty=nameWithType> property. If you want to create a property that can be used on all <xref:System.Windows.DependencyObject> types, then you should create an attached property. To learn more about attached properties, including how to create them, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property that enables any object to report information to the type that defines the attached property. In WPF, any type that inherits from <xref:System.Windows.DependencyObject> can use an attached property regardless of whether the type inherits from the type that defines the property. An attached property is a feature of the XAML language.  To set an attached property in XAML, use the *ownerType*.*propertyName* syntax. An example of an attached property is the <xref:System.Windows.Controls.DockPanel.Dock%2A?displayProperty=nameWithType> property. If you want to create a property that can be used on all <xref:System.Windows.DependencyObject> types, then you should create an attached property. To learn more about attached properties, including how to create them, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
 <a name="xamlAttributeUsage_DependencyProperty"></a>   
 ## XAML Attribute Usage  
@@ -186,7 +186,7 @@
   
  The <xref:System.Windows.DependencyProperty.AddOwner%2A> methodology recommended above is used when creating APIs declared within WPF. For instance, both <xref:System.Windows.Controls.Border> and <xref:System.Windows.Controls.Control> define a `BorderBrush` dependency property, which have similar functionality. <xref:System.Windows.Controls.Control> defines its `BorderBrush` property to the property system by calling <xref:System.Windows.DependencyProperty.AddOwner%2A> on original owner <xref:System.Windows.Controls.Border> and its registered <xref:System.Windows.Controls.Border.BorderBrushProperty> dependency property identifer. The <xref:System.Windows.DependencyProperty.AddOwner%2A> return value is then used to establish a static <xref:System.Windows.DependencyProperty> field (<xref:System.Windows.Controls.Control.BorderBrushProperty>) for that property on the added owner, and a `BorderBrush` property wrapper is also declared.  
   
- The added owner's dependency property identifier should be used for operations such as <xref:System.Windows.DependencyObject.GetValue%2A>. However, type-specific operations involving either types or instances of the class that was added as owner with different metadata will still return the expected results even if the original (not the added owner's) dependency property identifier is specified in calls to methods such as <xref:System.Windows.DependencyObject.GetValue%2A> or <xref:System.Windows.DependencyProperty.GetMetadata%2A>. The metadata for the added owner is perpetuated by the <xref:System.Windows.DependencyProperty.AddOwner%2A> call itself, not necessarily referenced exclusively by the adding owner class identifier field. Nevertheless, it is good practice to expose the  identifier, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>, because failing to do so creates disparity between the CLR and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] representations of your properties.  
+ The added owner's dependency property identifier should be used for operations such as <xref:System.Windows.DependencyObject.GetValue%2A>. However, type-specific operations involving either types or instances of the class that was added as owner with different metadata will still return the expected results even if the original (not the added owner's) dependency property identifier is specified in calls to methods such as <xref:System.Windows.DependencyObject.GetValue%2A> or <xref:System.Windows.DependencyProperty.GetMetadata%2A>. The metadata for the added owner is perpetuated by the <xref:System.Windows.DependencyProperty.AddOwner%2A> call itself, not necessarily referenced exclusively by the adding owner class identifier field. Nevertheless, it is good practice to expose the  identifier, as well as new CLR property wrappers, for dependency properties that are added to types using <xref:System.Windows.DependencyProperty.AddOwner%2A>, because failing to do so creates disparity between the CLR and XAML representations of your properties.  
   
  The supplied metadata is merged with the property metadata for the dependency property as it exists on the base owner. Any characteristics that were specified in the original base metadata will persist. Only those characteristics that were specifically changed in the new metadata will override the characteristics of the base metadata. Some characteristics, such as <xref:System.Windows.PropertyMetadata.DefaultValue%2A>, are replaced if they are specified in the new metadata. Others, such as <xref:System.Windows.PropertyChangedCallback>, are combined. Ultimately, the merge behavior depends on the property metadata type being used for the override, so the behavior described here is for the existing property metadata classes used by WPF dependency properties. For details, see [Dependency Property Metadata](/dotnet/framework/wpf/advanced/dependency-property-metadata) and [Framework Property Metadata](/dotnet/framework/wpf/advanced/framework-property-metadata).  
   
@@ -1206,7 +1206,7 @@
 ## Remarks  
  This method returns the type <xref:System.Windows.DependencyPropertyKey>, whereas <xref:System.Windows.DependencyProperty.RegisterAttached%2A> returns the type <xref:System.Windows.DependencyProperty>. Typically, the keys that represent read-only properties are not made public, because the keys can be used to set the dependency property value by calling <xref:System.Windows.DependencyObject.SetValue%28System.Windows.DependencyPropertyKey%2CSystem.Object%29>. Your class design will affect your requirements, but it is generally recommended to limit the access and visibility of any <xref:System.Windows.DependencyPropertyKey> to only those parts of your code that are necessary to set that dependency property as part of class or application logic. It is also recommended that you expose a dependency property identifier for the read-only dependency property, by exposing the value of <xref:System.Windows.DependencyPropertyKey.DependencyProperty%2A?displayProperty=nameWithType> as a `public static readonly` field on your class.  
   
- Read-only attached properties are a rare scenario, because the primary scenario for an attached property is its use in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Without a public setter, an attached property cannot be set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax.  
+ Read-only attached properties are a rare scenario, because the primary scenario for an attached property is its use in XAML. Without a public setter, an attached property cannot be set in XAML syntax.  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1255,7 +1255,7 @@
 ## Remarks  
  This method returns the type <xref:System.Windows.DependencyPropertyKey>, whereas <xref:System.Windows.DependencyProperty.RegisterAttached%2A> returns the type <xref:System.Windows.DependencyProperty>. Typically, the keys that represent the type <xref:System.Windows.DependencyProperty>. Typically, the keys that represent read-only properties are not made public, because the keys can be used to set the dependency property value by calling <xref:System.Windows.DependencyObject.SetValue%28System.Windows.DependencyPropertyKey%2CSystem.Object%29>. Your class design will affect your requirements, but it is generally recommended to limit the access and visibility of any <xref:System.Windows.DependencyPropertyKey> to only those parts of your code that are necessary to set that dependency property as part of class or application logic. It is also recommended that you expose a dependency property identifier for the read-only dependency property, by exposing the value of <xref:System.Windows.DependencyPropertyKey.DependencyProperty%2A?displayProperty=nameWithType> as a `public static readonly` field on your class.  
   
- Read-only attached properties are a rare scenario, because the primary scenario for an attached property is its use in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Without a public setter, an attached property cannot be set in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax.  
+ Read-only attached properties are a rare scenario, because the primary scenario for an attached property is its use in XAML. Without a public setter, an attached property cannot be set in XAML syntax.  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
diff --git a/xml/System.Windows/DynamicResourceExtension.xml b/xml/System.Windows/DynamicResourceExtension.xml
index 3aa430e2961..5b28e941038 100644
--- a/xml/System.Windows/DynamicResourceExtension.xml
+++ b/xml/System.Windows/DynamicResourceExtension.xml
@@ -33,11 +33,11 @@
 ## Remarks  
  Dynamic resource references are necessary when referencing content that might change at run-time. The reasons for the content change might be application-initiated or might be external. One example is if you are including styles that rely on system resources that report user-configured preferences, such as themes, font settings and so on.  
   
- This class is a markup extension implementation. Markup extension classes in WPF exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by the markup extension classes are not typically called from directly user code. This class particularly supports the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. For more information about dynamic resource references, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
+ This class is a markup extension implementation. Markup extension classes in WPF exist mainly to provide infrastructure support for some aspect of the WPF XAML processor implementation, and the members exposed by the markup extension classes are not typically called from directly user code. This class particularly supports the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) usage from XAML. For more information about dynamic resource references, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
   
 <a name="xamlTextUsage_DynamicResourceExtension"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
+ For XAML information, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
   
  ]]></format>
     </remarks>
@@ -101,7 +101,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This constructor is used by [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processors when processing the attribute syntax for the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
+ This constructor is used by XAML processors when processing the attribute syntax for the [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
   
  ]]></format>
         </remarks>
@@ -135,7 +135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) values during object creation.  
+ This method supports WPF XAML processor implementation, and is not intended to be called directly. The XAML processor implementation uses this method for proper handling of [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) values during object creation.  
   
  The property to be set by the provided value must be of type <xref:System.Windows.DependencyProperty>.  
   
@@ -184,7 +184,7 @@
   
 <a name="xamlTextUsage_ResourceKey"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
+ For XAML information, see [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/EventSetter.xml b/xml/System.Windows/EventSetter.xml
index a424e3f7871..59811196223 100644
--- a/xml/System.Windows/EventSetter.xml
+++ b/xml/System.Windows/EventSetter.xml
@@ -25,7 +25,7 @@
   
  You can only declare event setters for events that are routed events. You can declare event setters for routed events with a direct routing strategy, bubbling events, or tunneling events.  
   
- Instances of the <xref:System.Windows.EventSetter> class are usually created through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], as an object element within a style defined through [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. An <xref:System.Windows.EventSetter> might also be instantiated from code.  
+ Instances of the <xref:System.Windows.EventSetter> class are usually created through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], as an object element within a style defined through XAML. An <xref:System.Windows.EventSetter> might also be instantiated from code.  
   
  Event setters cannot be used in a style that is contained in a theme resource dictionary. This is because a theme resource dictionary at run time is often loose [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files, and does not have any scope defined where accompanying code-behind that defines the handlers can exist.  
   
@@ -202,11 +202,11 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  Setting the <xref:System.Windows.RoutedEventHandlerInfo.InvokeHandledEventsToo%2A> characteristics of how an event's handlers will be invoked must always be performed in code, in keeping with the general principle that there is no way to specify <xref:System.Windows.RoutedEventHandlerInfo.InvokeHandledEventsToo%2A> when assigning defined event handlers for instances directly to named events in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute syntax. Although setting this value in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] does not generate any compile-time errors, the resulting [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will produce a run-time exception when the style is used.  
+>  Setting the <xref:System.Windows.RoutedEventHandlerInfo.InvokeHandledEventsToo%2A> characteristics of how an event's handlers will be invoked must always be performed in code, in keeping with the general principle that there is no way to specify <xref:System.Windows.RoutedEventHandlerInfo.InvokeHandledEventsToo%2A> when assigning defined event handlers for instances directly to named events in XAML attribute syntax. Although setting this value in XAML does not generate any compile-time errors, the resulting XAML will produce a run-time exception when the style is used.  
   
 <a name="xamlTextUsage_HandledEventsToo"></a>   
 ## XAML Text Usage  
- This property should not be used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. See Remarks.  
+ This property should not be used in XAML. See Remarks.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index cd334cff5dc..7ef2a157bfe 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -668,7 +668,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor relies on type conversion for the <xref:System.Windows.Input.Cursor> class to evaluate the string. The provided string should evaluate to a <xref:System.Windows.Input.CursorType> value. See <xref:System.Windows.Input.Cursor> for details.  
+ When setting this property in XAML, the XAML processor relies on type conversion for the <xref:System.Windows.Input.Cursor> class to evaluate the string. The provided string should evaluate to a <xref:System.Windows.Input.CursorType> value. See <xref:System.Windows.Input.Cursor> for details.  
   
  Whether the cursor as established by this property will or will not display when the mouse pointer is over this element is also dependent on the value of the <xref:System.Windows.FrameworkContentElement.ForceCursor%2A> property. Also, event-related considerations such as an active drag, mouse capture, text editing modes within controls, and so on, will also affect the cursor with higher priority than the value you specify in this property.  
   
@@ -769,7 +769,7 @@
   
  Alternatively, you can use one of the following properties of the <xref:System.Windows.Data.Binding> class to specify the binding source explicitly: <xref:System.Windows.Data.Binding.ElementName%2A>, <xref:System.Windows.Data.Binding.Source%2A>, or <xref:System.Windows.Data.Binding.RelativeSource%2A>. For more information, see [How to: Specify the Binding Source](/dotnet/framework/wpf/data/how-to-specify-the-binding-source).  
   
- In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], <xref:System.Windows.FrameworkContentElement.DataContext%2A> is most commonly set to as a <xref:System.Windows.Data.Binding> declaration. You can use either property element syntax or attribute syntax. Attribute syntax is shown in the example on this page. You can also set <xref:System.Windows.FrameworkContentElement.DataContext%2A> in code.  
+ In XAML, <xref:System.Windows.FrameworkContentElement.DataContext%2A> is most commonly set to as a <xref:System.Windows.Data.Binding> declaration. You can use either property element syntax or attribute syntax. Attribute syntax is shown in the example on this page. You can also set <xref:System.Windows.FrameworkContentElement.DataContext%2A> in code.  
   
 <a name="xamlPropertyElementUsage_DataContext"></a>   
 ## XAML Property Element Usage  
@@ -1101,7 +1101,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], styles are almost always defined as a resource, rather than inline as an element, and that resource is usually referenced as a <xref:System.Windows.StaticResourceExtension>.  
+ When setting this property in XAML, styles are almost always defined as a resource, rather than inline as an element, and that resource is usually referenced as a <xref:System.Windows.StaticResourceExtension>.  
   
  Note that this property affects visual appearance but does not report so in metadata. This is because the visual appearance change is event-driven and may not apply at all times, and thus should not generally report any visual or layout information in metadata.  
   
@@ -1359,7 +1359,7 @@
 ## Remarks  
  This dependency property inherits property values. If there are child elements with no other value for <xref:System.Windows.FrameworkElement.InputScope%2A> established through local values or styles, the property system will set the value to be the <xref:System.Windows.FrameworkElement.InputScope%2A> value of the nearest parent element with this value assigned.  
   
- Although a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax usage is listed and is syntactically allowed, setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is not common.  
+ Although a XAML syntax usage is listed and is syntactically allowed, setting this property in XAML is not common.  
   
 <a name="dependencyPropertyInfo_InputScope"></a>   
 ## Dependency Property Information  
@@ -1695,17 +1695,17 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the identifying name of the element. The name provides an instance reference so that programmatic code-behind, such as event handler code, can refer to an element once it is constructed during parsing of [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].</summary>
+        <summary>Gets or sets the identifying name of the element. The name provides an instance reference so that programmatic code-behind, such as event handler code, can refer to an element once it is constructed during parsing of XAML.</summary>
         <value>The name of the element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common usage of this property is when specifying a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element name in markup.  
+ The most common usage of this property is when specifying a XAML element name in markup.  
   
- This property essentially provides a WPF framework-level convenience property to set the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive).  
+ This property essentially provides a WPF framework-level convenience property to set the XAML [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive).  
   
- Getting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code is not common, because if you have the appropriate reference in code already, you can just call methods and properties on the element reference and do not generally need the <xref:System.Windows.FrameworkContentElement.Name%2A>. An exception is if the string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code if the original <xref:System.Windows.FrameworkContentElement.Name%2A> was set from markup is also not recommended, and changing the property will not change the object reference. Such object references are created only when the underlying namescopes are explicitly created during [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] loading.  
+ Getting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code is not common, because if you have the appropriate reference in code already, you can just call methods and properties on the element reference and do not generally need the <xref:System.Windows.FrameworkContentElement.Name%2A>. An exception is if the string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkContentElement.Name%2A> from code if the original <xref:System.Windows.FrameworkContentElement.Name%2A> was set from markup is also not recommended, and changing the property will not change the object reference. Such object references are created only when the underlying namescopes are explicitly created during XAML loading.  
   
  You must specifically call <xref:System.Windows.FrameworkContentElement.RegisterName%2A> to make an effective change on the <xref:System.Windows.FrameworkContentElement.Name%2A> property of an already loaded element.  
   
@@ -2306,11 +2306,11 @@
   
  Note that this property returns only the resource dictionary declared directly within that element. This is different than the actual resource lookup process, where a child element can access any of the resources defined in each parent element, searching recursively upwards.  
   
- Resources can also be referenced by code from within the collection, but be aware that resources created in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will definitely not be accessible until after <xref:System.Windows.FrameworkContentElement.Loaded> is raised by the element that declares the dictionary. In fact, resources are parsed asynchronously, and not even the <xref:System.Windows.FrameworkContentElement.Loaded> event is an assurance that you can reference a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] defined resource. For this reason you should generally only access [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] defined resources as part of run-time code, or through other [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] techniques such as styles or resource extension references for attribute values. When you access resources through code, it is essentially equivalent to a [DynamicResource](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) reference made from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Resources can also be referenced by code from within the collection, but be aware that resources created in XAML will definitely not be accessible until after <xref:System.Windows.FrameworkContentElement.Loaded> is raised by the element that declares the dictionary. In fact, resources are parsed asynchronously, and not even the <xref:System.Windows.FrameworkContentElement.Loaded> event is an assurance that you can reference a XAML defined resource. For this reason you should generally only access XAML defined resources as part of run-time code, or through other XAML techniques such as styles or resource extension references for attribute values. When you access resources through code, it is essentially equivalent to a [DynamicResource](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) reference made from XAML.  
   
  The underlying <xref:System.Windows.ResourceDictionary> supports the methods required to add, remove, or query resources from within the collection by using code. The <xref:System.Windows.FrameworkContentElement.Resources%2A> property is settable to support the scenario of completely replacing the resources collection of an element to be a new or different <xref:System.Windows.ResourceDictionary>.  
   
- Notice that the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax shown does not include an element for the <xref:System.Windows.ResourceDictionary>. This is an example of implicit collection syntax; a tag representing the collection element can be omitted. The elements that are added as items to the collection are specified instead. For more information about implicit collections and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). One case where a <xref:System.Windows.ResourceDictionary> is still specified explicitly as an element is if you are introducing a merged dictionary, in which case there are typically no child elements for that <xref:System.Windows.ResourceDictionary>. For details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
+ Notice that the XAML syntax shown does not include an element for the <xref:System.Windows.ResourceDictionary>. This is an example of implicit collection syntax; a tag representing the collection element can be omitted. The elements that are added as items to the collection are specified instead. For more information about implicit collections and XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). One case where a <xref:System.Windows.ResourceDictionary> is still specified explicitly as an element is if you are introducing a merged dictionary, in which case there are typically no child elements for that <xref:System.Windows.ResourceDictionary>. For details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
   
 <a name="xamlPropertyElementUsage_Resources"></a>   
 ## XAML Property Element Usage  
@@ -2930,7 +2930,7 @@
  A string that becomes the display text for the <xref:System.Windows.FrameworkContentElement.ToolTip%2A>.  
   
  *toolTipObjectContent*  
- Some object, provided in object element form, that should be used as the content for the <xref:System.Windows.FrameworkContentElement>. Typically this would be a <xref:System.Windows.FrameworkElement> or some other element that creates layout compositing for the <xref:System.Windows.FrameworkContentElement.ToolTip%2A>, eventually containing text content within the compositing. In this usage, the <xref:System.Windows.Controls.ToolTip> element is created implicitly from the parsed [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], and the *toolTipObjectContent* content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
+ Some object, provided in object element form, that should be used as the content for the <xref:System.Windows.FrameworkContentElement>. Typically this would be a <xref:System.Windows.FrameworkElement> or some other element that creates layout compositing for the <xref:System.Windows.FrameworkContentElement.ToolTip%2A>, eventually containing text content within the compositing. In this usage, the <xref:System.Windows.Controls.ToolTip> element is created implicitly from the parsed XAML, and the *toolTipObjectContent* content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
   
  <`ToolTip` .../>  
  See <xref:System.Windows.Controls.ToolTip>.  
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index b09a288f4a1..fb92c02b0b2 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -77,7 +77,7 @@
   
  As can be seen from the class hierarchy, many WPF classes derive from <xref:System.Windows.FrameworkElement>, either directly or through intermediate base classes such as <xref:System.Windows.Controls.Panel> or <xref:System.Windows.Controls.Control>.  
   
- If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
+ If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create XAML child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
   
  ]]></format>
     </remarks>
@@ -132,7 +132,7 @@
   
  Because <xref:System.Windows.FrameworkElement.ActualHeight%2A> is a calculated value, you should be aware that there could be multiple or incremental reported changes to it as a result of various operations by the layout system. The layout system may be calculating required measure space for child elements, constraints by the parent element, and so on.  
   
- Although you cannot set this property from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you can base a <xref:System.Windows.Trigger> upon its value in a style.  
+ Although you cannot set this property from XAML, you can base a <xref:System.Windows.Trigger> upon its value in a style.  
   
 <a name="dependencyPropertyInfo_ActualHeight"></a>   
 ## Dependency Property Information  
@@ -204,7 +204,7 @@
   
  Because <xref:System.Windows.FrameworkElement.ActualWidth%2A> is a calculated value, you should be aware that there could be multiple or incremental reported changes to it as a result of various operations by the layout system. The layout system may be calculating required measure space for child elements, constraints by the parent element, and so on.  
   
- Although you cannot set this property from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], you can base a <xref:System.Windows.Trigger> upon its value in a style.  
+ Although you cannot set this property from XAML, you can base a <xref:System.Windows.Trigger> upon its value in a style.  
   
 <a name="dependencyPropertyInfo_ActualWidth"></a>   
 ## Dependency Property Information  
@@ -1055,7 +1055,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you set this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor relies on type conversion for the <xref:System.Windows.Input.Cursor> class to evaluate the string. The provided string should evaluate to a <xref:System.Windows.Input.CursorType> value. See <xref:System.Windows.Input.Cursor> for details.  
+ When you set this property in XAML, the XAML processor relies on type conversion for the <xref:System.Windows.Input.Cursor> class to evaluate the string. The provided string should evaluate to a <xref:System.Windows.Input.CursorType> value. See <xref:System.Windows.Input.Cursor> for details.  
   
  Whether the cursor as established by this property will or will not display when the mouse pointer is over this element is also dependent on the value of the <xref:System.Windows.FrameworkElement.ForceCursor%2A> property. Also, event-related considerations such as an active drag, mouse capture, text editing modes within controls, and so on, will also affect the cursor with higher priority than the value you specify in this property.  
   
@@ -1538,7 +1538,7 @@
   
 <a name="xamlTextUsage_FlowDirection"></a>   
 ## XAML Text Usage  
- This property can also be set on classes that are not <xref:System.Windows.FrameworkElement> derived classes, by the following [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attached property usage:  
+ This property can also be set on classes that are not <xref:System.Windows.FrameworkElement> derived classes, by the following XAML attached property usage:  
   
  `<` *object* `FrameworkElement.`**FlowDirection**="<xref:System.Windows.FlowDirection>`"/>`  
   
@@ -2000,7 +2000,7 @@
   
  If this element is a child element within some other element, then setting this property to a value is really only a suggested value. The layout system as well as the particular layout logic of the parent element will use the value as a nonbinding input during the layout process. In practical terms, a <xref:System.Windows.FrameworkElement> is almost always the child element of something else; even when you set the <xref:System.Windows.FrameworkElement.Height%2A> on <xref:System.Windows.Window>. (For <xref:System.Windows.Window>, that value is used when the underlying application model establishes the basic rendering assumptions that create the Hwnd that hosts the application.)  
   
- In addition to acceptable <xref:System.Double> values, this property can also be <xref:System.Double.NaN?displayProperty=nameWithType>. This is how you specify auto sizing behavior in code. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] you set the value to the string "Auto" (case insensitive) to enable the auto sizing behavior. Auto sizing behavior implies that the element will fill the height available to it. Note however that specific controls frequently supply default values through their default theme styles that will disable the auto sizing behavior unless it is specifically re-enabled.  
+ In addition to acceptable <xref:System.Double> values, this property can also be <xref:System.Double.NaN?displayProperty=nameWithType>. This is how you specify auto sizing behavior in code. In XAML you set the value to the string "Auto" (case insensitive) to enable the auto sizing behavior. Auto sizing behavior implies that the element will fill the height available to it. Note however that specific controls frequently supply default values through their default theme styles that will disable the auto sizing behavior unless it is specifically re-enabled.  
   
  The return value of this property is always the same as any value that was set to it. In contrast, the value of the <xref:System.Windows.FrameworkElement.ActualHeight%2A> may vary. This can happen either statically because the layout rejected the suggested size for some reason, or momentarily. The layout system itself works asynchronously relative to the property system's set of <xref:System.Windows.FrameworkElement.Height%2A> and may not have processed that particular sizing property change yet.  
   
@@ -2211,7 +2211,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This event will be raised whenever the <xref:System.Windows.FrameworkElement.EndInit%2A> or <xref:System.Windows.FrameworkElement.OnVisualParentChanged%2A> methods are called. Calls to either method could have come from application code, or through the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] processor behavior when a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] page is processed.  
+ This event will be raised whenever the <xref:System.Windows.FrameworkElement.EndInit%2A> or <xref:System.Windows.FrameworkElement.OnVisualParentChanged%2A> methods are called. Calls to either method could have come from application code, or through the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] processor behavior when a XAML page is processed.  
   
  Whether you choose to handle <xref:System.Windows.FrameworkElement.Loaded> or <xref:System.Windows.FrameworkElement.Initialized> depends on your requirements. If you do not need to read element properties, intend to reset properties, and do not need any layout information, <xref:System.Windows.FrameworkElement.Initialized> might be the better event to act upon. If you need all properties of the element to be available, and you will be setting properties that are likely to reset the layout, <xref:System.Windows.FrameworkElement.Loaded> might be the better event to act upon. Be careful of reentrancy if your handler resets any properties that are interpreted by the layout system to mean that a new layout pass is required. (You might need to check the <xref:System.Windows.FrameworkPropertyMetadata> values on the property if you are unsure of which properties can require a new layout pass if they are changed.)  
   
@@ -2248,7 +2248,7 @@
 ## Remarks  
  This dependency property inherits property values. If there are child elements without other values for <xref:System.Windows.FrameworkElement.InputScope%2A> established through local values or styles, then the property system will set the value to be the <xref:System.Windows.FrameworkElement.InputScope%2A> value of the nearest ancestor element with this value assigned.  
   
- Although a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax usage is listed and is syntactically allowed, setting this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is not common.  
+ Although a XAML syntax usage is listed and is syntactically allowed, setting this property in XAML is not common.  
   
 <a name="dependencyPropertyInfo_InputScope"></a>   
 ## Dependency Property Information  
@@ -2314,16 +2314,16 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether this element has been initialized, either during processing by a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor, or by explicitly having its <see cref="M:System.Windows.FrameworkElement.EndInit" /> method called.</summary>
+        <summary>Gets a value that indicates whether this element has been initialized, either during processing by a XAML processor, or by explicitly having its <see cref="M:System.Windows.FrameworkElement.EndInit" /> method called.</summary>
         <value>
-          <see langword="true" /> if the element is initialized per the aforementioned [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processing or method calls; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the element is initialized per the aforementioned XAML processing or method calls; otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  This property may also be `true` if this element has been moved within the logical tree such that it has a new parent element, and therefore becomes reloaded again.  
   
- This property is useful if you also are using <xref:System.Windows.FrameworkElement.BeginInit%2A> and <xref:System.Windows.FrameworkElement.EndInit%2A>. Elements in the logical tree that is loaded by a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor are assured to be initialized. Elements not in the logical tree are initialized when <xref:System.Windows.FrameworkElement.EndInit%2A> is called. In absence of any specific handling of <xref:System.Windows.FrameworkElement.BeginInit%2A> and <xref:System.Windows.FrameworkElement.EndInit%2A>, this will happen as soon as the constructor returns the initialized result.  
+ This property is useful if you also are using <xref:System.Windows.FrameworkElement.BeginInit%2A> and <xref:System.Windows.FrameworkElement.EndInit%2A>. Elements in the logical tree that is loaded by a XAML processor are assured to be initialized. Elements not in the logical tree are initialized when <xref:System.Windows.FrameworkElement.EndInit%2A> is called. In absence of any specific handling of <xref:System.Windows.FrameworkElement.BeginInit%2A> and <xref:System.Windows.FrameworkElement.EndInit%2A>, this will happen as soon as the constructor returns the initialized result.  
   
  ]]></format>
         </remarks>
@@ -2646,7 +2646,7 @@
 ## Remarks  
  The margin is the space between this element and other elements that will be adjacent when layout creates the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. Shared elements might be peer elements (such as other elements in the collection of a common parent control), or might also be this element's parent.  
   
- <xref:System.Windows.FrameworkElement.Margin%2A> is set as a <xref:System.Windows.Thickness> structure rather than as a number so that the margin can be set asymmetrically. The <xref:System.Windows.Thickness> structure itself supports string type conversion so that you can specify an asymmetric <xref:System.Windows.FrameworkElement.Margin%2A> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attribute syntax also.  
+ <xref:System.Windows.FrameworkElement.Margin%2A> is set as a <xref:System.Windows.Thickness> structure rather than as a number so that the margin can be set asymmetrically. The <xref:System.Windows.Thickness> structure itself supports string type conversion so that you can specify an asymmetric <xref:System.Windows.FrameworkElement.Margin%2A> in XAML attribute syntax also.  
   
  A non-zero margin applies space outside the element layout's <xref:System.Windows.FrameworkElement.ActualWidth%2A> and <xref:System.Windows.FrameworkElement.ActualHeight%2A>.  
   
@@ -2693,7 +2693,7 @@
   
  The default unit for a <xref:System.Windows.Thickness> measure is [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)]. You can also specify other units by appending the unit type strings `cm`, `in`, or `pt` to any measure.  
   
- Number values provided as [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] attributes need not specify decimal points (0 is acceptable, does not have to be provided as 0.0). For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
+ Number values provided as XAML attributes need not specify decimal points (0 is acceptable, does not have to be provided as 0.0). For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
   
  *thicknessReference*  
  An object reference to an existing <xref:System.Windows.Thickness>. This might be a `}`, a , or `}` reference. For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
@@ -3319,19 +3319,19 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the identifying name of the element. The name provides a reference so that code-behind, such as event handler code, can refer to a markup element after it is constructed during processing by a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor.</summary>
+        <summary>Gets or sets the identifying name of the element. The name provides a reference so that code-behind, such as event handler code, can refer to a markup element after it is constructed during processing by a XAML processor.</summary>
         <value>The name of the element. The default is an empty string.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common usage of this property is to specify a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element name as an attribute in markup.  
+ The most common usage of this property is to specify a XAML element name as an attribute in markup.  
   
- This property essentially provides a WPF framework-level convenience property to set the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive).  
+ This property essentially provides a WPF framework-level convenience property to set the XAML [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive).  
   
  Names must be unique within a namescope. For more information, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
   
- Getting a <xref:System.Windows.FrameworkElement.Name%2A> if you are creating elements in code is not common. If you have the appropriate reference in code already, you can just call methods and properties on the element reference and will not generally need the <xref:System.Windows.FrameworkElement.Name%2A>. An exception to this is if the <xref:System.Windows.FrameworkElement.Name%2A> string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkElement.Name%2A> from code-behind if the original <xref:System.Windows.FrameworkElement.Name%2A> was set from markup is also not recommended, and changing the property after loading the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will not change the original object reference. The object references are created only when the underlying namescopes are explicitly created during parsing. You must specifically call <xref:System.Windows.FrameworkElement.RegisterName%2A> to make an effective change to the <xref:System.Windows.FrameworkElement.Name%2A> property of an already loaded element.  
+ Getting a <xref:System.Windows.FrameworkElement.Name%2A> if you are creating elements in code is not common. If you have the appropriate reference in code already, you can just call methods and properties on the element reference and will not generally need the <xref:System.Windows.FrameworkElement.Name%2A>. An exception to this is if the <xref:System.Windows.FrameworkElement.Name%2A> string has some overloaded meaning, for instance if it is useful to display that name in UI. Setting a <xref:System.Windows.FrameworkElement.Name%2A> from code-behind if the original <xref:System.Windows.FrameworkElement.Name%2A> was set from markup is also not recommended, and changing the property after loading the XAML will not change the original object reference. The object references are created only when the underlying namescopes are explicitly created during parsing. You must specifically call <xref:System.Windows.FrameworkElement.RegisterName%2A> to make an effective change to the <xref:System.Windows.FrameworkElement.Name%2A> property of an already loaded element.  
   
  One notable case where setting <xref:System.Windows.FrameworkElement.Name%2A> from code is important is when registering names for elements that storyboards will run against, so that they can be referenced at run time. Before you can register a name, might also need to instantiate and assign a <xref:System.Windows.NameScope> instance. See the Example section, or [Storyboards Overview](/dotnet/framework/wpf/graphics-multimedia/storyboards-overview).  
   
@@ -3341,7 +3341,7 @@
   
  The <xref:System.Windows.FrameworkElement.Name%2A> property also serves as an identifier for other processes. For instance, the WPF automation model will use <xref:System.Windows.FrameworkElement.Name%2A> as the AutomationId for clients and providers.  
   
- The string values used for <xref:System.Windows.FrameworkElement.Name%2A> have some restrictions, as imposed by the underlying [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive) defined by the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] specification. Most notably, a <xref:System.Windows.FrameworkElement.Name%2A> must start with a letter or the underscore character (_), and must contain only letters, digits, or underscores. For more information, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
+ The string values used for <xref:System.Windows.FrameworkElement.Name%2A> have some restrictions, as imposed by the underlying [x:Name Directive](/dotnet/framework/xaml-services/x-name-directive) defined by the XAML specification. Most notably, a <xref:System.Windows.FrameworkElement.Name%2A> must start with a letter or the underscore character (_), and must contain only letters, digits, or underscores. For more information, see [WPF XAML Namescopes](/dotnet/framework/wpf/advanced/wpf-xaml-namescopes).  
   
  <xref:System.Windows.FrameworkElement.Name%2A> is one of the very few dependency properties that cannot be animated (<xref:System.Windows.UIPropertyMetadata.IsAnimationProhibited%2A> is `true` in metadata), because the name itself is vital for targeting an animation. Data binding a <xref:System.Windows.FrameworkElement.Name%2A> is technically possible, but is an extremely uncommon scenario because a data-bound <xref:System.Windows.FrameworkElement.Name%2A> cannot serve the main intended purpose of the property: to provide an identifier connection point for code-behind.  
   
@@ -4210,11 +4210,11 @@
   
  Note that this property returns only the resource dictionary declared directly within that element. This is different than the actual resource lookup process, where a child element can access any of the resources defined in each parent element, searching recursively upwards.  
   
- Resources can also be referenced by code from within the collection, but be aware that resources created in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] will definitely not be accessible until after <xref:System.Windows.FrameworkElement.Loaded> is raised by the element that declares the dictionary. In fact, resources are parsed asynchronously and not even the <xref:System.Windows.FrameworkElement.Loaded> event is an assurance that you can reference a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] defined resource. For this reason you should generally only access [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] defined resources as part of run-time code, or through other [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] techniques such as styles or resource extension references for attribute values. When you access resources through code, it is essentially equivalent to a [DynamicResource](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) reference made from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Resources can also be referenced by code from within the collection, but be aware that resources created in XAML will definitely not be accessible until after <xref:System.Windows.FrameworkElement.Loaded> is raised by the element that declares the dictionary. In fact, resources are parsed asynchronously and not even the <xref:System.Windows.FrameworkElement.Loaded> event is an assurance that you can reference a XAML defined resource. For this reason you should generally only access XAML defined resources as part of run-time code, or through other XAML techniques such as styles or resource extension references for attribute values. When you access resources through code, it is essentially equivalent to a [DynamicResource](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) reference made from XAML.  
   
  The underlying <xref:System.Windows.ResourceDictionary> supports the methods required to add, remove or query resources from within the collection by using code. The <xref:System.Windows.FrameworkElement.Resources%2A> property is settable to support the scenario of completely replacing the resources collection of an element to be a new or different <xref:System.Windows.ResourceDictionary>.  
   
- Notice that the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax shown does not include an element for the <xref:System.Windows.ResourceDictionary>. This is an example of implicit collection syntax; a tag representing the collection element can be omitted. The elements that are added as items to the collection are specified instead. For more information about implicit collections and [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). One case where a <xref:System.Windows.ResourceDictionary> is still specified explicitly as an element is if you are introducing a merged dictionary, in which case there are typically no child elements for that <xref:System.Windows.ResourceDictionary>. For details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
+ Notice that the XAML syntax shown does not include an element for the <xref:System.Windows.ResourceDictionary>. This is an example of implicit collection syntax; a tag representing the collection element can be omitted. The elements that are added as items to the collection are specified instead. For more information about implicit collections and XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). One case where a <xref:System.Windows.ResourceDictionary> is still specified explicitly as an element is if you are introducing a merged dictionary, in which case there are typically no child elements for that <xref:System.Windows.ResourceDictionary>. For details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
   
 <a name="xamlPropertyElementUsage_Resources"></a>   
 ## XAML Property Element Usage  
@@ -4985,7 +4985,7 @@
  A string that becomes the display text for the <xref:System.Windows.FrameworkElement.ToolTip%2A>.  
   
  *toolTipObjectContent*  
- Some object, provided in object element form, that should be used as the content for the <xref:System.Windows.FrameworkElement>. Typically this would be a <xref:System.Windows.FrameworkElement> or some other element that creates layout compositing for the <xref:System.Windows.FrameworkElement.ToolTip%2A>, eventually containing text content within the compositing. In this usage, the <xref:System.Windows.Controls.ToolTip> element is created implicitly from the parsed [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], and the *toolTipObjectContent* content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
+ Some object, provided in object element form, that should be used as the content for the <xref:System.Windows.FrameworkElement>. Typically this would be a <xref:System.Windows.FrameworkElement> or some other element that creates layout compositing for the <xref:System.Windows.FrameworkElement.ToolTip%2A>, eventually containing text content within the compositing. In this usage, the <xref:System.Windows.Controls.ToolTip> element is created implicitly from the parsed XAML, and the *toolTipObjectContent* content is set as its <xref:System.Windows.Controls.ContentControl.Content%2A?displayProperty=nameWithType> property.  
   
  <`ToolTip` .../>  
  See <xref:System.Windows.Controls.ToolTip>.  
@@ -5280,7 +5280,7 @@
    
   
 ## Examples  
- The following example is implemented as a button handler, where the button being clicked sets its background to a resource-defined brush obtained by calling <xref:System.Windows.FrameworkElement.TryFindResource%2A> on itself. This walks the element tree and finds the resource (the resource itself is defined in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] and is not shown).  
+ The following example is implemented as a button handler, where the button being clicked sets its background to a resource-defined brush obtained by calling <xref:System.Windows.FrameworkElement.TryFindResource%2A> on itself. This walks the element tree and finds the resource (the resource itself is defined in XAML and is not shown).  
   
  [!code-csharp[BaseElementsSmorgasbord#FETryFindResource](~/samples/snippets/csharp/VS_Snippets_Wpf/BaseElementsSmorgasbord/CSharp/Page1.xaml.cs#fetryfindresource)]
  [!code-vb[BaseElementsSmorgasbord#FETryFindResource](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BaseElementsSmorgasbord/visualbasic/page1.xaml.vb#fetryfindresource)]  
@@ -5674,7 +5674,7 @@
   
  The return value of this property is always the same as any value that was set to it. In contrast, the value of the <xref:System.Windows.FrameworkElement.ActualWidth%2A> may vary. The layout may have rejected the suggested size for some reason. Also, the layout system itself works asynchronously relative to the property system set of <xref:System.Windows.FrameworkElement.Width%2A> and may not have processed that particular sizing property change yet.  
   
- In addition to acceptable <xref:System.Double> values, this property can also be <xref:System.Double.NaN?displayProperty=nameWithType>. This is how you specify auto sizing behavior. In [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] you set the value to the string "Auto" (case insensitive) to enable the auto sizing behavior. Auto sizing behavior implies that the element will fill the width available to it. Note however that specific controls frequently supply default values in their default styles that will disable the auto sizing behavior unless it is specifically re-enabled.  
+ In addition to acceptable <xref:System.Double> values, this property can also be <xref:System.Double.NaN?displayProperty=nameWithType>. This is how you specify auto sizing behavior. In XAML you set the value to the string "Auto" (case insensitive) to enable the auto sizing behavior. Auto sizing behavior implies that the element will fill the width available to it. Note however that specific controls frequently supply default values in their default styles that will disable the auto sizing behavior unless it is specifically re-enabled.  
   
  In addition to the validation check, there is a nondeterministic upper value bound for <xref:System.Windows.FrameworkElement.Width%2A> that is enforced by the layout system (this is a very large number, larger than <xref:System.Single.MaxValue?displayProperty=nameWithType> but smaller than <xref:System.Double.MaxValue?displayProperty=nameWithType>). If you exceed this bound, the element will not render, and no exception is thrown. Do not set <xref:System.Windows.FrameworkElement.Width%2A> to a value that is significantly larger than the maximum size of any possible visual display, or you may exceed this nondeterministic upper bound.  
   
diff --git a/xml/System.Windows/FrameworkElementFactory.xml b/xml/System.Windows/FrameworkElementFactory.xml
index 47e947b315f..2ec0bda0b3d 100644
--- a/xml/System.Windows/FrameworkElementFactory.xml
+++ b/xml/System.Windows/FrameworkElementFactory.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a deprecated way to programmatically create templates, which are subclasses of <xref:System.Windows.FrameworkTemplate> such as <xref:System.Windows.Controls.ControlTemplate> or <xref:System.Windows.DataTemplate>; not all of the template functionality is available when you create a template using this class. The recommended way to programmatically create a template is to load [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] from a string or a memory stream using the <xref:System.Windows.Markup.XamlReader.Load%2A> method of the <xref:System.Windows.Markup.XamlReader> class.  
+ This class is a deprecated way to programmatically create templates, which are subclasses of <xref:System.Windows.FrameworkTemplate> such as <xref:System.Windows.Controls.ControlTemplate> or <xref:System.Windows.DataTemplate>; not all of the template functionality is available when you create a template using this class. The recommended way to programmatically create a template is to load XAML from a string or a memory stream using the <xref:System.Windows.Markup.XamlReader.Load%2A> method of the <xref:System.Windows.Markup.XamlReader> class.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/FrameworkPropertyMetadata.xml b/xml/System.Windows/FrameworkPropertyMetadata.xml
index 7398cf33038..94a964ffedb 100644
--- a/xml/System.Windows/FrameworkPropertyMetadata.xml
+++ b/xml/System.Windows/FrameworkPropertyMetadata.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_FrameworkPropertyMetadata"></a>   
 ## XAML Text Usage  
- This class is not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is not typically used in XAML.  
   
    
   
@@ -586,7 +586,7 @@
   
 <a name="xamlTextUsage_AffectsArrange"></a>   
 ## XAML Text Usage  
- Members of this class are either not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are either not typically used in XAML.  
   
    
   
@@ -637,7 +637,7 @@
   
 <a name="xamlTextUsage_AffectsMeasure"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
    
   
@@ -693,7 +693,7 @@
   
 <a name="xamlTextUsage_AffectsParentArrange"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -738,7 +738,7 @@
   
 <a name="xamlTextUsage_AffectsParentMeasure"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -779,7 +779,7 @@
   
 <a name="xamlTextUsage_AffectsRender"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
    
   
@@ -822,7 +822,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In absence of this property being `true`, binding updates are one-way by default, based on the default behavior of the <xref:System.Windows.Data.Binding> constructors or equivalent [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax.  
+ In absence of this property being `true`, binding updates are one-way by default, based on the default behavior of the <xref:System.Windows.Data.Binding> constructors or equivalent XAML syntax.  
   
  In existing elements, you will usually find this property set to `true` in metadata for dependency properties that both report state and are modifiable by user action, for example <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType>.  
   
@@ -832,7 +832,7 @@
   
 <a name="xamlTextUsage_BindsTwoWayByDefault"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
    
   
@@ -878,7 +878,7 @@
   
 <a name="xamlTextUsage_DefaultUpdateSourceTrigger"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -911,7 +911,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Property value inheritance is a feature of the WPF property system at the WPF framework level, whereby certain dependency properties can be locally set on an element at or near the root of a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] element tree and then have their value inherited by all elements within the logical tree of child elements that also possess that property. Property value inheritance is not enabled by default, and enabling it does have some performance implications. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
+ Property value inheritance is a feature of the WPF property system at the WPF framework level, whereby certain dependency properties can be locally set on an element at or near the root of a XAML element tree and then have their value inherited by all elements within the logical tree of child elements that also possess that property. Property value inheritance is not enabled by default, and enabling it does have some performance implications. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
   
 > [!NOTE]
 >  Although property value inheritance might appear to work for nonattached dependency properties, the inheritance behavior for a nonattached property through certain object-object divisions in the runtime tree is undefined. Always use <xref:System.Windows.DependencyProperty.RegisterAttached%2A> to register properties where you specify <xref:System.Windows.FrameworkPropertyMetadata.Inherits%2A> in the metadata.  
@@ -920,7 +920,7 @@
   
 <a name="xamlTextUsage_Inherits"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
    
   
@@ -969,7 +969,7 @@
   
 <a name="xamlTextUsage_IsDataBindingAllowed"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
    
   
@@ -1019,7 +1019,7 @@
   
 <a name="xamlTextUsage_IsNotDataBindable"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -1057,7 +1057,7 @@
   
 <a name="xamlTextUsage_Journal"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -1185,7 +1185,7 @@
   
 <a name="xamlTextUsage_OverridesInheritanceBehavior"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
@@ -1224,7 +1224,7 @@
   
 <a name="xamlTextUsage_SubPropertiesDoNotAffectRender"></a>   
 ## XAML Text Usage  
- Members of this class are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this class are not typically used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/FreezableCollection`1.xml b/xml/System.Windows/FreezableCollection`1.xml
index 01452cdd6fa..8d4d347e5df 100644
--- a/xml/System.Windows/FreezableCollection`1.xml
+++ b/xml/System.Windows/FreezableCollection`1.xml
@@ -59,13 +59,13 @@
  This class is provided to enable the creation of custom collection types that fully support data binding, change notification, property invalidation, and animation of its contents.  
   
 ### XAML Usage for FreezableCollection  
- <xref:System.Windows.FreezableCollection%601> supports a limited [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax.  
+ <xref:System.Windows.FreezableCollection%601> supports a limited XAML syntax.  
   
--   As an object element at the root, you can theoretically specify an unconstrained <xref:System.Windows.FreezableCollection%601> object element, which must also specify the [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) to declare the constraint. However, this is not a common scenario, because to do this, the <xref:System.Windows.FreezableCollection%601> must be the root element. This limitation exists because the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation in WPF can only support [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) when the element it is being set on is the root element, and you must use  on any open constraint generic if you want to instantiate a generic type in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. It is unlikely that you want a <xref:System.Windows.FreezableCollection%601> as the root element, even as loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+-   As an object element at the root, you can theoretically specify an unconstrained <xref:System.Windows.FreezableCollection%601> object element, which must also specify the [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) to declare the constraint. However, this is not a common scenario, because to do this, the <xref:System.Windows.FreezableCollection%601> must be the root element. This limitation exists because the XAML processor implementation in WPF can only support [x:TypeArguments Directive](/dotnet/framework/xaml-services/x-typearguments-directive) when the element it is being set on is the root element, and you must use  on any open constraint generic if you want to instantiate a generic type in XAML. It is unlikely that you want a <xref:System.Windows.FreezableCollection%601> as the root element, even as loose XAML.  
   
 -   If you derive from <xref:System.Windows.FreezableCollection%601> and apply a type constraint in the derived collection, the derived collection can support a variety of usages. This is possible because the constraint in your derivation eliminates the need to pass .  
   
-    -   The typical [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage for such a derived collection is through implicit collection syntax. Collections that support certain interfaces do not need to specify the collection itself as an object element. For details on collection syntax in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). For instance, an *object* with a *property* where the *property* was of type <xref:System.Windows.FreezableCollection%601> constrained by <xref:System.Windows.DependencyObject> could support the following syntax:  
+    -   The typical XAML usage for such a derived collection is through implicit collection syntax. Collections that support certain interfaces do not need to specify the collection itself as an object element. For details on collection syntax in XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). For instance, an *object* with a *property* where the *property* was of type <xref:System.Windows.FreezableCollection%601> constrained by <xref:System.Windows.DependencyObject> could support the following syntax:  
   
         ```  
         <object>  
diff --git a/xml/System.Windows/HierarchicalDataTemplate.xml b/xml/System.Windows/HierarchicalDataTemplate.xml
index 819e13d3861..7905d45e12e 100644
--- a/xml/System.Windows/HierarchicalDataTemplate.xml
+++ b/xml/System.Windows/HierarchicalDataTemplate.xml
@@ -333,7 +333,7 @@
   
 <a name="xamlTextUsage_ItemsSource"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see the <xref:System.Windows.Data.Binding> type.  
+ For XAML information, see the <xref:System.Windows.Data.Binding> type.  
   
    
   
diff --git a/xml/System.Windows/PropertyMetadata.xml b/xml/System.Windows/PropertyMetadata.xml
index 05e90999a56..9b3bf0af14b 100644
--- a/xml/System.Windows/PropertyMetadata.xml
+++ b/xml/System.Windows/PropertyMetadata.xml
@@ -29,7 +29,7 @@
   
 <a name="xamlTextUsage_PropertyMetadata"></a>   
 ## XAML Text Usage  
- This type, and members of this type, are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This type, and members of this type, are not typically used in XAML.  
   
  ]]></format>
     </remarks>
@@ -297,7 +297,7 @@
   
 <a name="xamlTextUsage_PropertyChangedCallback"></a>   
 ## XAML Text Usage  
- Members of this type are not typically used in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ Members of this type are not typically used in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/PropertyPath.xml b/xml/System.Windows/PropertyPath.xml
index f9863871962..9f3081d23a5 100644
--- a/xml/System.Windows/PropertyPath.xml
+++ b/xml/System.Windows/PropertyPath.xml
@@ -47,7 +47,7 @@
 <a name="xamlValues_PropertyPath"></a>   
 ## XAML Values  
  *propertyPath*  
- A string that is evaluated to be either a simple or complex property path. The syntax for setting a <xref:System.Windows.PropertyPath> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] is versatile but complex, and is described in the separate topic [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
+ A string that is evaluated to be either a simple or complex property path. The syntax for setting a <xref:System.Windows.PropertyPath> in XAML is versatile but complex, and is described in the separate topic [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
   
  ]]></format>
     </remarks>
@@ -187,11 +187,11 @@
   
  The path string for a <xref:System.Windows.PropertyPath> is typically established through the constructors: the <xref:System.Windows.PropertyPath.%23ctor%28System.Object%29> signature for bindings or single-step storyboard targets, the <xref:System.Windows.PropertyPath.%23ctor%28System.String%2CSystem.Object%5B%5D%29> signature for multi-step storyboard targets.  
   
- **XAML:** When you use a <xref:System.Windows.PropertyPath> to describe a property reference in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], as an attribute value, the string that you specify is first handled by a type converter (<xref:System.Windows.PropertyPathConverter>). This type converter then processes the string and based on its syntax will call one of the <xref:System.Windows.PropertyPath> constructor signatures. This indirection through the type converter handling an attribute value is generally how you use <xref:System.Windows.PropertyPath> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], rather than declaring a <xref:System.Windows.PropertyPath> object element and then applying specific values to attributes such as <xref:System.Windows.PropertyPath.Path%2A> and <xref:System.Windows.PropertyPath.PathParameters%2A>. For more information, see [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
+ **XAML:** When you use a <xref:System.Windows.PropertyPath> to describe a property reference in XAML, as an attribute value, the string that you specify is first handled by a type converter (<xref:System.Windows.PropertyPathConverter>). This type converter then processes the string and based on its syntax will call one of the <xref:System.Windows.PropertyPath> constructor signatures. This indirection through the type converter handling an attribute value is generally how you use <xref:System.Windows.PropertyPath> in XAML, rather than declaring a <xref:System.Windows.PropertyPath> object element and then applying specific values to attributes such as <xref:System.Windows.PropertyPath.Path%2A> and <xref:System.Windows.PropertyPath.PathParameters%2A>. For more information, see [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
   
 <a name="xamlTextUsage_Path"></a>   
 ## XAML Text Usage  
- Members of the <xref:System.Windows.PropertyPath> type are not typically set in a direct [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax. See Remarks.  
+ Members of the <xref:System.Windows.PropertyPath> type are not typically set in a direct XAML syntax. See Remarks.  
   
  ]]></format>
         </remarks>
@@ -227,11 +227,11 @@
   
  The actual evaluation of the property chain is performed by the storyboard animation mechanisms. At the <xref:System.Windows.PropertyPath> level, no validation is performed to make sure that the steps of the path connect at all. For instance, you can construct a property path that has <xref:System.Windows.Controls.Control.BackgroundProperty?displayProperty=nameWithType> as the first step, and <xref:System.Windows.FrameworkElement.FlowDirectionProperty?displayProperty=nameWithType> as the second step. But such a property path would fail if actually applied as a target, because the Brush type that fills <xref:System.Windows.Controls.Control.BackgroundProperty?displayProperty=nameWithType> does not have a <xref:System.Windows.FrameworkElement.FlowDirection%2A?displayProperty=nameWithType> property. Invalid property paths fail silently. For more information, see [Storyboards Overview](/dotnet/framework/wpf/graphics-multimedia/storyboards-overview).  
   
- **XAML:** When you use a <xref:System.Windows.PropertyPath> to describe a property reference in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], as an attribute value, the string that you specify is first handled by a type converter (<xref:System.Windows.PropertyPathConverter>). This type converter then processes the string and based on its syntax will call one of the <xref:System.Windows.PropertyPath> constructor signatures. This indirection through the type converter handling an attribute value is generally how you use <xref:System.Windows.PropertyPath> in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], rather than declaring a <xref:System.Windows.PropertyPath> object element and then applying specific values to attributes such as <xref:System.Windows.PropertyPath.Path%2A> and <xref:System.Windows.PropertyPath.PathParameters%2A>. For more information, see [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
+ **XAML:** When you use a <xref:System.Windows.PropertyPath> to describe a property reference in XAML, as an attribute value, the string that you specify is first handled by a type converter (<xref:System.Windows.PropertyPathConverter>). This type converter then processes the string and based on its syntax will call one of the <xref:System.Windows.PropertyPath> constructor signatures. This indirection through the type converter handling an attribute value is generally how you use <xref:System.Windows.PropertyPath> in XAML, rather than declaring a <xref:System.Windows.PropertyPath> object element and then applying specific values to attributes such as <xref:System.Windows.PropertyPath.Path%2A> and <xref:System.Windows.PropertyPath.PathParameters%2A>. For more information, see [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
   
 <a name="xamlTextUsage_PathParameters"></a>   
 ## XAML Text Usage  
- Members of the <xref:System.Windows.PropertyPath> type are not typically set in a direct [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax. See Remarks.  
+ Members of the <xref:System.Windows.PropertyPath> type are not typically set in a direct XAML syntax. See Remarks.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/ResourceDictionary.xml b/xml/System.Windows/ResourceDictionary.xml
index c8656dcd5aa..acfa7314350 100644
--- a/xml/System.Windows/ResourceDictionary.xml
+++ b/xml/System.Windows/ResourceDictionary.xml
@@ -57,13 +57,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The items in a <xref:System.Windows.ResourceDictionary> are not immediately processed when application code is loaded by a [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] loader. Instead, the <xref:System.Windows.ResourceDictionary> persists as an object, and the individual values are processed only when they are specifically requested.  
+ The items in a <xref:System.Windows.ResourceDictionary> are not immediately processed when application code is loaded by a XAML loader. Instead, the <xref:System.Windows.ResourceDictionary> persists as an object, and the individual values are processed only when they are specifically requested.  
   
  The <xref:System.Windows.ResourceDictionary> class is not derived from <xref:System.Collections.DictionaryBase>. Instead, the <xref:System.Windows.ResourceDictionary> class implements <xref:System.Collections.IDictionary> but relies on a <xref:System.Collections.Hashtable> internally.  
   
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], the <xref:System.Windows.ResourceDictionary> class is typically an implicit collection element that is the object element value of several `Resources` properties, when given in property element syntax. For details on implicit collections in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). An exception is when you want to specify a merged dictionary; for details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
+ In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], the <xref:System.Windows.ResourceDictionary> class is typically an implicit collection element that is the object element value of several `Resources` properties, when given in property element syntax. For details on implicit collections in XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). An exception is when you want to specify a merged dictionary; for details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
   
- Another possible [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage is to declare a resource dictionary as a discrete [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, and either load it at run time with <xref:System.Windows.Markup.XamlReader.Load%2A> or include it in a (full-trust) project as a resource or loose file. In this case, <xref:System.Windows.ResourceDictionary> can be declared as an object element, serving as the root element of the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. You must map the appropriate XML namespace values (default for the WPF namespace and typically `x:` for the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] namespace) onto the <xref:System.Windows.ResourceDictionary> element if you plan to use it as the root element. Then you can add child elements that define the resources, each with an [x:Key](/dotnet/framework/xaml-services/x-key-directive) value.  
+ Another possible XAML usage is to declare a resource dictionary as a discrete XAML file, and either load it at run time with <xref:System.Windows.Markup.XamlReader.Load%2A> or include it in a (full-trust) project as a resource or loose file. In this case, <xref:System.Windows.ResourceDictionary> can be declared as an object element, serving as the root element of the XAML. You must map the appropriate XML namespace values (default for the WPF namespace and typically `x:` for the XAML namespace) onto the <xref:System.Windows.ResourceDictionary> element if you plan to use it as the root element. Then you can add child elements that define the resources, each with an [x:Key](/dotnet/framework/xaml-services/x-key-directive) value.  
   
 <a name="xamlImplicitCollectionUsage_ResourceDictionary"></a>   
 ## XAML Implicit Collection Usage  
@@ -599,7 +599,7 @@ The invalidations happen when an implicit data template resource changes.</summa
   
  However, obtaining resources directly from an individual dictionary might be appropriate if you are retrieving resources from a known <xref:System.Windows.ResourceDictionary> location, and are doing so to avoid the possible performance and scope implications of run-time key lookup.  
   
- You do not use indexers to define collection members in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]. Instead, you create child elements in markup. The child elements are either child elements of <xref:System.Windows.ResourceDictionary>, or of a property element where the property type is `ResourceDictionary`. For details, see the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage sections in <xref:System.Windows.ResourceDictionary>.  
+ You do not use indexers to define collection members in XAML. Instead, you create child elements in markup. The child elements are either child elements of <xref:System.Windows.ResourceDictionary>, or of a property element where the property type is `ResourceDictionary`. For details, see the XAML usage sections in <xref:System.Windows.ResourceDictionary>.  
   
  ]]></format>
         </remarks>
@@ -665,7 +665,7 @@ The invalidations happen when an implicit data template resource changes.</summa
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Dictionaries are merged by adding a <xref:System.Windows.ResourceDictionary> to the generic collection referenced by <xref:System.Windows.ResourceDictionary.MergedDictionaries%2A>. A merged <xref:System.Windows.ResourceDictionary> does not have resource elements defined within it in markup. Instead, the merged dictionary is a <xref:System.Windows.ResourceDictionary> with no markup child elements defined (or with no elements added through code), but with a URI specified for <xref:System.Windows.ResourceDictionary.Source%2A>. The <xref:System.Windows.ResourceDictionary.Source%2A> designation enables the merged dictionary to come from an external source, such as a separate resource assembly that ships with the application, "loose [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)]", or a specific localization or global resources assembly.  
+ Dictionaries are merged by adding a <xref:System.Windows.ResourceDictionary> to the generic collection referenced by <xref:System.Windows.ResourceDictionary.MergedDictionaries%2A>. A merged <xref:System.Windows.ResourceDictionary> does not have resource elements defined within it in markup. Instead, the merged dictionary is a <xref:System.Windows.ResourceDictionary> with no markup child elements defined (or with no elements added through code), but with a URI specified for <xref:System.Windows.ResourceDictionary.Source%2A>. The <xref:System.Windows.ResourceDictionary.Source%2A> designation enables the merged dictionary to come from an external source, such as a separate resource assembly that ships with the application, "loose XAML", or a specific localization or global resources assembly.  
   
  Specifying resource elements within a <xref:System.Windows.ResourceDictionary> that has <xref:System.Windows.ResourceDictionary.Source%2A> specified is not supported.  
   
@@ -846,7 +846,7 @@ The invalidations happen when an implicit data template resource changes.</summa
 ## Remarks  
  Typically, <xref:System.Windows.ResourceDictionary.Source%2A> is specified as a Pack URI, which references the location of a resource dictionary that is included as a noncompiled Resource or Content build action by your application building project. For details on the Pack URI format, see [Pack URIs in WPF](/dotnet/framework/wpf/app-development/pack-uris-in-wpf).  
   
- Generally, the <xref:System.Windows.ResourceDictionary.Source%2A> property is set only for a <xref:System.Windows.ResourceDictionary> that is specified for the <xref:System.Windows.ResourceDictionary.MergedDictionaries%2A> property (either as a property element in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], or as a <xref:System.Windows.ResourceDictionary> item of the collection in code). In this context, setting the value for <xref:System.Windows.ResourceDictionary.Source%2A> will merge the dictionary contents found at the supplied URI into the current <xref:System.Windows.ResourceDictionary>. Any load failures will cause an exception to be thrown.  
+ Generally, the <xref:System.Windows.ResourceDictionary.Source%2A> property is set only for a <xref:System.Windows.ResourceDictionary> that is specified for the <xref:System.Windows.ResourceDictionary.MergedDictionaries%2A> property (either as a property element in XAML, or as a <xref:System.Windows.ResourceDictionary> item of the collection in code). In this context, setting the value for <xref:System.Windows.ResourceDictionary.Source%2A> will merge the dictionary contents found at the supplied URI into the current <xref:System.Windows.ResourceDictionary>. Any load failures will cause an exception to be thrown.  
   
    
   
diff --git a/xml/System.Windows/StaticResourceExtension.xml b/xml/System.Windows/StaticResourceExtension.xml
index e9388bec08f..91c2372d4d8 100644
--- a/xml/System.Windows/StaticResourceExtension.xml
+++ b/xml/System.Windows/StaticResourceExtension.xml
@@ -182,7 +182,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage information, see [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension).  
+ For XAML usage information, see [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/Style.xml b/xml/System.Windows/Style.xml
index f85e1b71a87..532b28fd877 100644
--- a/xml/System.Windows/Style.xml
+++ b/xml/System.Windows/Style.xml
@@ -52,7 +52,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can set a <xref:System.Windows.Style> on any element that derives from <xref:System.Windows.FrameworkElement> or <xref:System.Windows.FrameworkContentElement>. A style is most commonly declared as a resource inside the <xref:System.Windows.Application.Resources%2A> section. Because styles are resources, they obey the same scoping rules that apply to all resources, so where you declare a style affects where it can be applied. If, for instance, you declare the style in the root element of your application definition [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file, the style can be used anywhere in your application. If you are creating a navigation application and declare the style in one of the application's [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] files, the style can be used only in that [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] file. For more information on scoping rules for resources, see [XAML Resources](/dotnet/framework/wpf/advanced/xaml-resources).  
+ You can set a <xref:System.Windows.Style> on any element that derives from <xref:System.Windows.FrameworkElement> or <xref:System.Windows.FrameworkContentElement>. A style is most commonly declared as a resource inside the <xref:System.Windows.Application.Resources%2A> section. Because styles are resources, they obey the same scoping rules that apply to all resources, so where you declare a style affects where it can be applied. If, for instance, you declare the style in the root element of your application definition XAML file, the style can be used anywhere in your application. If you are creating a navigation application and declare the style in one of the application's XAML files, the style can be used only in that XAML file. For more information on scoping rules for resources, see [XAML Resources](/dotnet/framework/wpf/advanced/xaml-resources).  
   
  The style declaration consists of a <xref:System.Windows.Style> object that contains a collection of one or more <xref:System.Windows.Setter> objects. Each <xref:System.Windows.Setter> consists of a <xref:System.Windows.Setter.Property%2A> and a <xref:System.Windows.Setter.Value%2A>. The property is the name of the property of the element the style is to apply to. After the style is declared as a resource, it can then be referenced just like any other resource.  
   
@@ -394,7 +394,7 @@
 <a name="xamlValues_Resources"></a>   
 ## XAML Values  
  *oneOrMoreResourceElements*  
- One or more resource elements. To be referenced later in either [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) or [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) syntax in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], a resource element must have an `x:Key` attribute.  
+ One or more resource elements. To be referenced later in either [StaticResource Markup Extension](/dotnet/framework/wpf/advanced/staticresource-markup-extension) or [DynamicResource Markup Extension](/dotnet/framework/wpf/advanced/dynamicresource-markup-extension) syntax in XAML, a resource element must have an `x:Key` attribute.  
   
  \<ResourceDictionary Source=" *externalDictionarySource*"/>  
  An external dictionary source. For details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
diff --git a/xml/System.Windows/StyleTypedPropertyAttribute.xml b/xml/System.Windows/StyleTypedPropertyAttribute.xml
index 4110bee13b7..e86731c0f03 100644
--- a/xml/System.Windows/StyleTypedPropertyAttribute.xml
+++ b/xml/System.Windows/StyleTypedPropertyAttribute.xml
@@ -33,7 +33,7 @@
   
 <a name="xamlTextUsage_StyleTypedPropertyAttribute"></a>   
 ## XAML Text Usage  
- You cannot use this class or its properties in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this class or its properties in XAML.  
   
  ]]></format>
     </remarks>
@@ -103,7 +103,7 @@
   
 <a name="xamlTextUsage_Property"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this property in XAML.  
   
  ]]></format>
         </remarks>
@@ -146,7 +146,7 @@
   
 <a name="xamlTextUsage_StyleTargetType"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this property in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/SystemColors.xml b/xml/System.Windows/SystemColors.xml
index 6f19785ace3..fb410111da5 100644
--- a/xml/System.Windows/SystemColors.xml
+++ b/xml/System.Windows/SystemColors.xml
@@ -24,7 +24,7 @@
   
 <a name="xamlTextUsage_SystemColors"></a>   
 ## XAML Text Usage  
- You cannot declare this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], but you can use its static properties to assign values in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot declare this managed class in XAML, but you can use its static properties to assign values in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/TemplateBindingExpression.xml b/xml/System.Windows/TemplateBindingExpression.xml
index 3bb3b0795e8..d1abf382989 100644
--- a/xml/System.Windows/TemplateBindingExpression.xml
+++ b/xml/System.Windows/TemplateBindingExpression.xml
@@ -31,7 +31,7 @@
   
 <a name="xamlTextUsage_TemplateBindingExpression"></a>   
 ## XAML Text Usage  
- You cannot use this managed class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this managed class in XAML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/TemplateBindingExtension.xml b/xml/System.Windows/TemplateBindingExtension.xml
index 645b033c2a9..298acfa0726 100644
--- a/xml/System.Windows/TemplateBindingExtension.xml
+++ b/xml/System.Windows/TemplateBindingExtension.xml
@@ -35,7 +35,7 @@
   
 <a name="xamlTextUsage_TemplateBindingExtension"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
    
   
@@ -147,7 +147,7 @@
   
 <a name="xamlTextUsage_Converter"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
  ]]></format>
         </remarks>
@@ -194,7 +194,7 @@
   
 <a name="xamlTextUsage_ConverterParameter"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
  ]]></format>
         </remarks>
@@ -238,7 +238,7 @@
   
 <a name="xamlTextUsage_Property"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
+ For XAML information, see [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/TemplatePartAttribute.xml b/xml/System.Windows/TemplatePartAttribute.xml
index 29cb09fd430..1da621b8aa8 100644
--- a/xml/System.Windows/TemplatePartAttribute.xml
+++ b/xml/System.Windows/TemplatePartAttribute.xml
@@ -35,7 +35,7 @@
   
 <a name="xamlTextUsage_TemplatePartAttribute"></a>   
 ## XAML Text Usage  
- You cannot use this class or its properties in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this class or its properties in XAML.  
   
  ]]></format>
     </remarks>
@@ -104,7 +104,7 @@
   
 <a name="xamlTextUsage_Name"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this property in XAML.  
   
  ]]></format>
         </remarks>
@@ -147,7 +147,7 @@
   
 <a name="xamlTextUsage_Type"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this property in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/ThemeDictionaryExtension.xml b/xml/System.Windows/ThemeDictionaryExtension.xml
index 046cc37183c..d37a50032cf 100644
--- a/xml/System.Windows/ThemeDictionaryExtension.xml
+++ b/xml/System.Windows/ThemeDictionaryExtension.xml
@@ -27,11 +27,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension) usage from [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ This class is a markup extension implementation. Markup extension classes exist mainly to provide infrastructure support for some aspect of the WPF XAML processor implementation, and the members exposed by a markup extension are not typically called from user code. This extension supports the [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension) usage from XAML.  
   
 <a name="xamlTextUsage_ThemeDictionaryExtension"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension).  
+ For XAML information, see [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension).  
   
  ]]></format>
     </remarks>
@@ -131,7 +131,7 @@
   
 <a name="xamlTextUsage_AssemblyName"></a>   
 ## XAML Text Usage  
- For [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] information, see [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension).  
+ For XAML information, see [ThemeDictionary Markup Extension](/dotnet/framework/wpf/advanced/themedictionary-markup-extension).  
   
  ]]></format>
         </remarks>
@@ -165,7 +165,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports WPF [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation, and is not intended to be called directly. The [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] processor implementation uses this method for proper handling of `ThemeResourceDictionary` extension values during object creation.  
+ This method supports WPF XAML processor implementation, and is not intended to be called directly. The XAML processor implementation uses this method for proper handling of `ThemeResourceDictionary` extension values during object creation.  
   
  This implementation relies on services based on the passed `serviceProvider`. It must not be `null`. The `serviceProvider` object is expected to implement <xref:System.Windows.Markup.IXamlTypeResolver>.  
   
diff --git a/xml/System.Windows/Thickness.xml b/xml/System.Windows/Thickness.xml
index a640d1286ec..3c095a58b7e 100644
--- a/xml/System.Windows/Thickness.xml
+++ b/xml/System.Windows/Thickness.xml
@@ -82,7 +82,7 @@
  `pt` is points; 1pt==(96/72) px  
   
 > [!NOTE]
->  Values need not include the decimal point explicitly when specified as a string. The string "1" provided in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] evaluates to a value of 1.0 when referenced in code.  
+>  Values need not include the decimal point explicitly when specified as a string. The string "1" provided in XAML evaluates to a value of 1.0 when referenced in code.  
   
    
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 7c316e9f264..2ae25b1ce24 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -866,9 +866,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Effects.BitmapEffect> is an abstract type, therefore the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] usage requires an implemented derived class of <xref:System.Windows.Media.Effects.BitmapEffect>, such as <xref:System.Windows.Media.Effects.OuterGlowBitmapEffect>. Note that one implemented derived class is a collection type that allows you to specify more than one sequential <xref:System.Windows.Media.Effects.BitmapEffect>, using a nested tag syntax.  
+ <xref:System.Windows.Media.Effects.BitmapEffect> is an abstract type, therefore the XAML usage requires an implemented derived class of <xref:System.Windows.Media.Effects.BitmapEffect>, such as <xref:System.Windows.Media.Effects.OuterGlowBitmapEffect>. Note that one implemented derived class is a collection type that allows you to specify more than one sequential <xref:System.Windows.Media.Effects.BitmapEffect>, using a nested tag syntax.  
   
- No existing derived class of <xref:System.Windows.Media.Effects.BitmapEffect> supports a type converter, so the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax that you use for this property is generally property element syntax.  
+ No existing derived class of <xref:System.Windows.Media.Effects.BitmapEffect> supports a type converter, so the XAML syntax that you use for this property is generally property element syntax.  
   
 <a name="dependencyPropertyInfo_BitmapEffect"></a>   
 ## Dependency Property Information  
@@ -1378,11 +1378,11 @@ Image with an Elliptical Clip Region
    
   
 ## Examples  
- The following example adds a <xref:System.Windows.Input.CommandBinding> to a window using markup. Note that in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)], the <xref:System.Windows.Input.CommandBindingCollection> is not declared in the markup as an element; the collection object is inferred by the type that the property takes, and you populate the property element with one or more <xref:System.Windows.Input.CommandBinding> elements:  
+ The following example adds a <xref:System.Windows.Input.CommandBinding> to a window using markup. Note that in XAML, the <xref:System.Windows.Input.CommandBindingCollection> is not declared in the markup as an element; the collection object is inferred by the type that the property takes, and you populate the property element with one or more <xref:System.Windows.Input.CommandBinding> elements:  
   
  [!code-xaml[commandWithHandler#CommandHandlerCommandBinding](~/samples/snippets/csharp/VS_Snippets_Wpf/commandWithHandler/CSharp/Window1.xaml#commandhandlercommandbinding)]  
   
- For more information about the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax for collections, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail).  
+ For more information about the XAML syntax for collections, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail).  
   
  The following example does essentially the same thing in code:  
   
@@ -2764,7 +2764,7 @@ Image with an Elliptical Clip Region
   
  [!code-xaml[CommandingOverviewSnippets#CommandingOverviewXAMLKeyBinding](~/samples/snippets/csharp/VS_Snippets_Wpf/CommandingOverviewSnippets/CSharp/Window1.xaml#commandingoverviewxamlkeybinding)]  
   
- For more information about the [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] syntax for collections, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail).  
+ For more information about the XAML syntax for collections, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail).  
   
  ]]></format>
         </remarks>
@@ -12913,7 +12913,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
   
 > [!IMPORTANT]
->  Do not attempt to set this property, either in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] or in code, if using the WPF framework-level layout system. Nearly all typical application scenarios will use this layout system. The layout system will not respect sizes set in the <xref:System.Windows.UIElement.RenderSize%2A> property directly. The <xref:System.Windows.UIElement.RenderSize%2A> property is declared writable only to enable certain WPF core-level bridging cases that deliberately circumvent the typical layout protocols, such as support for the <xref:System.Windows.Documents.Adorner> class.  
+>  Do not attempt to set this property, either in XAML or in code, if using the WPF framework-level layout system. Nearly all typical application scenarios will use this layout system. The layout system will not respect sizes set in the <xref:System.Windows.UIElement.RenderSize%2A> property directly. The <xref:System.Windows.UIElement.RenderSize%2A> property is declared writable only to enable certain WPF core-level bridging cases that deliberately circumvent the typical layout protocols, such as support for the <xref:System.Windows.Documents.Adorner> class.  
   
  This property can be used for checking the applicable render size within layout system overrides such as <xref:System.Windows.UIElement.OnRender%2A> or <xref:System.Windows.UIElement.GetLayoutClip%2A>.  
   
diff --git a/xml/System.Windows/VisualStateManager.xml b/xml/System.Windows/VisualStateManager.xml
index 5fa327b1547..852831818d6 100644
--- a/xml/System.Windows/VisualStateManager.xml
+++ b/xml/System.Windows/VisualStateManager.xml
@@ -209,7 +209,7 @@
    
   
 ## Examples  
- The following example creates an application that prompts the user to guess a number between 1 and 100.  When the user enters a number, the application indicates whether the guess is too high, too low, or correct.  The following [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)] creates the user interface for the application and defines 4 states: `TooLow`, `TooHigh`, `Correct`, and `Guessing`. When the application begins, it is in the `Guessing` state. .  
+ The following example creates an application that prompts the user to guess a number between 1 and 100.  When the user enters a number, the application indicates whether the guess is too high, too low, or correct.  The following XAML creates the user interface for the application and defines 4 states: `TooLow`, `TooHigh`, `Correct`, and `Guessing`. When the application begins, it is in the `Guessing` state. .  
   
  [!code-xaml[VSMGoToElementState#GoToElementStateXaml](~/samples/snippets/csharp/VS_Snippets_Wpf/vsmgotoelementstate/csharp/mainwindow.xaml#gotoelementstatexaml)]  
   
diff --git a/xml/System.Windows/WeakEventManager+ListenerList.xml b/xml/System.Windows/WeakEventManager+ListenerList.xml
index 97beab3c505..197edc22b38 100644
--- a/xml/System.Windows/WeakEventManager+ListenerList.xml
+++ b/xml/System.Windows/WeakEventManager+ListenerList.xml
@@ -32,7 +32,7 @@
   
 <a name="xamlTextUsage_ListenerList"></a>   
 ## XAML Text Usage  
- You cannot use this class in [!INCLUDE[TLA2#tla_xaml](~/includes/tla2sharptla-xaml-md.md)].  
+ You cannot use this class in XAML.  
   
  ]]></format>
     </remarks>

From 8fbf0f9bdddfd32d11fc9e38e7b527cd85f7402f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:43:11 -0800
Subject: [PATCH 095/236] tla2sharptla-xbap

---
 xml/System.Windows.Controls/Page.xml                | 2 +-
 xml/System.Windows.Controls/WebBrowser.xml          | 2 +-
 xml/System.Windows.Documents/Hyperlink.xml          | 2 +-
 xml/System.Windows.Navigation/JournalEntry.xml      | 4 ++--
 xml/System.Windows.Navigation/NavigationService.xml | 4 ++--
 xml/System.Windows.Navigation/NavigationWindow.xml  | 2 +-
 xml/System.Windows/Application.xml                  | 6 +++---
 7 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index a2180c4bc22..f77bcb47748 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -62,7 +62,7 @@
   
 -   Set as the <xref:System.Windows.Application.StartupUri%2A> in a standalone application.  
   
--   Set as the <xref:System.Windows.Application.StartupUri%2A> in an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)].  
+-   Set as the <xref:System.Windows.Application.StartupUri%2A> in an XBAP.  
   
  An application typically has two or more pages, which can be navigated between using the following mechanisms:  
   
diff --git a/xml/System.Windows.Controls/WebBrowser.xml b/xml/System.Windows.Controls/WebBrowser.xml
index 75b32ea3736..bcf50da2cc2 100644
--- a/xml/System.Windows.Controls/WebBrowser.xml
+++ b/xml/System.Windows.Controls/WebBrowser.xml
@@ -45,7 +45,7 @@
   
 -   When <xref:System.Windows.Controls.WebBrowser> is hosted by a full-trust WPF application (a stand-alone application, for example), <xref:System.Windows.Controls.WebBrowser> can host HTML documents from any location.  
   
--   When <xref:System.Windows.Controls.WebBrowser> is hosted by a partial-trust WPF application (an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], for example), <xref:System.Windows.Controls.WebBrowser> can only host documents that are **Site Of Origin** application data files. For more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files).  
+-   When <xref:System.Windows.Controls.WebBrowser> is hosted by a partial-trust WPF application (an XBAP, for example), <xref:System.Windows.Controls.WebBrowser> can only host documents that are **Site Of Origin** application data files. For more information, see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files).  
   
 > [!CAUTION]
 >  The <xref:System.Windows.Controls.WebBrowser> control internally instantiates the native WebBrowser ActiveX control. WPF enables security features by applying feature controls to the WebBrowser ActiveX control. The feature controls that are applied differ for XBAPs and stand-alone applications. Some applications should apply additional feature controls to prevent malicious content from running. For more information, see the "WebBrowser Control and Feature Controls" section in [Security (WPF)](/dotnet/framework/wpf/security-wpf) and [WebBrowser Control Overviews and Tutorials](https://go.microsoft.com/fwlink/?LinkId=179388).  
diff --git a/xml/System.Windows.Documents/Hyperlink.xml b/xml/System.Windows.Documents/Hyperlink.xml
index 2b1c342e7d6..2741db92aaa 100644
--- a/xml/System.Windows.Documents/Hyperlink.xml
+++ b/xml/System.Windows.Documents/Hyperlink.xml
@@ -609,7 +609,7 @@
 ## Remarks  
  To link to a particular inline element, specify the element name preceded by a pound symbol (#).  
   
- When a user hovers the mouse over a <xref:System.Windows.Documents.Hyperlink> in an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], the URI stored in the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property is displayed in the status bar. <xref:System.Windows.Documents.Hyperlink> navigates to this URI when the user clicks the <xref:System.Windows.Documents.Hyperlink>. If the value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property changes after the user clicks the <xref:System.Windows.Documents.Hyperlink> and before the subsequent navigation request, <xref:System.Windows.Documents.Hyperlink> ignores the new value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property and navigates to the URI that was the value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property when the user clicked the <xref:System.Windows.Documents.Hyperlink>.  
+ When a user hovers the mouse over a <xref:System.Windows.Documents.Hyperlink> in an XBAP, the URI stored in the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property is displayed in the status bar. <xref:System.Windows.Documents.Hyperlink> navigates to this URI when the user clicks the <xref:System.Windows.Documents.Hyperlink>. If the value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property changes after the user clicks the <xref:System.Windows.Documents.Hyperlink> and before the subsequent navigation request, <xref:System.Windows.Documents.Hyperlink> ignores the new value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property and navigates to the URI that was the value of the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property when the user clicked the <xref:System.Windows.Documents.Hyperlink>.  
   
 > [!NOTE]
 >  You are not restricted to only using a <xref:System.Windows.Documents.Hyperlink> to do navigation. You can use the <xref:System.Windows.Documents.FixedPage.NavigateUri%2A> attached property as well, but only from the following: <xref:System.Windows.Documents.FixedPage>, <xref:System.Windows.Shapes.Path>, <xref:System.Windows.Controls.Canvas>, and <xref:System.Windows.Documents.Glyphs>.  
diff --git a/xml/System.Windows.Navigation/JournalEntry.xml b/xml/System.Windows.Navigation/JournalEntry.xml
index 47bc66acbb4..ee4890b6979 100644
--- a/xml/System.Windows.Navigation/JournalEntry.xml
+++ b/xml/System.Windows.Navigation/JournalEntry.xml
@@ -40,13 +40,13 @@
   
 -   The `GoForward` method is called (<xref:System.Windows.Navigation.NavigationService.GoForward%2A?displayProperty=nameWithType>, <xref:System.Windows.Navigation.NavigationWindow.GoForward%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.GoForward%2A?displayProperty=nameWithType>).  
   
--   The forward button on the navigation UI that is displayed from the current navigator ([!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
+-   The forward button on the navigation UI that is displayed from the current navigator (XBAP, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
  Likewise, an entry for the current item is added to forward navigation history before a back navigation occurs, which happens when:  
   
 -   The `GoBack` method is called (<xref:System.Windows.Navigation.NavigationService.GoBack%2A?displayProperty=nameWithType>, <xref:System.Windows.Navigation.NavigationWindow.GoBack%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.GoBack%2A?displayProperty=nameWithType>).  
   
--   The back button on the navigation UI that is displayed from the current navigator ([!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
+-   The back button on the navigation UI that is displayed from the current navigator (XBAP, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>).  
   
  Each entry in back and forward navigation history is an instance of the <xref:System.Windows.Navigation.JournalEntry> class.  
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 56c8f299eeb..ff991b4016f 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -73,9 +73,9 @@
   
  <xref:System.Windows.Navigation.NavigationService> is a `sealed` class and therefore cannot be instantiated; instead, <xref:System.Windows.Navigation.NavigationService> is used by navigators to enable navigation. In WPF, there are two navigators: <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame>.  
   
- Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. Physically, however, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7 in the following ways:  
+ Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. Physically, however, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7 in the following ways:  
   
--   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] the relevant navigation history entries are also added to Internet Explorer 7 navigation history.  
+-   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an XBAP the relevant navigation history entries are also added to Internet Explorer 7 navigation history.  
   
 -   When entries in the Internet Explorer 7 navigation UI are selected, Internet Explorer 7 causes <xref:System.Windows.Navigation.NavigationService> to navigate back or forwards to the content that is associated with those entries.  
   
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index 997f16fbad3..1fc30d5afd2 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -96,7 +96,7 @@
   
  Using <xref:System.Windows.Navigation.NavigationWindow.AddBackEntry%2A>, you can also remember multiple sets of state for a single page instance.  
   
- <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. However, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7.  
+ <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. However, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7.  
   
  **Content Model:**  <xref:System.Windows.Navigation.NavigationWindow> is a <xref:System.Windows.Controls.ContentControl>, which means that <xref:System.Windows.Navigation.NavigationWindow> can contain content such as text, images, or panels. Also, <xref:System.Windows.Navigation.NavigationWindow> is a root element and, consequently, cannot be part of another element's content. For more information about the content model for <xref:System.Windows.Controls.Button>, see [WPF Content Model](/dotnet/framework/wpf/controls/wpf-content-model).  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 89bf76198c7..17f0fc7ae11 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -356,9 +356,9 @@
   
  For [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)], <xref:System.Windows.Application.Exit> is raised in the following circumstances:  
   
--   An [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] is navigated away from.  
+-   An XBAP is navigated away from.  
   
--   In Internet Explorer 7, when the tab that is hosting the [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)] is closed.  
+-   In Internet Explorer 7, when the tab that is hosting the XBAP is closed.  
   
 -   When the browser is closed.  
   
@@ -1768,7 +1768,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
  An application stops running when <xref:System.Windows.Application.Shutdown%2A> is called; the value of the <xref:System.Windows.Application.ShutdownMode%2A> property determines when <xref:System.Windows.Application.Shutdown%2A> is called, and whether it happens automatically or you need to explicitly call it.  
   
- <xref:System.Windows.Application.Run%2A> can be called only from the thread that creates the <xref:System.Windows.Application> object. Also, <xref:System.Windows.Application.Run%2A> cannot be called from a [!INCLUDE[TLA2#tla_xbap](~/includes/tla2sharptla-xbap-md.md)].  
+ <xref:System.Windows.Application.Run%2A> can be called only from the thread that creates the <xref:System.Windows.Application> object. Also, <xref:System.Windows.Application.Run%2A> cannot be called from a XBAP.  
   
    
   

From 369afe1aab129133e3d29a397c918900e1f50e67 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:43:40 -0800
Subject: [PATCH 096/236] tla2sharptla-xbapsharpplural

---
 xml/System.Windows.Controls/DataGridHyperlinkColumn.xml | 2 +-
 xml/System.Windows.Navigation/NavigationService.xml     | 2 +-
 xml/System.Windows.Navigation/NavigationWindow.xml      | 2 +-
 xml/System.Windows/Application.xml                      | 2 +-
 xml/System.Windows/Window.xml                           | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml b/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
index 458be19a2c3..589593d7207 100644
--- a/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
+++ b/xml/System.Windows.Controls/DataGridHyperlinkColumn.xml
@@ -26,7 +26,7 @@
  ![DataGridHyperlinkColumn with email addresses](~/add/media/wpf-hyperlinkcolumn.png "DataGridHyperlinkColumn with email addresses")  
   
 > [!NOTE]
->  <xref:System.Windows.Documents.Hyperlink> navigation can only occur if either the direct or indirect parent of a <xref:System.Windows.Documents.Hyperlink> is a navigation host. Examples of navigation hosts include <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or any browser that can host [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)], such as Microsoft Internet Explorer 6 or later and Firefox 2.0 or later. For more information, see the "Navigation Hosts" topic in [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
+>  <xref:System.Windows.Documents.Hyperlink> navigation can only occur if either the direct or indirect parent of a <xref:System.Windows.Documents.Hyperlink> is a navigation host. Examples of navigation hosts include <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or any browser that can host XBAPs, such as Microsoft Internet Explorer 6 or later and Firefox 2.0 or later. For more information, see the "Navigation Hosts" topic in [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
   
  To populate the column, bind the column to the <xref:System.Uri> data by using the <xref:System.Windows.Controls.DataGridBoundColumn.Binding%2A> property. To display hyperlink text that is different than the URI string, bind the text value to the <xref:System.Windows.Controls.DataGridHyperlinkColumn.ContentBinding%2A> property. The <xref:System.Windows.Controls.DataGridBoundColumn.Binding%2A> property is applied to the <xref:System.Windows.Documents.Hyperlink> or <xref:System.Windows.Controls.TextBox> element created in the column. The <xref:System.Windows.FrameworkElement.DataContext%2A> for the element in each cell is the data item for the row the cell is in. Therefore, to set up the binding you only have to set the <xref:System.Windows.Data.Binding.Path%2A?displayProperty=nameWithType>. Optionally, you can specify a <xref:System.Windows.Data.Binding.Converter%2A?displayProperty=nameWithType> if you want to convert the data. For more information about data binding, see [Data Binding (WPF)](/dotnet/framework/wpf/data/data-binding-wpf).  
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index ff991b4016f..539a8428b29 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -73,7 +73,7 @@
   
  <xref:System.Windows.Navigation.NavigationService> is a `sealed` class and therefore cannot be instantiated; instead, <xref:System.Windows.Navigation.NavigationService> is used by navigators to enable navigation. In WPF, there are two navigators: <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame>.  
   
- Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. Physically, however, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7 in the following ways:  
+ Visually, XBAPs use Internet Explorer 7 as a navigator, to provide an integrated user experience. Physically, however, XBAPs actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7 in the following ways:  
   
 -   When content is navigated to by calling <xref:System.Windows.Navigation.NavigationService.Navigate%2A>, <xref:System.Windows.Navigation.NavigationService.GoBack%2A>, and <xref:System.Windows.Navigation.NavigationService.GoForward%2A> from within an XBAP the relevant navigation history entries are also added to Internet Explorer 7 navigation history.  
   
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index 1fc30d5afd2..663aee26997 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -96,7 +96,7 @@
   
  Using <xref:System.Windows.Navigation.NavigationWindow.AddBackEntry%2A>, you can also remember multiple sets of state for a single page instance.  
   
- <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] use Internet Explorer 7 as a navigator, to provide an integrated user experience. However, [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7.  
+ <xref:System.Windows.Navigation.NavigationWindow> is one of two navigators in WPF, the other being <xref:System.Windows.Controls.Frame>. Essentially, navigator is a class supports navigation and navigation history. Visually, XBAPs use Internet Explorer 7 as a navigator, to provide an integrated user experience. However, XBAPs actually use <xref:System.Windows.Navigation.NavigationWindow> as the navigator; the <xref:System.Windows.Application.MainWindow%2A> property of an XBAP running in Internet Explorer 7 will return a reference to the <xref:System.Windows.Navigation.NavigationWindow>, and the navigation history that is managed by the <xref:System.Windows.Navigation.NavigationWindow> is integrated with the navigation history that is managed by Internet Explorer 7.  
   
  **Content Model:**  <xref:System.Windows.Navigation.NavigationWindow> is a <xref:System.Windows.Controls.ContentControl>, which means that <xref:System.Windows.Navigation.NavigationWindow> can contain content such as text, images, or panels. Also, <xref:System.Windows.Navigation.NavigationWindow> is a root element and, consequently, cannot be part of another element's content. For more information about the content model for <xref:System.Windows.Controls.Button>, see [WPF Content Model](/dotnet/framework/wpf/controls/wpf-content-model).  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 17f0fc7ae11..e130ba9d9d8 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -354,7 +354,7 @@
   
  The exit code can be set from an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)], although the value is ignored.  
   
- For [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)], <xref:System.Windows.Application.Exit> is raised in the following circumstances:  
+ For XBAPs, <xref:System.Windows.Application.Exit> is raised in the following circumstances:  
   
 -   An XBAP is navigated away from.  
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index c93ab949af5..1e3e8f23271 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -65,7 +65,7 @@
   
 -   [!INCLUDE[TLA#tla_clickonce](~/includes/tlasharptla-clickonce-md.md)]-deployed standalone applications will request permission elevation when launched from either the Internet or Local Intranet zones.  
   
--   [!INCLUDE[TLA2#tla_xbap#plural](~/includes/tla2sharptla-xbapsharpplural-md.md)] that request anything less than full permissions will not be able to instantiate windows or dialog boxes.  
+-   XBAPs that request anything less than full permissions will not be able to instantiate windows or dialog boxes.  
   
  For information about standalone application deployment and security considerations, see [WPF Security Strategy - Platform Security](/dotnet/framework/wpf/wpf-security-strategy-platform-security).  
   

From b684489dbbb3c6e8329f43df19dd45c3c532106e Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:44:59 -0800
Subject: [PATCH 097/236] tla2sharptla-xml

---
 xml/System.ComponentModel/SortDescription.xml |  2 +-
 xml/System.Windows.Data/Binding.xml           |  8 ++---
 xml/System.Windows.Data/XmlDataProvider.xml   | 32 +++++++++----------
 .../XmlNamespaceMappingCollection.xml         |  2 +-
 .../IXpsFixedPageWriter.xml                   |  4 +--
 xml/System.Windows/FrameworkElement.xml       |  2 +-
 .../HierarchicalDataTemplate.xml              |  2 +-
 xml/System.Windows/TemplateKey.xml            |  2 +-
 8 files changed, 27 insertions(+), 27 deletions(-)

diff --git a/xml/System.ComponentModel/SortDescription.xml b/xml/System.ComponentModel/SortDescription.xml
index d6674d8e35c..e3d1ec88d85 100644
--- a/xml/System.ComponentModel/SortDescription.xml
+++ b/xml/System.ComponentModel/SortDescription.xml
@@ -253,7 +253,7 @@
 ## Remarks  
  This property should be a public property of the items in the underlying collection.  
   
- The string is interpreted by the particular <xref:System.ComponentModel.ICollectionView> object involved in the sorting. <xref:System.Windows.Data.BindingListCollectionView> only supports simple column names. <xref:System.Windows.Data.ListCollectionView> supports general property paths and `XPath` for [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data. Therefore, when the view is a <xref:System.Windows.Data.ListCollectionView> object, you can sort [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] nodes in an <xref:System.Windows.Data.XmlDataProvider> based on an attribute of those nodes. For example, if the attribute name is `Cost`, you would specify "@Cost" for the <xref:System.ComponentModel.SortDescription.PropertyName%2A> in the <xref:System.ComponentModel.SortDescription>.  
+ The string is interpreted by the particular <xref:System.ComponentModel.ICollectionView> object involved in the sorting. <xref:System.Windows.Data.BindingListCollectionView> only supports simple column names. <xref:System.Windows.Data.ListCollectionView> supports general property paths and `XPath` for [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data. Therefore, when the view is a <xref:System.Windows.Data.ListCollectionView> object, you can sort XML nodes in an <xref:System.Windows.Data.XmlDataProvider> based on an attribute of those nodes. For example, if the attribute name is `Cost`, you would specify "@Cost" for the <xref:System.ComponentModel.SortDescription.PropertyName%2A> in the <xref:System.ComponentModel.SortDescription>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 2bb518b1b31..5875fec8461 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -33,7 +33,7 @@
   
 -   The target property must be a dependency property. This also means that you cannot bind a field. Most properties of <xref:System.Windows.UIElement> objects are dependency properties and most dependency properties, except read-only ones, support data binding by default. (Only <xref:System.Windows.DependencyObject> types can define dependency properties and all <xref:System.Windows.UIElement> objects derive from <xref:System.Windows.DependencyObject>.)  
   
--   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. WPF data binding supports data in the form of CLR objects and [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data.  
+-   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. WPF data binding supports data in the form of CLR objects and XML. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your XML data.  
   
  Use the <xref:System.Windows.Data.Binding.Mode%2A> property to specify the direction of the data flow. To detect source changes in one-way or two-way bindings, the source must implement a suitable property change notification mechanism such as <xref:System.ComponentModel.INotifyPropertyChanged>. For an example, see [How to: Implement Property Change Notification](/dotnet/framework/wpf/data/how-to-implement-property-change-notification). The <xref:System.Windows.Data.Binding.UpdateSourceTrigger%2A> property specifies the timing of source updates. For more information, see "Basic Data Binding Concepts" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -495,18 +495,18 @@
       <Docs>
         <param name="target">The object from which to get namespace information.</param>
         <summary>Returns an [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] namespace manager object used by the binding attached to the specified object.</summary>
-        <returns>A returned object used for viewing [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] namespaces that relate to the binding on the passed object element. This object should be cast as <see cref="T:System.Xml.XmlNamespaceManager" />.</returns>
+        <returns>A returned object used for viewing XML namespaces that relate to the binding on the passed object element. This object should be cast as <see cref="T:System.Xml.XmlNamespaceManager" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  This method supports attached property usage for the <xref:System.Windows.Data.Binding.XmlNamespaceManager%2A> attached property.  
   
- [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] namespace managers are relevant only if the data in the binding came from an [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] binding source (<xref:System.Windows.Data.XmlDataProvider> object).  
+ XML namespace managers are relevant only if the data in the binding came from an XML binding source (<xref:System.Windows.Data.XmlDataProvider> object).  
   
  If a namespace manager was not specifically applied either in the original data source creation or by subsequently calling <xref:System.Windows.Data.Binding.SetXmlNamespaceManager%2A> on the binding, then this method will return `null`.  
   
- This method will always return `null` if the data behind the binding is not [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)].  
+ This method will always return `null` if the data behind the binding is not XML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index a07d3cfecf2..6b216798928 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -41,15 +41,15 @@
   
  <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
   
--   You can embed inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data using the <xref:System.Windows.Data.XmlDataProvider> class.  
+-   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
--   You can set the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property to the <xref:System.Uri> of an [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data file.  
+-   You can set the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property to the <xref:System.Uri> of an XML data file.  
   
 -   You can set the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property to an <xref:System.Xml.XmlDocument>.  
   
  <xref:System.Windows.Data.XmlDataProvider> performs a full refresh of all bindings when a <xref:System.Xml.XmlDocument.NodeChanged?displayProperty=nameWithType> event occurs. There are no optimizations for specific nodes.  
   
- The <xref:System.Windows.Data.XmlDataProvider.IsAsynchronous%2A?displayProperty=nameWithType> property is set to `true` by default, which means that the <xref:System.Windows.Data.XmlDataProvider> retrieves data and produces the collection of [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] nodes asynchronously by default.  
+ The <xref:System.Windows.Data.XmlDataProvider.IsAsynchronous%2A?displayProperty=nameWithType> property is set to `true` by default, which means that the <xref:System.Windows.Data.XmlDataProvider> retrieves data and produces the collection of XML nodes asynchronously by default.  
   
  ]]></format>
     </remarks>
@@ -128,7 +128,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Prepares the loading of either the inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] or the external [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file to produce a collection of [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] nodes.</summary>
+        <summary>Prepares the loading of either the inline XML or the external XML file to produce a collection of XML nodes.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -177,15 +177,15 @@
 ## Remarks  
  <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
   
--   You can embed inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data using the <xref:System.Windows.Data.XmlDataProvider> class.  
+-   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
--   You can set the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property to the <xref:System.Uri> of an [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data file.  
+-   You can set the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property to the <xref:System.Uri> of an XML data file.  
   
 -   You can set this property to an <xref:System.Xml.XmlDocument>.  
   
  <xref:System.Windows.Data.XmlDataProvider> performs a full refresh of all bindings on when a <xref:System.Xml.XmlDocument.NodeChanged?displayProperty=nameWithType> event occurs. There are no optimizations for specific nodes.  
   
- If the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is set, then any inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data is discarded. If the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property is set, then the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is cleared and any inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data is discarded.  
+ If the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is set, then any inline XML data is discarded. If the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property is set, then the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is cleared and any inline XML data is discarded.  
   
  Setting the following properties will implicitly cause this <xref:System.Windows.Data.XmlDataProvider> object to refresh: <xref:System.Windows.Data.XmlDataProvider.Source%2A>, <xref:System.Windows.Data.XmlDataProvider.Document%2A>, <xref:System.Windows.Data.XmlDataProvider.XmlNamespaceManager%2A>, and <xref:System.Windows.Data.XmlDataProvider.XPath%2A>. When changing multiple refresh-causing properties, the use of <xref:System.Windows.Data.DataSourceProvider.DeferRefresh%2A> is recommended.  
   
@@ -395,31 +395,31 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the <see cref="T:System.Uri" /> of the [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data file to use as the binding source.</summary>
-        <value>The <see cref="T:System.Uri" /> of the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data file to use as the binding source. The default value is <see langword="null" />.</value>
+        <value>The <see cref="T:System.Uri" /> of the XML data file to use as the binding source. The default value is <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
   
--   You can embed inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data using the <xref:System.Windows.Data.XmlDataProvider> class.  
+-   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
--   You can set this property to the <xref:System.Uri> of an [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data file.  
+-   You can set this property to the <xref:System.Uri> of an XML data file.  
   
 -   You can set the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property to an <xref:System.Xml.XmlDocument>.  
   
- If the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is set, then any inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data is discarded. If the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property is set, then the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is cleared and any inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data is discarded.  
+ If the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is set, then any inline XML data is discarded. If the <xref:System.Windows.Data.XmlDataProvider.Document%2A> property is set, then the <xref:System.Windows.Data.XmlDataProvider.Source%2A> property is cleared and any inline XML data is discarded.  
   
  Setting the following properties will implicitly cause this <xref:System.Windows.Data.XmlDataProvider> object to refresh: <xref:System.Windows.Data.XmlDataProvider.Source%2A>, <xref:System.Windows.Data.XmlDataProvider.Document%2A>, <xref:System.Windows.Data.XmlDataProvider.XmlNamespaceManager%2A>, and <xref:System.Windows.Data.XmlDataProvider.XPath%2A>. When changing multiple refresh-causing properties, the use of <xref:System.Windows.Data.DataSourceProvider.DeferRefresh%2A> is recommended.  
   
    
   
 ## Examples  
- In some applications, embedding the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] inline within the XAML page can be inconvenient because the exact content of the data must be known at compile time. Therefore, you can obtain the data from an external [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, as in the following example.  
+ In some applications, embedding the XML inline within the XAML page can be inconvenient because the exact content of the data must be known at compile time. Therefore, you can obtain the data from an external XML file, as in the following example.  
   
  [!code-xaml[XMLDataSource2#XmlFileExample](~/samples/snippets/csharp/VS_Snippets_Wpf/XmlDataSource2/CS/Window1.xaml#xmlfileexample)]  
   
- If the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data resides in a remote [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] file, you define access to the data by assigning an appropriate URL to the <xref:System.Windows.Data.XmlDataProvider.Source%2A> attribute as follows:  
+ If the XML data resides in a remote XML file, you define access to the data by assigning an appropriate URL to the <xref:System.Windows.Data.XmlDataProvider.Source%2A> attribute as follows:  
   
 ```  
 <XmlDataProvider x:Key="BookData" Source="http://MyUrl" XPath="Books"/>  
@@ -554,13 +554,13 @@
         <ReturnType>System.Xml.Serialization.IXmlSerializable</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] content.</summary>
-        <value>The inline [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] content.</value>
+        <summary>Gets the inline XML content.</summary>
+        <value>The inline XML content.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is used by the parser to compile the literal content of the embedded [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data island.  
+ This property is used by the parser to compile the literal content of the embedded XML data island.  
   
 <a name="xamlPropertyElementUsage_XmlSerializer"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml b/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
index 06da8c18721..db21980c4f5 100644
--- a/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
+++ b/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
@@ -43,7 +43,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Data.XmlNamespaceMapping> class provides a mapping between the namespace specified in your [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] binding source and a prefix you specify that you can use in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The <xref:System.Windows.Data.XmlNamespaceMapping> class provides a mapping between the namespace specified in your XML binding source and a prefix you specify that you can use in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
index b7f7a39863d..bbc4c1be68a 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
@@ -658,8 +658,8 @@
         <ReturnType>System.Xml.XmlWriter</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets an <see cref="T:System.Xml.XmlWriter" /> for writing [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] markup to the page.</summary>
-        <value>The <see cref="T:System.Xml.XmlWriter" /> for writing [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] markup to the page.</value>
+        <summary>Gets an <see cref="T:System.Xml.XmlWriter" /> for writing XML markup to the page.</summary>
+        <value>The <see cref="T:System.Xml.XmlWriter" /> for writing XML markup to the page.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index fb92c02b0b2..4708067d60a 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -2398,7 +2398,7 @@
   
  This dependency property inherits property values. If there are child elements without other values for <xref:System.Windows.FrameworkElement.Language%2A> established through local values or styles, the property system will set the value to be the <xref:System.Windows.FrameworkElement.Language%2A> value of the nearest ancestor element with this value assigned.  
   
- [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] defines the general meaning of the `xml:lang` attribute. <xref:System.Windows.FrameworkElement.Language%2A> essentially exposes the meaning of this attribute as a dependency property. <xref:System.Windows.FrameworkElement.Language%2A> can be adjusted programmatically, and can participate in property system value inheritance in a way that parallels how the `xml:lang` attribute can inherit to child element scope in [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)]. If you set <xref:System.Windows.FrameworkElement.Language%2A>, that value becomes the `xml:lang` and overwrites any previous value. For more information, see [xml:lang Handling in XAML](/dotnet/framework/xaml-services/xml-lang-handling-in-xaml).  
+ XML defines the general meaning of the `xml:lang` attribute. <xref:System.Windows.FrameworkElement.Language%2A> essentially exposes the meaning of this attribute as a dependency property. <xref:System.Windows.FrameworkElement.Language%2A> can be adjusted programmatically, and can participate in property system value inheritance in a way that parallels how the `xml:lang` attribute can inherit to child element scope in XML. If you set <xref:System.Windows.FrameworkElement.Language%2A>, that value becomes the `xml:lang` and overwrites any previous value. For more information, see [xml:lang Handling in XAML](/dotnet/framework/xaml-services/xml-lang-handling-in-xaml).  
   
 <a name="dependencyPropertyInfo_CultureInfo"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows/HierarchicalDataTemplate.xml b/xml/System.Windows/HierarchicalDataTemplate.xml
index 7905d45e12e..71f3eb78ecc 100644
--- a/xml/System.Windows/HierarchicalDataTemplate.xml
+++ b/xml/System.Windows/HierarchicalDataTemplate.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `dataType` parameter is either a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object or a string representing an [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] element. For more information, see [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
+ The `dataType` parameter is either a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object or a string representing an XML element. For more information, see [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/TemplateKey.xml b/xml/System.Windows/TemplateKey.xml
index e2a7d1a7e82..0dae575fb98 100644
--- a/xml/System.Windows/TemplateKey.xml
+++ b/xml/System.Windows/TemplateKey.xml
@@ -136,7 +136,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the type for which the template is designed.</summary>
-        <value>The <see cref="T:System.Type" /> that specifies the type of object that the template is used to display, or a string that specifies the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] tag name for the [!INCLUDE[TLA2#tla_xml](~/includes/tla2sharptla-xml-md.md)] data that the template is used to display.</value>
+        <value>The <see cref="T:System.Type" /> that specifies the type of object that the template is used to display, or a string that specifies the XML tag name for the XML data that the template is used to display.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

From 4cfb3bd975d65a8bc7caeb3dc09591dbf7ece57c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:46:58 -0800
Subject: [PATCH 098/236] tla2sharptla-xps

---
 xml/System.Printing/PrintQueue.xml            |  6 ++--
 .../FigureStructure.xml                       |  2 +-
 .../NamedElement.xml                          |  4 +--
 .../StoryFragment.xml                         |  6 ++--
 .../StoryFragments.xml                        |  4 +--
 xml/System.Windows.Documents/LinkTarget.xml   |  4 +--
 xml/System.Windows.Media/FormattedText.xml    |  4 +--
 .../IDocumentStructureProvider.xml            |  8 ++---
 .../IStoryFragmentProvider.xml                |  8 ++---
 .../IXpsFixedDocumentReader.xml               |  2 +-
 .../IXpsFixedDocumentSequenceReader.xml       |  2 +-
 .../IXpsFixedPageReader.xml                   |  8 ++---
 .../XpsDigSigPartAlteringRestrictions.xml     |  2 +-
 .../XpsDigitalSignature.xml                   |  8 ++---
 .../XpsDocument.xml                           | 12 +++----
 .../XpsResourceDictionary.xml                 |  2 +-
 .../XpsSignatureDefinition.xml                |  6 ++--
 .../FontSubsetterCommitPolicies.xml           |  2 +-
 .../XpsSerializationManager.xml               |  6 ++--
 .../XpsSerializerFactory.xml                  |  8 ++---
 xml/System.Windows.Xps/XpsDocumentWriter.xml  | 32 +++++++++----------
 ...m.Windows.Documents.DocumentStructures.xml |  8 ++---
 xml/ns-System.Windows.Xps.Packaging.xml       |  2 +-
 xml/ns-System.Windows.Xps.Serialization.xml   |  2 +-
 xml/ns-System.Windows.Xps.xml                 |  4 +--
 25 files changed, 76 insertions(+), 76 deletions(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index 19c204012b5..c07dbe47b68 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -575,7 +575,7 @@
         <param name="jobName">The name of the print job.</param>
         <param name="documentPath">The path and name of the document that is being printed.</param>
         <param name="fastCopy">
-          <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)]; otherwise, <see langword="false" />.</param>
+          <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid XPS; otherwise, <see langword="false" />.</param>
         <summary>Inserts a new print job for an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] Document into the queue, gives it the specified name, and specifies whether or not it should be validated.</summary>
         <returns>A <see cref="T:System.Printing.PrintSystemJobInfo" /> that represents the print job and its status.</returns>
         <remarks>
@@ -584,7 +584,7 @@
 ## Remarks  
  If `fastCopy` is `true`, then the printer must be an [Printing Overview](/dotnet/framework/wpf/advanced/printing-overview). If it is not, the <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> method throws an exception.  
   
- If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to [!INCLUDE[TLA#tla_com](~/includes/tlasharptla-com-md.md)]. The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
+ If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The XPS file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to [!INCLUDE[TLA#tla_com](~/includes/tlasharptla-com-md.md)]. The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
   
 -   The simplest way is to add the <xref:System.STAThreadAttribute> (that is, "`[System.STAThreadAttribute()]`") just above the first line of the application's `Main` method (usually "`static void Main(string[] args)`").  
   
@@ -643,7 +643,7 @@
         <param name="jobName">The path and name of the document that is being printed.</param>
         <param name="documentPath">The path and name of the document that is being printed.</param>
         <param name="fastCopy">
-          <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)]; otherwise, <see langword="false" />.</param>
+          <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid XPS; otherwise, <see langword="false" />.</param>
         <param name="printTicket">The settings of the print job.</param>
         <summary>Inserts a new print job for an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] Document into the queue, gives it the specified name and settings, and specifies whether or not it should be validated.</summary>
         <returns>A <see cref="T:System.Printing.PrintSystemJobInfo" /> that represents the print job and its status.</returns>
diff --git a/xml/System.Windows.Documents.DocumentStructures/FigureStructure.xml b/xml/System.Windows.Documents.DocumentStructures/FigureStructure.xml
index 681b90dbe40..e960188d25b 100644
--- a/xml/System.Windows.Documents.DocumentStructures/FigureStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/FigureStructure.xml
@@ -50,7 +50,7 @@
    
   
 ## Examples  
- The following example shows use of the <xref:System.Windows.Documents.DocumentStructures.FigureStructure> element as part of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows use of the <xref:System.Windows.Documents.DocumentStructures.FigureStructure> element as part of an XPS document.  
   
  [!code-xaml[DocumentStructure#DocStructStoryFragContent2](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage2_structure.xaml#docstructstoryfragcontent2)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml b/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
index ebad6e1dfc7..dee4ee2f8e2 100644
--- a/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
@@ -21,9 +21,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Each page of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document contains a <xref:System.Windows.Documents.FixedPage> element that defines its *content* in the form of positional text runs and graphics.  Through the use of document structure elements, pages of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document can also be associated with <xref:System.Windows.Documents.DocumentStructures.StoryFragment> elements that define the *structure* of the page in the form of sections, paragraphs, lists, figures, and tables.  The <xref:System.Windows.Documents.DocumentStructures.NamedElement> class is used to define the associations between content and structure parts of the document markup.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> is the child of a structural element, such as a table cell or bullet list item that is located in the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> hierarchy of a page.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> identifies an item in the <xref:System.Windows.Documents.FixedPage> hierarchy of the same page.  The item it refers to is the content of the structural element.  
+ Each page of an XPS document contains a <xref:System.Windows.Documents.FixedPage> element that defines its *content* in the form of positional text runs and graphics.  Through the use of document structure elements, pages of an XPS document can also be associated with <xref:System.Windows.Documents.DocumentStructures.StoryFragment> elements that define the *structure* of the page in the form of sections, paragraphs, lists, figures, and tables.  The <xref:System.Windows.Documents.DocumentStructures.NamedElement> class is used to define the associations between content and structure parts of the document markup.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> is the child of a structural element, such as a table cell or bullet list item that is located in the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> hierarchy of a page.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> identifies an item in the <xref:System.Windows.Documents.FixedPage> hierarchy of the same page.  The item it refers to is the content of the structural element.  
   
- For more information about structure elements of [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents, see Chapter 9 and Appendix E of the *XML Paper Specification (XPS)* available for download at [https://go.microsoft.com/fwlink/?LinkID=67000](https://go.microsoft.com/fwlink/?LinkID=67000).  
+ For more information about structure elements of XPS documents, see Chapter 9 and Appendix E of the *XML Paper Specification (XPS)* available for download at [https://go.microsoft.com/fwlink/?LinkID=67000](https://go.microsoft.com/fwlink/?LinkID=67000).  
   
    
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml b/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
index 09814b7506e..ac54813e56f 100644
--- a/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
@@ -43,17 +43,17 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An XPS story in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document is roughly analogous to a story in a newspaper or magazine. It is a passage of text and graphic content, usually on a single topic, within a single [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document. Typically, it spans multiple pages, but it can be shorter than a page like a sidebar - boxed story - in a magazine. A story can also be discontinuous like a front page newspaper story that is continued on page 4. Consequently, a given page can have more than one story and parts of more than one story. A header or footer is also a special kind of story that is entirely contained on a single page.  
+ An XPS story in an XPS document is roughly analogous to a story in a newspaper or magazine. It is a passage of text and graphic content, usually on a single topic, within a single XPS document. Typically, it spans multiple pages, but it can be shorter than a page like a sidebar - boxed story - in a magazine. A story can also be discontinuous like a front page newspaper story that is continued on page 4. Consequently, a given page can have more than one story and parts of more than one story. A header or footer is also a special kind of story that is entirely contained on a single page.  
   
  A <xref:System.Windows.Documents.DocumentStructures.StoryFragment> represents all or a portion of a story. It can never span more than one page, but it can occupy the whole of a page or share a page with other fragments. If a story is on more than one page, each part of it on each page is a separate fragment. Although stories can have discontinuous sets of fragments, no fragment can itself be discontinuous.  
   
  Only a <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element can be a parent of a <xref:System.Windows.Documents.DocumentStructures.StoryFragment>.  The location of the <xref:System.Windows.Documents.DocumentStructures.StoryBreak> elements within a <xref:System.Windows.Documents.DocumentStructures.StoryFragment> indicates if the story is contained in multiple fragments, and if the additional fragments either precede or follow the current fragment.  
   
- When a <xref:System.Windows.Documents.DocumentStructures.StoryFragment> ends in the middle of some structural element; say a `<TableRowGroupStructure>`, then [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document-producing applications must insert an appropriate end tag for the element (in this case `</TableRowGroupStructure>`) before the `</StoryFragment>` tag, even though the structure is being continued in a later fragment. (This is necessary to ensure that the element tree within the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> is valid XML.) The fragment that continues the story must begin with an opening tag for the interrupted structure. The entire tree of interrupted structures must be treated the same way (with one exception, discussed below): End tags must be added for every unmatched start tag above the point of interruption.  
+ When a <xref:System.Windows.Documents.DocumentStructures.StoryFragment> ends in the middle of some structural element; say a `<TableRowGroupStructure>`, then XPS document-producing applications must insert an appropriate end tag for the element (in this case `</TableRowGroupStructure>`) before the `</StoryFragment>` tag, even though the structure is being continued in a later fragment. (This is necessary to ensure that the element tree within the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> is valid XML.) The fragment that continues the story must begin with an opening tag for the interrupted structure. The entire tree of interrupted structures must be treated the same way (with one exception, discussed below): End tags must be added for every unmatched start tag above the point of interruption.  
   
  The exception applies when the story interruption comes immediately after a `</TableCellStructure>` tag, then the producing application must insert an empty table cell structure (`<TableCellStructure></TableCellStructure>`) at the corresponding point in the fragment that continues the story. This is necessary so that consuming applications that need to merge all fragments of a given story can use a simple algorithm to do this.  
   
- Assume, for example, that an application wanted to add the following material to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document:  
+ Assume, for example, that an application wanted to add the following material to an XPS document:  
   
 ```  
 <SectionStructure>  
diff --git a/xml/System.Windows.Documents.DocumentStructures/StoryFragments.xml b/xml/System.Windows.Documents.DocumentStructures/StoryFragments.xml
index 139d4e908fa..ec4dfc9bbf6 100644
--- a/xml/System.Windows.Documents.DocumentStructures/StoryFragments.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/StoryFragments.xml
@@ -47,12 +47,12 @@
   
  <xref:System.Windows.Documents.DocumentStructures.StoryFragments> is the root of one or more <xref:System.Windows.Documents.DocumentStructures.StoryFragment> elements.  
   
- For detailed information about the document structure of [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)], see Chapter 9 and Appendix E of the *XML Paper Specification (XPS)* that can be downloaded from the [Windows Hardware Developer Central](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For detailed information about the document structure of XPS, see Chapter 9 and Appendix E of the *XML Paper Specification (XPS)* that can be downloaded from the [Windows Hardware Developer Central](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
    
   
 ## Examples  
- The following example shows how to use of the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use of the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element in an XPS document.  
   
  [!code-xaml[DocumentStructure#DocStructStoryFrags1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructstoryfrags1)]  
   
diff --git a/xml/System.Windows.Documents/LinkTarget.xml b/xml/System.Windows.Documents/LinkTarget.xml
index 4085fbb484d..95a176ca600 100644
--- a/xml/System.Windows.Documents/LinkTarget.xml
+++ b/xml/System.Windows.Documents/LinkTarget.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/FormattedText.xml b/xml/System.Windows.Media/FormattedText.xml
index 8a55ac50d9d..944a71b7a59 100644
--- a/xml/System.Windows.Media/FormattedText.xml
+++ b/xml/System.Windows.Media/FormattedText.xml
@@ -26,9 +26,9 @@
  ![Text displayed using FormattedText object](~/add/media/formattedtext01.jpg "Text displayed using FormattedText object")  
 Example of a formatted text string  
   
- In terms of text features in WPF, <xref:System.Windows.Media.FormattedText> is considered "low-level" because it processes text as graphical elements. Other aspects of text in WPF handle text in the context of controls that are dedicated to text (<xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.TextBox>), implement the flow document model (see [Flow Document Overview](/dotnet/framework/wpf/advanced/flow-document-overview)), or support the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document model (see [Documents in WPF](/dotnet/framework/wpf/advanced/documents-in-wpf)).  
+ In terms of text features in WPF, <xref:System.Windows.Media.FormattedText> is considered "low-level" because it processes text as graphical elements. Other aspects of text in WPF handle text in the context of controls that are dedicated to text (<xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.TextBox>), implement the flow document model (see [Flow Document Overview](/dotnet/framework/wpf/advanced/flow-document-overview)), or support the XPS document model (see [Documents in WPF](/dotnet/framework/wpf/advanced/documents-in-wpf)).  
   
- Many of the setter methods in <xref:System.Windows.Media.FormattedText> have similarities to attached properties that are supported by <xref:System.Windows.Documents.TextElement>, but the <xref:System.Windows.Documents.TextElement> attached properties apply to the higher-level text support either for flow or [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)].  
+ Many of the setter methods in <xref:System.Windows.Media.FormattedText> have similarities to attached properties that are supported by <xref:System.Windows.Documents.TextElement>, but the <xref:System.Windows.Documents.TextElement> attached properties apply to the higher-level text support either for flow or XPS.  
   
    
   
diff --git a/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml b/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
index 8df0128c285..700e443ee31 100644
--- a/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
+++ b/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `DocumentStructure` element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `DocumentStructure` element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
@@ -43,13 +43,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Adds the <see langword="DocumentStructure" /> part of [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</summary>
-        <returns>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents the <see langword="DocumentStructure" /> part of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</returns>
+        <summary>Adds the <see langword="DocumentStructure" /> part of [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] to an XPS package.</summary>
+        <returns>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents the <see langword="DocumentStructure" /> part of an XPS package.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `DocumentStructure` element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 9 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `DocumentStructure` element of an XPS package, see chapter 9 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml b/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
index f0c2c55dfef..73ab8e25942 100644
--- a/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
+++ b/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
   
  ]]></format>
     </remarks>
@@ -43,13 +43,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Adds a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</summary>
-        <returns>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</returns>
+        <summary>Adds a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element to an XPS package.</summary>
+        <returns>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element in an XPS package.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
index 7972f931b4f..7aa4147eae0 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
@@ -224,7 +224,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, see chapter 2 in the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
index fb83a7c2362..54c451f9fb5 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
@@ -116,7 +116,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] sequence, see chapter 2 in the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] sequence, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
index 81492f5f4a6..f505667b82a 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
@@ -289,7 +289,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] page, see chapter 2 in the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] page, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
@@ -337,13 +337,13 @@
         <ReturnType>System.Windows.Xps.Packaging.XpsStructure</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> part of the markup of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</summary>
-        <value>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package.</value>
+        <summary>Gets the <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> part of the markup of an XPS package.</summary>
+        <value>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents a <see cref="T:System.Windows.Documents.DocumentStructures.StoryFragments" /> element in an XPS package.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/XpsDigSigPartAlteringRestrictions.xml b/xml/System.Windows.Xps.Packaging/XpsDigSigPartAlteringRestrictions.xml
index 7024dc3b3c1..af1cc494373 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDigSigPartAlteringRestrictions.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDigSigPartAlteringRestrictions.xml
@@ -37,7 +37,7 @@
    
   
 ## Examples  
- The following example shows how to use this enumeration to digitally sign an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this enumeration to digitally sign an XPS document.  
   
  [!code-csharp[XpsReadWriteSign#SignXpsDocument](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsReadWriteSign/CSharp/SignatureDefinitionsAndSigning.cs#signxpsdocument)]
  [!code-vb[XpsReadWriteSign#SignXpsDocument](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsReadWriteSign/visualbasic/signaturedefinitionsandsigning.vb#signxpsdocument)]  
diff --git a/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml b/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
index 26fbd8ebce5..e66d33d0c06 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDigitalSignature.xml
@@ -21,11 +21,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use <xref:System.Windows.Xps.Packaging.XpsDigitalSignature> instead of <xref:System.IO.Packaging.PackageDigitalSignature> when you work with an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  <xref:System.IO.Packaging.PackageDigitalSignature> is not [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)]-aware, and does not guarantee that all parts in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document are fully signed.  
+ Use <xref:System.Windows.Xps.Packaging.XpsDigitalSignature> instead of <xref:System.IO.Packaging.PackageDigitalSignature> when you work with an XPS document.  <xref:System.IO.Packaging.PackageDigitalSignature> is not XPS-aware, and does not guarantee that all parts in an XPS document are fully signed.  
   
  For more information about digital signatures, see the MSDN article *Digital Signing Framework of the Open Packaging Conventions* available at [https://go.microsoft.com/fwlink/?LinkId=74494](https://go.microsoft.com/fwlink/?LinkId=74494).  
   
- For more information about [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] see the *XML Paper Specification (XPS)* available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For more information about XPS see the *XML Paper Specification (XPS)* available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
  ]]></format>
     </remarks>
@@ -269,7 +269,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the document sequence reader for the signed document sequence.</summary>
-        <value>An <see cref="T:System.Windows.Xps.Packaging.IXpsFixedDocumentSequenceReader" />; or <see langword="null" /> if not all valid [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] parts have been signed in the document.</value>
+        <value>An <see cref="T:System.Windows.Xps.Packaging.IXpsFixedDocumentSequenceReader" />; or <see langword="null" /> if not all valid XPS parts have been signed in the document.</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Documents.FixedDocumentSequence" />
         <related type="ExternalDocumentation" href="https://go.microsoft.com/fwlink/?LinkId=74494">Digital Signing Framework of the Open Packaging Conventions</related>
@@ -375,7 +375,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Verifies the document digital signature against the X.509 certificate embedded in the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] <see cref="T:System.IO.Packaging.Package" />.</summary>
+        <summary>Verifies the document digital signature against the X.509 certificate embedded in the XPS <see cref="T:System.IO.Packaging.Package" />.</summary>
         <returns>One of the <see cref="T:System.IO.Packaging.VerifyResult" /> enumeration values that specify the result of the verification attempt.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Xps.Packaging/XpsDocument.xml b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
index 955d5741504..bf14b3c39f4 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDocument.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
@@ -29,15 +29,15 @@
   
  The <xref:System.Windows.Xps.Packaging.XpsDocument.%23ctor%2A> constructor is passed a reference to a <xref:System.IO.Packaging.Package> for writing, storing, and reading the content elements of the document.  
   
- A new empty [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] <xref:System.IO.Packaging.Package> is created by using the <xref:System.IO.Packaging.Package.%23ctor%2A> constructor.  
+ A new empty XPS <xref:System.IO.Packaging.Package> is created by using the <xref:System.IO.Packaging.Package.%23ctor%2A> constructor.  
   
- An existing [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] <xref:System.IO.Packaging.Package> is opened by using the <xref:System.IO.Packaging.Package.Open%2A?displayProperty=nameWithType> method.  
+ An existing XPS <xref:System.IO.Packaging.Package> is opened by using the <xref:System.IO.Packaging.Package.Open%2A?displayProperty=nameWithType> method.  
   
- A <xref:System.Windows.Documents.FixedDocumentSequence> root is added to an empty [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] <xref:System.IO.Packaging.Package> by calling the <xref:System.Windows.Xps.Packaging.XpsDocument.AddFixedDocumentSequence%2A> method.  
+ A <xref:System.Windows.Documents.FixedDocumentSequence> root is added to an empty XPS <xref:System.IO.Packaging.Package> by calling the <xref:System.Windows.Xps.Packaging.XpsDocument.AddFixedDocumentSequence%2A> method.  
   
  <xref:System.Printing.PrintTicket> elements with printer information and control can also be associated with the <xref:System.Windows.Documents.FixedDocumentSequence>, or on individual <xref:System.Windows.Documents.FixedDocument> and <xref:System.Windows.Documents.FixedPage> elements that are stored in the <xref:System.Windows.Xps.Packaging.XpsDocument>.  
   
- For more information about [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For more information about XPS see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
  ]]></format>
     </remarks>
@@ -429,7 +429,7 @@
         <ReturnType>System.IO.Packaging.PackageProperties</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the core <see cref="T:System.IO.Packaging.PackageProperties" /> of the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.</summary>
+        <summary>Gets the core <see cref="T:System.IO.Packaging.PackageProperties" /> of the XPS document.</summary>
         <value>The core properties of the <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /><see cref="T:System.IO.Packaging.Package" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -455,7 +455,7 @@
         <Parameter Name="xpsDocument" Type="System.Windows.Xps.Packaging.XpsDocument" />
       </Parameters>
       <Docs>
-        <param name="xpsDocument">The [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document to write.</param>
+        <param name="xpsDocument">The XPS document to write.</param>
         <summary>Creates an <see cref="T:System.Windows.Xps.XpsDocumentWriter" /> for writing an <see cref="T:System.Windows.Xps.Packaging.XpsDocument" />.</summary>
         <returns>The <see cref="T:System.Windows.Xps.XpsDocumentWriter" /> to use for writing the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</returns>
         <remarks>
diff --git a/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml b/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
index a1329ad16b7..c56ec92a433 100644
--- a/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class has no public constructor. Get a reference to an <xref:System.Windows.Xps.Packaging.XpsResourceDictionary> by using the <xref:System.Windows.Xps.Packaging.IXpsFixedPageWriter.AddResourceDictionary%2A?displayProperty=nameWithType> method.  
   
- For more information about the `ResourceDictionary` element of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] package, see chapter 7 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `ResourceDictionary` element of an XPS package, see chapter 7 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml b/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
index 2f5ab49d418..0936a86d11b 100644
--- a/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
@@ -21,11 +21,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about signature definitions in [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] packages, see Chapter 10 in the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For more information about signature definitions in XPS packages, see Chapter 10 in the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
  For information about <xref:System.IO.Packaging.Package> digital signatures, see the MSDN article Digital Signing Framework of the Open Packaging Conventions available at [https://go.microsoft.com/fwlink/?LinkId=74494](https://go.microsoft.com/fwlink/?LinkId=74494).  
   
- For information about [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For information about XPS see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
    
   
@@ -262,7 +262,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `SignBy` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages, see the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SignBy` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages, see the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
diff --git a/xml/System.Windows.Xps.Serialization/FontSubsetterCommitPolicies.xml b/xml/System.Windows.Xps.Serialization/FontSubsetterCommitPolicies.xml
index eddd082b40c..66697e9c594 100644
--- a/xml/System.Windows.Xps.Serialization/FontSubsetterCommitPolicies.xml
+++ b/xml/System.Windows.Xps.Serialization/FontSubsetterCommitPolicies.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When font glyphs for text in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document are saved in the document package, the document text displays identically on any computer or printer.  If glyphs are not saved in document and the required font is not installed on the local computer or printer, the rendering device must substitute glyphs from another font.  Substituting glyphs can change the appearance of the text when a different font is used.  
+ When font glyphs for text in an XPS document are saved in the document package, the document text displays identically on any computer or printer.  If glyphs are not saved in document and the required font is not installed on the local computer or printer, the rendering device must substitute glyphs from another font.  Substituting glyphs can change the appearance of the text when a different font is used.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
index e227722a27f..921bb239b76 100644
--- a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
@@ -215,7 +215,7 @@
 ## Remarks  
  The default font-subsetting policy is <xref:System.Windows.Xps.Serialization.FontSubsetterCommitPolicies.CommitEntireSequence>.  
   
- When font glyphs for text in an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document are saved in the document package, the document text displays identically on any computer or printer.  If glyphs are not saved in document and the required font is not installed on the local computer or printer, the rendering device must substitute glyphs from another font.  Substituting glyphs can change the appearance of the text when a different font is used.  
+ When font glyphs for text in an XPS document are saved in the document package, the document text displays identically on any computer or printer.  If glyphs are not saved in document and the required font is not installed on the local computer or printer, the rendering device must substitute glyphs from another font.  Substituting glyphs can change the appearance of the text when a different font is used.  
   
  <xref:System.Windows.Xps.Serialization.XpsSerializationManager.SetFontSubsettingPolicy%2A> determines the granularity of font-subsetting.  
   
@@ -223,7 +223,7 @@
   
  When creating interleaved documents, font-subsetting across a document sequence can require a large amount of memory to hold the complete document until the final font-subset can be determined.  <xref:System.Windows.Xps.Serialization.FontSubsetterCommitPolicies.CommitPerPage> or <xref:System.Windows.Xps.Serialization.FontSubsetterCommitPolicies.CommitPerDocument> can be specified to reduce application memory requirements when you create interleaved documents.  
   
- When `policy` is <xref:System.Windows.Xps.Serialization.FontSubsetterCommitPolicies.None>, all the glyphs for all fonts that are used in the [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document are saved, even glyphs for characters that not actually used in the text.  
+ When `policy` is <xref:System.Windows.Xps.Serialization.FontSubsetterCommitPolicies.None>, all the glyphs for all fonts that are used in the XPS document are saved, even glyphs for characters that not actually used in the text.  
   
  ]]></format>
         </remarks>
@@ -250,7 +250,7 @@
         <ReturnType>System.Windows.Xps.Serialization.XpsSerializationPrintTicketRequiredEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs when an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] serializer requests a <see cref="T:System.Printing.PrintTicket" />.</summary>
+        <summary>Occurs when an XPS serializer requests a <see cref="T:System.Printing.PrintTicket" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Xps.Serialization/XpsSerializerFactory.xml b/xml/System.Windows.Xps.Serialization/XpsSerializerFactory.xml
index f7f35c5c44d..082eb669975 100644
--- a/xml/System.Windows.Xps.Serialization/XpsSerializerFactory.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsSerializerFactory.xml
@@ -74,8 +74,8 @@
       </Parameters>
       <Docs>
         <param name="stream">The output stream that the returned serializer is to write to.</param>
-        <summary>Creates a <see cref="T:System.Windows.Documents.Serialization.SerializerWriter" /> that outputs [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] content to a specified <see cref="T:System.IO.Stream" />.</summary>
-        <returns>An output writer that serializes [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] content to the specified <paramref name="stream" />.</returns>
+        <summary>Creates a <see cref="T:System.Windows.Documents.Serialization.SerializerWriter" /> that outputs XPS content to a specified <see cref="T:System.IO.Stream" />.</summary>
+        <returns>An output writer that serializes XPS content to the specified <paramref name="stream" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -100,8 +100,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the standard file name extension for [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents.</summary>
-        <value>The standard file name extension (including the leading period) for [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents.</value>
+        <summary>Gets the standard file name extension for XPS documents.</summary>
+        <value>The standard file name extension (including the leading period) for XPS documents.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Xps/XpsDocumentWriter.xml b/xml/System.Windows.Xps/XpsDocumentWriter.xml
index 0a02cec4d37..8926cd1f0ba 100644
--- a/xml/System.Windows.Xps/XpsDocumentWriter.xml
+++ b/xml/System.Windows.Xps/XpsDocumentWriter.xml
@@ -398,7 +398,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write to an XPS document.  
   
  [!code-csharp[XpsSave#WriteToXpsWithDocumentPaginator](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writetoxpswithdocumentpaginator)]
  [!code-vb[XpsSave#WriteToXpsWithDocumentPaginator](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writetoxpswithdocumentpaginator)]  
@@ -445,7 +445,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use this method to write to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this method to write to an XPS document.  
   
  [!code-csharp[XpsSave#WriteToXpsWithFixedDocument](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writetoxpswithfixeddocument)]
  [!code-vb[XpsSave#WriteToXpsWithFixedDocument](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writetoxpswithfixeddocument)]  
@@ -492,7 +492,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write a sequence of [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents.  
+ The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write a sequence of XPS documents.  
   
  [!code-csharp[XpsSave#WriteToXpsWithFixedDocumentSequence](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writetoxpswithfixeddocumentsequence)]
  [!code-vb[XpsSave#WriteToXpsWithFixedDocumentSequence](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writetoxpswithfixeddocumentsequence)]  
@@ -571,7 +571,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write a <xref:System.Windows.Media.Visual> to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> method to write a <xref:System.Windows.Media.Visual> to an XPS document.  
   
  [!code-csharp[XpsSave#WriteToXpsWithVisual](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writetoxpswithvisual)]
  [!code-vb[XpsSave#WriteToXpsWithVisual](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writetoxpswithvisual)]  
@@ -610,16 +610,16 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
       <Docs>
         <param name="documentPath">The path of the source document.</param>
         <param name="notificationLevel">An indication of whether notification is enabled.</param>
-        <summary>Writes synchronously a specified [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
+        <summary>Writes synchronously a specified XPS document to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When `notificationLevel` is disabled, the <xref:System.Windows.Xps.XpsDocumentWriter> copies the serialized[!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document to the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue> that created the <xref:System.Windows.Xps.XpsDocumentWriter>. When `notificationLevel` is enabled, the <xref:System.Windows.Xps.XpsDocumentWriter> first deserializes the document, next reserializes it, and then writes it to the target with progress notifications as each page is output.  
+ When `notificationLevel` is disabled, the <xref:System.Windows.Xps.XpsDocumentWriter> copies the serializedXPS document to the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue> that created the <xref:System.Windows.Xps.XpsDocumentWriter>. When `notificationLevel` is enabled, the <xref:System.Windows.Xps.XpsDocumentWriter> first deserializes the document, next reserializes it, and then writes it to the target with progress notifications as each page is output.  
   
  Although the <xref:System.Windows.Xps.Packaging.XpsDocument> class has a singular name, an <xref:System.Windows.Xps.Packaging.XpsDocument> can be one <xref:System.Windows.Documents.FixedDocument> or a set of multiple documents. This method adds the <xref:System.Windows.Documents.FixedDocument> elements in the source to the sequence of <xref:System.Windows.Documents.FixedDocument> elements in the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue>.  
   
- If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationEnabled>, notifications are produced only when the document is serialized, not printed.  To receive notifications the document must be reserialized.  When a document is reserialized all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification (XPS)](https://go.microsoft.com/fwlink/?LinkID=65761) is removed.  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] content.  
+ If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationEnabled>, notifications are produced only when the document is serialized, not printed.  To receive notifications the document must be reserialized.  When a document is reserialized all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification (XPS)](https://go.microsoft.com/fwlink/?LinkID=65761) is removed.  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended XPS content.  
   
  If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationDisabled> the document will not be reserialized and any extended content will be preserved, even when printed.  
   
@@ -877,14 +877,14 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
       </Parameters>
       <Docs>
         <param name="documentPath">The path of the source document.</param>
-        <summary>Writes asynchronously a specified [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
+        <summary>Writes asynchronously a specified XPS document to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  Although the <xref:System.Windows.Xps.Packaging.XpsDocument> class has a singular name, an <xref:System.Windows.Xps.Packaging.XpsDocument> can be one <xref:System.Windows.Documents.FixedDocument> or a set of multiple documents. This method adds the <xref:System.Windows.Documents.FixedDocument> elements in the source to the set of <xref:System.Windows.Documents.FixedDocument> elements in the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue>.  
   
- This <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> method will reserialize the specified [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document which will remove all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification](https://go.microsoft.com/fwlink/?LinkID=65761).  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] content.  
+ This <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> method will reserialize the specified XPS document which will remove all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification](https://go.microsoft.com/fwlink/?LinkID=65761).  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended XPS content.  
   
  By design this <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> method does not call the <xref:System.Windows.Xps.XpsDocumentWriter.WritingPrintTicketRequired> event.  
   
@@ -925,7 +925,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to use this method to write to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this method to write to an XPS document.  
   
  [!code-csharp[XpsSave#WriteAsyncToXpsWithDocumentPaginator](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writeasynctoxpswithdocumentpaginator)]
  [!code-vb[XpsSave#WriteAsyncToXpsWithDocumentPaginator](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writeasynctoxpswithdocumentpaginator)]  
@@ -972,7 +972,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use this method to write to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this method to write to an XPS document.  
   
  [!code-csharp[XpsSave#WriteAsyncToXpsWithFixedDocument](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writeasynctoxpswithfixeddocument)]
  [!code-vb[XpsSave#WriteAsyncToXpsWithFixedDocument](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writeasynctoxpswithfixeddocument)]  
@@ -1019,7 +1019,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use this method to write to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this method to write to an XPS document.  
   
  [!code-csharp[XpsSave#WriteAsyncToXpsWithFixedDocumentSequence](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writeasynctoxpswithfixeddocumentsequence)]
  [!code-vb[XpsSave#WriteAsyncToXpsWithFixedDocumentSequence](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writeasynctoxpswithfixeddocumentsequence)]  
@@ -1098,7 +1098,7 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
    
   
 ## Examples  
- The following example shows how to use this method to write a <xref:System.Windows.Media.Visual> to an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document.  
+ The following example shows how to use this method to write a <xref:System.Windows.Media.Visual> to an XPS document.  
   
  [!code-csharp[XpsSave#WriteAsyncToXpsWithVisual](~/samples/snippets/csharp/VS_Snippets_Wpf/XpsSave/CSharp/XpsSaveHelper.cs#writeasynctoxpswithvisual)]
  [!code-vb[XpsSave#WriteAsyncToXpsWithVisual](~/samples/snippets/visualbasic/VS_Snippets_Wpf/XpsSave/visualbasic/xpssavehelper.vb#writeasynctoxpswithvisual)]  
@@ -1137,16 +1137,16 @@ By design, this `Write` method does not raise the <xref:System.Windows.Xps.XpsDo
       <Docs>
         <param name="documentPath">The path of the source document.</param>
         <param name="notificationLevel">An indication of whether notification is enabled.</param>
-        <summary>Writes asynchronously a specified [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document with notification option to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
+        <summary>Writes asynchronously a specified XPS document with notification option to the target <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> or <see cref="T:System.Printing.PrintQueue" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When `notificationLevel` is disabled, the <xref:System.Windows.Xps.XpsDocumentWriter> copies the serialized [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document to the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue> that created the <xref:System.Windows.Xps.XpsDocumentWriter>. When `notificationLevel` is enabled, the <xref:System.Windows.Xps.XpsDocumentWriter> first deserializes the document, next reserializes it, and then writes it to the target with progress notifications as each page is output.  
+ When `notificationLevel` is disabled, the <xref:System.Windows.Xps.XpsDocumentWriter> copies the serialized XPS document to the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue> that created the <xref:System.Windows.Xps.XpsDocumentWriter>. When `notificationLevel` is enabled, the <xref:System.Windows.Xps.XpsDocumentWriter> first deserializes the document, next reserializes it, and then writes it to the target with progress notifications as each page is output.  
   
  Although the <xref:System.Windows.Xps.Packaging.XpsDocument> class has a singular name, an <xref:System.Windows.Xps.Packaging.XpsDocument> can be one <xref:System.Windows.Documents.FixedDocument> or a set of multiple documents. This method adds the <xref:System.Windows.Documents.FixedDocument> elements in the source to the sequence of <xref:System.Windows.Documents.FixedDocument> elements in the target <xref:System.Windows.Xps.Packaging.XpsDocument> or <xref:System.Printing.PrintQueue>.  
   
- If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationEnabled>, notifications are produced only when the document is serialized, not printed.  To receive notifications the document must be reserialized.  When a document is reserialized all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification](https://go.microsoft.com/fwlink/?LinkID=65761) is removed.  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] content.  
+ If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationEnabled>, notifications are produced only when the document is serialized, not printed.  To receive notifications the document must be reserialized.  When a document is reserialized all content from the <xref:System.IO.Packaging.Package> that is not required to be preserved by the [XML Paper Specification](https://go.microsoft.com/fwlink/?LinkID=65761) is removed.  The reserialization will also remove all extensions from the <xref:System.Windows.Documents.FixedPage> markup, including any extended XPS content.  
   
  If `notificationLevel` is specified as <xref:System.Windows.Xps.XpsDocumentNotificationLevel.ReceiveNotificationDisabled> the document will not be reserialized and any extended content will be preserved, even when printed.  
   
diff --git a/xml/ns-System.Windows.Documents.DocumentStructures.xml b/xml/ns-System.Windows.Documents.DocumentStructures.xml
index cca167103f4..7bfaf059b54 100644
--- a/xml/ns-System.Windows.Documents.DocumentStructures.xml
+++ b/xml/ns-System.Windows.Documents.DocumentStructures.xml
@@ -5,13 +5,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The formatting and layout of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document enables different parts of the content to behave in a semantic form such as in paragraphs, tables, and lists.  Humans can perceive the semantic structure of the content from its appearance; but the physical format and layout of the markup does not explicitly identify the actual semantic elements.  To enable programmatic understanding of the document organization, the <xref:System.Windows.Documents.DocumentStructures> namespace provides structure elements that can be used to define the document by its semantic parts.  
+ The formatting and layout of an XPS document enables different parts of the content to behave in a semantic form such as in paragraphs, tables, and lists.  Humans can perceive the semantic structure of the content from its appearance; but the physical format and layout of the markup does not explicitly identify the actual semantic elements.  To enable programmatic understanding of the document organization, the <xref:System.Windows.Documents.DocumentStructures> namespace provides structure elements that can be used to define the document by its semantic parts.  
   
- Each page of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document contains a <xref:System.Windows.Documents.FixedPage> element that defines its *content* in the form of positional text runs and graphics.  Through the use of document structure elements, pages of an [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] document can also be associated with <xref:System.Windows.Documents.DocumentStructures.StoryFragment> elements that define the *structure* of the page in the form of sections, paragraphs, lists, figures, and tables.  The <xref:System.Windows.Documents.DocumentStructures.NamedElement> class is used to define the associations between content and structure parts of the document markup.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> is the child of a structural element, such as a table cell or bullet list item that is located in the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> hierarchy of a page.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> identifies an item in the <xref:System.Windows.Documents.FixedPage> hierarchy of the same page.  The item it refers to is the content of the structural element.  
+ Each page of an XPS document contains a <xref:System.Windows.Documents.FixedPage> element that defines its *content* in the form of positional text runs and graphics.  Through the use of document structure elements, pages of an XPS document can also be associated with <xref:System.Windows.Documents.DocumentStructures.StoryFragment> elements that define the *structure* of the page in the form of sections, paragraphs, lists, figures, and tables.  The <xref:System.Windows.Documents.DocumentStructures.NamedElement> class is used to define the associations between content and structure parts of the document markup.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> is the child of a structural element, such as a table cell or bullet list item that is located in the <xref:System.Windows.Documents.DocumentStructures.StoryFragment> hierarchy of a page.  A <xref:System.Windows.Documents.DocumentStructures.NamedElement> identifies an item in the <xref:System.Windows.Documents.FixedPage> hierarchy of the same page.  The item it refers to is the content of the structural element.  
   
- Applications that create [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents are not required to include structural markup, but use of document structure elements enhances the flexibility by which applications can access and use the content of a document.  
+ Applications that create XPS documents are not required to include structural markup, but use of document structure elements enhances the flexibility by which applications can access and use the content of a document.  
   
- For more information about structure elements of [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents, see Chapter 9 and Appendix E of the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=67000](https://go.microsoft.com/fwlink/?LinkID=67000).  
+ For more information about structure elements of XPS documents, see Chapter 9 and Appendix E of the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=67000](https://go.microsoft.com/fwlink/?LinkID=67000).  
   
  ]]></format>
     </remarks>
diff --git a/xml/ns-System.Windows.Xps.Packaging.xml b/xml/ns-System.Windows.Xps.Packaging.xml
index 83cef9d91ad..8627dbc93f4 100644
--- a/xml/ns-System.Windows.Xps.Packaging.xml
+++ b/xml/ns-System.Windows.Xps.Packaging.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In addition to the interfaces and the types that represent the major parts of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, the <xref:System.Windows.Xps.Packaging> namespace provides control over the packaging process, including digital signatures and Digital Rights Management (DRM) of [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents.  
+ In addition to the interfaces and the types that represent the major parts of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, the <xref:System.Windows.Xps.Packaging> namespace provides control over the packaging process, including digital signatures and Digital Rights Management (DRM) of XPS documents.  
   
  For more information, see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
diff --git a/xml/ns-System.Windows.Xps.Serialization.xml b/xml/ns-System.Windows.Xps.Serialization.xml
index f7b7a4513e5..f6789341852 100644
--- a/xml/ns-System.Windows.Xps.Serialization.xml
+++ b/xml/ns-System.Windows.Xps.Serialization.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)], see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For more information about XPS, see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
  ]]></format>
     </remarks>
diff --git a/xml/ns-System.Windows.Xps.xml b/xml/ns-System.Windows.Xps.xml
index 0dc4d8b8dd3..77336a54c91 100644
--- a/xml/ns-System.Windows.Xps.xml
+++ b/xml/ns-System.Windows.Xps.xml
@@ -5,9 +5,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Xps.XpsDocumentWriter> class provides the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods that output [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] documents to a data store or print queue.  Separate groups of write methods are provided for different content types including <xref:System.Windows.Documents.DocumentPaginator>, <xref:System.Windows.Media.Visual>, <xref:System.Windows.Documents.FixedPage>, <xref:System.Windows.Documents.FixedDocument>, and <xref:System.Windows.Documents.FixedDocumentSequence>.  The <xref:System.Windows.Xps.XpsDocumentWriter> methods enable you to also include a <xref:System.Printing.PrintTicket> with the document, plus pass additional information to the handlers of the <xref:System.Windows.Xps.XpsDocumentWriter.WritingCompleted>, <xref:System.Windows.Xps.XpsDocumentWriter.WritingProgressChanged>, and <xref:System.Windows.Xps.XpsDocumentWriter.WritingPrintTicketRequired> events.  
+ The <xref:System.Windows.Xps.XpsDocumentWriter> class provides the <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods that output XPS documents to a data store or print queue.  Separate groups of write methods are provided for different content types including <xref:System.Windows.Documents.DocumentPaginator>, <xref:System.Windows.Media.Visual>, <xref:System.Windows.Documents.FixedPage>, <xref:System.Windows.Documents.FixedDocument>, and <xref:System.Windows.Documents.FixedDocumentSequence>.  The <xref:System.Windows.Xps.XpsDocumentWriter> methods enable you to also include a <xref:System.Printing.PrintTicket> with the document, plus pass additional information to the handlers of the <xref:System.Windows.Xps.XpsDocumentWriter.WritingCompleted>, <xref:System.Windows.Xps.XpsDocumentWriter.WritingProgressChanged>, and <xref:System.Windows.Xps.XpsDocumentWriter.WritingPrintTicketRequired> events.  
   
- For more information about [!INCLUDE[TLA2#tla_xps](~/includes/tla2sharptla-xps-md.md)] see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
+ For more information about XPS see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
  ]]></format>
     </remarks>

From 4480a99405f4581bce52a70d3b78edc0d97b86ba Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:47:21 -0800
Subject: [PATCH 099/236] tla2sharptla-xrml

---
 xml/System.Security.RightsManagement/PublishLicense.xml   | 2 +-
 .../UnsignedPublishLicense.xml                            | 8 ++++----
 xml/System.Security.RightsManagement/UseLicense.xml       | 2 +-
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Security.RightsManagement/PublishLicense.xml b/xml/System.Security.RightsManagement/PublishLicense.xml
index 4831e234916..664791a0ce4 100644
--- a/xml/System.Security.RightsManagement/PublishLicense.xml
+++ b/xml/System.Security.RightsManagement/PublishLicense.xml
@@ -290,7 +290,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the serialized [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] string that was used to create this license.</summary>
+        <summary>Returns the serialized XrML string that was used to create this license.</summary>
         <returns>The serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string that was used to create this license.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
index 02e84bc5cc2..b36fc74d002 100644
--- a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
+++ b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
@@ -97,12 +97,12 @@
       </Parameters>
       <Docs>
         <param name="publishLicenseTemplate">The [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] publish-license template to use to create this license.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" /> class from a specified [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] publish-license template.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" /> class from a specified XrML publish-license template.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `publishLicenseTemplate` [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] `<RANGETIME>` or `<INTERVALTIME>` elements are ignored when the <xref:System.Security.RightsManagement.UnsignedPublishLicense> is created by the <xref:System.Security.RightsManagement.UnsignedPublishLicense.%23ctor%2A>(String) constructor.  To specify these values for the publish license, the <xref:System.Security.RightsManagement.ContentGrant> properties for <xref:System.Security.RightsManagement.ContentGrant.ValidFrom%2A> and <xref:System.Security.RightsManagement.ContentGrant.ValidUntil%2A> must be explicitly set.  The following example shows how to explicitly set the <xref:System.Security.RightsManagement.ContentGrant.ValidFrom%2A> and <xref:System.Security.RightsManagement.ContentGrant.ValidUntil%2A> properties.  
+ The `publishLicenseTemplate` XrML `<RANGETIME>` or `<INTERVALTIME>` elements are ignored when the <xref:System.Security.RightsManagement.UnsignedPublishLicense> is created by the <xref:System.Security.RightsManagement.UnsignedPublishLicense.%23ctor%2A>(String) constructor.  To specify these values for the publish license, the <xref:System.Security.RightsManagement.ContentGrant> properties for <xref:System.Security.RightsManagement.ContentGrant.ValidFrom%2A> and <xref:System.Security.RightsManagement.ContentGrant.ValidUntil%2A> must be explicitly set.  The following example shows how to explicitly set the <xref:System.Security.RightsManagement.ContentGrant.ValidFrom%2A> and <xref:System.Security.RightsManagement.ContentGrant.ValidUntil%2A> properties.  
   
  [!code-csharp[UnsignedPubLicense_snip#RmPkgPubGrants](~/samples/snippets/csharp/VS_Snippets_Wpf/UnsignedPubLicense_snip/CSharp/Window1.xaml.cs#rmpkgpubgrants)]
  [!code-vb[UnsignedPubLicense_snip#RmPkgPubGrants](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UnsignedPubLicense_snip/visualbasic/window1.xaml.vb#rmpkgpubgrants)]  
@@ -365,8 +365,8 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a serialized template created from the [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" />.</summary>
-        <returns>A serialized template created from the [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" />.</returns>
+        <summary>Returns a serialized template created from the XrML of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" />.</summary>
+        <returns>A serialized template created from the XrML of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Security.RightsManagement.UnsignedPublishLicense.#ctor(System.String)" />
       </Docs>
diff --git a/xml/System.Security.RightsManagement/UseLicense.xml b/xml/System.Security.RightsManagement/UseLicense.xml
index f001abed944..579111ac625 100644
--- a/xml/System.Security.RightsManagement/UseLicense.xml
+++ b/xml/System.Security.RightsManagement/UseLicense.xml
@@ -292,7 +292,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the serialized [!INCLUDE[TLA2#tla_xrml](~/includes/tla2sharptla-xrml-md.md)] string used to create this license.</summary>
+        <summary>Returns the serialized XrML string used to create this license.</summary>
         <returns>The serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string originally passed to the <see cref="M:System.Security.RightsManagement.UseLicense.#ctor(System.String)" /> constructor.</returns>
         <remarks>To be added.</remarks>
       </Docs>

From 45a461070c310c0c622d848b9d775c1aa0870b60 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:48:44 -0800
Subject: [PATCH 100/236] tlasharptla-2d

---
 xml/System.Windows.Controls/Viewport3D.xml              | 4 ++--
 xml/System.Windows.Media.Media3D/OrthographicCamera.xml | 2 +-
 xml/System.Windows.Media.Media3D/PerspectiveCamera.xml  | 2 +-
 xml/System.Windows.Media.Media3D/RotateTransform3D.xml  | 2 +-
 xml/System.Windows.Media.Media3D/SpecularMaterial.xml   | 2 +-
 xml/System.Windows.Media/MatrixTransform.xml            | 2 +-
 xml/System.Windows.Media/SkewTransform.xml              | 2 +-
 xml/System.Windows.Media/Transform.xml                  | 2 +-
 8 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Controls/Viewport3D.xml b/xml/System.Windows.Controls/Viewport3D.xml
index d4ce366724b..d107c5ed665 100644
--- a/xml/System.Windows.Controls/Viewport3D.xml
+++ b/xml/System.Windows.Controls/Viewport3D.xml
@@ -121,8 +121,8 @@
         <ReturnType>System.Windows.Media.Media3D.Camera</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a camera object that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents of the <see cref="T:System.Windows.Controls.Viewport3D" /> to the [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] surface of the <see cref="T:System.Windows.Controls.Viewport3D" />.</summary>
-        <value>The camera that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents to the [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] surface.</value>
+        <summary>Gets or sets a camera object that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents of the <see cref="T:System.Windows.Controls.Viewport3D" /> to the 2-D surface of the <see cref="T:System.Windows.Controls.Viewport3D" />.</summary>
+        <value>The camera that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents to the 2-D surface.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media.Media3D/OrthographicCamera.xml b/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
index a9eca19d529..d12fcd24fb8 100644
--- a/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
+++ b/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class specifies an orthogonal projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] visual surface. Like <xref:System.Windows.Media.Media3D.PerspectiveCamera>, it specifies a position, viewing direction, and "upward" direction. Unlike <xref:System.Windows.Media.Media3D.PerspectiveCamera>, however, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a projection that does not include perspective foreshortening. In other words, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a viewing box whose sides are parallel, instead of one whose sides meet in a point at the scene's horizon.  
+ This class specifies an orthogonal projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a 2-D visual surface. Like <xref:System.Windows.Media.Media3D.PerspectiveCamera>, it specifies a position, viewing direction, and "upward" direction. Unlike <xref:System.Windows.Media.Media3D.PerspectiveCamera>, however, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a projection that does not include perspective foreshortening. In other words, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a viewing box whose sides are parallel, instead of one whose sides meet in a point at the scene's horizon.  
   
  The following diagram shows the difference between orthographic and perspective-foreshortened camera projections.  
   
diff --git a/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml b/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
index 6594155ddb9..aba6d133549 100644
--- a/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
+++ b/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Media3D.PerspectiveCamera> specifies a projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] visual surface. This projection includes perspective foreshortening.  In other words, the <xref:System.Windows.Media.Media3D.PerspectiveCamera> describes a frustrum whose sides converge toward a point on the horizon.  Objects closer to the camera appear larger, and objects farther from the camera appear smaller.  
+ <xref:System.Windows.Media.Media3D.PerspectiveCamera> specifies a projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a 2-D visual surface. This projection includes perspective foreshortening.  In other words, the <xref:System.Windows.Media.Media3D.PerspectiveCamera> describes a frustrum whose sides converge toward a point on the horizon.  Objects closer to the camera appear larger, and objects farther from the camera appear smaller.  
   
  The following diagram shows the difference between orthographic and perspective-foreshortened camera projections.  
   
diff --git a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
index ed95522b38c..a309f206267 100644
--- a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Rotations in [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] usually consist of two arguments: a point around which to rotate an object or set of objects, and a value in degrees or radians that determines the amount of rotation. In [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)], it is necessary to specify a <xref:System.Windows.Media.Media3D.Vector3D> rather than a point around which to rotate.  
+ Rotations in 2-D usually consist of two arguments: a point around which to rotate an object or set of objects, and a value in degrees or radians that determines the amount of rotation. In [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)], it is necessary to specify a <xref:System.Windows.Media.Media3D.Vector3D> rather than a point around which to rotate.  
   
  Rotations in 3-D become more complicated when they are animated.  To animate a 3-D rotation using <xref:System.Windows.Media.Media3D.RotateTransform3D>, you can animate the <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Angle%2A> or <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Axis%2A> properties of an <xref:System.Windows.Media.Media3D.AxisAngleRotation3D>, or specify a <xref:System.Windows.Media.Media3D.QuaternionRotation3D> for the transform. 
   
diff --git a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
index 27c86643f16..01c1434f6df 100644
--- a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
+++ b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
@@ -126,7 +126,7 @@
         <ReturnType>System.Windows.Media.Brush</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] brush to apply to a specularly-lit [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model.</summary>
+        <summary>Gets or sets the 2-D brush to apply to a specularly-lit [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model.</summary>
         <value>The brush to apply.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Media/MatrixTransform.xml b/xml/System.Windows.Media/MatrixTransform.xml
index 59d7942039a..bc7a0d5fab8 100644
--- a/xml/System.Windows.Media/MatrixTransform.xml
+++ b/xml/System.Windows.Media/MatrixTransform.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  Use the <xref:System.Windows.Media.MatrixTransform> class to create custom transformations that are not provided by the <xref:System.Windows.Media.RotateTransform>, <xref:System.Windows.Media.SkewTransform>, <xref:System.Windows.Media.ScaleTransform>, or <xref:System.Windows.Media.TranslateTransform> classes.  
   
- A 3x3 matrix is used for transformations in a [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] x-y plane. You can multiply affine matrix transformations to form linear transformations, such as rotation and skew (shear) that are followed by translation.  
+ A 3x3 matrix is used for transformations in a 2-D x-y plane. You can multiply affine matrix transformations to form linear transformations, such as rotation and skew (shear) that are followed by translation.  
   
  An affine matrix transformation has its final column equal to (0, 0, 1); therefore, you only have to specify the members in the first two columns.  
   
diff --git a/xml/System.Windows.Media/SkewTransform.xml b/xml/System.Windows.Media/SkewTransform.xml
index e56f237703d..18a5f03b723 100644
--- a/xml/System.Windows.Media/SkewTransform.xml
+++ b/xml/System.Windows.Media/SkewTransform.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Media.SkewTransform> is useful for creating the illusion of 3-dimensional depth in a [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] object.  
+ A <xref:System.Windows.Media.SkewTransform> is useful for creating the illusion of 3-dimensional depth in a 2-D object.  
   
  **Freezable Features:** Because it inherits from the <xref:System.Windows.Freezable> class, the <xref:System.Windows.Media.SkewTransform> class provides several special features: <xref:System.Windows.Media.SkewTransform> objects can be declared as [resources](/dotnet/desktop-wpf/fundamentals/xaml-resources-define), shared among multiple objects, made read-only to improve performance, cloned, and made thread-safe. For more information about the different features provided by <xref:System.Windows.Freezable> objects, see [Freezable Objects Overview](/dotnet/framework/wpf/advanced/freezable-objects-overview).  
   
diff --git a/xml/System.Windows.Media/Transform.xml b/xml/System.Windows.Media/Transform.xml
index bfedf5512ac..a281d9a55fb 100644
--- a/xml/System.Windows.Media/Transform.xml
+++ b/xml/System.Windows.Media/Transform.xml
@@ -38,7 +38,7 @@
 ## Remarks  
  Use the <xref:System.Windows.Media.MatrixTransform> class to create custom transformations that are not provided by the <xref:System.Windows.Media.RotateTransform>, <xref:System.Windows.Media.ScaleTransform>, <xref:System.Windows.Media.SkewTransform>, and <xref:System.Windows.Media.TranslateTransform> classes.  
   
- A [!INCLUDE[TLA#tla_2d](~/includes/tlasharptla-2d-md.md)] x-y plane uses a 3x3 matrix for transformations. You can multiply affine transformation matrices to form linear transformations, such as rotation and skew (shear) that are followed by translation.  
+ A 2-D x-y plane uses a 3x3 matrix for transformations. You can multiply affine transformation matrices to form linear transformations, such as rotation and skew (shear) that are followed by translation.  
   
  An affine transformation matrix has its final column equal to (0, 0, 1); therefore, you only have to specify the members in the first two columns.  
   

From 4d0044ef0f6778a2cab59b0a92f911cb43f26e46 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:49:14 -0800
Subject: [PATCH 101/236] tlasharptla-3d

---
 xml/System.Windows.Controls/Viewport3D.xml              | 4 ++--
 xml/System.Windows.Media.Media3D/DiffuseMaterial.xml    | 2 +-
 xml/System.Windows.Media.Media3D/MatrixTransform3D.xml  | 4 ++--
 xml/System.Windows.Media.Media3D/OrthographicCamera.xml | 2 +-
 xml/System.Windows.Media.Media3D/PerspectiveCamera.xml  | 2 +-
 xml/System.Windows.Media.Media3D/RotateTransform3D.xml  | 2 +-
 xml/System.Windows.Media.Media3D/SpecularMaterial.xml   | 2 +-
 xml/System.Windows.Media.Media3D/Vector3D.xml           | 4 ++--
 xml/System.Windows/SystemParameters.xml                 | 4 ++--
 xml/System.Windows/WindowStyle.xml                      | 2 +-
 10 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/xml/System.Windows.Controls/Viewport3D.xml b/xml/System.Windows.Controls/Viewport3D.xml
index d107c5ed665..6ebad564d60 100644
--- a/xml/System.Windows.Controls/Viewport3D.xml
+++ b/xml/System.Windows.Controls/Viewport3D.xml
@@ -121,8 +121,8 @@
         <ReturnType>System.Windows.Media.Media3D.Camera</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a camera object that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents of the <see cref="T:System.Windows.Controls.Viewport3D" /> to the 2-D surface of the <see cref="T:System.Windows.Controls.Viewport3D" />.</summary>
-        <value>The camera that projects the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] contents to the 2-D surface.</value>
+        <summary>Gets or sets a camera object that projects the 3-D contents of the <see cref="T:System.Windows.Controls.Viewport3D" /> to the 2-D surface of the <see cref="T:System.Windows.Controls.Viewport3D" />.</summary>
+        <value>The camera that projects the 3-D contents to the 2-D surface.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media.Media3D/DiffuseMaterial.xml b/xml/System.Windows.Media.Media3D/DiffuseMaterial.xml
index f4eab9b9195..b9a9ed86d38 100644
--- a/xml/System.Windows.Media.Media3D/DiffuseMaterial.xml
+++ b/xml/System.Windows.Media.Media3D/DiffuseMaterial.xml
@@ -153,7 +153,7 @@
       </ReturnValue>
       <Docs>
         <summary>
-          <see cref="T:System.Windows.Media.Brush" /> to be applied as a <see cref="T:System.Windows.Media.Media3D.Material" /> to a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model.</summary>
+          <see cref="T:System.Windows.Media.Brush" /> to be applied as a <see cref="T:System.Windows.Media.Media3D.Material" /> to a 3-D model.</summary>
         <value>
           <see cref="T:System.Windows.Media.Brush" /> to apply.</value>
         <remarks>
diff --git a/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml b/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
index ba9c6d480f5..54c8ecb5582 100644
--- a/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/MatrixTransform3D.xml
@@ -219,7 +219,7 @@
         <ReturnType>System.Windows.Media.Media3D.Matrix3D</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> that specifies a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] transformation.</summary>
+        <summary>Gets or sets a <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> that specifies a 3-D transformation.</summary>
         <value>A Matrix3D that specifies a 3-D transformation.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -290,7 +290,7 @@
         <ReturnType>System.Windows.Media.Media3D.Matrix3D</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a matrix representation of the [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] transformation.</summary>
+        <summary>Gets a matrix representation of the 3-D transformation.</summary>
         <value>A <see cref="T:System.Windows.Media.Media3D.Matrix3D" /> representation of the 3-D transformation.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Media.Media3D/OrthographicCamera.xml b/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
index d12fcd24fb8..b4e76067bd7 100644
--- a/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
+++ b/xml/System.Windows.Media.Media3D/OrthographicCamera.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class specifies an orthogonal projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a 2-D visual surface. Like <xref:System.Windows.Media.Media3D.PerspectiveCamera>, it specifies a position, viewing direction, and "upward" direction. Unlike <xref:System.Windows.Media.Media3D.PerspectiveCamera>, however, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a projection that does not include perspective foreshortening. In other words, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a viewing box whose sides are parallel, instead of one whose sides meet in a point at the scene's horizon.  
+ This class specifies an orthogonal projection of a 3-D model to a 2-D visual surface. Like <xref:System.Windows.Media.Media3D.PerspectiveCamera>, it specifies a position, viewing direction, and "upward" direction. Unlike <xref:System.Windows.Media.Media3D.PerspectiveCamera>, however, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a projection that does not include perspective foreshortening. In other words, <xref:System.Windows.Media.Media3D.OrthographicCamera> describes a viewing box whose sides are parallel, instead of one whose sides meet in a point at the scene's horizon.  
   
  The following diagram shows the difference between orthographic and perspective-foreshortened camera projections.  
   
diff --git a/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml b/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
index aba6d133549..9defab922fc 100644
--- a/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
+++ b/xml/System.Windows.Media.Media3D/PerspectiveCamera.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Media3D.PerspectiveCamera> specifies a projection of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model to a 2-D visual surface. This projection includes perspective foreshortening.  In other words, the <xref:System.Windows.Media.Media3D.PerspectiveCamera> describes a frustrum whose sides converge toward a point on the horizon.  Objects closer to the camera appear larger, and objects farther from the camera appear smaller.  
+ <xref:System.Windows.Media.Media3D.PerspectiveCamera> specifies a projection of a 3-D model to a 2-D visual surface. This projection includes perspective foreshortening.  In other words, the <xref:System.Windows.Media.Media3D.PerspectiveCamera> describes a frustrum whose sides converge toward a point on the horizon.  Objects closer to the camera appear larger, and objects farther from the camera appear smaller.  
   
  The following diagram shows the difference between orthographic and perspective-foreshortened camera projections.  
   
diff --git a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
index a309f206267..96f2f3f1bd0 100644
--- a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Rotations in 2-D usually consist of two arguments: a point around which to rotate an object or set of objects, and a value in degrees or radians that determines the amount of rotation. In [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)], it is necessary to specify a <xref:System.Windows.Media.Media3D.Vector3D> rather than a point around which to rotate.  
+ Rotations in 2-D usually consist of two arguments: a point around which to rotate an object or set of objects, and a value in degrees or radians that determines the amount of rotation. In 3-D, it is necessary to specify a <xref:System.Windows.Media.Media3D.Vector3D> rather than a point around which to rotate.  
   
  Rotations in 3-D become more complicated when they are animated.  To animate a 3-D rotation using <xref:System.Windows.Media.Media3D.RotateTransform3D>, you can animate the <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Angle%2A> or <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Axis%2A> properties of an <xref:System.Windows.Media.Media3D.AxisAngleRotation3D>, or specify a <xref:System.Windows.Media.Media3D.QuaternionRotation3D> for the transform. 
   
diff --git a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
index 01c1434f6df..6757aaed42d 100644
--- a/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
+++ b/xml/System.Windows.Media.Media3D/SpecularMaterial.xml
@@ -126,7 +126,7 @@
         <ReturnType>System.Windows.Media.Brush</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the 2-D brush to apply to a specularly-lit [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] model.</summary>
+        <summary>Gets or sets the 2-D brush to apply to a specularly-lit 3-D model.</summary>
         <value>The brush to apply.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Media.Media3D/Vector3D.xml b/xml/System.Windows.Media.Media3D/Vector3D.xml
index 464901fc36c..09534c91c8e 100644
--- a/xml/System.Windows.Media.Media3D/Vector3D.xml
+++ b/xml/System.Windows.Media.Media3D/Vector3D.xml
@@ -234,7 +234,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Signed angles do not extend into [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] space, so an angle between 0 and 180 degrees is returned.  
+ Signed angles do not extend into 3-D space, so an angle between 0 and 180 degrees is returned.  
   
    
   
@@ -1396,7 +1396,7 @@
       </Parameters>
       <Docs>
         <param name="source">The <see cref="T:System.String" /> representation of the 3-D vector.</param>
-        <summary>Converts a <see cref="T:System.String" /> representation of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] vector into the equivalent <see cref="T:System.Windows.Media.Media3D.Vector3D" /> structure.</summary>
+        <summary>Converts a <see cref="T:System.String" /> representation of a 3-D vector into the equivalent <see cref="T:System.Windows.Media.Media3D.Vector3D" /> structure.</summary>
         <returns>The equivalent <see cref="T:System.Windows.Media.Media3D.Vector3D" /> structure.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index 283efe7ba31..8f14ea704f9 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -7467,7 +7467,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates the height, in pixels, of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] border.</summary>
+        <summary>Gets a value that indicates the height, in pixels, of a 3-D border.</summary>
         <value>The height of a border.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -7540,7 +7540,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates the width, in pixels, of a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] border.</summary>
+        <summary>Gets a value that indicates the width, in pixels, of a 3-D border.</summary>
         <value>The width of a border.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/WindowStyle.xml b/xml/System.Windows/WindowStyle.xml
index a8e0c01584e..81a23a3bf39 100644
--- a/xml/System.Windows/WindowStyle.xml
+++ b/xml/System.Windows/WindowStyle.xml
@@ -82,7 +82,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>A window with a [!INCLUDE[TLA#tla_3d](~/includes/tlasharptla-3d-md.md)] border.</summary>
+        <summary>A window with a 3-D border.</summary>
       </Docs>
     </Member>
     <Member MemberName="ToolWindow">

From 948fe37b419715cfe10f9471be462756cc7f3849 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:51:59 -0800
Subject: [PATCH 102/236] tlasharptla-aa

---
 .../AutomationFocusChangedEventArgs.xml                     | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
index 0dccdf5666a..6eac89e2c8c 100644
--- a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
@@ -52,7 +52,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `idObject` and `idChild` parameters contain the [!INCLUDE[TLA#tla_aa](~/includes/tlasharptla-aa-md.md)] object identifiers that UI Automation clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
+ The `idObject` and `idChild` parameters contain the Microsoft Active Accessibility object identifiers that UI Automation clients can use to link an <xref:System.Windows.Automation.AutomationElement> to an `IAccessible` object in an older accessible technology application.  
   
  ]]></format>
         </remarks>
@@ -82,7 +82,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the child [!INCLUDE[TLA#tla_aa](~/includes/tlasharptla-aa-md.md)] identifier of the object receiving focus.</summary>
+        <summary>Gets the child Microsoft Active Accessibility identifier of the object receiving focus.</summary>
         <value>The identifier.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -118,7 +118,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the [!INCLUDE[TLA#tla_aa](~/includes/tlasharptla-aa-md.md)] object that generated the event.</summary>
+        <summary>Gets the [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the Microsoft Active Accessibility object that generated the event.</summary>
         <value>The ID of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element that is receiving focus. For possible values, see <see href="/windows/win32/winauto/object-identifiers">Object Identifiers</see>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 371bc9c9f32862c03e569988b3325c7af488d64d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:53:07 -0800
Subject: [PATCH 103/236] tlasharptla-adonet

---
 xml/System.Windows.Data/Binding.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 5875fec8461..2bf21e6bd50 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -33,7 +33,7 @@
   
 -   The target property must be a dependency property. This also means that you cannot bind a field. Most properties of <xref:System.Windows.UIElement> objects are dependency properties and most dependency properties, except read-only ones, support data binding by default. (Only <xref:System.Windows.DependencyObject> types can define dependency properties and all <xref:System.Windows.UIElement> objects derive from <xref:System.Windows.DependencyObject>.)  
   
--   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. WPF data binding supports data in the form of CLR objects and XML. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with [!INCLUDE[TLA#tla_adonet](~/includes/tlasharptla-adonet-md.md)] data or Web Services, or an XmlNode that contains your XML data.  
+-   Although not specified in the figure, it should be noted that the binding source object is not restricted to being a custom CLR object. WPF data binding supports data in the form of CLR objects and XML. To provide some examples, your binding source may be a <xref:System.Windows.UIElement>, any list object, a CLR object that is associated with ADO.NET data or Web Services, or an XmlNode that contains your XML data.  
   
  Use the <xref:System.Windows.Data.Binding.Mode%2A> property to specify the direction of the data flow. To detect source changes in one-way or two-way bindings, the source must implement a suitable property change notification mechanism such as <xref:System.ComponentModel.INotifyPropertyChanged>. For an example, see [How to: Implement Property Change Notification](/dotnet/framework/wpf/data/how-to-implement-property-change-notification). The <xref:System.Windows.Data.Binding.UpdateSourceTrigger%2A> property specifies the timing of source updates. For more information, see "Basic Data Binding Concepts" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   

From 18f896c6ba7fcb65abe3e4ccacf8770c6d1d7911 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:55:38 -0800
Subject: [PATCH 104/236] tlasharptla-aero

---
 xml/Microsoft.Windows.Themes/BulletChrome.xml | 2 +-
 xml/Microsoft.Windows.Themes/ButtonChrome.xml | 2 +-
 xml/Microsoft.Windows.Themes/ScrollChrome.xml | 4 ++--
 xml/System.Windows.Shell/TaskbarItemInfo.xml  | 2 +-
 xml/System.Windows.Shell/ThumbButtonInfo.xml  | 2 +-
 5 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/Microsoft.Windows.Themes/BulletChrome.xml b/xml/Microsoft.Windows.Themes/BulletChrome.xml
index b0a3d53b29b..ddb13218fd0 100644
--- a/xml/Microsoft.Windows.Themes/BulletChrome.xml
+++ b/xml/Microsoft.Windows.Themes/BulletChrome.xml
@@ -317,7 +317,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is not available in the [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] theme.  
+ This property is not available in the Windows Aero theme.  
   
 <a name="dependencyPropertyInfo_BorderThickness"></a>   
 ## Dependency Property Information  
diff --git a/xml/Microsoft.Windows.Themes/ButtonChrome.xml b/xml/Microsoft.Windows.Themes/ButtonChrome.xml
index aa79caabf13..99163eaed4d 100644
--- a/xml/Microsoft.Windows.Themes/ButtonChrome.xml
+++ b/xml/Microsoft.Windows.Themes/ButtonChrome.xml
@@ -337,7 +337,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This property is not available in the [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] theme.
+ This property is not available in the Windows Aero theme.
 
 <a name="dependencyPropertyInfo_Fill"></a>
 ## Dependency Property Information
diff --git a/xml/Microsoft.Windows.Themes/ScrollChrome.xml b/xml/Microsoft.Windows.Themes/ScrollChrome.xml
index 2f77851d26b..063af483a20 100644
--- a/xml/Microsoft.Windows.Themes/ScrollChrome.xml
+++ b/xml/Microsoft.Windows.Themes/ScrollChrome.xml
@@ -237,7 +237,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This property does not exist in the [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] theme.
+ This property does not exist in the Windows Aero theme.
 
 <a name="dependencyPropertyInfo_HasOuterBorder"></a>
 ## Dependency Property Information
@@ -406,7 +406,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- This property does not exist in the [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] theme.
+ This property does not exist in the Windows Aero theme.
 
 <a name="dependencyPropertyInfo_Padding"></a>
 ## Dependency Property Information
diff --git a/xml/System.Windows.Shell/TaskbarItemInfo.xml b/xml/System.Windows.Shell/TaskbarItemInfo.xml
index b830f5c6618..5bad9efa0d1 100644
--- a/xml/System.Windows.Shell/TaskbarItemInfo.xml
+++ b/xml/System.Windows.Shell/TaskbarItemInfo.xml
@@ -24,7 +24,7 @@
   
  The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality that enables you to use the taskbar item to communicate status to a user and expose common tasks when the window is minimized or hidden. The functionality that is exposed by the <xref:System.Windows.Shell.TaskbarItemInfo> class is unavailable in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. Applications that use the <xref:System.Windows.Shell.TaskbarItemInfo> class can still run in earlier versions of Windows; however, these taskbar enhancements are unavailable in the earlier versions.  
   
- In [!INCLUDE[win7](~/includes/win7-md.md)], some taskbar functionality might be unavailable, depending on the user's settings. For example, taskbar functionality is unavailable if [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] is disabled or if the application is started with elevated permissions. Your application should provide other ways to interact with the user that do not depend on the enhanced taskbar functionality in [!INCLUDE[win7](~/includes/win7-md.md)].  
+ In [!INCLUDE[win7](~/includes/win7-md.md)], some taskbar functionality might be unavailable, depending on the user's settings. For example, taskbar functionality is unavailable if Windows Aero is disabled or if the application is started with elevated permissions. Your application should provide other ways to interact with the user that do not depend on the enhanced taskbar functionality in [!INCLUDE[win7](~/includes/win7-md.md)].  
   
  Program icons in the notification area, which is at the far right of the taskbar, are typically used to communicate application status to a user. By default, the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar hides program icons in the notification area. However, you can set the <xref:System.Windows.Shell.TaskbarItemInfo.Overlay%2A> property to add an image to the taskbar button to communicate status, such as online status in a messaging application. The overlay image lets users see the application status even if they cannot see the program icon in the notification area. You can also display the progress of running tasks in the taskbar button by setting the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> and <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> properties.  
   
diff --git a/xml/System.Windows.Shell/ThumbButtonInfo.xml b/xml/System.Windows.Shell/ThumbButtonInfo.xml
index c7bb61d93c6..cfdf8c03d5d 100644
--- a/xml/System.Windows.Shell/ThumbButtonInfo.xml
+++ b/xml/System.Windows.Shell/ThumbButtonInfo.xml
@@ -28,7 +28,7 @@
   
  The <xref:System.Windows.Shell.ThumbButtonInfo> class contains properties that describe how the [!INCLUDE[win7](~/includes/win7-md.md)] shell displays the buttons in the taskbar thumbnail. It provides a managed wrapper around the native Windows API. <xref:System.Windows.Shell.ThumbButtonInfo> objects are contained in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A?displayProperty=nameWithType> collection.  
   
- The enhanced taskbar functionality is not available in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. In [!INCLUDE[win7](~/includes/win7-md.md)], some functionality might not be available depending on the user's settings. For example, buttons are only shown in the taskbar thumbnail when [!INCLUDE[TLA#tla_aero](~/includes/tlasharptla-aero-md.md)] is enabled. Your application should provide alternate ways of interacting with the user that are not dependent on the enhanced taskbar functionality.  
+ The enhanced taskbar functionality is not available in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. In [!INCLUDE[win7](~/includes/win7-md.md)], some functionality might not be available depending on the user's settings. For example, buttons are only shown in the taskbar thumbnail when Windows Aero is enabled. Your application should provide alternate ways of interacting with the user that are not dependent on the enhanced taskbar functionality.  
   
  The following illustration shows a taskbar preview with two thumb buttons that provide access to the Play and Stop commands.  
   

From 7eaa312c0595a26d405dbe855129faa2d551ec64 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:56:01 -0800
Subject: [PATCH 105/236] tlasharptla-argb

---
 xml/System.Windows.Media/Colors.xml | 282 ++++++++++++++--------------
 1 file changed, 141 insertions(+), 141 deletions(-)

diff --git a/xml/System.Windows.Media/Colors.xml b/xml/System.Windows.Media/Colors.xml
index 184e0b7776e..cd3b84664d9 100644
--- a/xml/System.Windows.Media/Colors.xml
+++ b/xml/System.Windows.Media/Colors.xml
@@ -59,7 +59,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF0F8FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF0F8FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -96,7 +96,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFAEBD7</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFAEBD7</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -133,7 +133,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00FFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00FFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -170,7 +170,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF7FFFD4</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF7FFFD4</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -207,7 +207,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF0FFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF0FFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -244,7 +244,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF5F5DC</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF5F5DC</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -281,7 +281,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFE4C4</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFE4C4</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -318,7 +318,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF000000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF000000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -355,7 +355,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFEBCD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFEBCD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -392,7 +392,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF0000FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF0000FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -429,7 +429,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF8A2BE2</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF8A2BE2</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -466,7 +466,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFA52A2A</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFA52A2A</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -503,7 +503,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDEB887</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDEB887</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -540,7 +540,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF5F9EA0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF5F9EA0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -577,7 +577,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF7FFF00</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF7FFF00</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -614,7 +614,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFD2691E</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFD2691E</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -651,7 +651,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF7F50</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF7F50</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -688,7 +688,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF6495ED</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF6495ED</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -725,7 +725,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFF8DC</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFF8DC</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -762,7 +762,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDC143C</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDC143C</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -799,7 +799,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00FFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00FFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -836,7 +836,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00008B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00008B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -873,7 +873,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF008B8B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF008B8B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -910,7 +910,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFB8860B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFB8860B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -947,7 +947,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFA9A9A9</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFA9A9A9</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -984,7 +984,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF006400</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF006400</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1021,7 +1021,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFBDB76B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFBDB76B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1058,7 +1058,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF8B008B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF8B008B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1095,7 +1095,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF556B2F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF556B2F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1132,7 +1132,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF8C00</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF8C00</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1169,7 +1169,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF9932CC</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF9932CC</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1206,7 +1206,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF8B0000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF8B0000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1243,7 +1243,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFE9967A</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFE9967A</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1280,7 +1280,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF8FBC8F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF8FBC8F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1317,7 +1317,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF483D8B</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF483D8B</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1354,7 +1354,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF2F4F4F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF2F4F4F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1391,7 +1391,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00CED1</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00CED1</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1428,7 +1428,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF9400D3</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF9400D3</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1465,7 +1465,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF1493</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF1493</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1502,7 +1502,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00BFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00BFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1539,7 +1539,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF696969</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF696969</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1576,7 +1576,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF1E90FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF1E90FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1613,7 +1613,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFB22222</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFB22222</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1650,7 +1650,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFAF0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFAF0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1687,7 +1687,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF228B22</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF228B22</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1724,7 +1724,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF00FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF00FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1761,7 +1761,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDCDCDC</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDCDCDC</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1798,7 +1798,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF8F8FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF8F8FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1835,7 +1835,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFD700</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFD700</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1872,7 +1872,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDAA520</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDAA520</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1909,7 +1909,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF808080</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF808080</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1946,7 +1946,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF008000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF008000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1983,7 +1983,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFADFF2F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFADFF2F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2020,7 +2020,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF0FFF0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF0FFF0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2057,7 +2057,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF69B4</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF69B4</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2094,7 +2094,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFCD5C5C</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFCD5C5C</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2131,7 +2131,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF4B0082</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF4B0082</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2168,7 +2168,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFFF0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFFF0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2205,7 +2205,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF0E68C</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF0E68C</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2242,7 +2242,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFE6E6FA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFE6E6FA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2279,7 +2279,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFF0F5</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFF0F5</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2316,7 +2316,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF7CFC00</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF7CFC00</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2353,7 +2353,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFACD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFACD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2390,7 +2390,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFADD8E6</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFADD8E6</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2427,7 +2427,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF08080</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF08080</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2464,7 +2464,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFE0FFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFE0FFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2501,7 +2501,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFAFAD2</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFAFAD2</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2538,7 +2538,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFD3D3D3</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFD3D3D3</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2575,7 +2575,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF90EE90</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF90EE90</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2612,7 +2612,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFB6C1</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFB6C1</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2649,7 +2649,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFA07A</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFA07A</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2686,7 +2686,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF20B2AA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF20B2AA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2723,7 +2723,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF87CEFA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF87CEFA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2760,7 +2760,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF778899</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF778899</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2797,7 +2797,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFB0C4DE</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFB0C4DE</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2834,7 +2834,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFFE0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFFE0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2871,7 +2871,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00FF00</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00FF00</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2908,7 +2908,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF32CD32</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF32CD32</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2945,7 +2945,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFAF0E6</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFAF0E6</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2982,7 +2982,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF00FF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF00FF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3019,7 +3019,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF800000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF800000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3056,7 +3056,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF66CDAA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF66CDAA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3093,7 +3093,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF0000CD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF0000CD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3130,7 +3130,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFBA55D3</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFBA55D3</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3167,7 +3167,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF9370DB</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF9370DB</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3204,7 +3204,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF3CB371</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF3CB371</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3241,7 +3241,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF7B68EE</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF7B68EE</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3278,7 +3278,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00FA9A</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00FA9A</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3315,7 +3315,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF48D1CC</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF48D1CC</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3352,7 +3352,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFC71585</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFC71585</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3389,7 +3389,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF191970</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF191970</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3426,7 +3426,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF5FFFA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF5FFFA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3463,7 +3463,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFE4E1</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFE4E1</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3500,7 +3500,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFE4B5</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFE4B5</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3537,7 +3537,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFDEAD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFDEAD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3574,7 +3574,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF000080</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF000080</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3611,7 +3611,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFDF5E6</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFDF5E6</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3648,7 +3648,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF808000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF808000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3685,7 +3685,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF6B8E23</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF6B8E23</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3722,7 +3722,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFA500</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFA500</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3759,7 +3759,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF4500</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF4500</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3796,7 +3796,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDA70D6</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDA70D6</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3833,7 +3833,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFEEE8AA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFEEE8AA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3870,7 +3870,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF98FB98</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF98FB98</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3907,7 +3907,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFAFEEEE</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFAFEEEE</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3944,7 +3944,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDB7093</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDB7093</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -3981,7 +3981,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFEFD5</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFEFD5</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4018,7 +4018,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFDAB9</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFDAB9</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4055,7 +4055,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFCD853F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFCD853F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4092,7 +4092,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFC0CB</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFC0CB</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4129,7 +4129,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFDDA0DD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFDDA0DD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4166,7 +4166,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFB0E0E6</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFB0E0E6</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4203,7 +4203,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF800080</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF800080</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4240,7 +4240,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF0000</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF0000</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4277,7 +4277,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFBC8F8F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFBC8F8F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4314,7 +4314,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF4169E1</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF4169E1</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4351,7 +4351,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF8B4513</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF8B4513</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4388,7 +4388,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFA8072</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFA8072</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4425,7 +4425,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF4A460</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF4A460</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4462,7 +4462,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF2E8B57</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF2E8B57</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4499,7 +4499,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFF5EE</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFF5EE</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4536,7 +4536,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFA0522D</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFA0522D</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4573,7 +4573,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFC0C0C0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFC0C0C0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4610,7 +4610,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF87CEEB</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF87CEEB</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4647,7 +4647,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF6A5ACD</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF6A5ACD</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4684,7 +4684,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF708090</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF708090</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4721,7 +4721,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFAFA</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFAFA</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4758,7 +4758,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF00FF7F</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF00FF7F</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4795,7 +4795,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF4682B4</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF4682B4</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4832,7 +4832,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFD2B48C</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFD2B48C</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4869,7 +4869,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF008080</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF008080</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4906,7 +4906,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFD8BFD8</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFD8BFD8</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4943,7 +4943,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFF6347</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFF6347</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4980,7 +4980,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#00FFFFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#00FFFFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5017,7 +5017,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF40E0D0</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF40E0D0</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5054,7 +5054,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFEE82EE</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFEE82EE</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5091,7 +5091,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF5DEB3</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF5DEB3</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5128,7 +5128,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFFFF</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFFFF</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5165,7 +5165,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFF5F5F5</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFF5F5F5</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5202,7 +5202,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FFFFFF00</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FFFFFF00</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -5239,7 +5239,7 @@ Color Table including a color swatch, the color name, and the hexadecimal value
         <ReturnType>System.Windows.Media.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the system-defined color that has an [!INCLUDE[TLA#tla_argb](~/includes/tlasharptla-argb-md.md)] value of <c>#FF9ACD32</c>.</summary>
+        <summary>Gets the system-defined color that has an ARGB value of <c>#FF9ACD32</c>.</summary>
         <value>Represents colors in terms of alpha, red, green, and blue channels.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 7750298de67cc86bf5116714f65bcc772eae40be Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:56:23 -0800
Subject: [PATCH 106/236] tlasharptla-ascii

---
 xml/System.Windows.Markup/XmlLanguage.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Markup/XmlLanguage.xml b/xml/System.Windows.Markup/XmlLanguage.xml
index 734781f252c..09c70d18bc9 100644
--- a/xml/System.Windows.Markup/XmlLanguage.xml
+++ b/xml/System.Windows.Markup/XmlLanguage.xml
@@ -151,9 +151,9 @@
   
  The language string may be empty, or else must conform to [RFC 3066](https://go.microsoft.com/fwlink/?LinkId=132454) rules:  
   
--   The first subtag must consist of only [!INCLUDE[TLA#tla_ascii](~/includes/tlasharptla-ascii-md.md)] letters.  
+-   The first subtag must consist of only ASCII letters.  
   
--   Additional subtags must consist [!INCLUDE[TLA#tla_ascii](~/includes/tlasharptla-ascii-md.md)] letters or numerals.  
+-   Additional subtags must consist ASCII letters or numerals.  
   
 -   Subtags are separated by a single hyphen character.  
   

From c0744be63273cf46e1c2d9e3c8e4b625a015847a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:56:41 -0800
Subject: [PATCH 107/236] tlasharptla-baml

---
 xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml  | 8 ++++----
 xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml  | 4 ++--
 .../BamlLocalizableResourceKey.xml                        | 4 ++--
 xml/System.Windows/EventSetter.xml                        | 2 +-
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
index 5bd3cc0005a..8f0198ed92b 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
@@ -437,8 +437,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</summary>
-        <value>The generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</value>
+        <summary>Gets or sets the generated binary XAML (BAML) files.</summary>
+        <value>The generated binary XAML (BAML) files.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
@@ -1022,8 +1022,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies which culture satellite assembly will hold the generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</summary>
-        <value>A a value that specifies which culture satellite assembly will hold the generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</value>
+        <summary>Gets or sets a value that specifies which culture satellite assembly will hold the generated binary XAML (BAML) files.</summary>
+        <value>A a value that specifies which culture satellite assembly will hold the generated binary XAML (BAML) files.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
index d001ba85260..b808c82abf4 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
@@ -195,8 +195,8 @@
         <ReturnType>Microsoft.Build.Framework.ITaskItem[]</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</summary>
-        <value>The generated [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files.</value>
+        <summary>Gets or sets the generated binary XAML (BAML) files.</summary>
+        <value>The generated binary XAML (BAML) files.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
index 3d069fae3f0..1724c2a20c8 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class represents a key that can uniquely identify a localizable value inside [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)]. It represents a combination of a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A>, class name, and property name.  
+ This class represents a key that can uniquely identify a localizable value inside binary XAML (BAML). It represents a combination of a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A>, class name, and property name.  
   
  The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
   
@@ -67,7 +67,7 @@
       </Parameters>
       <Docs>
         <param name="uid">The Uid of an element that has a localizable resource.</param>
-        <param name="className">The class name of a localizable resource in [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)].</param>
+        <param name="className">The class name of a localizable resource in binary XAML (BAML).</param>
         <param name="propertyName">The property name of a localizable resource in BAML.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Markup.Localizer.BamlLocalizableResourceKey" /> class with the supplied Uid, class name, and property name.</summary>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows/EventSetter.xml b/xml/System.Windows/EventSetter.xml
index 59811196223..cb7562950cf 100644
--- a/xml/System.Windows/EventSetter.xml
+++ b/xml/System.Windows/EventSetter.xml
@@ -27,7 +27,7 @@
   
  Instances of the <xref:System.Windows.EventSetter> class are usually created through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], as an object element within a style defined through XAML. An <xref:System.Windows.EventSetter> might also be instantiated from code.  
   
- Event setters cannot be used in a style that is contained in a theme resource dictionary. This is because a theme resource dictionary at run time is often loose [!INCLUDE[TLA#tla_baml](~/includes/tlasharptla-baml-md.md)] files, and does not have any scope defined where accompanying code-behind that defines the handlers can exist.  
+ Event setters cannot be used in a style that is contained in a theme resource dictionary. This is because a theme resource dictionary at run time is often loose binary XAML (BAML) files, and does not have any scope defined where accompanying code-behind that defines the handlers can exist.  
   
  Handlers attached through event setters are invoked after any class handlers for an event, and also after any instance handlers. As a result, if a class handler or instance handler marks an event handled in its arguments, then the handler declared by an event setter is not invoked, unless the event setter specifically sets <xref:System.Windows.EventSetter.HandledEventsToo%2A> `true`.  
   

From 6571df65ecd0d4476acbd210aafd1e7154264ca9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:57:51 -0800
Subject: [PATCH 108/236] tlasharptla-bmp

---
 xml/System.Windows.Media.Imaging/BitmapEncoder.xml    | 2 +-
 xml/System.Windows.Media.Imaging/BitmapSource.xml     | 2 +-
 xml/System.Windows.Media.Imaging/BmpBitmapDecoder.xml | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
index a6eebde5447..670debd4789 100644
--- a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
@@ -273,7 +273,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images (and some older, non-standard [!INCLUDE[TLA#tla_bmp](~/includes/tlasharptla-bmp-md.md)] images) support palettes.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images (and some older, non-standard bitmap (BMP) images) support palettes.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index e8fc7411469..00813a88805 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of [!INCLUDE[TLA#tla_bmp](~/includes/tlasharptla-bmp-md.md)], [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)], [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)], [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Imaging/BmpBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BmpBitmapDecoder.xml
index 0ad7f17468d..cae610a4bbe 100644
--- a/xml/System.Windows.Media.Imaging/BmpBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BmpBitmapDecoder.xml
@@ -77,7 +77,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA#tla_bmp](~/includes/tlasharptla-bmp-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a bitmap (BMP) encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -124,7 +124,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA#tla_bmp](~/includes/tlasharptla-bmp-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a bitmap (BMP) encoded image.</exception>
       </Docs>
     </Member>
   </Members>

From 74528b4d1d76e35b5a0a562b3cae2e6577cc58fb Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:58:17 -0800
Subject: [PATCH 109/236] tlasharptla-bpp

---
 xml/System.Windows.Media/PixelFormats.xml | 34 +++++++++++------------
 1 file changed, 17 insertions(+), 17 deletions(-)

diff --git a/xml/System.Windows.Media/PixelFormats.xml b/xml/System.Windows.Media/PixelFormats.xml
index 76f4182900e..a15c85e3e96 100644
--- a/xml/System.Windows.Media/PixelFormats.xml
+++ b/xml/System.Windows.Media/PixelFormats.xml
@@ -38,7 +38,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr101010" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr101010" /> is a sRGB format with 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (blue, green, and red) is allocated 10 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr101010" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr101010" /> is a sRGB format with 32 bits per pixel (BPP). Each color channel (blue, green, and red) is allocated 10 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgr101010" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -74,13 +74,13 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr24" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr24" /> is a sRGB format with 24 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (blue, green, and red) is allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr24" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr24" /> is a sRGB format with 24 bits per pixel (BPP). Each color channel (blue, green, and red) is allocated 8 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgr24" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This format uses 24 bits of data per pixel (8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)] for each of the three primary colors blue, green, and red). This translates to 256 shades of each primary color to provide up to 16 million colors for each image. To display <xref:System.Windows.Media.PixelFormats.Bgr24%2A> images, the monitor and controller must be capable of displaying at least 32,000 colors.  
+ This format uses 24 bits of data per pixel (8 bits per pixel (BPP) for each of the three primary colors blue, green, and red). This translates to 256 shades of each primary color to provide up to 16 million colors for each image. To display <xref:System.Windows.Media.PixelFormats.Bgr24%2A> images, the monitor and controller must be capable of displaying at least 32,000 colors.  
   
 <a name="xamlAttributeUsage_Bgr24"></a>   
 ## XAML Attribute Usage  
@@ -111,7 +111,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr32" /> is a sRGB format with 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (blue, green, and red) is allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr32" /> is a sRGB format with 32 bits per pixel (BPP). Each color channel (blue, green, and red) is allocated 8 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgr32" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -147,7 +147,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr555" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr555" /> is a sRGB format with 16 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (blue, green, and red) is allocated 5 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr555" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr555" /> is a sRGB format with 16 bits per pixel (BPP). Each color channel (blue, green, and red) is allocated 5 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgr555" /> pixel format</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -183,7 +183,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr565" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr565" /> is a sRGB format with 16 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (blue, green, and red) is allocated 5, 6, and 5 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)] respectively.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgr565" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgr565" /> is a sRGB format with 16 bits per pixel (BPP). Each color channel (blue, green, and red) is allocated 5, 6, and 5 bits per pixel (BPP) respectively.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgr565" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -219,7 +219,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgra32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgra32" /> is a sRGB format with 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each channel (blue, green, red, and alpha) is allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Bgra32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Bgra32" /> is a sRGB format with 32 bits per pixel (BPP). Each channel (blue, green, red, and alpha) is allocated 8 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Bgra32" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -291,7 +291,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Cmyk32" /> pixel format which displays 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)] with each color channel (cyan, magenta, yellow, and black) allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Cmyk32" /> pixel format which displays 32 bits per pixel (BPP) with each color channel (cyan, magenta, yellow, and black) allocated 8 bits per pixel (BPP).</summary>
         <value>The CMYK32 pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -438,7 +438,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Gray32Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Gray32Float" /> displays a 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)] grayscale channel, allowing over 4 billion shades of gray. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Gray32Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Gray32Float" /> displays a 32 bits per pixel (BPP) grayscale channel, allowing over 4 billion shades of gray. This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Gray32Float" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -694,7 +694,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Pbgra32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Pbgra32" /> is a sRGB format with 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each channel (blue, green, red, and alpha) is allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is pre-multiplied by the alpha value.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Pbgra32" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Pbgra32" /> is a sRGB format with 32 bits per pixel (BPP). Each channel (blue, green, red, and alpha) is allocated 8 bits per pixel (BPP). Each color channel is pre-multiplied by the alpha value.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Pbgra32" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -730,7 +730,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Prgba128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Prgba128Float" /> is a ScRGB format with 128 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each channel (red, green, blue, and alpha) is allocated 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is pre-multiplied by the alpha value. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Prgba128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Prgba128Float" /> is a ScRGB format with 128 bits per pixel (BPP). Each channel (red, green, blue, and alpha) is allocated 32 bits per pixel (BPP). Each color channel is pre-multiplied by the alpha value. This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Prgba128Float" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -766,7 +766,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Prgba64" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Prgba64" /> is a sRGB format with 64 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each channel (blue, green, red, and alpha) is allocated 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is pre-multiplied by the alpha value. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Prgba64" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Prgba64" /> is a sRGB format with 64 bits per pixel (BPP). Each channel (blue, green, red, and alpha) is allocated 32 bits per pixel (BPP). Each color channel is pre-multiplied by the alpha value. This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Prgba64" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -802,7 +802,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> is a ScRGB format with 128 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is allocated 32 BPP. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> is a ScRGB format with 128 bits per pixel (BPP). Each color channel is allocated 32 BPP. This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgb128Float" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -838,7 +838,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb24" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb24" /> is a sRGB format with 24 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (red, green, and blue) is allocated 8 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)].</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb24" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb24" /> is a sRGB format with 24 bits per pixel (BPP). Each color channel (red, green, and blue) is allocated 8 bits per pixel (BPP).</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgb24" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -877,7 +877,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb48" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb48" /> is a sRGB format with 48 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel (red, green, and blue) is allocated 16 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgb48" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgb48" /> is a sRGB format with 48 bits per pixel (BPP). Each color channel (red, green, and blue) is allocated 16 bits per pixel (BPP). This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgb48" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -913,7 +913,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgba128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgba128Float" /> is a ScRGB format with 128 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each color channel is allocated 32 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgba128Float" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgba128Float" /> is a ScRGB format with 128 bits per pixel (BPP). Each color channel is allocated 32 bits per pixel (BPP). This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgba128Float" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -949,7 +949,7 @@
         <ReturnType>System.Windows.Media.PixelFormat</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgba64" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgba64" /> is an sRGB format with 64 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. Each channel (red, green, blue, and alpha) is allocated 16 [!INCLUDE[tla#tla_bpp](~/includes/tlasharptla-bpp-md.md)]. This format has a gamma of 1.0.</summary>
+        <summary>Gets the <see cref="P:System.Windows.Media.PixelFormats.Rgba64" /> pixel format. <see cref="P:System.Windows.Media.PixelFormats.Rgba64" /> is an sRGB format with 64 bits per pixel (BPP). Each channel (red, green, blue, and alpha) is allocated 16 bits per pixel (BPP). This format has a gamma of 1.0.</summary>
         <value>The <see cref="P:System.Windows.Media.PixelFormats.Rgba64" /> pixel format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From aab425e2f20e1357b741e46d3baee8a2035548ff Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:58:37 -0800
Subject: [PATCH 110/236] tlasharptla-caf

---
 xml/System.Windows.Annotations.Storage/XmlStreamStore.xml | 8 ++++----
 xml/ns-System.Windows.Annotations.xml                     | 2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml b/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
index b7626a8a293..2e66020fb13 100644
--- a/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
+++ b/xml/System.Windows.Annotations.Storage/XmlStreamStore.xml
@@ -55,7 +55,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `stream` must be in valid XML format and comply with the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)] schema.  
+ `stream` must be in valid XML format and comply with the Microsoft Annotations Framework schema.  
   
  ]]></format>
         </remarks>
@@ -445,7 +445,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `name` parameter works only for predefined [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)] namespaces.  For any other namespace given in the `name` parameter <xref:System.Windows.Annotations.Storage.XmlStreamStore.GetWellKnownCompatibleNamespaces%2A> will return `null`, even those namespaces registered through the `knownNamespaces` parameter of the <xref:System.Windows.Annotations.Storage.XmlStreamStore.%23ctor%2A> constructor.  
+ The `name` parameter works only for predefined Microsoft Annotations Framework namespaces.  For any other namespace given in the `name` parameter <xref:System.Windows.Annotations.Storage.XmlStreamStore.GetWellKnownCompatibleNamespaces%2A> will return `null`, even those namespaces registered through the `knownNamespaces` parameter of the <xref:System.Windows.Annotations.Storage.XmlStreamStore.%23ctor%2A> constructor.  
   
  The namespaces predefined by the Annotations Framework include the following:  
   
@@ -494,7 +494,7 @@
 ## Remarks  
  The <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> property will never return `null`, however the returned list can be empty if no namespaces are ignored.  
   
- <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> helps in XML markup compatibility when the program reads annotation content created by different versions of the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)].  When an older application is given annotation content created using a newer version of the Annotations Framework, <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> returns a list of the XML namespaces for elements and attributes not known to the older framework.  Unknown XML elements and attributes associated with newer namespaces are ignored when the annotation content is read and deserialized by the older application.  For more information see the *XML Markup Compatibility Specification* available at [https://go.microsoft.com/fwlink/?LinkId=73824](https://go.microsoft.com/fwlink/?LinkId=73824).  
+ <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> helps in XML markup compatibility when the program reads annotation content created by different versions of the Microsoft Annotations Framework.  When an older application is given annotation content created using a newer version of the Annotations Framework, <xref:System.Windows.Annotations.Storage.XmlStreamStore.IgnoredNamespaces%2A> returns a list of the XML namespaces for elements and attributes not known to the older framework.  Unknown XML elements and attributes associated with newer namespaces are ignored when the annotation content is read and deserialized by the older application.  For more information see the *XML Markup Compatibility Specification* available at [https://go.microsoft.com/fwlink/?LinkId=73824](https://go.microsoft.com/fwlink/?LinkId=73824).  
   
  ]]></format>
         </remarks>
@@ -548,7 +548,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets a list of all namespaces that are predefined by the Annotations Framework.</summary>
-        <value>The list of namespaces that are predefined by the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)].</value>
+        <value>The list of namespaces that are predefined by the Microsoft Annotations Framework.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/ns-System.Windows.Annotations.xml b/xml/ns-System.Windows.Annotations.xml
index 232425c12f0..bb2e4902787 100644
--- a/xml/ns-System.Windows.Annotations.xml
+++ b/xml/ns-System.Windows.Annotations.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Types in the <xref:System.Windows.Annotations> namespace are provided to support the management of user-created annotations on application data displayed in Windows Presentation Foundation document viewing controls.  Using the [!INCLUDE[TLA#tla_caf](~/includes/tlasharptla-caf-md.md)] applications can add support for user-created notes and highlights that are stored separate from the application document itself.  Since the user annotation information is stored separately from the document content, users can even add notes and highlights to read-only or rights-managed documents that cannot be physically changed.  
+ Types in the <xref:System.Windows.Annotations> namespace are provided to support the management of user-created annotations on application data displayed in Windows Presentation Foundation document viewing controls.  Using the Microsoft Annotations Framework applications can add support for user-created notes and highlights that are stored separate from the application document itself.  Since the user annotation information is stored separately from the document content, users can even add notes and highlights to read-only or rights-managed documents that cannot be physically changed.  
   
  The WPF document viewing controls that support user-annotation capabilities are based on <xref:System.Windows.Controls.Primitives.DocumentViewerBase> derived subclasses such as <xref:System.Windows.Controls.DocumentViewer>, <xref:System.Windows.Controls.FlowDocumentPageViewer>, and <xref:System.Windows.Controls.FlowDocumentScrollViewer> as well as <xref:System.Windows.Controls.FlowDocumentReader>.  
   

From 1fbebdcc4f6534e604b19d62ede665dd74fa0bdf Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:58:53 -0800
Subject: [PATCH 111/236] tlasharptla-cas

---
 xml/System.Windows.Markup/XamlReader.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index 85b893323bd..93e5e0b090c 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -41,7 +41,7 @@
 ## Code Access Security, Loose XAML, and XamlReader  
  XAML is a markup language that directly represents object instantiation and execution. Therefore, elements created in XAML have the same ability to interact with system resources (network access, file system IO, for example) as the equivalent generated code does.  
   
- WPF supports the .NET security framework [!INCLUDE[TLA#tla_cas](~/includes/tlasharptla-cas-md.md)]. This means that WPF content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
+ WPF supports the .NET security framework Code Access Security (CAS). This means that WPF content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
   
  The implications of these statements for <xref:System.Windows.Markup.XamlReader> is that your application design must make trust decisions about the XAML you decide to load. If you are loading XAML that is not trusted, consider implementing your own sandboxing technique for how you load the resulting object graph.  
   

From 4c4ce6fc141bbca4826676e00305f7a202c1d720 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:59:15 -0800
Subject: [PATCH 112/236] tlasharptla-clickonce

---
 xml/System.Windows/Application.xml | 2 +-
 xml/System.Windows/Window.xml      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index e130ba9d9d8..d40da0b467a 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -2171,7 +2171,7 @@ This example illustrates how to use XAML together with application-scope resourc
  [!code-csharp[ApplicationStartupSnippets#HandleStartupCODEBEHIND](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationStartupSnippets/CSharp/App.xaml.cs#handlestartupcodebehind)]
  [!code-vb[ApplicationStartupSnippets#HandleStartupCODEBEHIND](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationStartupSnippets/visualbasic/application.xaml.vb#handlestartupcodebehind)]  
   
- [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)] cannot retrieve and process command-line arguments because they are launched with [!INCLUDE[TLA#tla_clickonce](~/includes/tlasharptla-clickonce-md.md)] deployment (see [Deploying a WPF Application (WPF)](/dotnet/framework/wpf/app-development/deploying-a-wpf-application-wpf)). However, they can retrieve and process query string parameters from the URLs that are used to launch them.  
+ [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)] cannot retrieve and process command-line arguments because they are launched with ClickOnce deployment (see [Deploying a WPF Application (WPF)](/dotnet/framework/wpf/app-development/deploying-a-wpf-application-wpf)). However, they can retrieve and process query string parameters from the URLs that are used to launch them.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index 1e3e8f23271..4381f0cc356 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -63,7 +63,7 @@
   
  <xref:System.Windows.Window> needs `UnmanagedCode` security permission to be instantiated. This has the following consequences:  
   
--   [!INCLUDE[TLA#tla_clickonce](~/includes/tlasharptla-clickonce-md.md)]-deployed standalone applications will request permission elevation when launched from either the Internet or Local Intranet zones.  
+-   ClickOnce-deployed standalone applications will request permission elevation when launched from either the Internet or Local Intranet zones.  
   
 -   XBAPs that request anything less than full permissions will not be able to instantiate windows or dialog boxes.  
   

From 3a0fb22d1991501bb5f627df8a3adc1eb9104975 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 12:59:48 -0800
Subject: [PATCH 113/236] tlasharptla-clr

---
 .../ClassicBorderDecorator.xml                |   2 +-
 .../PlatformCulture.xml                       |   4 +-
 .../TextBoxBase.xml                           |   4 +-
 .../FlowDocumentPageViewer.xml                |   2 +-
 .../FlowDocumentReader.xml                    |   2 +-
 .../FlowDocumentScrollViewer.xml              |   2 +-
 .../ToolTipService.xml                        |   4 +-
 xml/System.Windows.Data/Binding.xml           |   4 +-
 xml/System.Windows.Input/Mouse.xml            |   8 +-
 xml/System.Windows.Interop/HwndSource.xml     |   2 +-
 .../NumberSubstitution.xml                    |   6 +-
 xml/System.Windows/ContentElement.xml         | 118 ++++++++---------
 xml/System.Windows/DataFormats.xml            |   4 +-
 xml/System.Windows/DependencyObjectType.xml   |   4 +-
 .../DependencyPropertyChangedEventArgs.xml    |   2 +-
 .../DependencyPropertyChangedEventHandler.xml |   2 +-
 xml/System.Windows/DependencyPropertyKey.xml  |   2 +-
 .../FrameworkContentElement.xml               |  10 +-
 xml/System.Windows/FrameworkElement.xml       |  16 +--
 .../HierarchicalDataTemplate.xml              |   2 +-
 xml/System.Windows/PropertyPath.xml           |   2 +-
 xml/System.Windows/RoutedEventHandler.xml     |   2 +-
 .../SourceChangedEventHandler.xml             |   2 +-
 xml/System.Windows/UIElement.xml              | 120 +++++++++---------
 xml/System.Windows/UIElement3D.xml            | 118 ++++++++---------
 25 files changed, 222 insertions(+), 222 deletions(-)

diff --git a/xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml b/xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml
index dce39082bf1..34b4dc70f45 100644
--- a/xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml
+++ b/xml/Microsoft.Windows.Themes/ClassicBorderDecorator.xml
@@ -370,7 +370,7 @@
  The [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension).  
   
  *theme*  
- An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] namespace in a specific assembly.  
+ An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> common language runtime (CLR) namespace in a specific assembly.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Windows.Themes/PlatformCulture.xml b/xml/Microsoft.Windows.Themes/PlatformCulture.xml
index 8fd523b9142..2890273dab8 100644
--- a/xml/Microsoft.Windows.Themes/PlatformCulture.xml
+++ b/xml/Microsoft.Windows.Themes/PlatformCulture.xml
@@ -60,7 +60,7 @@
  The [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension).
 
  *theme*
- An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] namespace in a specific assembly.
+ An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> common language runtime (CLR) namespace in a specific assembly.
 
  ]]></format>
     </remarks>
@@ -130,7 +130,7 @@
  The [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension).
 
  *theme*
- An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] namespace in a specific assembly.
+ An xmlns prefix mapping to the <xref:Microsoft.Windows.Themes> common language runtime (CLR) namespace in a specific assembly.
 
  <Grid
 
diff --git a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
index fe3ced9e958..058499a10d3 100644
--- a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
+++ b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
@@ -1381,7 +1381,7 @@ TextBox with CaretBrush set to blue
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it lets you handle the matching event from derived classes by using a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event might have been raised by a child element, which is not necessarily the element that invokes handlers. Therefore, your implementation needs to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.Primitives.TextBoxBase> can call private class handler methods when the event is received along the route. One scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it lets you handle the matching event from derived classes by using a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event might have been raised by a child element, which is not necessarily the element that invokes handlers. Therefore, your implementation needs to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.Primitives.TextBoxBase> can call private class handler methods when the event is received along the route. One scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
@@ -1827,7 +1827,7 @@ TextBox with CaretBrush set to blue
 ## Remarks  
  This method has no default implementation. Calling base() in your implementation is still recommended, in case an intermediate class in the inheritance implemented this method. You may call base() either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it lets you handle the matching event from derived classes by using a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, which is not necessarily the element that invokes handlers. Therefore, your implementation needs to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.Primitives.TextBoxBase> can choose to call private class handler methods when the event is received along the route. One scenario is to take the arguments of the event and mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it lets you handle the matching event from derived classes by using a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, which is not necessarily the element that invokes handlers. Therefore, your implementation needs to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.Primitives.TextBoxBase> can choose to call private class handler methods when the event is received along the route. One scenario is to take the arguments of the event and mark the event as handled.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
index c137ae17462..2654976a774 100644
--- a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
@@ -767,7 +767,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event might have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentPageViewer> could call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case, the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event might have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentPageViewer> could call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/FlowDocumentReader.xml b/xml/System.Windows.Controls/FlowDocumentReader.xml
index fac84faf87d..44444087dc1 100644
--- a/xml/System.Windows.Controls/FlowDocumentReader.xml
+++ b/xml/System.Windows.Controls/FlowDocumentReader.xml
@@ -1588,7 +1588,7 @@
   
  This method has no default implementation. Calling base() in your implementation is still recommended, in case an intermediate class in the inheritance implemented this method. You may call base() either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentReader> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentReader> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and mark the event as handled.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
index c51ad2f82c8..212aaec05e9 100644
--- a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
@@ -1042,7 +1042,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentScrollViewer> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.Controls.FlowDocumentScrollViewer> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/ToolTipService.xml b/xml/System.Windows.Controls/ToolTipService.xml
index 358d76c4cd0..1cb680ded03 100644
--- a/xml/System.Windows.Controls/ToolTipService.xml
+++ b/xml/System.Windows.Controls/ToolTipService.xml
@@ -2073,7 +2073,7 @@ This is an attached property. For information about how to get the value of this
 ## Remarks  
  The <xref:System.Windows.Controls.ToolTipService.ToolTipClosing> event occurs immediately before a tooltip closes.  
   
- This field registers the behavior of the <xref:System.Windows.Controls.ToolTipService.ToolTipClosingEvent> event for classes that use this service. The <xref:System.Windows.FrameworkElement> and <xref:System.Windows.FrameworkContentElement> classes both implement the <xref:System.Windows.Controls.ToolTipService> and expose this event through the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] accessors <xref:System.Windows.FrameworkElement.ToolTipClosing?displayProperty=nameWithType> and <xref:System.Windows.FrameworkContentElement.ToolTipClosing?displayProperty=nameWithType>.  
+ This field registers the behavior of the <xref:System.Windows.Controls.ToolTipService.ToolTipClosingEvent> event for classes that use this service. The <xref:System.Windows.FrameworkElement> and <xref:System.Windows.FrameworkContentElement> classes both implement the <xref:System.Windows.Controls.ToolTipService> and expose this event through the common language runtime (CLR) accessors <xref:System.Windows.FrameworkElement.ToolTipClosing?displayProperty=nameWithType> and <xref:System.Windows.FrameworkContentElement.ToolTipClosing?displayProperty=nameWithType>.  
   
  If you specify the tooltip as a <xref:System.Windows.Controls.ToolTip> object, the <xref:System.Windows.Controls.ToolTip.Closed> event is also raised when the tooltip closes.  
   
@@ -2141,7 +2141,7 @@ This is an attached property. For information about how to get the value of this
 ## Remarks  
  The <xref:System.Windows.Controls.ToolTipService.ToolTipOpening> event occurs immediately before a tooltip opens. This event does not occur if the tooltip is not defined or if the tooltip content is set to null.  
   
- This field registers the behavior of the <xref:System.Windows.Controls.ToolTipService.ToolTipOpening> event for classes that use this service. The <xref:System.Windows.FrameworkElement> and <xref:System.Windows.FrameworkContentElement> classes both implement the <xref:System.Windows.Controls.ToolTipService> and expose this event through the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] accessors <xref:System.Windows.FrameworkElement.ToolTipOpening?displayProperty=nameWithType> and <xref:System.Windows.FrameworkContentElement.ToolTipOpening?displayProperty=nameWithType>.  
+ This field registers the behavior of the <xref:System.Windows.Controls.ToolTipService.ToolTipOpening> event for classes that use this service. The <xref:System.Windows.FrameworkElement> and <xref:System.Windows.FrameworkContentElement> classes both implement the <xref:System.Windows.Controls.ToolTipService> and expose this event through the common language runtime (CLR) accessors <xref:System.Windows.FrameworkElement.ToolTipOpening?displayProperty=nameWithType> and <xref:System.Windows.FrameworkContentElement.ToolTipOpening?displayProperty=nameWithType>.  
   
  If you specify the tooltip as a <xref:System.Windows.Controls.ToolTip> object, the <xref:System.Windows.Controls.ToolTip.Opened> event is also raised when the tooltip opens.  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 2bf21e6bd50..54a35b8b036 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -1631,9 +1631,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When the binding source is [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data instead of a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, the <xref:System.Windows.Data.Binding.XPath%2A> property is used instead of the <xref:System.Windows.Data.Binding.Path%2A> property to indicate the path to the value on the binding source to use.  
+ When the binding source is [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data instead of a common language runtime (CLR) object, the <xref:System.Windows.Data.Binding.XPath%2A> property is used instead of the <xref:System.Windows.Data.Binding.Path%2A> property to indicate the path to the value on the binding source to use.  
   
- By setting the <xref:System.Windows.Data.Binding.XPath%2A> property, you are creating an `XPath` query to select a node or a collection of nodes (<xref:System.Xml.XmlElement?displayProperty=nameWithType> and <xref:System.Xml.XmlAttribute?displayProperty=nameWithType> both derive from <xref:System.Xml.XmlNode?displayProperty=nameWithType>). <xref:System.Xml.XmlNode?displayProperty=nameWithType> is a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, which means you can bind to its properties using the <xref:System.Windows.Data.Binding.Path%2A> property.  
+ By setting the <xref:System.Windows.Data.Binding.XPath%2A> property, you are creating an `XPath` query to select a node or a collection of nodes (<xref:System.Xml.XmlElement?displayProperty=nameWithType> and <xref:System.Xml.XmlAttribute?displayProperty=nameWithType> both derive from <xref:System.Xml.XmlNode?displayProperty=nameWithType>). <xref:System.Xml.XmlNode?displayProperty=nameWithType> is a common language runtime (CLR) object, which means you can bind to its properties using the <xref:System.Windows.Data.Binding.Path%2A> property.  
   
  The <xref:System.Xml.XmlNode.SelectNodes%2A?displayProperty=nameWithType> method handles the `XPath` expressions from the <xref:System.Windows.Data.Binding.XPath%2A> property. `XPath` functions are not supported. For `XPath` expression information, see the <xref:System.Xml.XmlNode.SelectNodes%2A> documentation and some examples provided in the Example section.  
   
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 1a422abea1a..34d5a1302ca 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -959,7 +959,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
+ The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
   
 > [!IMPORTANT]
 >  A few <xref:System.Windows.ContentElement> derived classes that have control-like behavior, for example, <xref:System.Windows.Documents.Hyperlink>, might have inherent class handling for mouse button events. The left mouse button down event is the most likely event to have class handling in a control. The class handling often marks the underlying <xref:System.Windows.Input.Mouse> class event as handled. Once the event is marked handled, other instance handlers that are attached to that element are not ordinarily raised. Any other class or instance handlers that are attached to elements in the bubbling direction towards the root in the UI tree are also not ordinarily raised.  
@@ -1236,7 +1236,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
+ The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events all along the route.  
   
@@ -1448,7 +1448,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
+ The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
@@ -1651,7 +1651,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
+ The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
diff --git a/xml/System.Windows.Interop/HwndSource.xml b/xml/System.Windows.Interop/HwndSource.xml
index 62286d8966e..dc88d940822 100644
--- a/xml/System.Windows.Interop/HwndSource.xml
+++ b/xml/System.Windows.Interop/HwndSource.xml
@@ -69,7 +69,7 @@
   
  **Object Lifetime**  
   
- An <xref:System.Windows.Interop.HwndSource> is a regular [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, and its lifetime is managed by the garbage collector. Because the <xref:System.Windows.Interop.HwndSource> represents an unmanaged resource, <xref:System.Windows.Interop.HwndSource> implements <xref:System.IDisposable>. Synchronously calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> immediately destroys the Win32 window if called from the owner thread. If called from another thread, the Win32 window is destroyed asynchronously. Calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> explicitly from the interoperating code might be necessary for certain interoperation scenarios.  
+ An <xref:System.Windows.Interop.HwndSource> is a regular common language runtime (CLR) object, and its lifetime is managed by the garbage collector. Because the <xref:System.Windows.Interop.HwndSource> represents an unmanaged resource, <xref:System.Windows.Interop.HwndSource> implements <xref:System.IDisposable>. Synchronously calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> immediately destroys the Win32 window if called from the owner thread. If called from another thread, the Win32 window is destroyed asynchronously. Calling <xref:System.Windows.Interop.HwndSource.Dispose%2A> explicitly from the interoperating code might be necessary for certain interoperation scenarios.  
   
  **Window Procedures**  
   
diff --git a/xml/System.Windows.Media/NumberSubstitution.xml b/xml/System.Windows.Media/NumberSubstitution.xml
index 6bbddd99c0a..6dd9161d30f 100644
--- a/xml/System.Windows.Media/NumberSubstitution.xml
+++ b/xml/System.Windows.Media/NumberSubstitution.xml
@@ -136,7 +136,7 @@ Example of the appearance of digits in different cultures
   
  This reference page represents two identically named but not entirely equivalent usages for the <xref:System.Windows.Media.NumberSubstitution.CultureOverride%2A> property:  
   
--   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
+-   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a common language runtime (CLR) property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
 -   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.CultureOverride**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is one of the string-format values as explained in XAML Values. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureOverride%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureOverride%2A>.  
   
@@ -220,7 +220,7 @@ Example of the appearance of digits in different cultures
   
  This reference page represents two identically named but not entirely equivalent usages for the <xref:System.Windows.Media.NumberSubstitution.CultureSource%2A> property:  
   
--   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
+-   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a common language runtime (CLR) property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
 -   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.CultureSource**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberCultureSource> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetCultureSource%2A> and <xref:System.Windows.Media.NumberSubstitution.SetCultureSource%2A>.  
   
@@ -548,7 +548,7 @@ Example of the appearance of digits in different cultures
   
  This reference page represents two identically named but not entirely equivalent usages for the <xref:System.Windows.Media.NumberSubstitution.Substitution%2A> property:  
   
--   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
+-   You can set this property in code on a <xref:System.Windows.Media.NumberSubstitution> instance, as a common language runtime (CLR) property. In this usage, the property is not backed by a dependency property identifier, it is backed by a private field and does not act as a dependency property.  
   
 -   You can set this property as an attached property usage in XAML. The attached property usage is the reason why this property has a Dependency Property Information section, because the attached property is backed by a dependency property identifier. In XAML, the usage is `<`*object* **NumberSubstitution.Substitution**`="`*value*`".../>`, where *object* is an object element where the specified number substitution logic applies, and *value* is a string representation of a <xref:System.Windows.Media.NumberSubstitutionMethod> value. In code, the attached property usage is supported by <xref:System.Windows.Media.NumberSubstitution.GetSubstitution%2A> and <xref:System.Windows.Media.NumberSubstitution.SetSubstitution%2A>.  
   
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index 995b4e19a5b..cae4fa8be02 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -4569,7 +4569,7 @@ The implementation of this method is typically to call the constructor of a spec
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4607,7 +4607,7 @@ The implementation of this method is typically to call the constructor of a spec
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4645,7 +4645,7 @@ The implementation of this method is typically to call the constructor of a spec
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4683,7 +4683,7 @@ The implementation of this method is typically to call the constructor of a spec
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4721,7 +4721,7 @@ The implementation of this method is typically to call the constructor of a spec
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4807,7 +4807,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4845,7 +4845,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4883,7 +4883,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5231,7 +5231,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5271,7 +5271,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5353,7 +5353,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5391,7 +5391,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5429,7 +5429,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5507,7 +5507,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5545,7 +5545,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -5581,7 +5581,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -5689,7 +5689,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5807,7 +5807,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5844,7 +5844,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5882,7 +5882,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -5920,7 +5920,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -5958,7 +5958,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -5996,7 +5996,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6034,7 +6034,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6072,7 +6072,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6110,7 +6110,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6148,7 +6148,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6186,7 +6186,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6232,7 +6232,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6342,7 +6342,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6460,7 +6460,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6498,7 +6498,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6536,7 +6536,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6574,7 +6574,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6612,7 +6612,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6650,7 +6650,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6688,7 +6688,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6726,7 +6726,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6764,7 +6764,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6802,7 +6802,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6840,7 +6840,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6878,7 +6878,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6916,7 +6916,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7051,7 +7051,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7089,7 +7089,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7127,7 +7127,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7165,7 +7165,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7203,7 +7203,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7241,7 +7241,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -7277,7 +7277,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7315,7 +7315,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7353,7 +7353,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -7389,7 +7389,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7427,7 +7427,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7465,7 +7465,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7503,7 +7503,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7541,7 +7541,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On\* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On\* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.ContentElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -10291,7 +10291,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
 ## Remarks  
  The `e` parameter is typed as the common base type for all routed event data; however, the event data should be given as the most specific event data type that is available for the event being raised, because <xref:System.Windows.RoutedEventArgs> derived classes contain the actual specific data properties that are intended for the specific event when it is raised.  
   
- <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events and data classes, which typically just contain properties that are related to the event.  
+ <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from common language runtime (CLR) events and data classes, which typically just contain properties that are related to the event.  
   
    
   
@@ -10463,7 +10463,7 @@ Note that by default a <xref:System.Windows.ContentElement.Focusable> is not foc
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
+ The most common scenario for using this API is when you implement the common language runtime (CLR) "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
   
  Calling this method has no effect if there were no handlers registered with criteria that match the input parameters for the method call.  
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 23c513715f8..6bb99b61cdb 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -42,7 +42,7 @@
 |<xref:System.Windows.DataFormats.Riff>|"RiffAudio"|Specifies the [!INCLUDE[TLA#tla_riff](~/includes/tlasharptla-riff-md.md)] audio data format.|  
 |<xref:System.Windows.DataFormats.Rtf>|"Rich Text Format"|Specifies the [!INCLUDE[TLA#tla_rtf](~/includes/tlasharptla-rtf-md.md)] data format.|  
 |<xref:System.Windows.DataFormats.Serializable>|"PersistentObject"|Specifies a data format that encapsulates any type of serializable data objects.|  
-|<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] string class data format.|  
+|<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the common language runtime (CLR) string class data format.|  
 |<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] symbolic link data format.|  
 |<xref:System.Windows.DataFormats.Text>|"Text"|Specifies the ANSI text data format.|  
 |<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] data format.|  
@@ -670,7 +670,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] string class data format.</summary>
+        <summary>Specifies the common language runtime (CLR) string class data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/DependencyObjectType.xml b/xml/System.Windows/DependencyObjectType.xml
index c7326c9ada2..d3352d18040 100644
--- a/xml/System.Windows/DependencyObjectType.xml
+++ b/xml/System.Windows/DependencyObjectType.xml
@@ -249,7 +249,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the name of the represented [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] system type.</summary>
+        <summary>Gets the name of the represented common language runtime (CLR) system type.</summary>
         <value>The name of the represented CLR system type.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -286,7 +286,7 @@
         <ReturnType>System.Type</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</summary>
+        <summary>Gets the common language runtime (CLR) system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</summary>
         <value>The CLR system type represented by this <see cref="T:System.Windows.DependencyObjectType" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows/DependencyPropertyChangedEventArgs.xml b/xml/System.Windows/DependencyPropertyChangedEventArgs.xml
index 3e3f412ce64..9e0c9955140 100644
--- a/xml/System.Windows/DependencyPropertyChangedEventArgs.xml
+++ b/xml/System.Windows/DependencyPropertyChangedEventArgs.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The events that use the <xref:System.Windows.DependencyPropertyChangedEventArgs> class for event data, and the <xref:System.Windows.DependencyPropertyChangedEventHandler> method implementations for handlers, generally follow the naming pattern `Is*Changed`, and are generally implemented as [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events without <xref:System.Windows.RoutedEvent> backing (they are not routed events). Some class handling methods that "handle" otherwise unexposed events that report a state change through a property change, such as <xref:System.Windows.Controls.Primitives.ButtonBase.OnIsPressedChanged%2A?displayProperty=nameWithType>, also use the <xref:System.Windows.DependencyPropertyChangedEventArgs> class for event data.  
+ The events that use the <xref:System.Windows.DependencyPropertyChangedEventArgs> class for event data, and the <xref:System.Windows.DependencyPropertyChangedEventHandler> method implementations for handlers, generally follow the naming pattern `Is*Changed`, and are generally implemented as common language runtime (CLR) events without <xref:System.Windows.RoutedEvent> backing (they are not routed events). Some class handling methods that "handle" otherwise unexposed events that report a state change through a property change, such as <xref:System.Windows.Controls.Primitives.ButtonBase.OnIsPressedChanged%2A?displayProperty=nameWithType>, also use the <xref:System.Windows.DependencyPropertyChangedEventArgs> class for event data.  
   
  The scenario for <xref:System.Windows.PropertyChangedCallback> is to use the arguments to report old and new values that come from the property system evaluation of the property. A callback that processes old and new values might choose special handling depending on these values, such as choosing to not respond to value changes that are deemed insignificant.  
   
diff --git a/xml/System.Windows/DependencyPropertyChangedEventHandler.xml b/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
index 71fa419476c..6d1f1352736 100644
--- a/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
+++ b/xml/System.Windows/DependencyPropertyChangedEventHandler.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  This delegate is the handler signature for particular events that report dependency property changes.  
   
- An event that uses this handler is exposed as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event, not as a routed event. Typically these events follow the naming pattern `Is(`*PropertyName*`)Changed`, where *PropertyName* is the <xref:System.Windows.DependencyProperty.Name%2A?displayProperty=nameWithType> of the property that changed. The arguments of the event are used to query the old and new value of the property, as reported by the particular event. Typically there is a 1:1 correspondence between properties that change and a particular event that reports the change. It is also possible, though uncommon, to have the same event report changes to more than one property. In this case, the <xref:System.Windows.DependencyPropertyChangedEventArgs> should be checked to determine the property that changed.  
+ An event that uses this handler is exposed as a common language runtime (CLR) event, not as a routed event. Typically these events follow the naming pattern `Is(`*PropertyName*`)Changed`, where *PropertyName* is the <xref:System.Windows.DependencyProperty.Name%2A?displayProperty=nameWithType> of the property that changed. The arguments of the event are used to query the old and new value of the property, as reported by the particular event. Typically there is a 1:1 correspondence between properties that change and a particular event that reports the change. It is also possible, though uncommon, to have the same event report changes to more than one property. In this case, the <xref:System.Windows.DependencyPropertyChangedEventArgs> should be checked to determine the property that changed.  
   
  The event data class <xref:System.Windows.DependencyPropertyChangedEventArgs> has a wider usage than just this delegate. <xref:System.Windows.DependencyPropertyChangedEventArgs> is also used to communicate data for <xref:System.Windows.PropertyChangedCallback> implementations, which are part of the customization features and internals of the WPF property system, and by the <xref:System.Windows.DependencyObject.OnPropertyChanged%2A> virtual method, which can be overridden to provide class-specific notifications whenever any dependency property on the object changes.  
   
diff --git a/xml/System.Windows/DependencyPropertyKey.xml b/xml/System.Windows/DependencyPropertyKey.xml
index 62cfb8de0ab..3e2a64d88ab 100644
--- a/xml/System.Windows/DependencyPropertyKey.xml
+++ b/xml/System.Windows/DependencyPropertyKey.xml
@@ -25,7 +25,7 @@
   
  The types that register a dependency property can use the <xref:System.Windows.DependencyPropertyKey> in calls to <xref:System.Windows.DependencyObject.SetValue%2A> and <xref:System.Windows.DependencyObject.ClearValue%2A> that adjust the property's value as part of class logic. If permitted by the access level of the key, related classes can use the key and the dependency property also. For instance, you can declare the key as internal, and other types within the same assembly can also set that dependency property.  
   
- The <xref:System.Windows.DependencyPropertyKey> returned by read-only dependency property registration should not be made public, because exposing the key makes the property settable, thus defeating the point of registering it as a read-only dependency property. Also, exposing the key causes a mismatch between the available dependency property behaviors and its [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property wrapper implementations, which is bad class design.  
+ The <xref:System.Windows.DependencyPropertyKey> returned by read-only dependency property registration should not be made public, because exposing the key makes the property settable, thus defeating the point of registering it as a read-only dependency property. Also, exposing the key causes a mismatch between the available dependency property behaviors and its common language runtime (CLR) property wrapper implementations, which is bad class design.  
   
  Instead of exposing the key itself, you should instead expose the <xref:System.Windows.DependencyPropertyKey.DependencyProperty%2A> value of the <xref:System.Windows.DependencyPropertyKey> as a `public static readonly`<xref:System.Windows.DependencyProperty> on your class. This enables the property to return a valid dependency property identifier for certain property system operations such as enumerating locally set values. However, the identifier thus obtained does not have the full capabilities of a <xref:System.Windows.DependencyProperty> for many property system operations.  
   
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 7ef2a157bfe..9e8658f10cd 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -763,7 +763,7 @@
 ## Remarks  
  *Data context* is a concept that allows elements to inherit information from their parent elements about the binding source that is used for binding, as well as other characteristics of the binding such as the path.  
   
- Data context can be set directly to a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object, with the bindings evaluating to properties of that object. Alternatively, you can set the data context to a <xref:System.Windows.Data.DataSourceProvider> object.  
+ Data context can be set directly to a common language runtime (CLR) object, with the bindings evaluating to properties of that object. Alternatively, you can set the data context to a <xref:System.Windows.Data.DataSourceProvider> object.  
   
  This dependency property inherits property values. If there are child elements with no other value for <xref:System.Windows.FrameworkContentElement.DataContext%2A> established through local values or styles, the property system will set the value to be the <xref:System.Windows.FrameworkContentElement.DataContext%2A> value of the nearest parent element with this value assigned.  
   
@@ -1779,7 +1779,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers. Therefore, your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers. Therefore, your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
   
  ]]></format>
         </remarks>
@@ -1814,7 +1814,7 @@
 ## Remarks  
  This method has no default implementation. You should still call base() in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
   
  ]]></format>
         </remarks>
@@ -2006,7 +2006,7 @@
 ## Remarks  
  This method has no default implementation. You should still call base() in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will have to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
   
  ]]></format>
         </remarks>
@@ -2041,7 +2041,7 @@
 ## Remarks  
  This method has no default implementation. You should still call base() in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkContentElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 4708067d60a..4d0e526f7d5 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -1530,7 +1530,7 @@
   
  This property is not automatically set as part of any application culture information, because an element might contain content that is not necessarily intended to obey the general flow direction implied by the culture information. For more information on globalization considerations, see [Globalization for WPF](/dotnet/framework/wpf/advanced/globalization-for-wpf).  
   
- This property has a defined [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property accessor, so it functions as a dependency property. However, it is also registered as attached, so it can also function as an attached property. The attached registration is mainly so that property value inheritance is supported, but the property can also be used as a true attached property. The attached property usage is only relevant if the object you intend to set the flow direction on has a <xref:System.Windows.FrameworkElement> parent element that performs layout upon it, is itself not a <xref:System.Windows.FrameworkElement>, and does not already have a more directly defined `FlowDirection` property. (Some of the flow document classes such as <xref:System.Windows.Documents.Block> and <xref:System.Windows.Documents.Inline> define their own `FlowDirection`, and this property can also set the flow direction. The property value is then read by the eventual content host without requiring attached property usage.)  
+ This property has a defined common language runtime (CLR) property accessor, so it functions as a dependency property. However, it is also registered as attached, so it can also function as an attached property. The attached registration is mainly so that property value inheritance is supported, but the property can also be used as a true attached property. The attached property usage is only relevant if the object you intend to set the flow direction on has a <xref:System.Windows.FrameworkElement> parent element that performs layout upon it, is itself not a <xref:System.Windows.FrameworkElement>, and does not already have a more directly defined `FlowDirection` property. (Some of the flow document classes such as <xref:System.Windows.Documents.Block> and <xref:System.Windows.Documents.Inline> define their own `FlowDirection`, and this property can also set the flow direction. The property value is then read by the eventual content host without requiring attached property usage.)  
   
 <a name="xamlAttributeUsage_FlowDirection"></a>   
 ## XAML Attribute Usage  
@@ -1796,7 +1796,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The main purpose of this method is to support attached property syntax for the <xref:System.Windows.FrameworkElement.FlowDirection%2A> property, therefore allowing child elements of a provided <xref:System.Windows.FrameworkElement> to specify flow direction for the arrangement within their parent element. To get the value on the current <xref:System.Windows.FrameworkElement>, use the direct [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] accessor <xref:System.Windows.FrameworkElement.FlowDirection%2A>.  
+ The main purpose of this method is to support attached property syntax for the <xref:System.Windows.FrameworkElement.FlowDirection%2A> property, therefore allowing child elements of a provided <xref:System.Windows.FrameworkElement> to specify flow direction for the arrangement within their parent element. To get the value on the current <xref:System.Windows.FrameworkElement>, use the direct common language runtime (CLR) accessor <xref:System.Windows.FrameworkElement.FlowDirection%2A>.  
   
  ]]></format>
         </remarks>
@@ -3463,7 +3463,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
@@ -3498,7 +3498,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
@@ -3570,7 +3570,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This particular On* method is not a class handler hook. Nor does it exactly follow the established [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] On* method convention that the matching event could be suppressed by overriding this method and not calling the base implementation.  
+ This particular On* method is not a class handler hook. Nor does it exactly follow the established common language runtime (CLR) On* method convention that the matching event could be suppressed by overriding this method and not calling the base implementation.  
   
  Note that the <xref:System.Windows.FrameworkElement.IsInitialized%2A> property is read-only, so you cannot set <xref:System.Windows.FrameworkElement.IsInitialized%2A> to force initialization behavior. Setting the initialization state is intended to be done only by the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework.  
   
@@ -3739,7 +3739,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled.  
   
  ]]></format>
         </remarks>
@@ -3774,7 +3774,7 @@
 ## Remarks  
  This method has no default implementation. You should still call the base implementation in case an intermediate class in the inheritance has implemented this method.  
   
- The purpose of this method is somewhat similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
+ The purpose of this method is somewhat similar to common language runtime (CLR) event pattern On* methods: it provides the means to handle the matching event from derived classes with a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because the routed event may have been raised by a child element, not necessarily the element that will invoke handlers, so your implementation will need to take the event arguments' source properties into account (and should not try to re-raise the event in most cases). Subclasses of <xref:System.Windows.FrameworkElement> could choose to call private class handler methods when the event is received along the route. One potential scenario is to take the arguments of the event and deliberately mark the event as handled to shorten the route.  
   
  ]]></format>
         </remarks>
@@ -4356,7 +4356,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports attached property syntax for the <xref:System.Windows.FrameworkElement.FlowDirection%2A> property, therefore allowing child elements of a provided <xref:System.Windows.FrameworkElement> to specify flow direction for the arrangement within their parent element. To set the value on the current <xref:System.Windows.FrameworkElement>, use the direct [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] accessor <xref:System.Windows.FrameworkElement.FlowDirection%2A>.  
+ This method supports attached property syntax for the <xref:System.Windows.FrameworkElement.FlowDirection%2A> property, therefore allowing child elements of a provided <xref:System.Windows.FrameworkElement> to specify flow direction for the arrangement within their parent element. To set the value on the current <xref:System.Windows.FrameworkElement>, use the direct common language runtime (CLR) accessor <xref:System.Windows.FrameworkElement.FlowDirection%2A>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/HierarchicalDataTemplate.xml b/xml/System.Windows/HierarchicalDataTemplate.xml
index 71f3eb78ecc..3918b63e74c 100644
--- a/xml/System.Windows/HierarchicalDataTemplate.xml
+++ b/xml/System.Windows/HierarchicalDataTemplate.xml
@@ -97,7 +97,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `dataType` parameter is either a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] object or a string representing an XML element. For more information, see [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
+ The `dataType` parameter is either a common language runtime (CLR) object or a string representing an XML element. For more information, see [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/PropertyPath.xml b/xml/System.Windows/PropertyPath.xml
index 9f3081d23a5..850b0b9de2f 100644
--- a/xml/System.Windows/PropertyPath.xml
+++ b/xml/System.Windows/PropertyPath.xml
@@ -81,7 +81,7 @@
         <Parameter Name="parameter" Type="System.Object" />
       </Parameters>
       <Docs>
-        <param name="parameter">A property path that either describes a path to a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property, or a single dependency property.</param>
+        <param name="parameter">A property path that either describes a path to a common language runtime (CLR) property, or a single dependency property.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.PropertyPath" /> class.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/RoutedEventHandler.xml b/xml/System.Windows/RoutedEventHandler.xml
index 680a3a9c5c2..b81807d296e 100644
--- a/xml/System.Windows/RoutedEventHandler.xml
+++ b/xml/System.Windows/RoutedEventHandler.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  The <xref:System.Windows.RoutedEventHandler> delegate is used for any routed event that does not report event-specific information in the event data. There are many such routed events; prominent examples include <xref:System.Windows.Controls.Primitives.ButtonBase.Click> and <xref:System.Windows.FrameworkElement.Loaded>.  
   
- The most noteworthy difference between writing a handler for a routed event as opposed to a general [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event is that the `sender` of the event (the element where the handler is attached and invoked) cannot be considered to necessarily be the source of the event. The source is reported as a property in the event data (<xref:System.Windows.RoutedEventArgs.Source%2A>). A difference between `sender` and <xref:System.Windows.RoutedEventArgs.Source%2A> is the result of the event being routed to different elements, during the traversal of the routed event through an element tree.  
+ The most noteworthy difference between writing a handler for a routed event as opposed to a general common language runtime (CLR) event is that the `sender` of the event (the element where the handler is attached and invoked) cannot be considered to necessarily be the source of the event. The source is reported as a property in the event data (<xref:System.Windows.RoutedEventArgs.Source%2A>). A difference between `sender` and <xref:System.Windows.RoutedEventArgs.Source%2A> is the result of the event being routed to different elements, during the traversal of the routed event through an element tree.  
   
  You can use either `sender` or <xref:System.Windows.RoutedEventArgs.Source%2A> for an object reference if you are deliberately not interested in the routing behavior of a direct or bubbling routed event and you only intend to handle routed events on the elements where they are first raised. In this circumstance, `sender` and <xref:System.Windows.RoutedEventArgs.Source%2A> are the same object.  
   
diff --git a/xml/System.Windows/SourceChangedEventHandler.xml b/xml/System.Windows/SourceChangedEventHandler.xml
index 894b6a2f98a..8d25bfb8f71 100644
--- a/xml/System.Windows/SourceChangedEventHandler.xml
+++ b/xml/System.Windows/SourceChangedEventHandler.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The "SourceChanged" event that this delegate represents handlers for is not exposed as a public [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event, as is the case with most routed events. Instead, "SourceChanged" is a routed event that remains private to the WPF infrastructure and is direct routed. Because it is direct routed, `sender` and the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event data are always the same object. You can add and remove handlers to this event despite the private access level of the event itself by using the public methods <xref:System.Windows.PresentationSource.AddSourceChangedHandler%2A> and <xref:System.Windows.PresentationSource.RemoveSourceChangedHandler%2A>.  
+ The "SourceChanged" event that this delegate represents handlers for is not exposed as a public common language runtime (CLR) event, as is the case with most routed events. Instead, "SourceChanged" is a routed event that remains private to the WPF infrastructure and is direct routed. Because it is direct routed, `sender` and the <xref:System.Windows.RoutedEventArgs.Source%2A> in the event data are always the same object. You can add and remove handlers to this event despite the private access level of the event itself by using the public methods <xref:System.Windows.PresentationSource.AddSourceChangedHandler%2A> and <xref:System.Windows.PresentationSource.RemoveSourceChangedHandler%2A>.  
   
  The `sender` of the event will be a derived class of <xref:System.Windows.PresentationSource>.  
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 2ae25b1ce24..983495fe00e 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -1900,7 +1900,7 @@ Image with an Elliptical Clip Region
   
 -   A style or template is applied to an element, which sets that dependency property value differently.  
   
- For example, the apparent "default" of <xref:System.Windows.UIElement.Focusable%2A> for a <xref:System.Windows.Controls.Button> control will be `true`, even though <xref:System.Windows.Controls.Button> inherits <xref:System.Windows.UIElement.Focusable%2A> as a [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] property directly from <xref:System.Windows.UIElement>. This is because the applied metadata value for the <xref:System.Windows.UIElement.Focusable%2A> dependency property was overridden within the static constructor of the <xref:System.Windows.Controls.Control> base class, which is situated between <xref:System.Windows.Controls.Button> and <xref:System.Windows.UIElement> in the class hierarchy.  
+ For example, the apparent "default" of <xref:System.Windows.UIElement.Focusable%2A> for a <xref:System.Windows.Controls.Button> control will be `true`, even though <xref:System.Windows.Controls.Button> inherits <xref:System.Windows.UIElement.Focusable%2A> as a common language runtime (CLR) property directly from <xref:System.Windows.UIElement>. This is because the applied metadata value for the <xref:System.Windows.UIElement.Focusable%2A> dependency property was overridden within the static constructor of the <xref:System.Windows.Controls.Control> base class, which is situated between <xref:System.Windows.Controls.Button> and <xref:System.Windows.UIElement> in the class hierarchy.  
   
  When inherited by <xref:System.Windows.Controls.Control> or its derived classes, <xref:System.Windows.Controls.Control> redefines the default value of this property to be `true`.  
   
@@ -6475,7 +6475,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6513,7 +6513,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6551,7 +6551,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6589,7 +6589,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6627,7 +6627,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6711,7 +6711,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6749,7 +6749,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6787,7 +6787,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7135,7 +7135,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7175,7 +7175,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7257,7 +7257,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7295,7 +7295,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7333,7 +7333,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7603,7 +7603,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7641,7 +7641,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -7677,7 +7677,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -7785,7 +7785,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7903,7 +7903,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7940,7 +7940,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7978,7 +7978,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8016,7 +8016,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8054,7 +8054,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8092,7 +8092,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8130,7 +8130,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8168,7 +8168,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8206,7 +8206,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8244,7 +8244,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8282,7 +8282,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8328,7 +8328,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8438,7 +8438,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8556,7 +8556,7 @@ Image with an Elliptical Clip Region
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -8594,7 +8594,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8632,7 +8632,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8670,7 +8670,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8708,7 +8708,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8746,7 +8746,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8784,7 +8784,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8822,7 +8822,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8860,7 +8860,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8898,7 +8898,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8936,7 +8936,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -8974,7 +8974,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -9012,7 +9012,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -9147,7 +9147,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9185,7 +9185,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9300,7 +9300,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9338,7 +9338,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9376,7 +9376,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9414,7 +9414,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -9450,7 +9450,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9488,7 +9488,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9526,7 +9526,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  ]]></format>
         </remarks>
@@ -9562,7 +9562,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9600,7 +9600,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9638,7 +9638,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9676,7 +9676,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -9714,7 +9714,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -12686,7 +12686,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  The `e` parameter is typed as the common base type for all routed event data; however, the event data should be given as the most specific event data type that is available for the event being raised, because <xref:System.Windows.RoutedEventArgs> derived classes contain the actual specific data properties that are intended for the specific event when it is raised.  
   
- <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events and data classes, which typically just contain properties that are related to the event.  
+ <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from common language runtime (CLR) events and data classes, which typically just contain properties that are related to the event.  
   
    
   
@@ -12858,7 +12858,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
+ The most common scenario for using this API is when you implement the common language runtime (CLR) "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level. The example that follows this remarks section illustrates this scenario.  
   
  Calling this method has no effect if there were no handlers registered with criteria that matches the input parameters for the method call.  
   
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 95ac184384c..2a63b7e49c6 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -4862,7 +4862,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4902,7 +4902,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4942,7 +4942,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -4982,7 +4982,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5022,7 +5022,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5110,7 +5110,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5150,7 +5150,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5190,7 +5190,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5561,7 +5561,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5603,7 +5603,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5689,7 +5689,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5729,7 +5729,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5769,7 +5769,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5849,7 +5849,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -5889,7 +5889,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  <xref:System.Windows.UIElement3D.OnMouseEnter%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -5927,7 +5927,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event, with a direct routing strategy. Marking the event as handled is still useful for preventing the typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  <xref:System.Windows.UIElement3D.OnMouseLeave%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -6041,7 +6041,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6165,7 +6165,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6204,7 +6204,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6244,7 +6244,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6284,7 +6284,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6324,7 +6324,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6364,7 +6364,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6404,7 +6404,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6444,7 +6444,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6484,7 +6484,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6524,7 +6524,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6564,7 +6564,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6612,7 +6612,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6728,7 +6728,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6852,7 +6852,7 @@
   
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -6892,7 +6892,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6932,7 +6932,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -6972,7 +6972,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7012,7 +7012,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7052,7 +7052,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7092,7 +7092,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7132,7 +7132,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7172,7 +7172,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7212,7 +7212,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7252,7 +7252,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7292,7 +7292,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7332,7 +7332,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled. Another scenario that is specifically for Preview events is to mark them handled so that the matching bubbling class handlers are not invoked.  
   
@@ -7469,7 +7469,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7509,7 +7509,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7549,7 +7549,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7589,7 +7589,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7629,7 +7629,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7669,7 +7669,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  <xref:System.Windows.UIElement3D.OnStylusEnter%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -7707,7 +7707,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7747,7 +7747,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7787,7 +7787,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation. You may call base either before or after your special handling, depending on your requirements.  
   
- The purpose of this method is similar to [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
+ The purpose of this method is similar to common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. Marking the event as handled is still useful for preventing typical instance handlers (those that do not specify `handledEventsToo`) from being invoked.  
   
  <xref:System.Windows.UIElement3D.OnStylusLeave%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -7825,7 +7825,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7865,7 +7865,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7905,7 +7905,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7945,7 +7945,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -7985,7 +7985,7 @@
 ## Remarks  
  This method has no default implementation. Because an intermediate class in the inheritance might implement this method, we recommend that you call the base implementation in your implementation.  
   
- The purpose of this method is similar to the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
+ The purpose of this method is similar to the common language runtime (CLR) event pattern On* methods: this method provides the means to handle the matching event from derived classes by establishing a class handler instead of an instance handler. In this case the matching event is a routed event. The implementation pattern of the On* methods is different for routed events because a routed event can be raised by a child element, which is not necessarily the element that will invoke handlers. Therefore, your implementation needs to examine the source properties of the event data. It should not try to reraise the event in most cases.  
   
  Either by overriding this method or by registering class handlers with <xref:System.Windows.EventManager.RegisterClassHandler%2A>, derived classes of <xref:System.Windows.UIElement3D> can call private class handler methods when the event is received along the event route. One scenario where class handling is appropriate is to manipulate the event data and mark the routed event as handled.  
   
@@ -10941,7 +10941,7 @@
 ## Remarks  
  The `e` parameter is typed as the common base type for all routed event data; however, the event data should be given as the most specific event data type that is available for the event being raised, because <xref:System.Windows.RoutedEventArgs> derived classes contain the actual specific data properties that are intended for the specific event when it is raised.  
   
- <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] events and data classes, which typically just contain properties that are related to the event.  
+ <xref:System.Windows.RoutedEventArgs> is not just the state properties for the event; it also identifies which routed event to raise. This event-raising pattern and the routed event data both differ from common language runtime (CLR) events and data classes, which typically just contain properties that are related to the event.  
   
  <xref:System.Windows.UIElement3D.RaiseEvent%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -11103,7 +11103,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The most common scenario for using this API is when you implement the [!INCLUDE[TLA#tla_clr](~/includes/tlasharptla-clr-md.md)] "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level.  
+ The most common scenario for using this API is when you implement the common language runtime (CLR) "wrapper" event that is associated with a custom routed event, specifically when you implement the "remove" logic for handlers at the CLR level.  
   
  Calling this method has no effect if there were no handlers registered with criteria that match the input parameters for the method call.  
   

From 9414dcc3279da4459999646152e69a5f3a7a28a4 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:00:13 -0800
Subject: [PATCH 114/236] tlasharptla-com

---
 xml/System.Printing/PrintQueue.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index c07dbe47b68..badf0411251 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -584,7 +584,7 @@
 ## Remarks  
  If `fastCopy` is `true`, then the printer must be an [Printing Overview](/dotnet/framework/wpf/advanced/printing-overview). If it is not, the <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> method throws an exception.  
   
- If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The XPS file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to [!INCLUDE[TLA#tla_com](~/includes/tlasharptla-com-md.md)]. The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
+ If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The XPS file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to Component Object Model (COM). The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
   
 -   The simplest way is to add the <xref:System.STAThreadAttribute> (that is, "`[System.STAThreadAttribute()]`") just above the first line of the application's `Main` method (usually "`static void Main(string[] args)`").  
   

From 4026401feb2399518e303cb5cf04f02356759dd8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:00:39 -0800
Subject: [PATCH 115/236] tlasharptla-dhtml

---
 xml/System.Windows/UIElement.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 983495fe00e..08056d9df58 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -43,7 +43,7 @@
   
  <xref:System.Windows.UIElement> also includes APIs that relate to the WPF event model, including methods that can raise specified routed events that are sourced from an element instance.  
   
- In terms of architecture, <xref:System.Windows.UIElement> can be considered roughly equivalent to a window handle in [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] programming, or an Element in [!INCLUDE[TLA#tla_dhtml](~/includes/tlasharptla-dhtml-md.md)] programming. <xref:System.Windows.UIElement> is a base element at the WPF core level.  
+ In terms of architecture, <xref:System.Windows.UIElement> can be considered roughly equivalent to a window handle in [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] programming, or an Element in Dynamic HTML (DHTML) programming. <xref:System.Windows.UIElement> is a base element at the WPF core level.  
   
  A <xref:System.Windows.UIElement> has the following capabilities that are specifically defined by the <xref:System.Windows.UIElement> class:  
   

From fc530b4cdf916f4c339ad33187b6755c5e0dd2dc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:01:08 -0800
Subject: [PATCH 116/236] tlasharptla-dipixel

---
 xml/System.Windows.Controls.Primitives/Popup.xml   |  4 ++--
 xml/System.Windows.Controls/AccessText.xml         |  4 ++--
 xml/System.Windows.Controls/ComboBox.xml           |  2 +-
 xml/System.Windows.Controls/ContextMenu.xml        |  4 ++--
 xml/System.Windows.Controls/ContextMenuService.xml |  4 ++--
 xml/System.Windows.Controls/Control.xml            |  2 +-
 xml/System.Windows.Controls/GridViewColumn.xml     |  2 +-
 xml/System.Windows.Controls/InkCanvas.xml          |  8 ++++----
 xml/System.Windows.Controls/ScrollViewer.xml       |  2 +-
 .../WindowsFormsHost.xml                           |  2 +-
 .../OuterGlowBitmapEffect.xml                      |  2 +-
 xml/System.Windows/FrameworkElement.xml            | 14 +++++++-------
 12 files changed, 25 insertions(+), 25 deletions(-)

diff --git a/xml/System.Windows.Controls.Primitives/Popup.xml b/xml/System.Windows.Controls.Primitives/Popup.xml
index 8192028601b..f19e5c92a72 100644
--- a/xml/System.Windows.Controls.Primitives/Popup.xml
+++ b/xml/System.Windows.Controls.Primitives/Popup.xml
@@ -610,7 +610,7 @@
  `double`  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings do not have to explicitly include decimal points. For example, a value of `1` is acceptable.  
+ A string representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings do not have to explicitly include decimal points. For example, a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions apply as those that are mentioned in the Property Value section of this topic.  
   
@@ -1555,7 +1555,7 @@
  `double`  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings do not have to explicitly include decimal points. For example, a value of `1` is acceptable.  
+ A string representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings do not have to explicitly include decimal points. For example, a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions apply as those that are mentioned in the Property Value section of this topic.  
   
diff --git a/xml/System.Windows.Controls/AccessText.xml b/xml/System.Windows.Controls/AccessText.xml
index 4fd6f178335..9dbbe10448b 100644
--- a/xml/System.Windows.Controls/AccessText.xml
+++ b/xml/System.Windows.Controls/AccessText.xml
@@ -398,7 +398,7 @@
  *Double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This value is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For example, you can specify a value of `1`.  
+ A string representation of a <xref:System.Double> value. This value is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For example, you can specify a value of `1`.  
   
  *qualifiedDouble*  
  A *double* value that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -792,7 +792,7 @@
  *double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This value is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For example, you can specify a value of `1`.  
+ A string representation of a <xref:System.Double> value. This value is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For example, you can specify a value of `1`.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply here.  
   
diff --git a/xml/System.Windows.Controls/ComboBox.xml b/xml/System.Windows.Controls/ComboBox.xml
index 3ae3226da6e..64806935c2a 100644
--- a/xml/System.Windows.Controls/ComboBox.xml
+++ b/xml/System.Windows.Controls/ComboBox.xml
@@ -633,7 +633,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
   
diff --git a/xml/System.Windows.Controls/ContextMenu.xml b/xml/System.Windows.Controls/ContextMenu.xml
index a2cf1a3ab5e..fb469fe8989 100644
--- a/xml/System.Windows.Controls/ContextMenu.xml
+++ b/xml/System.Windows.Controls/ContextMenu.xml
@@ -395,7 +395,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
   
@@ -1202,7 +1202,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable. The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable. The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
diff --git a/xml/System.Windows.Controls/ContextMenuService.xml b/xml/System.Windows.Controls/ContextMenuService.xml
index ba511e537cc..46631d4a8c5 100644
--- a/xml/System.Windows.Controls/ContextMenuService.xml
+++ b/xml/System.Windows.Controls/ContextMenuService.xml
@@ -652,7 +652,7 @@
  *double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ A string representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -1355,7 +1355,7 @@
  *double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ A string representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
diff --git a/xml/System.Windows.Controls/Control.xml b/xml/System.Windows.Controls/Control.xml
index d1a76a8ffa5..d945a6b60ca 100644
--- a/xml/System.Windows.Controls/Control.xml
+++ b/xml/System.Windows.Controls/Control.xml
@@ -508,7 +508,7 @@
  *double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For example, a value of `1` is acceptable.  
+ A string representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For example, a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions that are mentioned in the Property Value section apply here.  
   
diff --git a/xml/System.Windows.Controls/GridViewColumn.xml b/xml/System.Windows.Controls/GridViewColumn.xml
index b1b200929bb..954a4586c33 100644
--- a/xml/System.Windows.Controls/GridViewColumn.xml
+++ b/xml/System.Windows.Controls/GridViewColumn.xml
@@ -1035,7 +1035,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index 14d18c3d5af..048d84a457d 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -359,7 +359,7 @@
 <a name="xamlValues_Bottom"></a>   
 ## XAML Values  
  *double*  
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -1756,7 +1756,7 @@
 <a name="xamlValues_Left"></a>   
 ## XAML Values  
  *double*  
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -2650,7 +2650,7 @@
 <a name="xamlValues_Right"></a>   
 ## XAML Values  
  *double*  
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance, a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -3711,7 +3711,7 @@
 <a name="xamlValues_Top"></a>   
 ## XAML Values  
  *double*  
- String representation of a <xref:System.Double> value. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
diff --git a/xml/System.Windows.Controls/ScrollViewer.xml b/xml/System.Windows.Controls/ScrollViewer.xml
index 527232419a8..d577e32a277 100644
--- a/xml/System.Windows.Controls/ScrollViewer.xml
+++ b/xml/System.Windows.Controls/ScrollViewer.xml
@@ -1879,7 +1879,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When a user drags a finger across an object, it is considered a translate manipulation.  The <xref:System.Windows.Controls.ScrollViewer> uses that manipulation to scroll. The <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> property specifies how much the <xref:System.Windows.Controls.ScrollViewer> scrolls for each unit of translation.  For example, if <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> is 2, the <xref:System.Windows.Controls.ScrollViewer> will scroll 2 [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] for every [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] of the translate manipulation.  
+ When a user drags a finger across an object, it is considered a translate manipulation.  The <xref:System.Windows.Controls.ScrollViewer> uses that manipulation to scroll. The <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> property specifies how much the <xref:System.Windows.Controls.ScrollViewer> scrolls for each unit of translation.  For example, if <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> is 2, the <xref:System.Windows.Controls.ScrollViewer> will scroll 2 [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] for every device-independent unit (1/96th inch) of the translate manipulation.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml b/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
index 5e435685130..02b603f23d3 100644
--- a/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
+++ b/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
@@ -527,7 +527,7 @@
 <a name="xamlValues_FontSize"></a>   
 ## XAML Values  
  *double*  
- String representation of a <xref:System.Double> value equal to or greater than 0.0, but smaller than <xref:System.Double.PositiveInfinity>. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of 1 is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0, but smaller than <xref:System.Double.PositiveInfinity>. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of 1 is acceptable.  
   
 <a name="dependencyPropertyInfo_FontSize"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml b/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
index a0fe67c078d..6fc2639195c 100644
--- a/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/OuterGlowBitmapEffect.xml
@@ -289,7 +289,7 @@
       </ReturnValue>
       <Docs>
         <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.BlurEffect" />. Gets or sets the thickness of the halo glow.</summary>
-        <value>The thickness of the halo glow, in [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)]. The valid range of values is from 1 through 199. The default is 20.</value>
+        <value>The thickness of the halo glow, in device-independent unit (1/96th inch). The valid range of values is from 1 through 199. The default is 20.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 4d0e526f7d5..dceb7c9ad56 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -2032,7 +2032,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. See Remarks for upper bound information. This value is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. See Remarks for upper bound information. This value is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
@@ -2691,7 +2691,7 @@
   
  The attribute usage will also accept abbreviated values that apply in the order provided, symmetrically and logically. For instance, `Margin="20"` will be interpreted to mean a <xref:System.Windows.Thickness> with all properties set to 20. `Margin="20,50"` will be interpreted to mean a <xref:System.Windows.Thickness> with <xref:System.Windows.Thickness.Left%2A> and <xref:System.Windows.Thickness.Right%2A> set to 20, and <xref:System.Windows.Thickness.Top%2A> and <xref:System.Windows.Thickness.Bottom%2A> set to 50.  
   
- The default unit for a <xref:System.Windows.Thickness> measure is [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)]. You can also specify other units by appending the unit type strings `cm`, `in`, or `pt` to any measure.  
+ The default unit for a <xref:System.Windows.Thickness> measure is device-independent unit (1/96th inch). You can also specify other units by appending the unit type strings `cm`, `in`, or `pt` to any measure.  
   
  Number values provided as XAML attributes need not specify decimal points (0 is acceptable, does not have to be provided as 0.0). For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
   
@@ -2789,7 +2789,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply, except that you must use [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) if you need to explicitly set the value to be <xref:System.Double.PositiveInfinity>.  
   
@@ -2894,7 +2894,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply, except that you must use [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) to set the value to be <xref:System.Double.PositiveInfinity>.  
   
@@ -3086,7 +3086,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
   
@@ -3191,7 +3191,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. This is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  The same <xref:System.Double> range restrictions as mentioned in the Property Value section apply.  
   
@@ -5702,7 +5702,7 @@
  *double*  
  <xref:System.Double>  
   
- String representation of a <xref:System.Double> value equal to or greater than 0.0. See Remarks for upper bound information. This value is interpreted as a [!INCLUDE[TLA#tla_dipixel](~/includes/tlasharptla-dipixel-md.md)] measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
+ String representation of a <xref:System.Double> value equal to or greater than 0.0. See Remarks for upper bound information. This value is interpreted as a device-independent unit (1/96th inch) measurement. Strings need not explicitly include decimal points. For instance a value of `1` is acceptable.  
   
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  

From 6807a77047c813637e29d6cb469e27228d43e01c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:19:49 -0800
Subject: [PATCH 117/236] tlasharptla-dipixelsharpplural

---
 ...ierarchicalVirtualizationAndScrollInfo.xml |  8 ++--
 .../Popup.xml                                 |  4 +-
 .../TextBoxBase.xml                           | 12 +++---
 .../RibbonGalleryCategoriesPanel.xml          | 32 +++++++-------
 .../RibbonTabHeadersPanel.xml                 | 16 +++----
 .../RibbonTabsPanel.xml                       | 16 +++----
 xml/System.Windows.Controls/AccessText.xml    |  4 +-
 .../ColumnDefinition.xml                      |  4 +-
 xml/System.Windows.Controls/ComboBox.xml      |  2 +-
 xml/System.Windows.Controls/ContextMenu.xml   |  4 +-
 .../ContextMenuService.xml                    |  4 +-
 xml/System.Windows.Controls/Control.xml       |  2 +-
 xml/System.Windows.Controls/DataGrid.xml      | 16 +++----
 .../DataGridColumn.xml                        |  8 ++--
 .../GridViewColumn.xml                        |  2 +-
 ...chicalVirtualizationHeaderDesiredSizes.xml |  6 +--
 ...archicalVirtualizationItemDesiredSizes.xml | 24 +++++------
 xml/System.Windows.Controls/InkCanvas.xml     |  8 ++--
 xml/System.Windows.Controls/RowDefinition.xml |  4 +-
 xml/System.Windows.Controls/ScrollUnit.xml    |  2 +-
 xml/System.Windows.Controls/ScrollViewer.xml  | 10 ++---
 xml/System.Windows.Controls/TextBlock.xml     |  8 ++--
 .../ToolTipService.xml                        |  4 +-
 .../VirtualizationCacheLengthUnit.xml         |  2 +-
 xml/System.Windows.Controls/WrapPanel.xml     |  4 +-
 .../AnchoredBlock.xml                         | 14 +++----
 xml/System.Windows.Documents/Block.xml        | 14 +++----
 xml/System.Windows.Documents/Figure.xml       |  4 +-
 xml/System.Windows.Documents/Floater.xml      |  4 +-
 xml/System.Windows.Documents/FlowDocument.xml | 26 ++++++------
 xml/System.Windows.Documents/List.xml         |  2 +-
 xml/System.Windows.Documents/ListItem.xml     | 14 +++----
 xml/System.Windows.Documents/Paragraph.xml    |  2 +-
 xml/System.Windows.Documents/Table.xml        |  2 +-
 xml/System.Windows.Documents/TableCell.xml    | 10 ++---
 xml/System.Windows.Documents/TextElement.xml  |  2 +-
 .../InertiaExpansionBehavior.xml              |  4 +-
 .../InertiaTranslationBehavior.xml            |  4 +-
 .../ManipulationDelta.xml                     | 14 +++----
 .../ManipulationVelocities.xml                |  8 ++--
 .../DropShadowBitmapEffect.xml                |  2 +-
 .../BitmapSource.xml                          |  8 ++--
 xml/System.Windows.Media/FormattedText.xml    | 42 +++++++++----------
 xml/System.Windows/FigureLength.xml           |  2 +-
 xml/System.Windows/FrameworkElement.xml       | 28 ++++++-------
 xml/System.Windows/GridLength.xml             |  4 +-
 xml/System.Windows/Thickness.xml              | 10 ++---
 47 files changed, 213 insertions(+), 213 deletions(-)

diff --git a/xml/System.Windows.Controls.Primitives/IHierarchicalVirtualizationAndScrollInfo.xml b/xml/System.Windows.Controls.Primitives/IHierarchicalVirtualizationAndScrollInfo.xml
index 96ecc0adb72..7289a8e34b0 100644
--- a/xml/System.Windows.Controls.Primitives/IHierarchicalVirtualizationAndScrollInfo.xml
+++ b/xml/System.Windows.Controls.Primitives/IHierarchicalVirtualizationAndScrollInfo.xml
@@ -62,8 +62,8 @@
         <ReturnType>System.Windows.Controls.HierarchicalVirtualizationHeaderDesiredSizes</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets an object that represents the desired size of the control's header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] and in logical units.</summary>
-        <value>An object that represents the desired size of the control's header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] and in logical units.</value>
+        <summary>Gets an object that represents the desired size of the control's header, in device-independent units (1/96th inch per unit) and in logical units.</summary>
+        <value>An object that represents the desired size of the control's header, in device-independent units (1/96th inch per unit) and in logical units.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -114,8 +114,8 @@
         <ReturnType>System.Windows.Controls.HierarchicalVirtualizationItemDesiredSizes</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets an object that represents the desired size of the control's items, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] and in logical units.</summary>
-        <value>An object that represents the desired size of the control's items, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] and in logical units.</value>
+        <summary>Gets or sets an object that represents the desired size of the control's items, in device-independent units (1/96th inch per unit) and in logical units.</summary>
+        <value>An object that represents the desired size of the control's items, in device-independent units (1/96th inch per unit) and in logical units.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls.Primitives/Popup.xml b/xml/System.Windows.Controls.Primitives/Popup.xml
index f19e5c92a72..1a97c01eb2f 100644
--- a/xml/System.Windows.Controls.Primitives/Popup.xml
+++ b/xml/System.Windows.Controls.Primitives/Popup.xml
@@ -617,7 +617,7 @@
  `qualifiedDouble`  
  A `double` value as described earlier in this table, followed by one of the following unit declaration strings: `px`, `in`, `cm`, or `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in=96px  
   
@@ -1562,7 +1562,7 @@
  `qualifiedDouble`  
  A `double` value as described earlier in this table, followed by one of the following unit declaration strings: `px`, `in`, `cm`, or `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in=96px  
   
diff --git a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
index 058499a10d3..b828a4e264e 100644
--- a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
+++ b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
@@ -649,7 +649,7 @@ TextBox with CaretBrush set to blue
       </ReturnValue>
       <Docs>
         <summary>Gets the vertical size of the visible content area.</summary>
-        <value>A floating-point value that specifies the vertical size of the visible content area, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the vertical size of the visible content area, in device-independent units (1/96th inch per unit).  
   
  The value of this property is 0.0 if the text-editing control is not configured to support scrolling.  
   
@@ -689,7 +689,7 @@ TextBox with CaretBrush set to blue
       </ReturnValue>
       <Docs>
         <summary>Gets the horizontal size of the visible content area.</summary>
-        <value>A floating-point value that specifies the horizontal size of the visible content area, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the horizontal size of the visible content area, in device-independent units (1/96th inch per unit).  
   
  The value of this property is 0.0 if the text editing control is not configured to support scrolling.  
   
@@ -729,7 +729,7 @@ TextBox with CaretBrush set to blue
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the horizontal scroll position.</summary>
-        <value>A floating-point value that specifies the horizontal scroll position, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the horizontal scroll position, in device-independent units (1/96th inch per unit).  
   
  Setting this property causes the text editing control to scroll to the specified horizontal offset. Reading this property returns the current horizontal offset.  
   
@@ -2825,7 +2825,7 @@ If this property is `null`, selected text is not rendered.
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the vertical scroll position.</summary>
-        <value>A floating-point value that specifies the vertical scroll position, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the vertical scroll position, in device-independent units (1/96th inch per unit).  
   
  Setting this property causes the text editing control to scroll to the specified vertical offset. Reading this property returns the current vertical offset.  
   
@@ -2939,7 +2939,7 @@ If this property is `null`, selected text is not rendered.
       </ReturnValue>
       <Docs>
         <summary>Gets the vertical size of the scrollable content area.</summary>
-        <value>A floating-point value that specifies the vertical size of the scrollable content area, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the vertical size of the scrollable content area, in device-independent units (1/96th inch per unit).  
   
  The value of this property is 0.0 if the text editing control is not configured to support scrolling.  
   
@@ -2979,7 +2979,7 @@ If this property is `null`, selected text is not rendered.
       </ReturnValue>
       <Docs>
         <summary>Gets the horizontal size of the scrollable content area.</summary>
-        <value>A floating-point value that specifies the horizontal size of the scrollable content area, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+        <value>A floating-point value that specifies the horizontal size of the scrollable content area, in device-independent units (1/96th inch per unit).  
   
  The value of this property is 0.0 if the text editing control is not configured to support scrolling.  
   
diff --git a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonGalleryCategoriesPanel.xml b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonGalleryCategoriesPanel.xml
index 9fd05601c3f..39853e1cc1e 100644
--- a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonGalleryCategoriesPanel.xml
+++ b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonGalleryCategoriesPanel.xml
@@ -169,8 +169,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the vertical size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The vertical size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the vertical size of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The vertical size of the scrolled content in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -194,8 +194,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the horizontal size of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the scrolled content in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -225,8 +225,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the horizontal offset of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal offset of the scrolled content in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -673,8 +673,8 @@
         <Parameter Name="offset" Type="System.Double" />
       </Parameters>
       <Docs>
-        <param name="offset">The amount that content is horizontally offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <summary>Sets the amount that content is horizontal offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <param name="offset">The amount that content is horizontally offset in the containing viewport in device-independent units (1/96th inch per unit).</param>
+        <summary>Sets the amount that content is horizontal offset in the containing viewport in device-independent units (1/96th inch per unit).</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -701,8 +701,8 @@
         <Parameter Name="offset" Type="System.Double" />
       </Parameters>
       <Docs>
-        <param name="offset">The amount that content is vertically offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <summary>Sets the amount that content is vertical offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <param name="offset">The amount that content is vertically offset in the containing viewport in device-independent units (1/96th inch per unit).</param>
+        <summary>Sets the amount that content is vertical offset in the containing viewport in device-independent units (1/96th inch per unit).</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -757,8 +757,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the vertical offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The vertical offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the vertical offset of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The vertical offset of the scrolled content in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -782,8 +782,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the vertical size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The vertical size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the vertical size of the content's visible range in device-independent units (1/96th inch per unit).</summary>
+        <value>The vertical size of the content's visible range in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -807,8 +807,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the horizontal size of the content's visible range in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the content's visible range in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabHeadersPanel.xml b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabHeadersPanel.xml
index 25426ffede8..260f8707d8c 100644
--- a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabHeadersPanel.xml
+++ b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabHeadersPanel.xml
@@ -185,8 +185,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal size of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the scrolled content in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -217,8 +217,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal offset of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal offset of the scrolled content in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -814,8 +814,8 @@
         <Parameter Name="offset" Type="System.Double" />
       </Parameters>
       <Docs>
-        <param name="offset">The amount that content is horizontally offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <summary>Sets the amount that content is horizontal offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <param name="offset">The amount that content is horizontally offset in the containing viewport in device-independent units (1/96th inch per unit).</param>
+        <summary>Sets the amount that content is horizontal offset in the containing viewport in device-independent units (1/96th inch per unit).</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -938,8 +938,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal size of the content's visible range in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the content's visible range in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabsPanel.xml b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabsPanel.xml
index 2fc4f1f262f..b9ae10103d6 100644
--- a/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabsPanel.xml
+++ b/xml/System.Windows.Controls.Ribbon.Primitives/RibbonTabsPanel.xml
@@ -185,8 +185,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal size of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the scrolled content in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -217,8 +217,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal offset of the scrolled content in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal offset of the scrolled content in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal offset of the scrolled content in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -704,8 +704,8 @@
         <Parameter Name="offset" Type="System.Double" />
       </Parameters>
       <Docs>
-        <param name="offset">The amount that content is horizontally offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <summary>Sets the amount that content is horizontal offset in the containing viewport in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <param name="offset">The amount that content is horizontally offset in the containing viewport in device-independent units (1/96th inch per unit).</param>
+        <summary>Sets the amount that content is horizontal offset in the containing viewport in device-independent units (1/96th inch per unit).</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -828,8 +828,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The horizontal size of the content's visible range in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. This property has no default value.</value>
+        <summary>Gets the horizontal size of the content's visible range in device-independent units (1/96th inch per unit).</summary>
+        <value>The horizontal size of the content's visible range in device-independent units (1/96th inch per unit). This property has no default value.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls/AccessText.xml b/xml/System.Windows.Controls/AccessText.xml
index 9dbbe10448b..30464115c32 100644
--- a/xml/System.Windows.Controls/AccessText.xml
+++ b/xml/System.Windows.Controls/AccessText.xml
@@ -403,7 +403,7 @@
  *qualifiedDouble*  
  A *double* value that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -799,7 +799,7 @@
  *qualifiedDouble*  
  A *double* value that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ColumnDefinition.xml b/xml/System.Windows.Controls/ColumnDefinition.xml
index b18f87ef8d8..fa83f4ac496 100644
--- a/xml/System.Windows.Controls/ColumnDefinition.xml
+++ b/xml/System.Windows.Controls/ColumnDefinition.xml
@@ -132,7 +132,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -237,7 +237,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ComboBox.xml b/xml/System.Windows.Controls/ComboBox.xml
index 64806935c2a..865582e4d79 100644
--- a/xml/System.Windows.Controls/ComboBox.xml
+++ b/xml/System.Windows.Controls/ComboBox.xml
@@ -640,7 +640,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ContextMenu.xml b/xml/System.Windows.Controls/ContextMenu.xml
index fb469fe8989..39d90e44619 100644
--- a/xml/System.Windows.Controls/ContextMenu.xml
+++ b/xml/System.Windows.Controls/ContextMenu.xml
@@ -402,7 +402,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1207,7 +1207,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ContextMenuService.xml b/xml/System.Windows.Controls/ContextMenuService.xml
index 46631d4a8c5..86f45112d3b 100644
--- a/xml/System.Windows.Controls/ContextMenuService.xml
+++ b/xml/System.Windows.Controls/ContextMenuService.xml
@@ -657,7 +657,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1360,7 +1360,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/Control.xml b/xml/System.Windows.Controls/Control.xml
index d945a6b60ca..8f099c6c47b 100644
--- a/xml/System.Windows.Controls/Control.xml
+++ b/xml/System.Windows.Controls/Control.xml
@@ -515,7 +515,7 @@
  *qualifiedDouble*  
  A *double* value as previously described that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/DataGrid.xml b/xml/System.Windows.Controls/DataGrid.xml
index d505cc3c982..f2e469a43e6 100644
--- a/xml/System.Windows.Controls/DataGrid.xml
+++ b/xml/System.Windows.Controls/DataGrid.xml
@@ -1439,7 +1439,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the height of the column headers row.</summary>
-        <value>The height of the column headers row, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The height of the column headers row, in device-independent units (1/96th inch per unit). The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1707,7 +1707,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the standard width and sizing mode of columns and headers in the <see cref="T:System.Windows.Controls.DataGrid" />.</summary>
-        <value>The width and sizing mode of the columns and headers, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="P:System.Windows.Controls.DataGridLength.SizeToHeader" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The width and sizing mode of the columns and headers, in device-independent units (1/96th inch per unit). The registered default is <see cref="P:System.Windows.Controls.DataGridLength.SizeToHeader" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2926,7 +2926,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum width constraint of the columns and headers in the <see cref="T:System.Windows.Controls.DataGrid" />.</summary>
-        <value>The maximum width of the columns and headers in the <see cref="T:System.Windows.Controls.DataGrid" />, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="F:System.Double.PositiveInfinity" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The maximum width of the columns and headers in the <see cref="T:System.Windows.Controls.DataGrid" />, in device-independent units (1/96th inch per unit). The registered default is <see cref="F:System.Double.PositiveInfinity" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3016,7 +3016,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the minimum width constraint of the columns and headers in the <see cref="T:System.Windows.Controls.DataGrid" />.</summary>
-        <value>The minimum width of the columns and headers, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is 20. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The minimum width of the columns and headers, in device-independent units (1/96th inch per unit). The registered default is 20. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3080,7 +3080,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the minimum height constraint of the rows and headers in the <see cref="T:System.Windows.Controls.DataGrid" />.</summary>
-        <value>The minimum height constraint of rows, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is 0.0. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The minimum height constraint of rows, in device-independent units (1/96th inch per unit). The registered default is 0.0. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -5023,7 +5023,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the rendered width of the row headers column.</summary>
-        <value>The rendered width of the row header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is 0.0. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The rendered width of the row header, in device-independent units (1/96th inch per unit). The registered default is 0.0. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -5231,7 +5231,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the width of the row header column.</summary>
-        <value>The width of the row header column, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The width of the row header column, in device-independent units (1/96th inch per unit). The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -5284,7 +5284,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the suggested height for all rows.</summary>
-        <value>The height of the rows, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The height of the rows, in device-independent units (1/96th inch per unit). The registered default is <see cref="F:System.Double.NaN" />. For more information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls/DataGridColumn.xml b/xml/System.Windows.Controls/DataGridColumn.xml
index cbdbbe7badf..ec8d2a84222 100644
--- a/xml/System.Windows.Controls/DataGridColumn.xml
+++ b/xml/System.Windows.Controls/DataGridColumn.xml
@@ -68,8 +68,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the current width of the column, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The width of the column in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is 0. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <summary>Gets the current width of the column, in device-independent units (1/96th inch per unit).</summary>
+        <value>The width of the column in device-independent units (1/96th inch per unit). The registered default is 0. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1125,7 +1125,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum width constraint of the column.</summary>
-        <value>The maximum column width, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is <see cref="F:System.Double.PositiveInfinity" />. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The maximum column width, in device-independent units (1/96th inch per unit). The registered default is <see cref="F:System.Double.PositiveInfinity" />. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1190,7 +1190,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the minimum width constraint of the column.</summary>
-        <value>The minimum column width, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The registered default is 20. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
+        <value>The minimum column width, in device-independent units (1/96th inch per unit). The registered default is 20. For information about what can influence the value, see <see cref="T:System.Windows.DependencyProperty" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls/GridViewColumn.xml b/xml/System.Windows.Controls/GridViewColumn.xml
index 954a4586c33..ad9688fe89d 100644
--- a/xml/System.Windows.Controls/GridViewColumn.xml
+++ b/xml/System.Windows.Controls/GridViewColumn.xml
@@ -1040,7 +1040,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/HierarchicalVirtualizationHeaderDesiredSizes.xml b/xml/System.Windows.Controls/HierarchicalVirtualizationHeaderDesiredSizes.xml
index 8ac08812474..c134bbfd24e 100644
--- a/xml/System.Windows.Controls/HierarchicalVirtualizationHeaderDesiredSizes.xml
+++ b/xml/System.Windows.Controls/HierarchicalVirtualizationHeaderDesiredSizes.xml
@@ -38,7 +38,7 @@
       </Parameters>
       <Docs>
         <param name="logicalSize">The size of the header, in logical units.</param>
-        <param name="pixelSize">The size of the header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="pixelSize">The size of the header, in device-independent units (1/96th inch per unit).</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Controls.HierarchicalVirtualizationHeaderDesiredSizes" /> class.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -226,8 +226,8 @@
         <ReturnType>System.Windows.Size</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the size of the header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The size of the header, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the size of the header, in device-independent units (1/96th inch per unit).</summary>
+        <value>The size of the header, in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/HierarchicalVirtualizationItemDesiredSizes.xml b/xml/System.Windows.Controls/HierarchicalVirtualizationItemDesiredSizes.xml
index 517ddf89f77..6d2ccbca41b 100644
--- a/xml/System.Windows.Controls/HierarchicalVirtualizationItemDesiredSizes.xml
+++ b/xml/System.Windows.Controls/HierarchicalVirtualizationItemDesiredSizes.xml
@@ -47,10 +47,10 @@
         <param name="logicalSizeInViewport">The size of the control's child items that are in the viewport, in logical units.</param>
         <param name="logicalSizeBeforeViewport">The size of the control's child items that are in the cache before the viewport, in logical units.</param>
         <param name="logicalSizeAfterViewport">The size of the control's child items that are in the cache after the viewport, in logical units.</param>
-        <param name="pixelSize">The size of the control's child items, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <param name="pixelSizeInViewport">The size of the control's child items that are in viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <param name="pixelSizeBeforeViewport">The size of the control's child items that are in the cache before the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
-        <param name="pixelSizeAfterViewport">The size of the control's child items that are in the cache after the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="pixelSize">The size of the control's child items, in device-independent units (1/96th inch per unit).</param>
+        <param name="pixelSizeInViewport">The size of the control's child items that are in viewport, in device-independent units (1/96th inch per unit).</param>
+        <param name="pixelSizeBeforeViewport">The size of the control's child items that are in the cache before the viewport, in device-independent units (1/96th inch per unit).</param>
+        <param name="pixelSizeAfterViewport">The size of the control's child items that are in the cache after the viewport, in device-independent units (1/96th inch per unit).</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Controls.HierarchicalVirtualizationItemDesiredSizes" /> class.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -304,8 +304,8 @@
         <ReturnType>System.Windows.Size</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the size of the control's child items, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The size of the control's child items, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the size of the control's child items, in device-independent units (1/96th inch per unit).</summary>
+        <value>The size of the control's child items, in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -326,8 +326,8 @@
         <ReturnType>System.Windows.Size</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the size of the control's child items that are in the cache after the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The size of the control's child items that are in the cache after the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the size of the control's child items that are in the cache after the viewport, in device-independent units (1/96th inch per unit).</summary>
+        <value>The size of the control's child items that are in the cache after the viewport, in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -348,8 +348,8 @@
         <ReturnType>System.Windows.Size</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the size of the control's child items that are in the cache before the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The size of the control's child items that are in the cache before the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the size of the control's child items that are in the cache before the viewport, in device-independent units (1/96th inch per unit).</summary>
+        <value>The size of the control's child items that are in the cache before the viewport, in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -370,8 +370,8 @@
         <ReturnType>System.Windows.Size</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the size of the control's child items that are in the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The size of the control's child items that are in the viewport, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the size of the control's child items that are in the viewport, in device-independent units (1/96th inch per unit).</summary>
+        <value>The size of the control's child items that are in the viewport, in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index 048d84a457d..a2f65e0bd0f 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -364,7 +364,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1761,7 +1761,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2655,7 +2655,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -3716,7 +3716,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/RowDefinition.xml b/xml/System.Windows.Controls/RowDefinition.xml
index b19f40f4bbf..c83b15608f5 100644
--- a/xml/System.Windows.Controls/RowDefinition.xml
+++ b/xml/System.Windows.Controls/RowDefinition.xml
@@ -200,7 +200,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -305,7 +305,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ScrollUnit.xml b/xml/System.Windows.Controls/ScrollUnit.xml
index 69500a5918f..4b84993377b 100644
--- a/xml/System.Windows.Controls/ScrollUnit.xml
+++ b/xml/System.Windows.Controls/ScrollUnit.xml
@@ -57,7 +57,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>The <see cref="P:System.Windows.Controls.VirtualizingPanel.ScrollUnit" /> is measured in terms of [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <summary>The <see cref="P:System.Windows.Controls.VirtualizingPanel.ScrollUnit" /> is measured in terms of device-independent units (1/96th inch per unit).</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Controls/ScrollViewer.xml b/xml/System.Windows.Controls/ScrollViewer.xml
index d577e32a277..61fa28b6f18 100644
--- a/xml/System.Windows.Controls/ScrollViewer.xml
+++ b/xml/System.Windows.Controls/ScrollViewer.xml
@@ -692,7 +692,7 @@
       <Docs>
         <param name="element">The element from which the property value is read.</param>
         <summary>Returns the value of the <see cref="P:System.Windows.Controls.ScrollViewer.PanningDeceleration" /> property for the specified object.</summary>
-        <returns>The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond.</returns>
+        <returns>The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in device-independent units (1/96th inch per unit) per squared millisecond.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1760,8 +1760,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond when in inertia.</summary>
-        <value>The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond.</value>
+        <summary>Gets or sets the rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in device-independent units (1/96th inch per unit) per squared millisecond when in inertia.</summary>
+        <value>The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in device-independent units (1/96th inch per unit) per squared millisecond.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1879,7 +1879,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When a user drags a finger across an object, it is considered a translate manipulation.  The <xref:System.Windows.Controls.ScrollViewer> uses that manipulation to scroll. The <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> property specifies how much the <xref:System.Windows.Controls.ScrollViewer> scrolls for each unit of translation.  For example, if <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> is 2, the <xref:System.Windows.Controls.ScrollViewer> will scroll 2 [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] for every device-independent unit (1/96th inch) of the translate manipulation.  
+ When a user drags a finger across an object, it is considered a translate manipulation.  The <xref:System.Windows.Controls.ScrollViewer> uses that manipulation to scroll. The <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> property specifies how much the <xref:System.Windows.Controls.ScrollViewer> scrolls for each unit of translation.  For example, if <xref:System.Windows.Controls.ScrollViewer.PanningRatio%2A> is 2, the <xref:System.Windows.Controls.ScrollViewer> will scroll 2 device-independent units (1/96th inch per unit) for every device-independent unit (1/96th inch) of the translate manipulation.  
   
  ]]></format>
         </remarks>
@@ -2507,7 +2507,7 @@
       </Parameters>
       <Docs>
         <param name="element">The object on which to set the <see cref="P:System.Windows.Controls.ScrollViewer.PanningDeceleration" /> property.</param>
-        <param name="value">The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond.</param>
+        <param name="value">The rate <see cref="T:System.Windows.Controls.ScrollViewer" /> slows in device-independent units (1/96th inch per unit) per squared millisecond.</param>
         <summary>Sets the <see cref="P:System.Windows.Controls.ScrollViewer.PanningDeceleration" /> property for the specified object.</summary>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index 38e82822222..c6f6ffbc9bd 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -599,7 +599,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1618,7 +1618,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1986,7 +1986,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1995,7 +1995,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/ToolTipService.xml b/xml/System.Windows.Controls/ToolTipService.xml
index 1cb680ded03..11e8c507a16 100644
--- a/xml/System.Windows.Controls/ToolTipService.xml
+++ b/xml/System.Windows.Controls/ToolTipService.xml
@@ -872,7 +872,7 @@
  `qualifiedDouble`  
  A <xref:System.Double> value that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2229,7 +2229,7 @@ This is an attached property. For information about how to get the value of this
  `qualifiedDouble`  
  A <xref:System.Double> value that is followed by one of these unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Controls/VirtualizationCacheLengthUnit.xml b/xml/System.Windows.Controls/VirtualizationCacheLengthUnit.xml
index 8a3daa38cc7..f7d9805e79a 100644
--- a/xml/System.Windows.Controls/VirtualizationCacheLengthUnit.xml
+++ b/xml/System.Windows.Controls/VirtualizationCacheLengthUnit.xml
@@ -86,7 +86,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>The <see cref="P:System.Windows.Controls.VirtualizingPanel.CacheLength" /> is measured in terms of [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
+        <summary>The <see cref="P:System.Windows.Controls.VirtualizingPanel.CacheLength" /> is measured in terms of device-independent units (1/96th inch per unit).</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Controls/WrapPanel.xml b/xml/System.Windows.Controls/WrapPanel.xml
index 8b2852542da..a07f6dda40e 100644
--- a/xml/System.Windows.Controls/WrapPanel.xml
+++ b/xml/System.Windows.Controls/WrapPanel.xml
@@ -142,7 +142,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -258,7 +258,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/AnchoredBlock.xml b/xml/System.Windows.Documents/AnchoredBlock.xml
index 4d87d9c7fe6..8bc4dde6572 100644
--- a/xml/System.Windows.Documents/AnchoredBlock.xml
+++ b/xml/System.Windows.Documents/AnchoredBlock.xml
@@ -210,7 +210,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -219,7 +219,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -333,7 +333,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -521,7 +521,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -530,7 +530,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -638,7 +638,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -647,7 +647,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/Block.xml b/xml/System.Windows.Documents/Block.xml
index 81345c615b5..82917e280df 100644
--- a/xml/System.Windows.Documents/Block.xml
+++ b/xml/System.Windows.Documents/Block.xml
@@ -185,7 +185,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -194,7 +194,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -774,7 +774,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -962,7 +962,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -971,7 +971,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1103,7 +1103,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1112,7 +1112,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/Figure.xml b/xml/System.Windows.Documents/Figure.xml
index 1a4652d317e..7a94c74bfd1 100644
--- a/xml/System.Windows.Documents/Figure.xml
+++ b/xml/System.Windows.Documents/Figure.xml
@@ -433,7 +433,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -612,7 +612,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/Floater.xml b/xml/System.Windows.Documents/Floater.xml
index 29047b9cee6..a6828cd68fb 100644
--- a/xml/System.Windows.Documents/Floater.xml
+++ b/xml/System.Windows.Documents/Floater.xml
@@ -290,12 +290,12 @@
  *double*  
  <xref:System.Double>  
   
- A string representation of a <xref:System.Double> value equal to or greater than 0.0 but smaller than <xref:System.Double.PositiveInfinity>. An unqualified value is measured in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. Strings need not explicitly include decimal points.  
+ A string representation of a <xref:System.Double> value equal to or greater than 0.0 but smaller than <xref:System.Double.PositiveInfinity>. An unqualified value is measured in device-independent units (1/96th inch per unit). Strings need not explicitly include decimal points.  
   
  *qualifiedDouble*  
  A `double` value as described above, (except `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/FlowDocument.xml b/xml/System.Windows.Documents/FlowDocument.xml
index 8db54143d5f..68e5822d0ee 100644
--- a/xml/System.Windows.Documents/FlowDocument.xml
+++ b/xml/System.Windows.Documents/FlowDocument.xml
@@ -315,7 +315,7 @@
  *qualifiedDouble*  
  A *double* value as described above (excepting `Auto`), followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -505,7 +505,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -616,7 +616,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -996,7 +996,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1657,7 +1657,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1870,7 +1870,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -1977,7 +1977,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2084,7 +2084,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2191,7 +2191,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2363,7 +2363,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2472,7 +2472,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2481,7 +2481,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2586,7 +2586,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/List.xml b/xml/System.Windows.Documents/List.xml
index e9419f121ad..906a9a30904 100644
--- a/xml/System.Windows.Documents/List.xml
+++ b/xml/System.Windows.Documents/List.xml
@@ -230,7 +230,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/ListItem.xml b/xml/System.Windows.Documents/ListItem.xml
index 9693dd977a9..841f2eaf950 100644
--- a/xml/System.Windows.Documents/ListItem.xml
+++ b/xml/System.Windows.Documents/ListItem.xml
@@ -288,7 +288,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -297,7 +297,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -484,7 +484,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -692,7 +692,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -701,7 +701,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -833,7 +833,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -842,7 +842,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/Paragraph.xml b/xml/System.Windows.Documents/Paragraph.xml
index 8cddba9630a..7819c5ef057 100644
--- a/xml/System.Windows.Documents/Paragraph.xml
+++ b/xml/System.Windows.Documents/Paragraph.xml
@@ -592,7 +592,7 @@
  *qualifiedDouble*  
  A `double` value as described above, (except `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/Table.xml b/xml/System.Windows.Documents/Table.xml
index 865f49e5397..3f033db0f92 100644
--- a/xml/System.Windows.Documents/Table.xml
+++ b/xml/System.Windows.Documents/Table.xml
@@ -150,7 +150,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/TableCell.xml b/xml/System.Windows.Documents/TableCell.xml
index e7959b498be..cfec5016523 100644
--- a/xml/System.Windows.Documents/TableCell.xml
+++ b/xml/System.Windows.Documents/TableCell.xml
@@ -279,7 +279,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -288,7 +288,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -543,7 +543,7 @@
  *qualifiedDouble*  
  A *double* value as described above, (excepting `Auto`) followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -761,7 +761,7 @@
  *qualifiedUniformThickness*  
  A value described by *uniformThickness* followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -770,7 +770,7 @@
  *qualifiedIndependentThickness*  
  A value described by *independentThickness*, with each independent value followed by one of the following unit specifiers: `px`, `in`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Documents/TextElement.xml b/xml/System.Windows.Documents/TextElement.xml
index 8e04cff57f8..e140223402a 100644
--- a/xml/System.Windows.Documents/TextElement.xml
+++ b/xml/System.Windows.Documents/TextElement.xml
@@ -402,7 +402,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit specifiers: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows.Input/InertiaExpansionBehavior.xml b/xml/System.Windows.Input/InertiaExpansionBehavior.xml
index 3b7cbb2b76a..7ef0e52ae64 100644
--- a/xml/System.Windows.Input/InertiaExpansionBehavior.xml
+++ b/xml/System.Windows.Input/InertiaExpansionBehavior.xml
@@ -85,8 +85,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the rate that resizing slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per square milliseconds.</summary>
-        <value>The rate that resizing slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per square milliseconds. The default is <see cref="F:System.Double.NaN" />.</value>
+        <summary>Gets or sets the rate that resizing slows in device-independent units (1/96th inch per unit) per square milliseconds.</summary>
+        <value>The rate that resizing slows in device-independent units (1/96th inch per unit) per square milliseconds. The default is <see cref="F:System.Double.NaN" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Input/InertiaTranslationBehavior.xml b/xml/System.Windows.Input/InertiaTranslationBehavior.xml
index be59151d1f3..efd0fcea3e1 100644
--- a/xml/System.Windows.Input/InertiaTranslationBehavior.xml
+++ b/xml/System.Windows.Input/InertiaTranslationBehavior.xml
@@ -85,8 +85,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the rate the linear movement slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond.</summary>
-        <value>The rate the linear movement slows in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per squared millisecond.  The default is <see cref="F:System.Double.NaN" />.</value>
+        <summary>Gets or sets the rate the linear movement slows in device-independent units (1/96th inch per unit) per squared millisecond.</summary>
+        <value>The rate the linear movement slows in device-independent units (1/96th inch per unit) per squared millisecond.  The default is <see cref="F:System.Double.NaN" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Input/ManipulationDelta.xml b/xml/System.Windows.Input/ManipulationDelta.xml
index d4c5c02a4e3..645f8039a16 100644
--- a/xml/System.Windows.Input/ManipulationDelta.xml
+++ b/xml/System.Windows.Input/ManipulationDelta.xml
@@ -56,10 +56,10 @@
         <Parameter Name="expansion" Type="System.Windows.Vector" />
       </Parameters>
       <Docs>
-        <param name="translation">The linear motion of the manipulation in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="translation">The linear motion of the manipulation in device-independent units (1/96th inch per unit).</param>
         <param name="rotation">The rotation of the manipulation in degrees.</param>
         <param name="scale">The amount the manipulation has resized as a multiplier.</param>
-        <param name="expansion">The amount the manipulation has resized in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="expansion">The amount the manipulation has resized in device-independent units (1/96th inch per unit).</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Input.ManipulationDelta" /> class.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -87,13 +87,13 @@
         <ReturnType>System.Windows.Vector</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the amount the manipulation has resized in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The amount the manipulation has resized in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets or sets the amount the manipulation has resized in device-independent units (1/96th inch per unit).</summary>
+        <value>The amount the manipulation has resized in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> and <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> properties both report a resizing manipulation.  The difference between the two is the way in which the value is reported.  The <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> property reports the resizing manipulation in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> property reports the value as a multiplier.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 0.5, the manipulation is interpreted as decreasing the size by 50 percent.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 2, the manipulation is interpreted as increasing the size by 100 percent.  
+ The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> and <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> properties both report a resizing manipulation.  The difference between the two is the way in which the value is reported.  The <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> property reports the resizing manipulation in device-independent units (1/96th inch per unit). The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> property reports the value as a multiplier.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 0.5, the manipulation is interpreted as decreasing the size by 50 percent.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 2, the manipulation is interpreted as increasing the size by 100 percent.  
   
  ]]></format>
         </remarks>
@@ -171,7 +171,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> and <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> properties both report a resizing manipulation.  The difference between the two is the way in which the value is reported.  The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> property reports the value as a multiplier.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 0.5, the manipulation is interpreted as decreasing the size by 50 percent.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 2, the manipulation is interpreted as increasing the size by 100 percent. The <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> property reports the resizing manipulation in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].  
+ The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> and <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> properties both report a resizing manipulation.  The difference between the two is the way in which the value is reported.  The <xref:System.Windows.Input.ManipulationDelta.Scale%2A> property reports the value as a multiplier.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 0.5, the manipulation is interpreted as decreasing the size by 50 percent.  If <xref:System.Windows.Input.ManipulationDelta.Scale%2A> is 2, the manipulation is interpreted as increasing the size by 100 percent. The <xref:System.Windows.Input.ManipulationDelta.Expansion%2A> property reports the resizing manipulation in device-independent units (1/96th inch per unit).  
   
    
   
@@ -209,7 +209,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the linear motion of the manipulation.</summary>
-        <value>The linear motion of the manipulation in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The linear motion of the manipulation in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Input/ManipulationVelocities.xml b/xml/System.Windows.Input/ManipulationVelocities.xml
index d195259cc2c..798fd525a42 100644
--- a/xml/System.Windows.Input/ManipulationVelocities.xml
+++ b/xml/System.Windows.Input/ManipulationVelocities.xml
@@ -38,9 +38,9 @@
         <Parameter Name="expansionVelocity" Type="System.Windows.Vector" />
       </Parameters>
       <Docs>
-        <param name="linearVelocity">The speed of linear motion in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per millisecond.</param>
+        <param name="linearVelocity">The speed of linear motion in device-independent units (1/96th inch per unit) per millisecond.</param>
         <param name="angularVelocity">The speed of rotation in degrees per millisecond.</param>
-        <param name="expansionVelocity">The rate at which the manipulation is resized in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per millisecond.</param>
+        <param name="expansionVelocity">The rate at which the manipulation is resized in device-independent units (1/96th inch per unit) per millisecond.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Input.ManipulationVelocities" /> class.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -97,7 +97,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the rate at which the manipulation is resized.</summary>
-        <value>The rate at which the manipulation is resized in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per millisecond.</value>
+        <value>The rate at which the manipulation is resized in device-independent units (1/96th inch per unit) per millisecond.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -125,7 +125,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the speed of linear motion.</summary>
-        <value>The speed of linear motion in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] per millisecond.</value>
+        <value>The speed of linear motion in device-independent units (1/96th inch per unit) per millisecond.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml b/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
index 1d2f14f7a0e..9658689bd8a 100644
--- a/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
+++ b/xml/System.Windows.Media.Effects/DropShadowBitmapEffect.xml
@@ -458,7 +458,7 @@
       </ReturnValue>
       <Docs>
         <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.DropShadowEffect" />. Gets or sets the distance between the object and the shadow that it casts.</summary>
-        <value>The distance between the plane of the object casting the shadow and the shadow plane measured in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The valid range of values is from 0 through 300. The default is 5.</value>
+        <value>The distance between the plane of the object casting the shadow and the shadow plane measured in device-independent units (1/96th inch per unit). The valid range of values is from 0 through 300. The default is 5.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index 00813a88805..dd5a8e0d01b 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -836,8 +836,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the height of the source bitmap in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The height of the bitmap in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the height of the source bitmap in device-independent units (1/96th inch per unit).</summary>
+        <value>The height of the bitmap in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -983,8 +983,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the width of the bitmap in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</summary>
-        <value>The width of the bitmap in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <summary>Gets the width of the bitmap in device-independent units (1/96th inch per unit).</summary>
+        <value>The width of the bitmap in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/FormattedText.xml b/xml/System.Windows.Media/FormattedText.xml
index 944a71b7a59..303b7558447 100644
--- a/xml/System.Windows.Media/FormattedText.xml
+++ b/xml/System.Windows.Media/FormattedText.xml
@@ -123,7 +123,7 @@ Example of a formatted text string
         <param name="culture">The specific culture of the text.</param>
         <param name="flowDirection">The direction the text is read.</param>
         <param name="typeface">The font family, weight, style and stretch the text should be formatted with.</param>
-        <param name="emSize">The font size for the text's em measure, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font size for the text's em measure, provided in device-independent units (1/96th inch per unit).</param>
         <param name="foreground">The brush used to paint the each glyph.</param>
         <param name="pixelsPerDip">The Pixels Per Density Independent Pixel value, which is the equivalent of the scale factor. For example, if the DPI of a screen is 120 (or 1.25 because 120/96 = 1.25) , 1.25 pixel per density independent pixel is drawn. DIP is the unit of measurement used by WPF to be independent of device resolution and DPIs.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Media.FormattedText" /> class with the specified text, culture, flow direction, typeface, font size, foreground brush, and pixelsPerDip value.</summary>
@@ -168,7 +168,7 @@ Example of a formatted text string
         <param name="culture">The specific culture of the text.</param>
         <param name="flowDirection">The direction the text is read.</param>
         <param name="typeface">The font family, weight, style and stretch the text should be formatted with.</param>
-        <param name="emSize">The font size for the text's em measure, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font size for the text's em measure, provided in device-independent units (1/96th inch per unit).</param>
         <param name="foreground">The brush used to paint the each glyph.</param>
         <param name="numberSubstitution">The number substitution behavior to apply to the text.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Media.FormattedText" /> class with the specified text, culture, flow direction, typeface, font size, brush, and number substitution behavior.</summary>
@@ -203,7 +203,7 @@ Example of a formatted text string
         <param name="culture">The specific culture of the text.</param>
         <param name="flowDirection">The direction the text is read.</param>
         <param name="typeface">The font family, weight, style and stretch the text should be formatted with.</param>
-        <param name="emSize">The font size for the text's em measure, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font size for the text's em measure, provided in device-independent units (1/96th inch per unit).</param>
         <param name="foreground">The brush used to paint the each glyph.</param>
         <param name="numberSubstitution">Specifies how numbers in text     are displayed, based on <see cref="T:System.Windows.Media.NumberSubstitution" />. This value can be <see langword="null" />.</param>
         <param name="pixelsPerDip">The Pixels Per Density Independent Pixel value, which is the equivalent of the scale factor. For example, if the DPI of a screen is 120 (or 1.25 because 120/96 = 1.25) , 1.25 pixel per density independent pixel is drawn. DIP is the unit of measurement used by WPF to be independent of device resolution and DPIs.</param>
@@ -245,7 +245,7 @@ Example of a formatted text string
         <param name="culture">The specific culture of the text.</param>
         <param name="flowDirection">The direction the text is read.</param>
         <param name="typeface">The font family, weight, style and stretch the text should be formatted with.</param>
-        <param name="emSize">The font size for the text's em measure, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font size for the text's em measure, provided in device-independent units (1/96th inch per unit).</param>
         <param name="foreground">The brush used to paint the each glyph.</param>
         <param name="numberSubstitution">The number substitution behavior to apply to the text.</param>
         <param name="textFormattingMode">The <see cref="T:System.Windows.Media.TextFormattingMode" /> to apply to the text.</param>
@@ -282,7 +282,7 @@ Example of a formatted text string
         <param name="culture">The specific culture of the text.</param>
         <param name="flowDirection">The direction the text is read.</param>
         <param name="typeface">The font family, weight, style and stretch the text should be formatted with.</param>
-        <param name="emSize">The font size for the text's em measure, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font size for the text's em measure, provided in device-independent units (1/96th inch per unit).</param>
         <param name="foreground">he brush used to paint the each glyph.</param>
         <param name="numberSubstitution">Specifies how numbers in text     are displayed, based on <see cref="T:System.Windows.Media.NumberSubstitution" />. This value can be <see langword="null" />.</param>
         <param name="textFormattingMode">The formatting mode that affects how WPF displays text.</param>
@@ -310,7 +310,7 @@ Example of a formatted text string
       </ReturnValue>
       <Docs>
         <summary>Gets the distance from the top of the first line to the baseline of the first line of a <see cref="T:System.Windows.Media.FormattedText" /> object.</summary>
-        <value>The distance from the top of the first line to the baseline of the first line, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The distance from the top of the first line to the baseline of the first line, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -483,7 +483,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets the distance from the topmost drawn pixel of the first line to the bottommost drawn pixel of the last line.</summary>
-        <value>The distance from the topmost drawn pixel of the first line to the bottommost drawn pixel of the last line, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The distance from the topmost drawn pixel of the first line to the bottommost drawn pixel of the last line, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -537,7 +537,7 @@ Example of an image brush applied to the stroke and highlight
       <Parameters />
       <Docs>
         <summary>Retrieves an array of text widths. Each element in the array represents the maximum text width of sequential lines of text.</summary>
-        <returns>An array of maximum text widths, each width provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</returns>
+        <returns>An array of maximum text widths, each width provided in device-independent units (1/96th inch per unit).</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -567,7 +567,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets the distance from the top of the first line to the bottom of the last line of the <see cref="T:System.Windows.Media.FormattedText" /> object.</summary>
-        <value>The distance from the top of the first line to the bottom of the last line, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The distance from the top of the first line to the bottom of the last line, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -590,7 +590,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets the line height, or line spacing, between lines of text.</summary>
-        <value>The line spacing between lines of text, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The line spacing between lines of text, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -662,7 +662,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum height of a text column.</summary>
-        <value>The maximum height of a text column, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The maximum height of a text column, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -706,7 +706,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum text width (length) for a line of text.</summary>
-        <value>The maximum text width for a line of text, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The maximum text width for a line of text, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -748,7 +748,7 @@ Example of an image brush applied to the stroke and highlight
       </ReturnValue>
       <Docs>
         <summary>Gets the smallest possible text width that can fully contain the specified text content.</summary>
-        <value>The minimum text width of the text source, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The minimum text width of the text source, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -791,7 +791,7 @@ Minimum text width
       </ReturnValue>
       <Docs>
         <summary>Gets the distance from the bottom of the last line of text to the bottommost drawn pixel.</summary>
-        <value>The distance from the bottom of the last line to the bottommost inked pixel, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The distance from the bottom of the last line to the bottommost inked pixel, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -821,7 +821,7 @@ Minimum text width
       </ReturnValue>
       <Docs>
         <summary>Gets the maximum distance from the leading alignment point to the leading drawn pixel of a line.</summary>
-        <value>The maximum distance from the leading alignment point to the leading drawn pixel of a line, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The maximum distance from the leading alignment point to the leading drawn pixel of a line, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -851,7 +851,7 @@ Minimum text width
       </ReturnValue>
       <Docs>
         <summary>Gets the maximum distance from the trailing inked pixel to the trailing alignment point of a line.</summary>
-        <value>The maximum distance from the trailing inked pixel to the trailing alignment point of a line, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The maximum distance from the trailing inked pixel to the trailing alignment point of a line, provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1146,7 +1146,7 @@ Minimum text width
         <Parameter Name="emSize" Type="System.Double" />
       </Parameters>
       <Docs>
-        <param name="emSize">The font 'em' measure size, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font 'em' measure size, provided in device-independent units (1/96th inch per unit).</param>
         <summary>Sets the font size for the entire set of characters in the <see cref="T:System.Windows.Media.FormattedText" /> object.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1181,7 +1181,7 @@ Minimum text width
         <Parameter Name="count" Type="System.Int32" />
       </Parameters>
       <Docs>
-        <param name="emSize">The font 'em' measure size, provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="emSize">The font 'em' measure size, provided in device-independent units (1/96th inch per unit).</param>
         <param name="startIndex">The start index of the initial character to apply the font size to.</param>
         <param name="count">The number of characters to apply the font size to.</param>
         <summary>Sets the font size for a specified subset of characters in the <see cref="T:System.Windows.Media.FormattedText" /> object.</summary>
@@ -1657,7 +1657,7 @@ Minimum text width
         <Parameter Name="maxTextWidths" Type="System.Double[]" />
       </Parameters>
       <Docs>
-        <param name="maxTextWidths">An array of maximum text widths, each width provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</param>
+        <param name="maxTextWidths">An array of maximum text widths, each width provided in device-independent units (1/96th inch per unit).</param>
         <summary>Sets an array of maximum text widths within the <see cref="T:System.Windows.Media.FormattedText" />, on a per-line basis. Each element in the array represents the maximum text width of sequential lines of text.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1949,7 +1949,7 @@ Example of text decoration types
       </ReturnValue>
       <Docs>
         <summary>Gets the width between the leading and trailing alignment points of a line, excluding any trailing white-space characters.</summary>
-        <value>The width between the leading and trailing alignment points of a line, excluding any trailing white-space characters. Provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The width between the leading and trailing alignment points of a line, excluding any trailing white-space characters. Provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1979,7 +1979,7 @@ Example of text decoration types
       </ReturnValue>
       <Docs>
         <summary>Gets the width between the leading and trailing alignment points of a line, including any trailing white-space characters.</summary>
-        <value>The width between the leading and trailing alignment points of a line, including any trailing white-space characters. Provided in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)].</value>
+        <value>The width between the leading and trailing alignment points of a line, including any trailing white-space characters. Provided in device-independent units (1/96th inch per unit).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/FigureLength.xml b/xml/System.Windows/FigureLength.xml
index e22a5719aa8..db5b2378fea 100644
--- a/xml/System.Windows/FigureLength.xml
+++ b/xml/System.Windows/FigureLength.xml
@@ -53,7 +53,7 @@
  *qualifiedDouble*  
  A *double* value as described above followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index dceb7c9ad56..4acb08ac537 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -123,7 +123,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the rendered height of this element.</summary>
-        <value>The element's height, as a value in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is 0 (zero).</value>
+        <value>The element's height, as a value in device-independent units (1/96th inch per unit). The default value is 0 (zero).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -195,7 +195,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the rendered width of this element.</summary>
-        <value>The element's width, as a value in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is 0 (zero).</value>
+        <value>The element's width, as a value in device-independent units (1/96th inch per unit). The default value is 0 (zero).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1991,7 +1991,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the suggested height of the element.</summary>
-        <value>The height of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is <see cref="F:System.Double.NaN" />. This value must be equal to or greater than 0.0.</value>
+        <value>The height of the element, in device-independent units (1/96th inch per unit). The default value is <see cref="F:System.Double.NaN" />. This value must be equal to or greater than 0.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2037,7 +2037,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2762,7 +2762,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum height constraint of the element.</summary>
-        <value>The maximum height of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is <see cref="F:System.Double.PositiveInfinity" />. This value can be any value equal to or greater than 0.0. <see cref="F:System.Double.PositiveInfinity" /> is also valid.</value>
+        <value>The maximum height of the element, in device-independent units (1/96th inch per unit). The default value is <see cref="F:System.Double.PositiveInfinity" />. This value can be any value equal to or greater than 0.0. <see cref="F:System.Double.PositiveInfinity" /> is also valid.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2796,7 +2796,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -2867,7 +2867,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the maximum width constraint of the element.</summary>
-        <value>The maximum width of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is <see cref="F:System.Double.PositiveInfinity" />. This value can be any value equal to or greater than 0.0. <see cref="F:System.Double.PositiveInfinity" /> is also valid.</value>
+        <value>The maximum width of the element, in device-independent units (1/96th inch per unit). The default value is <see cref="F:System.Double.PositiveInfinity" />. This value can be any value equal to or greater than 0.0. <see cref="F:System.Double.PositiveInfinity" /> is also valid.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2901,7 +2901,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -3059,7 +3059,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the minimum height constraint of the element.</summary>
-        <value>The minimum height of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is 0.0. This value can be any value equal to or greater than 0.0. However, <see cref="F:System.Double.PositiveInfinity" /> is NOT valid, nor is <see cref="F:System.Double.NaN" />.</value>
+        <value>The minimum height of the element, in device-independent units (1/96th inch per unit). The default value is 0.0. This value can be any value equal to or greater than 0.0. However, <see cref="F:System.Double.PositiveInfinity" /> is NOT valid, nor is <see cref="F:System.Double.NaN" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3093,7 +3093,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -3164,7 +3164,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the minimum width constraint of the element.</summary>
-        <value>The minimum width of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is 0.0. This value can be any value equal to or greater than 0.0. However, <see cref="F:System.Double.PositiveInfinity" /> is not valid, nor is <see cref="F:System.Double.NaN" />.</value>
+        <value>The minimum width of the element, in device-independent units (1/96th inch per unit). The default value is 0.0. This value can be any value equal to or greater than 0.0. However, <see cref="F:System.Double.PositiveInfinity" /> is not valid, nor is <see cref="F:System.Double.NaN" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3198,7 +3198,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
@@ -5665,7 +5665,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the width of the element.</summary>
-        <value>The width of the element, in [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]. The default value is <see cref="F:System.Double.NaN" />. This value must be equal to or greater than 0.0. See Remarks for upper bound information.</value>
+        <value>The width of the element, in device-independent units (1/96th inch per unit). The default value is <see cref="F:System.Double.NaN" />. This value must be equal to or greater than 0.0. See Remarks for upper bound information.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -5707,7 +5707,7 @@
  *qualifiedDouble*  
  A *double* value as described above, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows/GridLength.xml b/xml/System.Windows/GridLength.xml
index fd2b2f87d8e..83e0b3d0754 100644
--- a/xml/System.Windows/GridLength.xml
+++ b/xml/System.Windows/GridLength.xml
@@ -49,7 +49,7 @@
 <a name="xamlValues_GridLength"></a>   
 ## XAML Values  
  *doubleLength*  
- The element's length, described as either a <xref:System.Double> value that specifies a [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] measure, or as a *qualifiedDouble* (see below).  
+ The element's length, described as either a <xref:System.Double> value that specifies a device-independent units (1/96th inch per unit) measure, or as a *qualifiedDouble* (see below).  
   
  *autoValue*  
  The element's length, described by either the value Auto or *. See <xref:System.Windows.GridUnitType> for more information on the values Auto and *.  
@@ -57,7 +57,7 @@
  *qualifiedDouble*  
  A *double* value as described above for any of the measures, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   
diff --git a/xml/System.Windows/Thickness.xml b/xml/System.Windows/Thickness.xml
index 3c095a58b7e..80f710f80d0 100644
--- a/xml/System.Windows/Thickness.xml
+++ b/xml/System.Windows/Thickness.xml
@@ -59,21 +59,21 @@
 <a name="xamlValues_Thickness"></a>   
 ## XAML Values  
  *left*  
- The left edge of the frame, described as either a <xref:System.Double> value that specifies a [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] measure, or as a *qualifiedDouble* (see below). If only a single measure is specified, that measure is applied to ALL of the left,top,right,bottom values of a <xref:System.Windows.Thickness>. If only a pair of left,top measures are specified, these measures are applied symmetrically to a <xref:System.Windows.Thickness>: the left value is used for right; the top value is used for bottom.  
+ The left edge of the frame, described as either a <xref:System.Double> value that specifies a device-independent units (1/96th inch per unit) measure, or as a *qualifiedDouble* (see below). If only a single measure is specified, that measure is applied to ALL of the left,top,right,bottom values of a <xref:System.Windows.Thickness>. If only a pair of left,top measures are specified, these measures are applied symmetrically to a <xref:System.Windows.Thickness>: the left value is used for right; the top value is used for bottom.  
   
  *top*  
- The top edge of the frame, described as either a <xref:System.Double> value that specifies a [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] measure, or as a *qualifiedDouble* (see below). If only a pair of left,top measures are specified, these measures are applied symmetrically to a <xref:System.Windows.Thickness>: the left value is used for right; the top value is used for bottom.  
+ The top edge of the frame, described as either a <xref:System.Double> value that specifies a device-independent units (1/96th inch per unit) measure, or as a *qualifiedDouble* (see below). If only a pair of left,top measures are specified, these measures are applied symmetrically to a <xref:System.Windows.Thickness>: the left value is used for right; the top value is used for bottom.  
   
  *right*  
- The right edge of the frame, described as either a <xref:System.Double> value that specifies a [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] measure, or as a *qualifiedDouble* (see below). If left unspecified, will use the left value.  
+ The right edge of the frame, described as either a <xref:System.Double> value that specifies a device-independent units (1/96th inch per unit) measure, or as a *qualifiedDouble* (see below). If left unspecified, will use the left value.  
   
  *bottom*  
- The bottom edge of the frame, described as either a <xref:System.Double> value that specifies a [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)] measure, or as a *qualifiedDouble* (see below). If left unspecified, will use the left value.  
+ The bottom edge of the frame, described as either a <xref:System.Double> value that specifies a device-independent units (1/96th inch per unit) measure, or as a *qualifiedDouble* (see below). If left unspecified, will use the left value.  
   
  *qualifiedDouble*  
  A *double* value as described above for any of the measures, followed by one of the following unit declaration strings: `px`, `in`, `cm`, `pt`.  
   
- `px` (default) is [!INCLUDE[TLA#tla_dipixel#plural](~/includes/tlasharptla-dipixelsharpplural-md.md)]  
+ `px` (default) is device-independent units (1/96th inch per unit)  
   
  `in` is inches; 1in==96px  
   

From e6ce8d729929070ed3546b02f18c3e9763200221 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:24:49 -0800
Subject: [PATCH 118/236] tlasharptla-dll

---
 xml/System.Windows.Automation/ClientSideProviderDescription.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Automation/ClientSideProviderDescription.xml b/xml/System.Windows.Automation/ClientSideProviderDescription.xml
index 0e38ed73dc2..19f6eae82dc 100644
--- a/xml/System.Windows.Automation/ClientSideProviderDescription.xml
+++ b/xml/System.Windows.Automation/ClientSideProviderDescription.xml
@@ -241,7 +241,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the name of the executable or [!INCLUDE[TLA#tla_dll](~/includes/tlasharptla-dll-md.md)] for the process where the window resides.</summary>
+        <summary>Gets the name of the executable or dynamic-link library (DLL) for the process where the window resides.</summary>
         <value>The image name.</value>
         <remarks>To be added.</remarks>
       </Docs>

From 1297002e684b79b95082c09c8758282c391c3d55 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:42:58 -0800
Subject: [PATCH 119/236] tlasharptla-dpi

---
 .../BitmapSource.xml                             | 16 ++++++++--------
 .../WriteableBitmap.xml                          |  4 ++--
 xml/System.Windows.Media/ContainerVisual.xml     |  4 ++--
 xml/System.Windows.Media/Visual.xml              |  4 ++--
 xml/System.Windows.Media/VisualTreeHelper.xml    |  4 ++--
 xml/System.Windows/UIElement.xml                 |  2 +-
 6 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index dd5a8e0d01b..b1db23a1e09 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -438,8 +438,8 @@
       <Docs>
         <param name="pixelWidth">The width of the bitmap.</param>
         <param name="pixelHeight">The height of the bitmap.</param>
-        <param name="dpiX">The horizontal [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
-        <param name="dpiY">The vertical [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
+        <param name="dpiX">The horizontal dots per inch (dpi) of the bitmap.</param>
+        <param name="dpiY">The vertical dots per inch (dpi) of the bitmap.</param>
         <param name="pixelFormat">The pixel format of the bitmap.</param>
         <param name="palette">The palette of the bitmap.</param>
         <param name="pixels">An array of bytes that represents the content of a bitmap image.</param>
@@ -498,8 +498,8 @@
       <Docs>
         <param name="pixelWidth">The width of the bitmap.</param>
         <param name="pixelHeight">The height of the bitmap.</param>
-        <param name="dpiX">The horizontal [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
-        <param name="dpiY">The vertical [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
+        <param name="dpiX">The horizontal dots per inch (dpi) of the bitmap.</param>
+        <param name="dpiY">The vertical dots per inch (dpi) of the bitmap.</param>
         <param name="pixelFormat">The pixel format of the bitmap.</param>
         <param name="palette">The palette of the bitmap.</param>
         <param name="buffer">A pointer to the buffer that contains the bitmap data in memory.</param>
@@ -656,8 +656,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the horizontal [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the image.</summary>
-        <value>The horizontal [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the image; that is, the [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] along the x-axis.</value>
+        <summary>Gets the horizontal dots per inch (dpi) of the image.</summary>
+        <value>The horizontal dots per inch (dpi) of the image; that is, the dots per inch (dpi) along the x-axis.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -679,8 +679,8 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the vertical [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the image.</summary>
-        <value>The vertical [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the image; that is, the [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] along the y-axis.</value>
+        <summary>Gets the vertical dots per inch (dpi) of the image.</summary>
+        <value>The vertical dots per inch (dpi) of the image; that is, the dots per inch (dpi) along the y-axis.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Imaging/WriteableBitmap.xml b/xml/System.Windows.Media.Imaging/WriteableBitmap.xml
index cd23f0343bf..9f78a94c6ef 100644
--- a/xml/System.Windows.Media.Imaging/WriteableBitmap.xml
+++ b/xml/System.Windows.Media.Imaging/WriteableBitmap.xml
@@ -135,8 +135,8 @@
       <Docs>
         <param name="pixelWidth">The desired width of the bitmap.</param>
         <param name="pixelHeight">The desired height of the bitmap.</param>
-        <param name="dpiX">The horizontal [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
-        <param name="dpiY">The vertical [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] of the bitmap.</param>
+        <param name="dpiX">The horizontal dots per inch (dpi) of the bitmap.</param>
+        <param name="dpiY">The vertical dots per inch (dpi) of the bitmap.</param>
         <param name="pixelFormat">The <see cref="T:System.Windows.Media.PixelFormat" /> of the bitmap.</param>
         <param name="palette">The <see cref="T:System.Windows.Media.Imaging.BitmapPalette" /> of the bitmap.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Media.Imaging.WriteableBitmap" /> class with the specified parameters.</summary>
diff --git a/xml/System.Windows.Media/ContainerVisual.xml b/xml/System.Windows.Media/ContainerVisual.xml
index fa56ba1ac78..e5b053bea79 100644
--- a/xml/System.Windows.Media/ContainerVisual.xml
+++ b/xml/System.Windows.Media/ContainerVisual.xml
@@ -669,7 +669,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
@@ -708,7 +708,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
diff --git a/xml/System.Windows.Media/Visual.xml b/xml/System.Windows.Media/Visual.xml
index 106de7ba793..4b881b18d67 100644
--- a/xml/System.Windows.Media/Visual.xml
+++ b/xml/System.Windows.Media/Visual.xml
@@ -1312,7 +1312,7 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
@@ -1345,7 +1345,7 @@ Visual class hierarchy
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels, eliminating the soft edges produced by anti-aliasing.  
   
diff --git a/xml/System.Windows.Media/VisualTreeHelper.xml b/xml/System.Windows.Media/VisualTreeHelper.xml
index 8c416f8d6f3..fb705840870 100644
--- a/xml/System.Windows.Media/VisualTreeHelper.xml
+++ b/xml/System.Windows.Media/VisualTreeHelper.xml
@@ -771,7 +771,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
@@ -808,7 +808,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)] setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
+ Pixel snapping is the process in which content layout is fixed so that object edges are rendered on device-specific pixels. The WPF graphics system uses device-independent units to enable resolution and device independence. Each device independent pixel automatically scales with the system's dots per inch (dpi) setting. This provides WPF applications proper scaling for different dpi settings and makes the application automatically dpi-aware.  
   
  However, this dpi independence can create irregular edge rendering due to anti-aliasing. These artifacts, commonly seen as blurry, or "soft" edges, can occur when the location of an edge falls in the middle of a device pixel rather than between device pixels. To address this issue, WPF provides a way for object edges in a visual tree to "snap" to device pixels through pixel snapping, eliminating the soft edges produced by anti-aliasing.  
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 08056d9df58..afe7929da7b 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -13204,7 +13204,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can set this property to `true` on your root element to enable pixel snap rendering throughout the UI. For devices operating at greater than 96 [!INCLUDE[TLA#tla_dpi](~/includes/tlasharptla-dpi-md.md)], pixel snap rendering can minimize anti-aliasing visual artifacts in the vicinity of single-unit solid lines.  
+ You can set this property to `true` on your root element to enable pixel snap rendering throughout the UI. For devices operating at greater than 96 dots per inch (dpi), pixel snap rendering can minimize anti-aliasing visual artifacts in the vicinity of single-unit solid lines.  
   
  When inherited by <xref:System.Windows.FrameworkElement> or any possible derived classes, <xref:System.Windows.FrameworkElement> overrides the metadata for this dependency property to set the <xref:System.Windows.FrameworkPropertyMetadata.Inherits%2A> metadata property to `true`. What this achieves is that only the outermost element in a subtree needs to specify <xref:System.Windows.UIElement.SnapsToDevicePixels%2A> as `true`, and all child elements of that subtree will then report <xref:System.Windows.UIElement.SnapsToDevicePixels%2A> as `true` and will have the <xref:System.Windows.UIElement.SnapsToDevicePixels%2A> visual effect.  
   

From 42b488e5e368325fd035684c2ee2dffecb8a9947 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:45:34 -0800
Subject: [PATCH 120/236] tlasharptla-emf

---
 xml/System.Printing/PrintQueue.xml       | 4 ++--
 xml/System.Printing/PrintQueueStream.xml | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index badf0411251..b44ae78ec0f 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -424,7 +424,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is [!INCLUDE[TLA#tla_emf](~/includes/tlasharptla-emf-md.md)] or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
@@ -481,7 +481,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is [!INCLUDE[TLA#tla_emf](~/includes/tlasharptla-emf-md.md)] or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
diff --git a/xml/System.Printing/PrintQueueStream.xml b/xml/System.Printing/PrintQueueStream.xml
index 7feb2d76268..ef1bd673323 100644
--- a/xml/System.Printing/PrintQueueStream.xml
+++ b/xml/System.Printing/PrintQueueStream.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this class to write device specific information to a spool file that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is [!INCLUDE[TLA#tla_emf](~/includes/tlasharptla-emf-md.md)] or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
+ Use this class to write device specific information to a spool file that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
   
 > [!CAUTION]
 >  Classes within the <xref:System.Printing> namespace are not supported for use within a Windows service or ASP.NET application or service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.  

From ad56a81722e8781b17215cf1f6d22242e41f007c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:45:58 -0800
Subject: [PATCH 121/236] tlasharptla-exif

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml    | 10 +++++-----
 .../BitmapMetadataBlob.xml                             |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index 5cc99965df4..d32a452ff7a 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index 734f2dc8755..b9da8d76ef5 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: [!INCLUDE[TLA#tla_exif](~/includes/tlasharptla-exif-md.md)], tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
     </remarks>

From 0731bcd6a7ff33515db6ec088a81262f6a02662b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:46:19 -0800
Subject: [PATCH 122/236] tlasharptla-gdi

---
 xml/System.Windows.Interop/Imaging.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Interop/Imaging.xml b/xml/System.Windows.Interop/Imaging.xml
index f7850b2182f..9f48bc671a5 100644
--- a/xml/System.Windows.Interop/Imaging.xml
+++ b/xml/System.Windows.Interop/Imaging.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class provides creation mechanisms for the primary bitmap imaging class in WPF, <xref:System.Windows.Media.Imaging.BitmapSource>. This includes methods that create a <xref:System.Windows.Media.Imaging.BitmapSource> based on [!INCLUDE[TLA#tla_gdi](~/includes/tlasharptla-gdi-md.md)] objects , and memory sections.  
+ This class provides creation mechanisms for the primary bitmap imaging class in WPF, <xref:System.Windows.Media.Imaging.BitmapSource>. This includes methods that create a <xref:System.Windows.Media.Imaging.BitmapSource> based on Microsoft Windows Graphics Device Interface (GDI) objects , and memory sections.  
   
  ]]></format>
     </remarks>

From 0527cc7fa12db976635acafd11fb395a2bb965d0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:46:42 -0800
Subject: [PATCH 123/236] tlasharptla-gif

---
 xml/System.Windows.Media.Imaging/BitmapDecoder.xml          | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapEncoder.xml          | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapFrame.xml            | 2 +-
 xml/System.Windows.Media.Imaging/BitmapPalette.xml          | 2 +-
 xml/System.Windows.Media.Imaging/BitmapPalettes.xml         | 2 +-
 xml/System.Windows.Media.Imaging/BitmapSource.xml           | 2 +-
 xml/System.Windows.Media.Imaging/GifBitmapDecoder.xml       | 4 ++--
 xml/System.Windows.Media.Imaging/GifBitmapEncoder.xml       | 2 +-
 xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml | 2 +-
 9 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index d399889467e..edc70e4058a 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -26,7 +26,7 @@
   
  Unless a specific codec is selected, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an [!INCLUDE[TLA#tla_isv](~/includes/tlasharptla-isv-md.md)] to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
   
- [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] are the only implemented image formats that support multiple frames.  
+ [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) are the only implemented image formats that support multiple frames.  
   
    
   
@@ -486,7 +486,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images support more than one frame.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images support more than one frame.  
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> objects returned by this property are frozen.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
index 670debd4789..72c3800965f 100644
--- a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
@@ -196,7 +196,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)], and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], Graphics Interchange Format (GIF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
   
 <a name="xamlTextUsage_Frames"></a>   
 ## XAML Text Usage  
@@ -273,7 +273,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images (and some older, non-standard bitmap (BMP) images) support palettes.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images (and some older, non-standard bitmap (BMP) images) support palettes.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapFrame.xml b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
index 030042dc622..3cd5c533b15 100644
--- a/xml/System.Windows.Media.Imaging/BitmapFrame.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
@@ -29,7 +29,7 @@
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> returned from a decoder is always frozen. If you require a modifiable copy, you must first create a copy of the <xref:System.Windows.Media.Imaging.BitmapFrame> by using the <xref:System.Windows.Media.Imaging.BitmapSource.Clone%2A> method.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] format images support multiple frames.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) format images support multiple frames.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapPalette.xml b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
index 70428a9a12e..477d75af2ae 100644
--- a/xml/System.Windows.Media.Imaging/BitmapPalette.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] image formats support image palettes. However, other image types can be used to define a <xref:System.Windows.Media.Imaging.BitmapPalette>. Attempting to define a <xref:System.Windows.Media.Imaging.BitmapPalette> for an unsupported bitmap format does not result in an exception; the designated <xref:System.Windows.Media.Imaging.BitmapPalette> is simply ignored.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) image formats support image palettes. However, other image types can be used to define a <xref:System.Windows.Media.Imaging.BitmapPalette>. Attempting to define a <xref:System.Windows.Media.Imaging.BitmapPalette> for an unsupported bitmap format does not result in an exception; the designated <xref:System.Windows.Media.Imaging.BitmapPalette> is simply ignored.  
   
  [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports both custom color palettes and predefined palettes defined by the <xref:System.Windows.Media.Imaging.BitmapPalettes> class.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapPalettes.xml b/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
index 76843ffddeb..04ff7db155b 100644
--- a/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapPalettes> properties whose names end with "Transparent" have an additional "color" that is fully transparent. In the case of palettes that already have 256 colors, the last color is replaced by the transparent color.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] image formats support palettes.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) image formats support palettes.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index b1db23a1e09..4f7ceabd873 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)], [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Imaging/GifBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/GifBitmapDecoder.xml
index 1186b02b56a..3bf8cae0093 100644
--- a/xml/System.Windows.Media.Imaging/GifBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/GifBitmapDecoder.xml
@@ -77,7 +77,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a Graphics Interchange Format (GIF) encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -124,7 +124,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a Graphics Interchange Format (GIF) encoded image.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Imaging/GifBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/GifBitmapEncoder.xml
index ab1ed69166c..8debbb64ace 100644
--- a/xml/System.Windows.Media.Imaging/GifBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/GifBitmapEncoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images do not support global preview, global thumbnails, global metadata, frame level thumbnails, or frame level metadata. [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images do support multiple frames.  
+ Graphics Interchange Format (GIF) images do not support global preview, global thumbnails, global metadata, frame level thumbnails, or frame level metadata. Graphics Interchange Format (GIF) images do support multiple frames.  
   
  Encoding does not work in partial trust. See [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security) for information on partial trust.  
   
diff --git a/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
index fe79537589e..a121f5801b1 100644
--- a/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
@@ -155,7 +155,7 @@
   
  Any frame obtained from a <xref:System.Windows.Media.Imaging.LateBoundBitmapDecoder> while the image is downloading will return a width/height of `1,1` until the frames have finished downloading.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and [!INCLUDE[TLA#tla_gif](~/includes/tlasharptla-gif-md.md)] images support more than one frame.  
+ Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images support more than one frame.  
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> objects that this property returns are frozen.  
   

From 543555e9df2eb97a7f2a48a4607098073fb2cf5d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:47:20 -0800
Subject: [PATCH 124/236] tlasharptla-gui

---
 xml/System.Printing/PrintQueue.xml                              | 2 +-
 xml/System.Windows.Automation.Peers/AutomationPeer.xml          | 2 +-
 .../ContentElementAutomationPeer.xml                            | 2 +-
 .../FrameworkElementAutomationPeer.xml                          | 2 +-
 .../GenericRootAutomationPeer.xml                               | 2 +-
 xml/System.Windows.Automation.Peers/GroupBoxAutomationPeer.xml  | 2 +-
 xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml | 2 +-
 xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml      | 2 +-
 xml/System.Windows.Automation.Peers/LabelAutomationPeer.xml     | 2 +-
 xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml  | 2 +-
 xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml   | 2 +-
 xml/System.Windows.Automation.Peers/TextAutomationPeer.xml      | 2 +-
 .../UIElement3DAutomationPeer.xml                               | 2 +-
 xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml | 2 +-
 xml/System.Windows.Automation.Peers/WindowAutomationPeer.xml    | 2 +-
 15 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index b44ae78ec0f..48b05ffff25 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -431,7 +431,7 @@
 > [!CAUTION]
 >  If the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> is not closed with <xref:System.IO.Stream.Close%2A> before the end of the thread in which <xref:System.Printing.PrintQueue.AddJob%2A> is called, then an <xref:System.InvalidOperationException> is thrown when that thread ends because the spooler thread cannot gain control over the <xref:System.IO.Stream> object.  
   
- In the print queue's [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)], the job has the name "Print System Document". To give the job a different name, use the <xref:System.Printing.PrintQueue.AddJob%28System.String%29> overload.  
+ In the print queue's graphical user interface (GUI), the job has the name "Print System Document". To give the job a different name, use the <xref:System.Printing.PrintQueue.AddJob%28System.String%29> overload.  
   
  Other ways to print in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
   
diff --git a/xml/System.Windows.Automation.Peers/AutomationPeer.xml b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
index f497bc7a31b..159c170bd08 100644
--- a/xml/System.Windows.Automation.Peers/AutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
@@ -1037,7 +1037,7 @@ This method calls the derived implementation of <xref:System.Windows.Automation.
 ## Remarks  
  You can think of this value as a string that users use to explain the control they are referring to. This property is used by tools such as Narrator to tell the user what the control is. For example, a button with a string "OK" should return "OK". A <xref:System.Windows.Controls.ListBox> control that lets users select a color might return "Colors".  
   
- Make sure that you have assigned a name to all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that accessibility tools such as screen readers can refer to each control in a localized manner.  
+ Make sure that you have assigned a name to all controls in the graphical user interface (GUI) so that accessibility tools such as screen readers can refer to each control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
index 64845ddaba6..b556ded5db6 100644
--- a/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ContentElementAutomationPeer.xml
@@ -497,7 +497,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/FrameworkElementAutomationPeer.xml b/xml/System.Windows.Automation.Peers/FrameworkElementAutomationPeer.xml
index f70b80070c5..ea5eceef39f 100644
--- a/xml/System.Windows.Automation.Peers/FrameworkElementAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/FrameworkElementAutomationPeer.xml
@@ -164,7 +164,7 @@ For example, if the element is a <xref:System.Windows.Controls.ComboBox> control
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/GenericRootAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GenericRootAutomationPeer.xml
index 50ad39c4e4f..689abff2f27 100644
--- a/xml/System.Windows.Automation.Peers/GenericRootAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GenericRootAutomationPeer.xml
@@ -179,7 +179,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/GroupBoxAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GroupBoxAutomationPeer.xml
index 6c1b39c2278..69df54332d9 100644
--- a/xml/System.Windows.Automation.Peers/GroupBoxAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GroupBoxAutomationPeer.xml
@@ -123,7 +123,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
index 36b7ba74344..f966a6eb13c 100644
--- a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
@@ -127,7 +127,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
index aa2688b668c..a449b8138a6 100644
--- a/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ItemAutomationPeer.xml
@@ -441,7 +441,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as if it were a string of text that users use to explain which control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as if it were a string of text that users use to explain which control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  This method is called by <xref:System.Windows.Automation.Peers.AutomationPeer.GetName%2A>.  
   
diff --git a/xml/System.Windows.Automation.Peers/LabelAutomationPeer.xml b/xml/System.Windows.Automation.Peers/LabelAutomationPeer.xml
index 9d062177be1..a8a5bdc4c36 100644
--- a/xml/System.Windows.Automation.Peers/LabelAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/LabelAutomationPeer.xml
@@ -123,7 +123,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as if it were a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
index 6a2a32e9a4d..af42598d331 100644
--- a/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
@@ -180,7 +180,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
index 3d9c0318aee..27035809b84 100644
--- a/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
@@ -157,7 +157,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/TextAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TextAutomationPeer.xml
index 16db7f4de20..9e92d5fff31 100644
--- a/xml/System.Windows.Automation.Peers/TextAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TextAutomationPeer.xml
@@ -78,7 +78,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
index a347c91cbc3..99191ec346f 100644
--- a/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/UIElement3DAutomationPeer.xml
@@ -588,7 +588,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can think of the name property as what users use to explain the control they are referring to. Be sure to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ You can think of the name property as what users use to explain the control they are referring to. Be sure to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  This method calls the <xref:System.Windows.Automation.AutomationProperties.GetName%2A?displayProperty=nameWithType> method to get the value. <xref:System.Windows.Automation.AutomationProperties.GetName%2A?displayProperty=nameWithType> returns a value only when the <xref:System.Windows.Automation.AutomationProperties.Name%2A?displayProperty=nameWithType> property is set. You can override <xref:System.Windows.Automation.Peers.UIElement3DAutomationPeer.GetNameCore%2A> and add logic to provide a name in a way that makes sense for your <xref:System.Windows.UIElement3D>.  
   
diff --git a/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml b/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
index 3894680d1df..c1cfdcb5571 100644
--- a/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/UIElementAutomationPeer.xml
@@ -491,7 +491,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Automation.AutomationProperties.Name%2A> property functions similar to a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The <xref:System.Windows.Automation.AutomationProperties.Name%2A> property functions similar to a string of text that users use to explain the control they are referring to. Make certain that you have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation.Peers/WindowAutomationPeer.xml b/xml/System.Windows.Automation.Peers/WindowAutomationPeer.xml
index aea19849359..5df959b0806 100644
--- a/xml/System.Windows.Automation.Peers/WindowAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/WindowAutomationPeer.xml
@@ -166,7 +166,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the [!INCLUDE[TLA#tla_gui](~/includes/tlasharptla-gui-md.md)] so that you can programmatically refer to the control in a localized manner.  
+ The name property can be thought of as the string of text that a user would use to explain which control is being referred to. It is important to have a textual representation for all controls in the graphical user interface (GUI) so that you can programmatically refer to the control in a localized manner.  
   
  ]]></format>
         </remarks>

From cce380341346e85325179b2bbd492f2223dd476c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:47:40 -0800
Subject: [PATCH 125/236] tlasharptla-html

---
 xml/System.Windows.Documents/Block.xml     | 2 +-
 xml/System.Windows.Documents/Hyperlink.xml | 2 +-
 xml/System.Windows/DataFormats.xml         | 4 ++--
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.Windows.Documents/Block.xml b/xml/System.Windows.Documents/Block.xml
index 82917e280df..b73ba1403b1 100644
--- a/xml/System.Windows.Documents/Block.xml
+++ b/xml/System.Windows.Documents/Block.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Elements that inherit from the <xref:System.Windows.Documents.Block> class (such as <xref:System.Windows.Documents.Section>) can be used to group elements under a common parent or to apply common attributes to a group. Conceptually, this is similar to how you might use the \<DIV> tag in [!INCLUDE[TLA#tla_html](~/includes/tlasharptla-html-md.md)].  
+ Elements that inherit from the <xref:System.Windows.Documents.Block> class (such as <xref:System.Windows.Documents.Section>) can be used to group elements under a common parent or to apply common attributes to a group. Conceptually, this is similar to how you might use the \<DIV> tag in HTML.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Documents/Hyperlink.xml b/xml/System.Windows.Documents/Hyperlink.xml
index 2741db92aaa..9c41ca4755f 100644
--- a/xml/System.Windows.Documents/Hyperlink.xml
+++ b/xml/System.Windows.Documents/Hyperlink.xml
@@ -968,7 +968,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property corresponds to the `TARGET` attribute of an [!INCLUDE[TLA#tla_html](~/includes/tlasharptla-html-md.md)] hyperlink.  
+ This property corresponds to the `TARGET` attribute of an HTML hyperlink.  
   
 <a name="dependencyPropertyInfo_TargetName"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 6bb99b61cdb..2ad7a8eed1a 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -33,7 +33,7 @@
 |<xref:System.Windows.DataFormats.Dif>|"DataInterchangeFormat"|Specifies the Windows Data Interchange Format (DIF) data format.|  
 |<xref:System.Windows.DataFormats.EnhancedMetafile>|"EnhancedMetafile"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] enhanced metafile format.|  
 |<xref:System.Windows.DataFormats.FileDrop>|"FileDrop"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] file drop format.|  
-|<xref:System.Windows.DataFormats.Html>|"HTML Format"|Specifies the [!INCLUDE[TLA#tla_html](~/includes/tlasharptla-html-md.md)] data format.|  
+|<xref:System.Windows.DataFormats.Html>|"HTML Format"|Specifies the HTML data format.|  
 |<xref:System.Windows.DataFormats.Locale>|"Locale"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] locale (culture) data format.|  
 |<xref:System.Windows.DataFormats.MetafilePicture>|"MetaFilePict"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] metafile picture data format.|  
 |<xref:System.Windows.DataFormats.OemText>|"OEMText"|Specifies the standard [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] OEM text data format.|  
@@ -383,7 +383,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_html](~/includes/tlasharptla-html-md.md)] data format.</summary>
+        <summary>Specifies the HTML data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From fe3e7f1e95699a327fa8d2d224a390d12acd4a90 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:48:03 -0800
Subject: [PATCH 126/236] tlasharptla-icc

---
 xml/System.Windows.Media/Color.xml           | 16 ++++++++--------
 xml/System.Windows.Media/ColorContext.xml    |  6 +++---
 xml/System.Windows.Media/SolidColorBrush.xml |  2 +-
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Windows.Media/Color.xml b/xml/System.Windows.Media/Color.xml
index 6e7bd0024ad..4fac16c0eac 100644
--- a/xml/System.Windows.Media/Color.xml
+++ b/xml/System.Windows.Media/Color.xml
@@ -99,7 +99,7 @@
  *profileUri*  
  <xref:System.Uri?displayProperty=nameWithType>  
   
- The [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
+ The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
   
  *alphaValue*  
  <xref:System.Single?displayProperty=nameWithType>  
@@ -322,13 +322,13 @@
         <ReturnType>System.Windows.Media.ColorContext</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</summary>
-        <value>The [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</value>
+        <summary>Gets the International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</summary>
+        <value>The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
  ]]></format>
         </remarks>
@@ -539,14 +539,14 @@
       <Docs>
         <param name="a">The alpha channel for the new color,a value between 0 and 1.</param>
         <param name="values">A collection of values that specify the color channels for the new color. These values map to the <paramref name="profileUri" />.</param>
-        <param name="profileUri">The [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
+        <param name="profileUri">The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
         <summary>Creates a new <see cref="T:System.Windows.Media.Color" /> structure by using the specified alpha channel, color channel values, and color profile.</summary>
         <returns>A <see cref="T:System.Windows.Media.Color" /> structure with the specified values.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
    
   
@@ -687,14 +687,14 @@
       </Parameters>
       <Docs>
         <param name="values">A collection of values that specify the color channels for the new color. These values map to the <paramref name="profileUri" />.</param>
-        <param name="profileUri">The [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
+        <param name="profileUri">The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
         <summary>Creates a new <see cref="T:System.Windows.Media.Color" /> structure by using the specified color channel values and color profile.</summary>
         <returns>A <see cref="T:System.Windows.Media.Color" /> structure with the specified values and an alpha channel value of 1.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
    
   
diff --git a/xml/System.Windows.Media/ColorContext.xml b/xml/System.Windows.Media/ColorContext.xml
index 39361a9db50..9be52f39361 100644
--- a/xml/System.Windows.Media/ColorContext.xml
+++ b/xml/System.Windows.Media/ColorContext.xml
@@ -73,7 +73,7 @@
       </Parameters>
       <Docs>
         <param name="profileUri">The <see cref="T:System.Uri" /> that identifies the location of the desired color profile.</param>
-        <summary>Initializes a new instance of <see cref="T:System.Windows.Media.ColorContext" /> with the [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile located at a given <see cref="T:System.Uri" />.</summary>
+        <summary>Initializes a new instance of <see cref="T:System.Windows.Media.ColorContext" /> with the International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile located at a given <see cref="T:System.Uri" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -304,8 +304,8 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a <see cref="T:System.Uri" /> that represents the location of a [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</summary>
-        <value>A <see cref="T:System.Uri" /> that represents the location of a [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</value>
+        <summary>Gets a <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</summary>
+        <value>A <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/SolidColorBrush.xml b/xml/System.Windows.Media/SolidColorBrush.xml
index be8144ec6a3..6aa048502e9 100644
--- a/xml/System.Windows.Media/SolidColorBrush.xml
+++ b/xml/System.Windows.Media/SolidColorBrush.xml
@@ -85,7 +85,7 @@
  *profileUri*  
  <xref:System.Uri?displayProperty=nameWithType>  
   
- The [!INCLUDE[TLA#tla_icc](~/includes/tlasharptla-icc-md.md)] or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
+ The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
   
  *alphaValue*  
  <xref:System.Single?displayProperty=nameWithType>  

From 1735fb595139c67cb99db4ae7513ca3daef84247 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:48:21 -0800
Subject: [PATCH 127/236] tlasharptla-icm

---
 xml/System.Windows.Media/Color.xml           | 16 ++++++++--------
 xml/System.Windows.Media/ColorContext.xml    |  6 +++---
 xml/System.Windows.Media/SolidColorBrush.xml |  2 +-
 3 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.Windows.Media/Color.xml b/xml/System.Windows.Media/Color.xml
index 4fac16c0eac..0a64b5aa3ee 100644
--- a/xml/System.Windows.Media/Color.xml
+++ b/xml/System.Windows.Media/Color.xml
@@ -99,7 +99,7 @@
  *profileUri*  
  <xref:System.Uri?displayProperty=nameWithType>  
   
- The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
+ The International Color Consortium (ICC) or Image Color Management (ICM) color profile.  
   
  *alphaValue*  
  <xref:System.Single?displayProperty=nameWithType>  
@@ -322,13 +322,13 @@
         <ReturnType>System.Windows.Media.ColorContext</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</summary>
-        <value>The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile of the color.</value>
+        <summary>Gets the International Color Consortium (ICC) or Image Color Management (ICM) color profile of the color.</summary>
+        <value>The International Color Consortium (ICC) or Image Color Management (ICM) color profile of the color.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or Image Color Management (ICM) color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
  ]]></format>
         </remarks>
@@ -539,14 +539,14 @@
       <Docs>
         <param name="a">The alpha channel for the new color,a value between 0 and 1.</param>
         <param name="values">A collection of values that specify the color channels for the new color. These values map to the <paramref name="profileUri" />.</param>
-        <param name="profileUri">The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
+        <param name="profileUri">The International Color Consortium (ICC) or Image Color Management (ICM) color profile for the new color.</param>
         <summary>Creates a new <see cref="T:System.Windows.Media.Color" /> structure by using the specified alpha channel, color channel values, and color profile.</summary>
         <returns>A <see cref="T:System.Windows.Media.Color" /> structure with the specified values.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or Image Color Management (ICM) color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
    
   
@@ -687,14 +687,14 @@
       </Parameters>
       <Docs>
         <param name="values">A collection of values that specify the color channels for the new color. These values map to the <paramref name="profileUri" />.</param>
-        <param name="profileUri">The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile for the new color.</param>
+        <param name="profileUri">The International Color Consortium (ICC) or Image Color Management (ICM) color profile for the new color.</param>
         <summary>Creates a new <see cref="T:System.Windows.Media.Color" /> structure by using the specified color channel values and color profile.</summary>
         <returns>A <see cref="T:System.Windows.Media.Color" /> structure with the specified values and an alpha channel value of 1.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
+ A International Color Consortium (ICC) or Image Color Management (ICM) color profile contains a color system profile for a particular application or device such as a color printer. This profile is matched to a common profile that in turn can be mapped to the individual profiles of other devices. This allows the color system used by one computer device to match the colors from other applications and devices on the same or other computer systems.  
   
    
   
diff --git a/xml/System.Windows.Media/ColorContext.xml b/xml/System.Windows.Media/ColorContext.xml
index 9be52f39361..7227eea1092 100644
--- a/xml/System.Windows.Media/ColorContext.xml
+++ b/xml/System.Windows.Media/ColorContext.xml
@@ -73,7 +73,7 @@
       </Parameters>
       <Docs>
         <param name="profileUri">The <see cref="T:System.Uri" /> that identifies the location of the desired color profile.</param>
-        <summary>Initializes a new instance of <see cref="T:System.Windows.Media.ColorContext" /> with the International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile located at a given <see cref="T:System.Uri" />.</summary>
+        <summary>Initializes a new instance of <see cref="T:System.Windows.Media.ColorContext" /> with the International Color Consortium (ICC) or Image Color Management (ICM) color profile located at a given <see cref="T:System.Uri" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -304,8 +304,8 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</summary>
-        <value>A <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.</value>
+        <summary>Gets a <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or Image Color Management (ICM) color profile.</summary>
+        <value>A <see cref="T:System.Uri" /> that represents the location of a International Color Consortium (ICC) or Image Color Management (ICM) color profile.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/SolidColorBrush.xml b/xml/System.Windows.Media/SolidColorBrush.xml
index 6aa048502e9..73289ebe6a4 100644
--- a/xml/System.Windows.Media/SolidColorBrush.xml
+++ b/xml/System.Windows.Media/SolidColorBrush.xml
@@ -85,7 +85,7 @@
  *profileUri*  
  <xref:System.Uri?displayProperty=nameWithType>  
   
- The International Color Consortium (ICC) or [!INCLUDE[TLA#tla_icm](~/includes/tlasharptla-icm-md.md)] color profile.  
+ The International Color Consortium (ICC) or Image Color Management (ICM) color profile.  
   
  *alphaValue*  
  <xref:System.Single?displayProperty=nameWithType>  

From e61013e075d0ed673cc7a7744fcdaa894baffc41 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:48:36 -0800
Subject: [PATCH 128/236] tlasharptla-id

---
 xml/System.IO.Packaging/Package.xml                         | 2 +-
 xml/System.IO.Packaging/PackageDigitalSignatureManager.xml  | 4 ++--
 xml/System.IO.Packaging/PackageRelationshipSelector.xml     | 2 +-
 .../AutomationElement+AutomationElementInformation.xml      | 6 +++---
 .../AutomationFocusChangedEventArgs.xml                     | 4 ++--
 xml/System.Windows.Automation/DockPattern.xml               | 2 +-
 xml/System.Windows.Automation/ExpandCollapsePattern.xml     | 2 +-
 .../RangeValuePatternIdentifiers.xml                        | 2 +-
 xml/System.Windows.Automation/StructureChangedEventArgs.xml | 6 +++---
 .../TransformPatternIdentifiers.xml                         | 2 +-
 xml/System.Windows.Automation/ValuePatternIdentifiers.xml   | 2 +-
 xml/System.Windows.Automation/WindowClosedEventArgs.xml     | 2 +-
 xml/System.Windows.Controls/SelectionChangedEventArgs.xml   | 2 +-
 xml/System.Windows.Controls/TextChangedEventArgs.xml        | 4 ++--
 14 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/xml/System.IO.Packaging/Package.xml b/xml/System.IO.Packaging/Package.xml
index 51ff3793155..a6a187227d8 100644
--- a/xml/System.IO.Packaging/Package.xml
+++ b/xml/System.IO.Packaging/Package.xml
@@ -635,7 +635,7 @@
         <param name="targetMode">Indicates if the target part is <see cref="F:System.IO.Packaging.TargetMode.Internal" /> or <see cref="F:System.IO.Packaging.TargetMode.External" /> to the package.</param>
         <param name="relationshipType">A URI that uniquely defines the role of the relationship.</param>
         <param name="id">A unique XML identifier.</param>
-        <summary>Creates a package-level relationship to a part with a given URI, target mode, relationship type, and [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</summary>
+        <summary>Creates a package-level relationship to a part with a given URI, target mode, relationship type, and identifier (ID).</summary>
         <returns>The package-level relationship to the specified part.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
index d8746a356ab..26c9e4c718f 100644
--- a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
+++ b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
@@ -714,7 +714,7 @@
         <param name="certificate">The X.509 certificate to use to digitally sign each of the specified parts and relationships.</param>
         <param name="relationshipSelectors">The list of <see cref="T:System.IO.Packaging.PackageRelationship" /> objects to sign.</param>
         <param name="signatureId">An identification string to associate with the signature.</param>
-        <summary>Signs a list of package parts and package relationships with a given X.509 certificate and [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</summary>
+        <summary>Signs a list of package parts and package relationships with a given X.509 certificate and identifier (ID).</summary>
         <returns>The digital signature used to sign the elements specified in the <paramref name="parts" /> and <paramref name="relationshipSelectors" /> lists.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -778,7 +778,7 @@
         <param name="signatureId">An identification string to associate with the signature.</param>
         <param name="signatureObjects">A list of custom data objects to sign.</param>
         <param name="objectReferences">A list of references to custom objects to sign.</param>
-        <summary>Signs a list of package parts, package relationships, or custom objects with a specified X.509 certificate and signature [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</summary>
+        <summary>Signs a list of package parts, package relationships, or custom objects with a specified X.509 certificate and signature identifier (ID).</summary>
         <returns>The digital signature used to sign the elements specified in the <paramref name="parts" /> and <paramref name="relationshipSelectors" /> lists.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.IO.Packaging/PackageRelationshipSelector.xml b/xml/System.IO.Packaging/PackageRelationshipSelector.xml
index 43c417e2ed7..eb268ef3115 100644
--- a/xml/System.IO.Packaging/PackageRelationshipSelector.xml
+++ b/xml/System.IO.Packaging/PackageRelationshipSelector.xml
@@ -84,7 +84,7 @@
         <exception cref="T:System.ArgumentNullException">
           <paramref name="sourceUri" /> or <paramref name="selectionCriteria" /> is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentOutOfRangeException">The <paramref name="selectorType" /> parameter is not valid.</exception>
-        <exception cref="T:System.Xml.XmlException">The <paramref name="selectorType" /> parameter is <see cref="F:System.IO.Packaging.PackageRelationshipSelectorType.Id" /> but <paramref name="selectionCriteria" /> is not a valid [!INCLUDE[TLA#tla_xsd](~/includes/tlasharptla-xsd-md.md)] [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</exception>
+        <exception cref="T:System.Xml.XmlException">The <paramref name="selectorType" /> parameter is <see cref="F:System.IO.Packaging.PackageRelationshipSelectorType.Id" /> but <paramref name="selectionCriteria" /> is not a valid [!INCLUDE[TLA#tla_xsd](~/includes/tlasharptla-xsd-md.md)] identifier (ID).</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="selectionCriteria" /> is not valid for the specified <paramref name="selectorType" />.
 
 -or-
diff --git a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
index 3bccea3f1f1..1153f3af379 100644
--- a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
+++ b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
@@ -122,7 +122,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a string containing the UI Automation [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] for the element.</summary>
+        <summary>Gets a string containing the UI Automation identifier (ID) for the element.</summary>
         <value>An ID for an element that is unique among siblings within its container.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -817,13 +817,13 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the process [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of this element.</summary>
+        <summary>Gets the process identifier (ID) of this element.</summary>
         <value>The ID of the process that hosts the element. The default value for the property is 0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The process [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is assigned by the operating system. It can be seen in the **PID** column of the **Processes** tab in Task Manager.  
+ The process identifier (ID) is assigned by the operating system. It can be seen in the **PID** column of the **Processes** tab in Task Manager.  
   
  For more information, see <xref:System.Windows.Automation.AutomationElement.ProcessIdProperty>.  
   
diff --git a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
index 6eac89e2c8c..93d8b24a44b 100644
--- a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
@@ -45,7 +45,7 @@
         <Parameter Name="idChild" Type="System.Int32" />
       </Parameters>
       <Docs>
-        <param name="idObject">The [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the object that received focus.</param>
+        <param name="idObject">The identifier (ID) of the object that received focus.</param>
         <param name="idChild">The child ID of the object that received focus.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Automation.AutomationFocusChangedEventArgs" /> class.</summary>
         <remarks>
@@ -118,7 +118,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the Microsoft Active Accessibility object that generated the event.</summary>
+        <summary>Gets the identifier (ID) of the Microsoft Active Accessibility object that generated the event.</summary>
         <value>The ID of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element that is receiving focus. For possible values, see <see href="/windows/win32/winauto/object-identifiers">Object Identifiers</see>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation/DockPattern.xml b/xml/System.Windows.Automation/DockPattern.xml
index 071411a849d..01ef915380c 100644
--- a/xml/System.Windows.Automation/DockPattern.xml
+++ b/xml/System.Windows.Automation/DockPattern.xml
@@ -169,7 +169,7 @@
 ## Remarks  
  This identifier is used by UI Automation client applications. UI Automation providers should use the equivalent field in <xref:System.Windows.Automation.DockPatternIdentifiers>.  
   
- The pattern [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified <xref:System.Windows.Automation.AutomationElement>.  
+ The pattern identifier (ID) is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified <xref:System.Windows.Automation.AutomationElement>.  
   
    
   
diff --git a/xml/System.Windows.Automation/ExpandCollapsePattern.xml b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
index 46ed6639a64..9684130b837 100644
--- a/xml/System.Windows.Automation/ExpandCollapsePattern.xml
+++ b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
@@ -258,7 +258,7 @@
 ## Remarks  
  This identifier is used by UI Automation client applications. UI Automation providers should use the equivalent field in <xref:System.Windows.Automation.ExpandCollapsePatternIdentifiers>.  
   
- The pattern [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified <xref:System.Windows.Automation.AutomationElement>.  
+ The pattern identifier (ID) is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified <xref:System.Windows.Automation.AutomationElement>.  
   
    
   
diff --git a/xml/System.Windows.Automation/RangeValuePatternIdentifiers.xml b/xml/System.Windows.Automation/RangeValuePatternIdentifiers.xml
index 39ad90a7105..15a8365a8ee 100644
--- a/xml/System.Windows.Automation/RangeValuePatternIdentifiers.xml
+++ b/xml/System.Windows.Automation/RangeValuePatternIdentifiers.xml
@@ -177,7 +177,7 @@
 ## Remarks  
  This identifier is used by UI Automation providers. UI Automation client applications should use the equivalent field in <xref:System.Windows.Automation.RangeValuePattern>.  
   
- The pattern [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to specify the pattern to return.  
+ The pattern identifier (ID) is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to specify the pattern to return.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/StructureChangedEventArgs.xml b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
index d4311160091..148ac61f9b1 100644
--- a/xml/System.Windows.Automation/StructureChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/StructureChangedEventArgs.xml
@@ -45,8 +45,8 @@
       </Parameters>
       <Docs>
         <param name="structureChangeType">A single value that specifies the type of change.</param>
-        <param name="runtimeId">The runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the UI Automation element whose structure changed.</param>
-        <summary>Initializes a new instance of the <see cref="P:System.Windows.Automation.StructureChangedEventArgs.StructureChangeType" /> class, specifying the type of change and the [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the element whose structure changed.</summary>
+        <param name="runtimeId">The runtime identifier (ID) of the UI Automation element whose structure changed.</param>
+        <summary>Initializes a new instance of the <see cref="P:System.Windows.Automation.StructureChangedEventArgs.StructureChangeType" /> class, specifying the type of change and the identifier (ID) of the element whose structure changed.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -97,7 +97,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves the UI Automation runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] of the UI Automation element whose structure changed.</summary>
+        <summary>Retrieves the UI Automation runtime identifier (ID) of the UI Automation element whose structure changed.</summary>
         <returns>The runtime ID of the UI Automation element whose structure changed.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Automation/TransformPatternIdentifiers.xml b/xml/System.Windows.Automation/TransformPatternIdentifiers.xml
index 9f546a7960e..e42d033a950 100644
--- a/xml/System.Windows.Automation/TransformPatternIdentifiers.xml
+++ b/xml/System.Windows.Automation/TransformPatternIdentifiers.xml
@@ -148,7 +148,7 @@
 ## Remarks  
  This value is used by UI Automation providers. UI Automation client applications should use the equivalent field in <xref:System.Windows.Automation.TransformPattern>.  
   
- The pattern [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified UI Automation element.  
+ The pattern identifier (ID) is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified UI Automation element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/ValuePatternIdentifiers.xml b/xml/System.Windows.Automation/ValuePatternIdentifiers.xml
index 6c3b763f7f2..0025b47ff5a 100644
--- a/xml/System.Windows.Automation/ValuePatternIdentifiers.xml
+++ b/xml/System.Windows.Automation/ValuePatternIdentifiers.xml
@@ -88,7 +88,7 @@
 ## Remarks  
  This identifier is used by UI Automation providers. UI Automation client applications should use the equivalent field in <xref:System.Windows.Automation.ValuePattern>.  
   
- The pattern [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified UI Automation element.  
+ The pattern identifier (ID) is passed to methods such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPattern%2A> to retrieve the control pattern of interest from the specified UI Automation element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Automation/WindowClosedEventArgs.xml b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
index 14f2f3420f4..43ab29bda9f 100644
--- a/xml/System.Windows.Automation/WindowClosedEventArgs.xml
+++ b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
@@ -78,7 +78,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves the UI Automation runtime [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)] associated with this event.</summary>
+        <summary>Retrieves the UI Automation runtime identifier (ID) associated with this event.</summary>
         <returns>The UI Automation runtime ID of the window on which the event was raised.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Controls/SelectionChangedEventArgs.xml b/xml/System.Windows.Controls/SelectionChangedEventArgs.xml
index 2e890588ab1..455aa1c509a 100644
--- a/xml/System.Windows.Controls/SelectionChangedEventArgs.xml
+++ b/xml/System.Windows.Controls/SelectionChangedEventArgs.xml
@@ -53,7 +53,7 @@
         <Parameter Name="addedItems" Type="System.Collections.IList" />
       </Parameters>
       <Docs>
-        <param name="id">The event [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</param>
+        <param name="id">The event identifier (ID).</param>
         <param name="removedItems">The items that were unselected during this event.</param>
         <param name="addedItems">The items that were selected during this event.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Controls.SelectionChangedEventArgs" /> class.</summary>
diff --git a/xml/System.Windows.Controls/TextChangedEventArgs.xml b/xml/System.Windows.Controls/TextChangedEventArgs.xml
index 1b04c20ecff..8b66aa22f06 100644
--- a/xml/System.Windows.Controls/TextChangedEventArgs.xml
+++ b/xml/System.Windows.Controls/TextChangedEventArgs.xml
@@ -62,7 +62,7 @@
         <Parameter Name="action" Type="System.Windows.Controls.UndoAction" />
       </Parameters>
       <Docs>
-        <param name="id">The event [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</param>
+        <param name="id">The event identifier (ID).</param>
         <param name="action">The <see cref="P:System.Windows.Controls.TextChangedEventArgs.UndoAction" /> caused by the text change.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Controls.TextChangedEventArgs" /> class, using the specified event ID and undo action.</summary>
         <remarks>To be added.</remarks>
@@ -88,7 +88,7 @@
         <Parameter Name="changes" Type="System.Collections.Generic.ICollection&lt;System.Windows.Controls.TextChange&gt;" />
       </Parameters>
       <Docs>
-        <param name="id">The event [!INCLUDE[TLA#tla_id](~/includes/tlasharptla-id-md.md)].</param>
+        <param name="id">The event identifier (ID).</param>
         <param name="action">The <see cref="P:System.Windows.Controls.TextChangedEventArgs.UndoAction" /> caused by the text change.</param>
         <param name="changes">The changes that occurred during this event. For more information, see <see cref="P:System.Windows.Controls.TextChangedEventArgs.Changes" />.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Controls.TextChangedEventArgs" /> class, using the specified event ID, undo action, and text changes.</summary>

From 3b3484a0fe7796fd38e48992699d192d1982ace0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:49:01 -0800
Subject: [PATCH 129/236] tlasharptla-idsharpplural

---
 xml/System.Windows.Automation/Automation.xml  | 2 +-
 xml/System.Windows.Automation/ControlType.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Automation/Automation.xml b/xml/System.Windows.Automation/Automation.xml
index 3c39a9557f0..df7c51f722b 100644
--- a/xml/System.Windows.Automation/Automation.xml
+++ b/xml/System.Windows.Automation/Automation.xml
@@ -266,7 +266,7 @@
       <Docs>
         <param name="runtimeId1">The first run-time ID to compare.</param>
         <param name="runtimeId2">The second run-time ID to compare.</param>
-        <summary>Compares two integer arrays containing run-time [!INCLUDE[TLA#tla_id#plural](~/includes/tlasharptla-idsharpplural-md.md)] to determine whether their content is the same.</summary>
+        <summary>Compares two integer arrays containing run-time identifiers (IDs) to determine whether their content is the same.</summary>
         <returns>
           <see langword="true" /> if the compared run-time IDs refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element; otherwise <see langword="false" />.</returns>
         <remarks>
diff --git a/xml/System.Windows.Automation/ControlType.xml b/xml/System.Windows.Automation/ControlType.xml
index 8759b2e2735..2ad5db4a5a1 100644
--- a/xml/System.Windows.Automation/ControlType.xml
+++ b/xml/System.Windows.Automation/ControlType.xml
@@ -405,7 +405,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves an array of the required property [!INCLUDE[TLA#tla_id#plural](~/includes/tlasharptla-idsharpplural-md.md)] for this control type.</summary>
+        <summary>Retrieves an array of the required property identifiers (IDs) for this control type.</summary>
         <returns>An array of property IDs.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From fb9b31a1978ce9628cf186ed7d8c0608cd7a87cc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:51:25 -0800
Subject: [PATCH 130/236] tlasharptla-ie

---
 xml/System.Windows.Media/Brushes.xml           | 2 +-
 xml/System.Windows.Media/Colors.xml            | 2 +-
 xml/System.Windows.Navigation/JournalEntry.xml | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Media/Brushes.xml b/xml/System.Windows.Media/Brushes.xml
index dace619fac8..793e7535491 100644
--- a/xml/System.Windows.Media/Brushes.xml
+++ b/xml/System.Windows.Media/Brushes.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Color names in Windows Presentation Foundation match the color names in the .NET Framework, Windows Forms, and [!INCLUDE[TLA#tla_ie](~/includes/tlasharptla-ie-md.md)]. These colors and their names are based on the UNIX X11 color values.  
+ Color names in Windows Presentation Foundation match the color names in the .NET Framework, Windows Forms, and Microsoft Internet Explorer. These colors and their names are based on the UNIX X11 color values.  
   
  The following image shows the color of each predefined brush, its name, and its hexadecimal value.  
   
diff --git a/xml/System.Windows.Media/Colors.xml b/xml/System.Windows.Media/Colors.xml
index cd3b84664d9..af5ba07b5b1 100644
--- a/xml/System.Windows.Media/Colors.xml
+++ b/xml/System.Windows.Media/Colors.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The Windows Presentation Foundation color names match the .NET Framework, Windows Forms, and [!INCLUDE[TLA#tla_ie](~/includes/tlasharptla-ie-md.md)] color names. This representation is based on UNIX X11 named color values.  
+ The Windows Presentation Foundation color names match the .NET Framework, Windows Forms, and Microsoft Internet Explorer color names. This representation is based on UNIX X11 named color values.  
   
  The following image shows each predefined color, its name, and its hexadecimal value.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntry.xml b/xml/System.Windows.Navigation/JournalEntry.xml
index ee4890b6979..827ce05a58e 100644
--- a/xml/System.Windows.Navigation/JournalEntry.xml
+++ b/xml/System.Windows.Navigation/JournalEntry.xml
@@ -32,7 +32,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Windows Presentation Foundation implements a navigation history service that stores one entry for each piece of content that has been previously navigated to, just like navigation history in [!INCLUDE[TLA#tla_ie](~/includes/tlasharptla-ie-md.md)]. Navigation history comprises two stacks, one that remembers back navigation history, and one that remembers forward navigation history.  
+ Windows Presentation Foundation implements a navigation history service that stores one entry for each piece of content that has been previously navigated to, just like navigation history in Microsoft Internet Explorer. Navigation history comprises two stacks, one that remembers back navigation history, and one that remembers forward navigation history.  
   
  An entry for the current item is added to back navigation history when a forward navigation occurs. This occurs in the following situations:  
   

From 529dbd0253cde71e9c2395a150e7e66cb9afd6a0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:51:50 -0800
Subject: [PATCH 131/236] tlasharptla-ie6

---
 xml/System.Windows.Controls/Page.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index f77bcb47748..5f2ced41999 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -999,7 +999,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the navigation UI of a <see cref="T:System.Windows.Navigation.NavigationWindow" /> on [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)] is visible.</summary>
+        <summary>Gets or sets a value that indicates whether the navigation UI of a <see cref="T:System.Windows.Navigation.NavigationWindow" /> on Microsoft Internet Explorer 6 is visible.</summary>
         <value>
           <see langword="true" /> if the navigation UI of a host <see cref="T:System.Windows.Navigation.NavigationWindow" /> is visible; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -1009,7 +1009,7 @@
  <xref:System.Windows.Navigation.NavigationWindow> displays navigation UI by default to enable browser-style forwards and backwards navigation. If a page is set as the <xref:System.Windows.Application.StartupUri%2A>, <xref:System.Windows.Application> automatically opens a <xref:System.Windows.Navigation.NavigationWindow> to host the page in. If the page does not want to use the default <xref:System.Windows.Navigation.NavigationWindow> navigation UI, it can set <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> to `false`.  
   
 > [!NOTE]
->  Because WPF does not integrate with the navigation UI for [!INCLUDE[TLA#tla_ie6](~/includes/tlasharptla-ie6-md.md)], it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. WPF does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
+>  Because WPF does not integrate with the navigation UI for Microsoft Internet Explorer 6, it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. WPF does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
   
    
   

From cb3c22e3c8546251983246193d2883130cbf2a9a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:52:12 -0800
Subject: [PATCH 132/236] tlasharptla-ie7

---
 xml/System.Windows.Controls/Page.xml                        | 2 +-
 xml/System.Windows.Navigation/CustomContentState.xml        | 4 ++--
 .../JournalEntryUnifiedViewConverter.xml                    | 6 +++---
 3 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 5f2ced41999..7ca36442ec6 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -1009,7 +1009,7 @@
  <xref:System.Windows.Navigation.NavigationWindow> displays navigation UI by default to enable browser-style forwards and backwards navigation. If a page is set as the <xref:System.Windows.Application.StartupUri%2A>, <xref:System.Windows.Application> automatically opens a <xref:System.Windows.Navigation.NavigationWindow> to host the page in. If the page does not want to use the default <xref:System.Windows.Navigation.NavigationWindow> navigation UI, it can set <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> to `false`.  
   
 > [!NOTE]
->  Because WPF does not integrate with the navigation UI for Microsoft Internet Explorer 6, it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. WPF does integrate with the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] has no effect.  
+>  Because WPF does not integrate with the navigation UI for Microsoft Internet Explorer 6, it provides its own navigation UI, which can be shown or hidden by setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>. WPF does integrate with the Windows Internet Explorer 7 navigation UI, so setting <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A> on pages in Windows Internet Explorer 7 has no effect.  
   
    
   
diff --git a/xml/System.Windows.Navigation/CustomContentState.xml b/xml/System.Windows.Navigation/CustomContentState.xml
index aa9b7bb14b9..674e06778cc 100644
--- a/xml/System.Windows.Navigation/CustomContentState.xml
+++ b/xml/System.Windows.Navigation/CustomContentState.xml
@@ -122,13 +122,13 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The name for the content that is stored in navigation history. The value of <see cref="P:System.Windows.Navigation.CustomContentState.JournalEntryName" /> is displayed from <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />, and [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)] navigation UI.</summary>
+        <summary>The name for the content that is stored in navigation history. The value of <see cref="P:System.Windows.Navigation.CustomContentState.JournalEntryName" /> is displayed from <see cref="T:System.Windows.Navigation.NavigationWindow" />, <see cref="T:System.Windows.Controls.Frame" />, and Windows Internet Explorer 7 navigation UI.</summary>
         <value>The <see cref="T:System.String" /> name of the content that is stored in navigation history.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Entries stored in back and forward navigation history are typically available from the back and forward drop down navigation buttons on the navigation UI of the host navigator, including <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)].  
+ Entries stored in back and forward navigation history are typically available from the back and forward drop down navigation buttons on the navigation UI of the host navigator, including <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or Windows Internet Explorer 7.  
   
  <xref:System.Windows.Navigation.CustomContentState.JournalEntryName%2A> is the <xref:System.String> value that is displayed in a navigation history drop down list.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
index 354b017ea78..a152de60094 100644
--- a/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
+++ b/xml/System.Windows.Navigation/JournalEntryUnifiedViewConverter.xml
@@ -32,7 +32,7 @@
   
 -   A button for navigating forward one piece of content at a time.  
   
--   An [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list that shows:  
+-   An Windows Internet Explorer 7-style drop-down list that shows:  
   
     -   A combined list of up to nine items in back navigation history and up to nine items in forward navigation history.  
   
@@ -44,9 +44,9 @@
   
  **Forward Navigation History**: <xref:System.Windows.Controls.Frame.ForwardStack%2A?displayProperty=nameWithType>, <xref:System.Windows.Navigation.NavigationWindow.ForwardStack%2A?displayProperty=nameWithType>.  
   
- To create the [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame> use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to merge their individual back navigation history and forward navigation history into a single list of navigation history entries. The resulting list contains up to nine entries from back navigation history and up to nine entries from forward navigation history, plus an entry for the current content.  
+ To create the Windows Internet Explorer 7-style drop-down list, <xref:System.Windows.Navigation.NavigationWindow> and <xref:System.Windows.Controls.Frame> use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to merge their individual back navigation history and forward navigation history into a single list of navigation history entries. The resulting list contains up to nine entries from back navigation history and up to nine entries from forward navigation history, plus an entry for the current content.  
   
- If you create custom navigation UI, and need to provide an [!INCLUDE[TLA#tla_ie7](~/includes/tlasharptla-ie7-md.md)]-style drop-down list, you can use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to similar effect.  
+ If you create custom navigation UI, and need to provide an Windows Internet Explorer 7-style drop-down list, you can use <xref:System.Windows.Navigation.JournalEntryUnifiedViewConverter> to similar effect.  
   
 ## XAML Attribute Usage  
  This class is not typically used in XAML.  

From 7e642062342eca851dac5d1b3c185234d0add6be Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:52:50 -0800
Subject: [PATCH 133/236] tlasharptla-iegeneric

---
 xml/System.Windows.Controls/Page.xml | 16 ++++++++--------
 xml/System.Windows/Window.xml        |  2 +-
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 7ca36442ec6..34aaaf9413a 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -70,7 +70,7 @@
   
 -   Programmatically by using <xref:System.Windows.Navigation.NavigationService>.  
   
--   Visually by using the navigation UI of the host, including [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)], <xref:System.Windows.Navigation.NavigationWindow>, and <xref:System.Windows.Controls.Frame>.  
+-   Visually by using the navigation UI of the host, including Windows Internet Explorer, <xref:System.Windows.Navigation.NavigationWindow>, and <xref:System.Windows.Controls.Frame>.  
   
  For structured navigation using page functions (<xref:System.Windows.Navigation.PageFunction%601>), see [Structured Navigation Overview](/dotnet/framework/wpf/app-development/structured-navigation-overview) and [Navigation Topologies Overview](/dotnet/framework/wpf/app-development/navigation-topologies-overview).  
   
@@ -1299,13 +1299,13 @@
   
 -   <xref:System.Windows.Navigation.NavigationWindow>  
   
--   [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)]  
+-   Windows Internet Explorer  
   
  If a <xref:System.Windows.Controls.Page> is hosted by a <xref:System.Windows.Controls.Frame>, setting <xref:System.Windows.Controls.Page.WindowHeight%2A> has no effect, but you can still get the value of <xref:System.Windows.Controls.Page.WindowHeight%2A>.  
   
- A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowHeight%2A> to change the height of [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)]; the height cannot be changed by setting <xref:System.Windows.FrameworkElement.Height%2A>, <xref:System.Windows.FrameworkElement.MinHeight%2A>, or <xref:System.Windows.FrameworkElement.MaxHeight%2A>.  
+ A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowHeight%2A> to change the height of Windows Internet Explorer; the height cannot be changed by setting <xref:System.Windows.FrameworkElement.Height%2A>, <xref:System.Windows.FrameworkElement.MinHeight%2A>, or <xref:System.Windows.FrameworkElement.MaxHeight%2A>.  
   
- The minimum height of the [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)] window is 150 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowHeight%2A> may not be applied if it would cause the total height of the [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)] window to be less than 150 pixels.  
+ The minimum height of the Windows Internet Explorer window is 150 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowHeight%2A> may not be applied if it would cause the total height of the Windows Internet Explorer window to be less than 150 pixels.  
   
    
   
@@ -1348,7 +1348,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)], is the name of the file that is currently being hosted (with an .xaml extension if the page is loose [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], or an .xbap extension if the page is part of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).  
+ By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and Windows Internet Explorer, is the name of the file that is currently being hosted (with an .xaml extension if the page is loose [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], or an .xbap extension if the page is part of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).  
   
  A page can change the default by setting its <xref:System.Windows.Controls.Page.WindowTitle%2A> property.  
   
@@ -1410,13 +1410,13 @@
   
 -   <xref:System.Windows.Navigation.NavigationWindow>  
   
--   [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)]  
+-   Windows Internet Explorer  
   
  If a <xref:System.Windows.Controls.Page> is hosted by a <xref:System.Windows.Controls.Frame>, setting <xref:System.Windows.Controls.Page.WindowWidth%2A> has no effect, but you can still get the value of <xref:System.Windows.Controls.Page.WindowWidth%2A>.  
   
- A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowWidth%2A> to change the width of [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)]; the width cannot be changed by setting <xref:System.Windows.FrameworkElement.Width%2A>, <xref:System.Windows.FrameworkElement.MinWidth%2A>, or <xref:System.Windows.FrameworkElement.MaxWidth%2A>.  
+ A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowWidth%2A> to change the width of Windows Internet Explorer; the width cannot be changed by setting <xref:System.Windows.FrameworkElement.Width%2A>, <xref:System.Windows.FrameworkElement.MinWidth%2A>, or <xref:System.Windows.FrameworkElement.MaxWidth%2A>.  
   
- The minimum width of the [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)] window is 250 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowWidth%2A> may not be applied if it would cause the total width of the [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)] window to be less than 250 pixels.  
+ The minimum width of the Windows Internet Explorer window is 250 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowWidth%2A> may not be applied if it would cause the total width of the Windows Internet Explorer window to be less than 250 pixels.  
   
    
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index 4381f0cc356..a02e29ce54c 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2372,7 +2372,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The title of a <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, or [!INCLUDE[TLA#tla_iegeneric](~/includes/tlasharptla-iegeneric-md.md)], can also be set by using <xref:System.Windows.Controls.Page.WindowTitle%2A?displayProperty=nameWithType>.  
+ The title of a <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, or Windows Internet Explorer, can also be set by using <xref:System.Windows.Controls.Page.WindowTitle%2A?displayProperty=nameWithType>.  
   
 <a name="dependencyPropertyInfo_WindowTitle"></a>   
 ## Dependency Property Information  

From 32e0a86db95d52889f21593f66a065e2beca21da Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:53:13 -0800
Subject: [PATCH 134/236] tlasharptla-ifd

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml    | 10 +++++-----
 .../BitmapMetadataBlob.xml                             |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index d32a452ff7a..31f7c9bbfee 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index b9da8d76ef5..b0a83f0dcca 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), [!INCLUDE[TLA#tla_ifd](~/includes/tlasharptla-ifd-md.md)], [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
     </remarks>

From 7abcb9526924805ecd1a75ad568986d3bb57eea8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:54:07 -0800
Subject: [PATCH 135/236] tlasharptla-ime

---
 xml/System.Windows.Documents/FrameworkTextComposition.xml | 2 +-
 xml/System.Windows.Input/ApplicationCommands.xml          | 2 +-
 xml/System.Windows.Input/KeyEventArgs.xml                 | 2 +-
 xml/System.Windows/ContentElement.xml                     | 2 +-
 xml/System.Windows/SystemParameters.xml                   | 2 +-
 xml/System.Windows/UIElement.xml                          | 2 +-
 xml/System.Windows/UIElement3D.xml                        | 2 +-
 7 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.Windows.Documents/FrameworkTextComposition.xml b/xml/System.Windows.Documents/FrameworkTextComposition.xml
index d489f193738..ec3a437210c 100644
--- a/xml/System.Windows.Documents/FrameworkTextComposition.xml
+++ b/xml/System.Windows.Documents/FrameworkTextComposition.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.TextCompositionEventArgs.TextComposition%2A?displayProperty=nameWithType> property is a <xref:System.Windows.Documents.FrameworkTextComposition> when the user enters text into a <xref:System.Windows.Controls.TextBox> by using an [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)] and the <xref:System.Windows.Input.TextCompositionManager.TextInput>, <xref:System.Windows.Input.TextCompositionManager.TextInputUpdate>, or <xref:System.Windows.Input.TextCompositionManager.TextInputStart> event occurs.  
+ The <xref:System.Windows.Input.TextCompositionEventArgs.TextComposition%2A?displayProperty=nameWithType> property is a <xref:System.Windows.Documents.FrameworkTextComposition> when the user enters text into a <xref:System.Windows.Controls.TextBox> by using an Input Method Editor (IME) and the <xref:System.Windows.Input.TextCompositionManager.TextInput>, <xref:System.Windows.Input.TextCompositionManager.TextInputUpdate>, or <xref:System.Windows.Input.TextCompositionManager.TextInputStart> event occurs.  
   
  <xref:System.Windows.Documents.FrameworkTextComposition> is the base class of <xref:System.Windows.Documents.FrameworkRichTextComposition>. The <xref:System.Windows.Documents.FrameworkRichTextComposition> class defines properties that return <xref:System.Windows.Documents.TextPointer> objects to indicate the position of the text composition.  When the user enters text into a <xref:System.Windows.Controls.RichTextBox>, <xref:System.Windows.Input.TextCompositionEventArgs.TextComposition%2A?displayProperty=nameWithType> is a <xref:System.Windows.Documents.FrameworkRichTextComposition>.  
   
diff --git a/xml/System.Windows.Input/ApplicationCommands.xml b/xml/System.Windows.Input/ApplicationCommands.xml
index 71721b09337..3aab1f0074f 100644
--- a/xml/System.Windows.Input/ApplicationCommands.xml
+++ b/xml/System.Windows.Input/ApplicationCommands.xml
@@ -341,7 +341,7 @@
 ## Remarks  
  This command indicates intention to open the correction list.  
   
- The correction list is different depending on the context. For example, with [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)] input the correction list identifies reconversion choices.  
+ The correction list is different depending on the context. For example, with Input Method Editor (IME) input the correction list identifies reconversion choices.  
   
  There is not necessarily an implementation for the command on any given object; in many cases the implementation for the command is the responsibility of the application writer.  
   
diff --git a/xml/System.Windows.Input/KeyEventArgs.xml b/xml/System.Windows.Input/KeyEventArgs.xml
index c08956d7059..81d9db4c9d1 100644
--- a/xml/System.Windows.Input/KeyEventArgs.xml
+++ b/xml/System.Windows.Input/KeyEventArgs.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Windows.Input.Key</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the keyboard key referenced by the event, if the key will be processed by an [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)].</summary>
+        <summary>Gets the keyboard key referenced by the event, if the key will be processed by an Input Method Editor (IME).</summary>
         <value>The <see cref="T:System.Windows.Input.Key" /> referenced by the event.</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Input.KeyEventHandler" />
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index cae4fa8be02..4f8e7255f49 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -2164,7 +2164,7 @@ The default implementation of this property caches the value and also calculates
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether an input method system, such as an [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)], is enabled for processing the input to this element.</summary>
+        <summary>Gets a value that indicates whether an input method system, such as an Input Method Editor (IME), is enabled for processing the input to this element.</summary>
         <value>
           <see langword="true" /> if an input method is active; otherwise, <see langword="false" />. The default value of the underlying attached property is <see langword="true" />; however, this value is influenced by the state of input methods at runtime.</value>
         <remarks>
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index 8f14ea704f9..c1d5094b6d5 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -2699,7 +2699,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the system is ready to use a Unicode-based [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)] on a Unicode application.</summary>
+        <summary>Gets a value that indicates whether the system is ready to use a Unicode-based Input Method Editor (IME) on a Unicode application.</summary>
         <value>
           <see langword="true" /> if the Input Method Manager/Input Method Editor features are enabled; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index afe7929da7b..75bdcac8936 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -3256,7 +3256,7 @@ Image with an Elliptical Clip Region
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether an input method system, such as an [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)],  is enabled for processing the input to this element.</summary>
+        <summary>Gets a value indicating whether an input method system, such as an Input Method Editor (IME),  is enabled for processing the input to this element.</summary>
         <value>
           <see langword="true" /> if an input method is active; otherwise, <see langword="false" />. The default value of the underlying attached property is <see langword="true;" /> however, this will be influenced by the actual state of input methods at runtime.</value>
         <remarks>
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 2a63b7e49c6..829fecd98cb 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -2115,7 +2115,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether an input method system, such as an [!INCLUDE[TLA#tla_ime](~/includes/tlasharptla-ime-md.md)],  is enabled for processing the input to this element.</summary>
+        <summary>Gets a value indicating whether an input method system, such as an Input Method Editor (IME),  is enabled for processing the input to this element.</summary>
         <value>
           <see langword="true" /> if an input method is active; otherwise, <see langword="false" />. The default value of the underlying attached property is <see langword="true;" /> however, this will be influenced by the actual state of input methods at runtime.</value>
         <remarks>

From de81f9ba5d0a337961069d981ade71d894c10400 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:55:13 -0800
Subject: [PATCH 136/236] tlasharptla-isf

---
 xml/System.Windows.Controls/InkCanvas.xml          | 14 +++++++-------
 .../InkCanvasClipboardFormat.xml                   |  2 +-
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index a2f65e0bd0f..9f6b4fab71b 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -431,7 +431,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -528,7 +528,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)].  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
   
    
   
@@ -568,7 +568,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)].  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
   
    
   
@@ -2417,7 +2417,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
   
  ]]></format>
         </remarks>
@@ -2447,7 +2447,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -2490,7 +2490,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)], and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -2556,7 +2556,7 @@
    
   
 ## Examples  
- The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)].  
+ The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
   
  [!code-csharp[InkCanvasSamples#26](~/samples/snippets/csharp/VS_Snippets_Wpf/InkCanvasSamples/CSharp/Window1.xaml.cs#26)]
  [!code-vb[InkCanvasSamples#26](~/samples/snippets/visualbasic/VS_Snippets_Wpf/InkCanvasSamples/VisualBasic/Window1.xaml.vb#26)]  
diff --git a/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml b/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
index 27d677e7a08..48099b873db 100644
--- a/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
+++ b/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, [!INCLUDE[TLA#tla_isf](~/includes/tlasharptla-isf-md.md)].  
+ The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
   
  [!code-csharp[InkCanvasSamples#26](~/samples/snippets/csharp/VS_Snippets_Wpf/InkCanvasSamples/CSharp/Window1.xaml.cs#26)]
  [!code-vb[InkCanvasSamples#26](~/samples/snippets/visualbasic/VS_Snippets_Wpf/InkCanvasSamples/VisualBasic/Window1.xaml.vb#26)]  

From 12fbc97fefee62c839e28d6c33152c06d2ed10f0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:55:45 -0800
Subject: [PATCH 137/236] tlasharptla-isv

---
 xml/System.Windows.Media.Imaging/BitmapDecoder.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index edc70e4058a..8d5936fff05 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapDecoder> is not a <xref:System.Windows.Media.Imaging.BitmapFrame> itself; rather, it is a container for <xref:System.Windows.Media.Imaging.BitmapFrame> objects. Each <xref:System.Windows.Media.Imaging.BitmapFrame> in the container can potentially have different attributes, including different sizes, resolutions, or palettes.  
   
- Unless a specific codec is selected, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an [!INCLUDE[TLA#tla_isv](~/includes/tlasharptla-isv-md.md)] to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
+ Unless a specific codec is selected, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an independent software vendor (ISV) to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
   
  [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) are the only implemented image formats that support multiple frames.  
   

From 0963b21cb41394414120b74414b45a041c495a3c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:56:05 -0800
Subject: [PATCH 138/236] tlasharptla-jpeg

---
 xml/System.Windows.Media.Imaging/BitmapImage.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapImage.xml b/xml/System.Windows.Media.Imaging/BitmapImage.xml
index 2ea617d6470..e03b2331780 100644
--- a/xml/System.Windows.Media.Imaging/BitmapImage.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapImage.xml
@@ -548,7 +548,7 @@
 ## Remarks  
  If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelWidth%2A> is also set, the aspect ratio of the bitmap is ignored. If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelWidth%2A> is not set, the aspect ratio remains the same.  
   
- The [!INCLUDE[TLA#tla_jpeg](~/includes/tlasharptla-jpeg-md.md)] and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
+ The JPEG and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
   
 <a name="dependencyPropertyInfo_DecodePixelHeight"></a>   
 ## Dependency Property Information  
@@ -619,7 +619,7 @@
 ## Remarks  
  If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelHeight%2A> is also set, the aspect ratio of the bitmap is ignored. If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelHeight%2A> is not set, the aspect ratio remains the same.  
   
- The [!INCLUDE[TLA#tla_jpeg](~/includes/tlasharptla-jpeg-md.md)] and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
+ The JPEG and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
   
 <a name="dependencyPropertyInfo_DecodePixelWidth"></a>   
 ## Dependency Property Information  

From 8d4b7d76ef7efa5cf064f19ad666e34e30f58a34 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:56:29 -0800
Subject: [PATCH 139/236] tlasharptla-jpegorg

---
 xml/System.Windows.Media.Imaging/BitmapDecoder.xml     |  2 +-
 xml/System.Windows.Media.Imaging/BitmapSource.xml      |  2 +-
 xml/System.Windows.Media.Imaging/JpegBitmapDecoder.xml |  4 ++--
 xml/System.Windows.Media.Imaging/JpegBitmapEncoder.xml | 10 +++++-----
 4 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index 8d5936fff05..ab5eb901454 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -663,7 +663,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- None of the native formats support global thumbnails. [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
+ None of the native formats support global thumbnails. Joint Photographics Experts Group (JPEG), [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
   
  The <xref:System.Windows.Media.Imaging.BitmapSource> returned by this property is frozen.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index 4f7ceabd873..937d83b0423 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)], [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Imaging/JpegBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/JpegBitmapDecoder.xml
index d75926942ef..a71886e668b 100644
--- a/xml/System.Windows.Media.Imaging/JpegBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/JpegBitmapDecoder.xml
@@ -90,7 +90,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a Joint Photographics Experts Group (JPEG) encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -141,7 +141,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a Joint Photographics Experts Group (JPEG) encoded image.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Imaging/JpegBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/JpegBitmapEncoder.xml
index 5ca73c8a063..afdd5cfeeb5 100644
--- a/xml/System.Windows.Media.Imaging/JpegBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/JpegBitmapEncoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] format bitmaps support frame level thumbnails and frame level metadata. They do not support preview, global thumbnails, global metadata, or multiple frames.  
+ Joint Photographics Experts Group (JPEG) format bitmaps support frame level thumbnails and frame level metadata. They do not support preview, global thumbnails, global metadata, or multiple frames.  
   
  Encoding does not work in partial trust. See [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security) for information on partial trust.  
   
@@ -88,7 +88,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether a [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] image should be flipped horizontally during encoding.</summary>
+        <summary>Gets or sets a value that indicates whether a Joint Photographics Experts Group (JPEG) image should be flipped horizontally during encoding.</summary>
         <value>
           <see langword="true" /> if the image is flipped horizontally during encoding; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -134,7 +134,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether a [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] image should be flipped vertically during encoding.</summary>
+        <summary>Gets or sets a value that indicates whether a Joint Photographics Experts Group (JPEG) image should be flipped vertically during encoding.</summary>
         <value>
           <see langword="true" /> if the image is flipped vertically during encoding; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -181,7 +181,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates the quality level of the resulting [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] image.</summary>
+        <summary>Gets or sets a value that indicates the quality level of the resulting Joint Photographics Experts Group (JPEG) image.</summary>
         <value>The quality level of the JPEG image. The value range is 1 (lowest quality) to 100 (highest quality) inclusive.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -218,7 +218,7 @@
         <ReturnType>System.Windows.Media.Imaging.Rotation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that represents the degree to which a [!INCLUDE[TLA#tla_jpegorg](~/includes/tlasharptla-jpegorg-md.md)] image is rotated.</summary>
+        <summary>Gets or sets a value that represents the degree to which a Joint Photographics Experts Group (JPEG) image is rotated.</summary>
         <value>The degree to which the image is rotated.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From dee2e1bb7ab6fd01316e9d3cd950301a710a754a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:57:12 -0800
Subject: [PATCH 140/236] tlasharptla-longhorn

---
 xml/System.Windows/Window.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index a02e29ce54c..c93ac8b0507 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2694,7 +2694,7 @@
 ## Remarks  
  <xref:System.Windows.Window.WindowStyle%2A> can be one of the <xref:System.Windows.WindowStyle> enumeration values, including <xref:System.Windows.WindowStyle.None>, <xref:System.Windows.WindowStyle.ToolWindow>, <xref:System.Windows.WindowStyle.SingleBorderWindow> (default), and <xref:System.Windows.WindowStyle.ThreeDBorderWindow>.  
   
- The following figure shows the window styles on [!INCLUDE[TLA#tla_longhorn](~/includes/tlasharptla-longhorn-md.md)] (Windows Vista Aero theme, with transparent glass enabled):  
+ The following figure shows the window styles on Windows Vista (Windows Vista Aero theme, with transparent glass enabled):  
   
  ![Window styles](~/add/media/windowoverviewfigure6.PNG "Window styles")  
   

From 0d0a8a21b437af67303e978960d33f608a3da718 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:57:31 -0800
Subject: [PATCH 141/236] tlasharptla-mdi

---
 xml/System.Windows.Automation/WindowPattern.xml | 2 +-
 xml/System.Windows/Application.xml              | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Automation/WindowPattern.xml b/xml/System.Windows.Automation/WindowPattern.xml
index eda3fb6487c..a882f2c641d 100644
--- a/xml/System.Windows.Automation/WindowPattern.xml
+++ b/xml/System.Windows.Automation/WindowPattern.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Examples of controls that support this control pattern include top-level application windows, [!INCLUDE[TLA#tla_mdi](~/includes/tlasharptla-mdi-md.md)] child windows, modal dialogs and balloon help windows.  
+ Examples of controls that support this control pattern include top-level application windows, multiple-document interface (MDI) child windows, modal dialogs and balloon help windows.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index d40da0b467a..d25dba74e4d 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -2348,7 +2348,7 @@ This example illustrates how to use XAML together with application-scope resourc
    
   
 ## Examples  
- The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to [!INCLUDE[TLA#tla_mdi](~/includes/tlasharptla-mdi-md.md)] applications like [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)], or multiple-instance Single Document Interface (SDI) applications like [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)].  
+ The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to multiple-document interface (MDI) applications like [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)], or multiple-instance Single Document Interface (SDI) applications like [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)].  
   
  [!code-csharp[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationWindowsSnippets/CSharp/WindowMenuItem.cs#windowmenuitemcode)]
  [!code-vb[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationWindowsSnippets/visualbasic/windowmenuitem.vb#windowmenuitemcode)]  

From 7372da48422d48f0698f9f8c8d4df8f4698ba53d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:58:02 -0800
Subject: [PATCH 142/236] tlasharptla-mime

---
 xml/System.IO.Packaging/PackWebResponse.xml          | 2 +-
 xml/System.IO.Packaging/PackageProperties.xml        | 2 +-
 xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml | 4 ++--
 xml/System.Windows.Resources/ContentTypes.xml        | 2 +-
 xml/System.Windows.Resources/StreamResourceInfo.xml  | 4 ++--
 5 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System.IO.Packaging/PackWebResponse.xml b/xml/System.IO.Packaging/PackWebResponse.xml
index 5f4f149e6bd..f30e4a5b9f7 100644
--- a/xml/System.IO.Packaging/PackWebResponse.xml
+++ b/xml/System.IO.Packaging/PackWebResponse.xml
@@ -118,7 +118,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] content type of the response stream's content.</summary>
+        <summary>Gets the Multipurpose Internet Mail Extensions (MIME) content type of the response stream's content.</summary>
         <value>The MIME type of the stream's content.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.IO.Packaging/PackageProperties.xml b/xml/System.IO.Packaging/PackageProperties.xml
index 0f7e54fef9d..53b8a6fe6ad 100644
--- a/xml/System.IO.Packaging/PackageProperties.xml
+++ b/xml/System.IO.Packaging/PackageProperties.xml
@@ -184,7 +184,7 @@
 ## Remarks  
  Example <xref:System.IO.Packaging.PackageProperties.ContentType%2A> values include "Whitepaper", "Security Bulletin", and "Exam".  
   
- This <xref:System.IO.Packaging.PackageProperties.ContentType%2A> property is distinct from [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] content types as defined in RFC 2616.  
+ This <xref:System.IO.Packaging.PackageProperties.ContentType%2A> property is distinct from Multipurpose Internet Mail Extensions (MIME) content types as defined in RFC 2616.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml b/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
index d3da5fe0ee8..478e1f91a12 100644
--- a/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
@@ -333,8 +333,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that identifies the [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] associated with the codec.</summary>
-        <value>The [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] types associated with the codec.</value>
+        <summary>Gets a value that identifies the Multipurpose Internet Mail Extensions (MIME) associated with the codec.</summary>
+        <value>The Multipurpose Internet Mail Extensions (MIME) types associated with the codec.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Resources/ContentTypes.xml b/xml/System.Windows.Resources/ContentTypes.xml
index 240cd0487a8..6d116f4e361 100644
--- a/xml/System.Windows.Resources/ContentTypes.xml
+++ b/xml/System.Windows.Resources/ContentTypes.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The only purpose of this class is to provide the [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] type string for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] as a public field.  
+ The only purpose of this class is to provide the Multipurpose Internet Mail Extensions (MIME) type string for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] as a public field.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Resources/StreamResourceInfo.xml b/xml/System.Windows.Resources/StreamResourceInfo.xml
index 1d494a6fef4..a55f75ced25 100644
--- a/xml/System.Windows.Resources/StreamResourceInfo.xml
+++ b/xml/System.Windows.Resources/StreamResourceInfo.xml
@@ -90,7 +90,7 @@
       </Parameters>
       <Docs>
         <param name="stream">The reference stream.</param>
-        <param name="contentType">The [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] content type of the stream.</param>
+        <param name="contentType">The Multipurpose Internet Mail Extensions (MIME) content type of the stream.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Resources.StreamResourceInfo" /> class based on a provided stream.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -122,7 +122,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the content type of a stream.</summary>
-        <value>The [!INCLUDE[TLA#tla_mime](~/includes/tlasharptla-mime-md.md)] content type.</value>
+        <value>The Multipurpose Internet Mail Extensions (MIME) content type.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

From b2bf53fb735d4ee5ae6c42259b397dd5573871ad Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:58:29 -0800
Subject: [PATCH 143/236] tlasharptla-msbuild

---
 .../BamlLocalizableResourceKey.xml                        | 2 +-
 xml/System.Windows/Application.xml                        | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
index 1724c2a20c8..8e6e6eb4709 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class represents a key that can uniquely identify a localizable value inside binary XAML (BAML). It represents a combination of a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A>, class name, and property name.  
   
- The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
+ The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` Microsoft build engine (MSBuild) target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
   
  `<TextBlock x:Uid="myBlock">Click </TextBlock>`  
     
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index d25dba74e4d..114d5aff8b0 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -43,7 +43,7 @@
   
  <xref:System.Windows.Application> implements the singleton pattern to provide shared access to its window, property, and resource scope services. Consequently, only one instance of the <xref:System.Windows.Application> class can be created per <xref:System.AppDomain>.  
   
- You can implement an <xref:System.Windows.Application> using markup, markup and code-behind, or code. If <xref:System.Windows.Application> is implemented with markup, whether markup or markup and code-behind, the markup file must be configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] `ApplicationDefinition` item.  
+ You can implement an <xref:System.Windows.Application> using markup, markup and code-behind, or code. If <xref:System.Windows.Application> is implemented with markup, whether markup or markup and code-behind, the markup file must be configured as an Microsoft build engine (MSBuild) `ApplicationDefinition` item.  
   
 > [!NOTE]
 >  A standalone application does not require an <xref:System.Windows.Application> object; it is possible to implement a custom `static` entry point method (`Main`) that opens a window without creating an instance of <xref:System.Windows.Application>. However, [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)] require an <xref:System.Windows.Application> object.  
@@ -704,7 +704,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an Microsoft build engine (MSBuild) Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  
@@ -746,7 +746,7 @@
 ## Remarks  
  You must explicitly convert the return value to the same type as the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.  
   
- The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an Microsoft build engine (MSBuild) Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  
@@ -797,7 +797,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The XAML file can be an application code file (configured as an [!INCLUDE[TLA#tla_msbuild](~/includes/tlasharptla-msbuild-md.md)] Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
+ The XAML file can be an application code file (configured as an Microsoft build engine (MSBuild) Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
 > [!NOTE]
 >  This method is not thread-safe.  

From b3508d14a89604ad9d794631f47b58465c584c34 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:58:55 -0800
Subject: [PATCH 144/236] tlasharptla-mswin

---
 .../AuthenticationType.xml                    |  2 +-
 xml/System.Windows.Media/FontFamily.xml       |  2 +-
 xml/System.Windows.Shell/JumpList.xml         | 12 +++----
 xml/System.Windows/Application.xml            |  2 +-
 xml/System.Windows/Clipboard.xml              |  2 +-
 xml/System.Windows/DataFormats.xml            | 36 +++++++++----------
 xml/System.Windows/ReasonSessionEnding.xml    |  2 +-
 7 files changed, 29 insertions(+), 29 deletions(-)

diff --git a/xml/System.Security.RightsManagement/AuthenticationType.xml b/xml/System.Security.RightsManagement/AuthenticationType.xml
index 93583cac04f..2722cc07542 100644
--- a/xml/System.Security.RightsManagement/AuthenticationType.xml
+++ b/xml/System.Security.RightsManagement/AuthenticationType.xml
@@ -101,7 +101,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] authentication in a corporate domain environment.</summary>
+        <summary>Windows authentication in a corporate domain environment.</summary>
       </Docs>
     </Member>
     <Member MemberName="WindowsPassport">
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index 286f4ac1594..d36dfa338eb 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -102,7 +102,7 @@ Example of typefaces that are members of the "Times New Roman" font family
   
  A composite font family is available to applications through the <xref:System.Windows.Media.FontFamily> and <xref:System.Windows.Media.Typeface> constructors just like any other font family. Each composite font family is named, and, as with other fonts, can provide localized variants of its name in multiple languages.  
   
- The following markup example shows how a composite font family can be defined as a disk file. This file can be stored in the default [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] font directory as with any other installed font, or can be referenced in any location by including its URI when referencing the family by name.  
+ The following markup example shows how a composite font family can be defined as a disk file. This file can be stored in the default Windows font directory as with any other installed font, or can be referenced in any location by including its URI when referencing the family by name.  
   
  The following example shows the font family markup in a ".CompositeFont" file.  
   
diff --git a/xml/System.Windows.Shell/JumpList.xml b/xml/System.Windows.Shell/JumpList.xml
index 97ad8d8fe51..199158b545b 100644
--- a/xml/System.Windows.Shell/JumpList.xml
+++ b/xml/System.Windows.Shell/JumpList.xml
@@ -37,7 +37,7 @@
 ## Remarks  
  The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality for starting programs directly from the taskbar button by using Jump Lists. Jump Lists are also used in the [!INCLUDE[win7](~/includes/win7-md.md)] Start menu. You access a Jump List by right-clicking a taskbar button or by clicking the arrow next to a program in the Start menu. For more information about Jump Lists, see the [Taskbar](https://go.microsoft.com/fwlink/?LinkId=178478) section of the Windows User Experience Interaction Guidelines.  
   
- The <xref:System.Windows.Shell.JumpList> class provides a managed wrapper for the Jump List functionality in the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar and manages the data passed to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell. The functionality exposed by the <xref:System.Windows.Shell.JumpList> class is not available in versions of [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. Applications that use the <xref:System.Windows.Shell.JumpList> class will run in other versions of [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)], but the Jump List will not be available. For more information about the Windows shell and native Jump List APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479).  
+ The <xref:System.Windows.Shell.JumpList> class provides a managed wrapper for the Jump List functionality in the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar and manages the data passed to the Windows shell. The functionality exposed by the <xref:System.Windows.Shell.JumpList> class is not available in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. Applications that use the <xref:System.Windows.Shell.JumpList> class will run in other versions of Windows, but the Jump List will not be available. For more information about the Windows shell and native Jump List APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479).  
   
  The following illustration shows the Jump List for Windows Media Player, with items in the **Tasks** and **Frequent** categories.  
   
@@ -52,23 +52,23 @@ Windows Media Player Jump List
   
  Jump items are placed into categories in the <xref:System.Windows.Shell.JumpList>. By default, a <xref:System.Windows.Shell.JumpItem> is displayed in the **Tasks** category. Alternatively, you can specify a <xref:System.Windows.Shell.JumpItem.CustomCategory%2A> for the <xref:System.Windows.Shell.JumpItem>.  
   
- You can specify whether the standard **Recent** and **Frequent** categories are displayed in the <xref:System.Windows.Shell.JumpList> by setting the <xref:System.Windows.Shell.JumpList.ShowRecentCategory%2A> and <xref:System.Windows.Shell.JumpList.ShowFrequentCategory%2A> properties. The contents of these categories are managed by the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell. Because these categories might contain much of the same data, you typically display one or the other in your <xref:System.Windows.Shell.JumpList>, but not both. [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] automatically manages recent items if they are opened through a common file dialog box or used to open an application through file type association. When an item is accessed through the Jump List, you can notify the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell to add the item to the **Recent** category by calling the <xref:System.Windows.Shell.JumpList.AddToRecentCategory%2A> method.  
+ You can specify whether the standard **Recent** and **Frequent** categories are displayed in the <xref:System.Windows.Shell.JumpList> by setting the <xref:System.Windows.Shell.JumpList.ShowRecentCategory%2A> and <xref:System.Windows.Shell.JumpList.ShowFrequentCategory%2A> properties. The contents of these categories are managed by the Windows shell. Because these categories might contain much of the same data, you typically display one or the other in your <xref:System.Windows.Shell.JumpList>, but not both. Windows automatically manages recent items if they are opened through a common file dialog box or used to open an application through file type association. When an item is accessed through the Jump List, you can notify the Windows shell to add the item to the **Recent** category by calling the <xref:System.Windows.Shell.JumpList.AddToRecentCategory%2A> method.  
   
 ## Applying a Jump List to the Windows Shell  
- You cannot access the shell's Jump List directly or read its contents into the <xref:System.Windows.Shell.JumpList> class. Instead, the <xref:System.Windows.Shell.JumpList> class provides a representation of a Jump List that you can work with, and then apply to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell. You typically create a <xref:System.Windows.Shell.JumpList> and set it one time when the application is first run. However, you can modify or replace the <xref:System.Windows.Shell.JumpList> at run time.  
+ You cannot access the shell's Jump List directly or read its contents into the <xref:System.Windows.Shell.JumpList> class. Instead, the <xref:System.Windows.Shell.JumpList> class provides a representation of a Jump List that you can work with, and then apply to the Windows shell. You typically create a <xref:System.Windows.Shell.JumpList> and set it one time when the application is first run. However, you can modify or replace the <xref:System.Windows.Shell.JumpList> at run time.  
   
  When you have set the <xref:System.Windows.Shell.JumpList> properties, you must apply the <xref:System.Windows.Shell.JumpList> to the Windows shell before its contents appear in the taskbar Jump List. This is done automatically when the <xref:System.Windows.Shell.JumpList> is first attached to an application, either in XAML or in a call to the <xref:System.Windows.Shell.JumpList.SetJumpList%2A> method. If you modify the contents of the <xref:System.Windows.Shell.JumpList> at run time, you must call the <xref:System.Windows.Shell.JumpList.Apply%2A> method to apply its current contents to the Windows shell.  
   
 ## Setting a Jump List in XAML  
- A <xref:System.Windows.Shell.JumpList> is not automatically attached to an <xref:System.Windows.Application> object. You attach a <xref:System.Windows.Shell.JumpList> to an <xref:System.Windows.Application> object in XAML by using the attached property syntax. The <xref:System.Windows.Shell.JumpList> class implements the <xref:System.ComponentModel.ISupportInitialize> interface to support XAML declaration of a <xref:System.Windows.Shell.JumpList>. If the <xref:System.Windows.Shell.JumpList> is declared in XAML and attached to the current <xref:System.Windows.Application>, it is automatically applied to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell when the <xref:System.Windows.Shell.JumpList> is initialized.  
+ A <xref:System.Windows.Shell.JumpList> is not automatically attached to an <xref:System.Windows.Application> object. You attach a <xref:System.Windows.Shell.JumpList> to an <xref:System.Windows.Application> object in XAML by using the attached property syntax. The <xref:System.Windows.Shell.JumpList> class implements the <xref:System.ComponentModel.ISupportInitialize> interface to support XAML declaration of a <xref:System.Windows.Shell.JumpList>. If the <xref:System.Windows.Shell.JumpList> is declared in XAML and attached to the current <xref:System.Windows.Application>, it is automatically applied to the Windows shell when the <xref:System.Windows.Shell.JumpList> is initialized.  
   
 ## Setting and Modifying a Jump List in Code  
- You attach a <xref:System.Windows.Shell.JumpList> to an <xref:System.Windows.Application> object in code by calling the static <xref:System.Windows.Shell.JumpList.SetJumpList%2A> method. This also applies the <xref:System.Windows.Shell.JumpList> to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell.  
+ You attach a <xref:System.Windows.Shell.JumpList> to an <xref:System.Windows.Application> object in code by calling the static <xref:System.Windows.Shell.JumpList.SetJumpList%2A> method. This also applies the <xref:System.Windows.Shell.JumpList> to the Windows shell.  
   
  To modify a <xref:System.Windows.Shell.JumpList> at run time, you call the <xref:System.Windows.Shell.JumpList.GetJumpList%2A> method to get the <xref:System.Windows.Shell.JumpList> that is currently attached to an <xref:System.Windows.Application>. After you have modified the properties of the <xref:System.Windows.Shell.JumpList>, you must call the <xref:System.Windows.Shell.JumpList.Apply%2A> method to apply the changes to the Windows shell.  
   
 > [!NOTE]
->  You typically create one <xref:System.Windows.Shell.JumpList> that is attached to the <xref:System.Windows.Application> and applied to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell. However, you can create multiple <xref:System.Windows.Shell.JumpList> objects. Only one <xref:System.Windows.Shell.JumpList> at a time can be applied to the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] shell, and only one <xref:System.Windows.Shell.JumpList> at a time can be associated with an <xref:System.Windows.Application>. The .NET Framework does not require that these be the same <xref:System.Windows.Shell.JumpList>.  
+>  You typically create one <xref:System.Windows.Shell.JumpList> that is attached to the <xref:System.Windows.Application> and applied to the Windows shell. However, you can create multiple <xref:System.Windows.Shell.JumpList> objects. Only one <xref:System.Windows.Shell.JumpList> at a time can be applied to the Windows shell, and only one <xref:System.Windows.Shell.JumpList> at a time can be associated with an <xref:System.Windows.Application>. The .NET Framework does not require that these be the same <xref:System.Windows.Shell.JumpList>.  
   
 > [!NOTE]
 >  This class contains a link demand at the class level that applies to all members. A <xref:System.Security.SecurityException> is thrown when the immediate caller does not have full-trust permission. For more information about security demands, see [Link Demands](/dotnet/framework/misc/link-demands) and [Inheritance Demands](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/x4yx82e6(v=vs.100)).  
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 114d5aff8b0..ae96938450c 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -1941,7 +1941,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
  `NAME=VALUE; expires=DAY, DD-MMM-YYYY HH:MM:SS GMT`  
   
- Persistent cookies are stored in the current [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] installation's Temporary Internet Files folder until they expire, in which case they are deleted. You can delete a persistent cookie from your application by setting its expiry date to a date/time value that is in the past.  
+ Persistent cookies are stored in the current Windows installation's Temporary Internet Files folder until they expire, in which case they are deleted. You can delete a persistent cookie from your application by setting its expiry date to a date/time value that is in the past.  
   
  For an overview of cookies in WPF, see [Navigation Overview](/dotnet/framework/wpf/app-development/navigation-overview).  
   
diff --git a/xml/System.Windows/Clipboard.xml b/xml/System.Windows/Clipboard.xml
index 29ed8958472..733d3814b6c 100644
--- a/xml/System.Windows/Clipboard.xml
+++ b/xml/System.Windows/Clipboard.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- All applications for [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] share the system Clipboard, so the contents are subject to change when you switch to another application.  
+ All applications for Windows share the system Clipboard, so the contents are subject to change when you switch to another application.  
   
  For a list of predefined formats available to use with the <xref:System.Windows.Clipboard> class, see the <xref:System.Windows.DataFormats> class.  
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 2ad7a8eed1a..a35f1af4160 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -31,19 +31,19 @@
 |<xref:System.Windows.DataFormats.CommaSeparatedValue>|"CSV"|Specifies a comma-separated value (CSV) data format.|  
 |<xref:System.Windows.DataFormats.Dib>|"DeviceIndependentBitmap"|Specifies the device-independent bitmap (DIB) data format.|  
 |<xref:System.Windows.DataFormats.Dif>|"DataInterchangeFormat"|Specifies the Windows Data Interchange Format (DIF) data format.|  
-|<xref:System.Windows.DataFormats.EnhancedMetafile>|"EnhancedMetafile"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] enhanced metafile format.|  
-|<xref:System.Windows.DataFormats.FileDrop>|"FileDrop"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] file drop format.|  
+|<xref:System.Windows.DataFormats.EnhancedMetafile>|"EnhancedMetafile"|Specifies the Windows enhanced metafile format.|  
+|<xref:System.Windows.DataFormats.FileDrop>|"FileDrop"|Specifies the Windows file drop format.|  
 |<xref:System.Windows.DataFormats.Html>|"HTML Format"|Specifies the HTML data format.|  
-|<xref:System.Windows.DataFormats.Locale>|"Locale"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] locale (culture) data format.|  
-|<xref:System.Windows.DataFormats.MetafilePicture>|"MetaFilePict"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] metafile picture data format.|  
-|<xref:System.Windows.DataFormats.OemText>|"OEMText"|Specifies the standard [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] OEM text data format.|  
-|<xref:System.Windows.DataFormats.Palette>|"Palette"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] palette data format.|  
-|<xref:System.Windows.DataFormats.PenData>|"PenData"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] pen data format.|  
+|<xref:System.Windows.DataFormats.Locale>|"Locale"|Specifies the Windows locale (culture) data format.|  
+|<xref:System.Windows.DataFormats.MetafilePicture>|"MetaFilePict"|Specifies the Windows metafile picture data format.|  
+|<xref:System.Windows.DataFormats.OemText>|"OEMText"|Specifies the standard Windows OEM text data format.|  
+|<xref:System.Windows.DataFormats.Palette>|"Palette"|Specifies the Windows palette data format.|  
+|<xref:System.Windows.DataFormats.PenData>|"PenData"|Specifies the Windows pen data format.|  
 |<xref:System.Windows.DataFormats.Riff>|"RiffAudio"|Specifies the [!INCLUDE[TLA#tla_riff](~/includes/tlasharptla-riff-md.md)] audio data format.|  
 |<xref:System.Windows.DataFormats.Rtf>|"Rich Text Format"|Specifies the [!INCLUDE[TLA#tla_rtf](~/includes/tlasharptla-rtf-md.md)] data format.|  
 |<xref:System.Windows.DataFormats.Serializable>|"PersistentObject"|Specifies a data format that encapsulates any type of serializable data objects.|  
 |<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the common language runtime (CLR) string class data format.|  
-|<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] symbolic link data format.|  
+|<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the Windows symbolic link data format.|  
 |<xref:System.Windows.DataFormats.Text>|"Text"|Specifies the ANSI text data format.|  
 |<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] data format.|  
 |<xref:System.Windows.DataFormats.UnicodeText>|"UnicodeText"|Specifies the [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] text data format.|  
@@ -205,12 +205,12 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] enhanced metafile format.</summary>
+        <summary>Specifies the Windows enhanced metafile format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The enhanced metafile format is a [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] file that stores an image in terms of graphic objects rather than pixels. When resized, a metafile preserves an image better than a bitmap.  
+ The enhanced metafile format is a Windows file that stores an image in terms of graphic objects rather than pixels. When resized, a metafile preserves an image better than a bitmap.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   
@@ -238,7 +238,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] file drop format.</summary>
+        <summary>Specifies the Windows file drop format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -414,7 +414,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] locale (culture) data format.</summary>
+        <summary>Specifies the Windows locale (culture) data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -445,7 +445,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] metafile picture data format.</summary>
+        <summary>Specifies the Windows metafile picture data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -478,7 +478,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the standard [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] OEM text data format.</summary>
+        <summary>Specifies the standard Windows OEM text data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -509,7 +509,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] palette data format.</summary>
+        <summary>Specifies the Windows palette data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -540,12 +540,12 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] pen data format.</summary>
+        <summary>Specifies the Windows pen data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] pen data consists of pen strokes for handwriting software.  
+ Windows pen data consists of pen strokes for handwriting software.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   
@@ -701,7 +701,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)] symbolic link data format.</summary>
+        <summary>Specifies the Windows symbolic link data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/ReasonSessionEnding.xml b/xml/System.Windows/ReasonSessionEnding.xml
index 888abdbd089..926db74f812 100644
--- a/xml/System.Windows/ReasonSessionEnding.xml
+++ b/xml/System.Windows/ReasonSessionEnding.xml
@@ -61,7 +61,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The session is ending because the user is shutting down [!INCLUDE[TLA#tla_mswin](~/includes/tlasharptla-mswin-md.md)].</summary>
+        <summary>The session is ending because the user is shutting down Windows.</summary>
       </Docs>
     </Member>
   </Members>

From 17f78345cc60b0c2dd7db0e979b338ef9a167b31 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:59:16 -0800
Subject: [PATCH 145/236] tlasharptla-net

---
 xml/System.Printing/PrintQueue.xml                        | 2 +-
 xml/System.Windows.Forms.Integration/ElementHost.xml      | 2 +-
 .../JournalEntryListConverter.xml                         | 2 +-
 xml/System.Windows/ContentElement.xml                     | 4 ++--
 xml/System.Windows/DataFormats.xml                        | 2 +-
 xml/System.Windows/FrameworkElement.xml                   | 4 ++--
 xml/System.Windows/UIElement.xml                          | 6 +++---
 xml/System.Windows/UIElement3D.xml                        | 8 ++++----
 8 files changed, 15 insertions(+), 15 deletions(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index 48b05ffff25..5fb8cfd8cb4 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -584,7 +584,7 @@
 ## Remarks  
  If `fastCopy` is `true`, then the printer must be an [Printing Overview](/dotnet/framework/wpf/advanced/printing-overview). If it is not, the <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> method throws an exception.  
   
- If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The XPS file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to Component Object Model (COM). The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
+ If `fastCopy` is `false`, then it is not necessary to use an XPSDrv printer. The XPS file being added to the queue is converted to the printer's page description language, such as PCL or Postscript. However, this kind of printing makes a call to Component Object Model (COM). The call to COM requires that the calling thread have a single-threaded apartment (<xref:System.Threading.ApartmentState.STA>) instead of multiple-threaded apartment (<xref:System.Threading.ApartmentState.MTA>) which is the default in Microsoft .NET 2.0 and later. (For more on threading and apartment states, see [Managed and Unmanaged Threading](https://msdn.microsoft.com/library/db425c20-4b2f-4433-bf96-76071c7881e5), and <xref:System.Threading.ApartmentState>.) There are two ways of doing this:  
   
 -   The simplest way is to add the <xref:System.STAThreadAttribute> (that is, "`[System.STAThreadAttribute()]`") just above the first line of the application's `Main` method (usually "`static void Main(string[] args)`").  
   
diff --git a/xml/System.Windows.Forms.Integration/ElementHost.xml b/xml/System.Windows.Forms.Integration/ElementHost.xml
index 8ff3bf1b929..1fa86ec995b 100644
--- a/xml/System.Windows.Forms.Integration/ElementHost.xml
+++ b/xml/System.Windows.Forms.Integration/ElementHost.xml
@@ -2079,7 +2079,7 @@
 ## Remarks  
  The <xref:System.Windows.Forms.Integration.ElementHost.OnPaintBackground%2A> method paints the parent control's background into an offscreen HBITMAP. This bitmap is used as the background in the hosted element to support transparency.  
   
- This method supports the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] infrastructure and is not intended to be used directly from your code.  
+ This method supports the Microsoft .NET infrastructure and is not intended to be used directly from your code.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Navigation/JournalEntryListConverter.xml b/xml/System.Windows.Navigation/JournalEntryListConverter.xml
index c5a4ea06593..41eed5de5c7 100644
--- a/xml/System.Windows.Navigation/JournalEntryListConverter.xml
+++ b/xml/System.Windows.Navigation/JournalEntryListConverter.xml
@@ -45,7 +45,7 @@
       </Attributes>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Microsoft .NET infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index 4f8e7255f49..45145ea3779 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -125,7 +125,7 @@
 ## Remarks  
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
  ]]></format>
         </remarks>
@@ -173,7 +173,7 @@
   
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
    
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index a35f1af4160..1d322a99bab 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -867,7 +867,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] programming language. In [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], XAML is typically used to describe user interfaces (UI), documents, and media experiences.  
+ XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any Microsoft .NET programming language. In [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], XAML is typically used to describe user interfaces (UI), documents, and media experiences.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 4acb08ac537..8d81e7659f8 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -2109,7 +2109,7 @@
 ## Remarks  
  When <xref:System.Windows.FrameworkElement.Height%2A> and <xref:System.Windows.FrameworkElement.Width%2A> properties are explicitly set on an element, these measurements take higher precedent during layout and will cancel the typical effects of setting <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> to <xref:System.Windows.HorizontalAlignment.Stretch>.  
   
- <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> is the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in subclassed elements, particularly controls. This generally occurs in one of two ways: the dependency property is re-registered to a particular subclass, but with different metadata for setting its defaults; or there is a default style being applied that sets that dependency property value differently. For example, the apparent "default" of <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> for a <xref:System.Windows.Controls.Label> control will be <xref:System.Windows.HorizontalAlignment.Left>, even though <xref:System.Windows.Controls.Label> inherits <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> direct from <xref:System.Windows.FrameworkElement>. This is because that value was reset within the default style of <xref:System.Windows.Controls.Label>, within the style's control template.  
+ <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> is the Microsoft .NET property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in subclassed elements, particularly controls. This generally occurs in one of two ways: the dependency property is re-registered to a particular subclass, but with different metadata for setting its defaults; or there is a default style being applied that sets that dependency property value differently. For example, the apparent "default" of <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> for a <xref:System.Windows.Controls.Label> control will be <xref:System.Windows.HorizontalAlignment.Left>, even though <xref:System.Windows.Controls.Label> inherits <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> direct from <xref:System.Windows.FrameworkElement>. This is because that value was reset within the default style of <xref:System.Windows.Controls.Label>, within the style's control template.  
   
  <xref:System.Windows.Controls.Canvas> does not use <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> when composing layout, because <xref:System.Windows.Controls.Canvas> is based on absolute positioning.  
   
@@ -5551,7 +5551,7 @@
 ## Remarks  
  When <xref:System.Windows.FrameworkElement.Height%2A> and <xref:System.Windows.FrameworkElement.Width%2A> properties are explicitly set on an element, these measurements take layout precedent and cancel the regular effects of setting this property to <xref:System.Windows.VerticalAlignment.Stretch>.  
   
- <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> is the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes, particularly controls. This generally occurs in one of two ways: the dependency property is re-registered to a particular  derived class, but with different metadata for setting its defaults; or there is a default style being applied that sets that dependency property value differently. For example, the apparent "default" of <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> for a <xref:System.Windows.Controls.ComboBoxItem> control will be <xref:System.Windows.VerticalAlignment.Center>, even though <xref:System.Windows.Controls.ComboBoxItem> inherits <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> direct from <xref:System.Windows.FrameworkElement>. This is because that value was reset within the default style of <xref:System.Windows.Controls.ComboBoxItem>, within the style's control template.  
+ <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> is the Microsoft .NET property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes, particularly controls. This generally occurs in one of two ways: the dependency property is re-registered to a particular  derived class, but with different metadata for setting its defaults; or there is a default style being applied that sets that dependency property value differently. For example, the apparent "default" of <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> for a <xref:System.Windows.Controls.ComboBoxItem> control will be <xref:System.Windows.VerticalAlignment.Center>, even though <xref:System.Windows.Controls.ComboBoxItem> inherits <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> direct from <xref:System.Windows.FrameworkElement>. This is because that value was reset within the default style of <xref:System.Windows.Controls.ComboBoxItem>, within the style's control template.  
   
  <xref:System.Windows.Controls.Canvas> does not use <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> when composing layout, because <xref:System.Windows.Controls.Canvas> is based on absolute positioning.  
   
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 75bdcac8936..1d7bddab221 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -153,7 +153,7 @@
 ## Remarks  
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
  ]]></format>
         </remarks>
@@ -201,7 +201,7 @@
   
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
    
   
@@ -1894,7 +1894,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  Only the focused element receives keyboard input.  
   
- <xref:System.Windows.UIElement.Focusable%2A> is the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes, particularly in controls. This commonly occurs in one of two ways:  
+ <xref:System.Windows.UIElement.Focusable%2A> is the Microsoft .NET property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes, particularly in controls. This commonly occurs in one of two ways:  
   
 -   The dependency property is inherited by a particular derived class, but that derived class overrides the metadata of the dependency property and changes the property default value.  
   
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 829fecd98cb..9c0a0d12505 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -138,7 +138,7 @@
 ## Remarks  
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
  <xref:System.Windows.UIElement3D.AddHandler%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -188,7 +188,7 @@
   
  You can add the same handler for the same event multiple times without raising an exception. However, the handler is actually invoked multiple times when the event is handled. Therefore, consider how this behavior might have side effects that should be accounted for in your handler implementation.  
   
- You typically use this method to provide the implementation of the "add" accessor for the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] event access pattern of a custom routed event.  
+ You typically use this method to provide the implementation of the "add" accessor for the Microsoft .NET event access pattern of a custom routed event.  
   
  <xref:System.Windows.UIElement3D.AddHandler%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -1078,7 +1078,7 @@
 ## Remarks  
  Only the focused element receives keyboard input.  
   
- <xref:System.Windows.UIElement3D.Focusable%2A> is the [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes. This commonly occurs in one of two ways:  
+ <xref:System.Windows.UIElement3D.Focusable%2A> is the Microsoft .NET property accessor for what is in reality a dependency property. This particular dependency property quite frequently has its apparent "default" value set differently in derived element classes. This commonly occurs in one of two ways:  
   
 -   The dependency property is inherited by a particular derived class, but that derived class overrides the metadata of the dependency property and changes the property default value.  
   
@@ -3225,7 +3225,7 @@
 ## Remarks  
  Determination of the <xref:System.Windows.UIElement3D.IsVisible%2A> value takes many factors into account. In contrast, <xref:System.Windows.UIElement3D.Visibility%2A>, which is a settable property, only indicates the intention to programmatically make an element visible or invisible.  
   
- Changes to the value of this property will typically raise the <xref:System.Windows.UIElement3D.IsVisibleChanged> event. There is no matching [!INCLUDE[TLA#tla_net](~/includes/tlasharptla-net-md.md)] "On*" class handling override method that would allow some derived class to override that behavior and handle the event, but a class handler could still be attached directly with <xref:System.Windows.EventManager.RegisterClassHandler%2A>.  
+ Changes to the value of this property will typically raise the <xref:System.Windows.UIElement3D.IsVisibleChanged> event. There is no matching Microsoft .NET "On*" class handling override method that would allow some derived class to override that behavior and handle the event, but a class handler could still be attached directly with <xref:System.Windows.EventManager.RegisterClassHandler%2A>.  
   
  Elements where <xref:System.Windows.UIElement3D.IsVisible%2A> is `false` do not participate in input events (or commands), do not influence either the measure or arrange passes of layout, are not focusable, are not in a tab sequence, and will not be reported in hit testing. In contrast, elements where <xref:System.Windows.UIElement3D.IsEnabled%2A> is `false` will still participate in events and commands, and hit testing, but are also not focusable.  
   

From 8ffb904e9eb4867b2098d6de645c33f5af727546 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 13:59:48 -0800
Subject: [PATCH 146/236] tlasharptla-netframewkattr

---
 .../PropertyFilterAttribute.xml               |  8 +++---
 .../MarkupExtensionReturnTypeAttribute.xml    |  8 +++---
 .../AttachedPropertyBrowsableAttribute.xml    |  2 +-
 ...dPropertyBrowsableForChildrenAttribute.xml | 22 ++++++++--------
 ...achedPropertyBrowsableForTypeAttribute.xml | 26 +++++++++----------
 ...BrowsableWhenAttributePresentAttribute.xml | 16 ++++++------
 6 files changed, 41 insertions(+), 41 deletions(-)

diff --git a/xml/System.ComponentModel/PropertyFilterAttribute.xml b/xml/System.ComponentModel/PropertyFilterAttribute.xml
index 5a707fac557..de9b743b65c 100644
--- a/xml/System.ComponentModel/PropertyFilterAttribute.xml
+++ b/xml/System.ComponentModel/PropertyFilterAttribute.xml
@@ -107,7 +107,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to compare to this <see cref="T:System.ComponentModel.PropertyFilterAttribute" />.</param>
-        <summary>Returns a value that indicates whether the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is equal to a specified object.</summary>
+        <summary>Returns a value that indicates whether the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> .NET Framework attribute is equal to a specified object.</summary>
         <returns>
           <see langword="true" /> if the specified <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> is equal to the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" />; otherwise, <see langword="false" />.</returns>
         <remarks>
@@ -144,7 +144,7 @@
         <ReturnType>System.ComponentModel.PropertyFilterOptions</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the filter options for this <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Gets the filter options for this <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> .NET Framework attribute.</summary>
         <value>The property filter options.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -175,7 +175,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the hash code for the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Returns the hash code for the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> .NET Framework attribute.</summary>
         <returns>A signed 32-bit integer value.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -202,7 +202,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to compare. This object is expected to be a <see cref="T:System.ComponentModel.PropertyFilterAttribute" />.</param>
-        <summary>Returns a value that indicates whether the property filter options of the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] match the property filter options of the provided object.</summary>
+        <summary>Returns a value that indicates whether the property filter options of the current <see cref="T:System.ComponentModel.PropertyFilterAttribute" /> .NET Framework attribute match the property filter options of the provided object.</summary>
         <returns>
           <see langword="true" /> if a match exists; otherwise, <see langword="false" />.</returns>
         <remarks>
diff --git a/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml b/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
index efbbcb8086e..cfaf4e7ca79 100644
--- a/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
+++ b/xml/System.Windows.Markup/MarkupExtensionReturnTypeAttribute.xml
@@ -34,7 +34,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Markup.MarkupExtension> derived custom class should apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to indicate a possible type-safe return type that is returned by its <xref:System.Windows.Markup.MarkupExtension.ProvideValue%2A> implementation. In other words, if a markup extension always returns a more specific type than type of <xref:System.Object>, and casting to that type is a primary scenario, the markup extension class should attribute with <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> and report that type.  
+ A <xref:System.Windows.Markup.MarkupExtension> derived custom class should apply this .NET Framework attribute to indicate a possible type-safe return type that is returned by its <xref:System.Windows.Markup.MarkupExtension.ProvideValue%2A> implementation. In other words, if a markup extension always returns a more specific type than type of <xref:System.Object>, and casting to that type is a primary scenario, the markup extension class should attribute with <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> and report that type.  
   
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.MarkupExtensionReturnTypeAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
@@ -158,7 +158,7 @@
         <Parameter Name="expressionType" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="returnType">The return type that this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] reports.</param>
+        <param name="returnType">The return type that this  .NET Framework attribute reports.</param>
         <param name="expressionType">Deprecated; do not use.</param>
         <summary>Deprecated; do not use.</summary>
         <remarks>
@@ -241,8 +241,8 @@
         <ReturnType>System.Type</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the <see cref="T:System.Windows.Markup.MarkupExtension" /> return type that this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] reports.</summary>
-        <value>The type-safe return type of the specific <see cref="M:System.Windows.Markup.MarkupExtension.ProvideValue(System.IServiceProvider)" /> implementation of the markup extension where the <see cref="T:System.Windows.Markup.MarkupExtensionReturnTypeAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is applied.</value>
+        <summary>Gets the <see cref="T:System.Windows.Markup.MarkupExtension" /> return type that this .NET Framework attribute reports.</summary>
+        <value>The type-safe return type of the specific <see cref="M:System.Windows.Markup.MarkupExtension.ProvideValue(System.IServiceProvider)" /> implementation of the markup extension where the <see cref="T:System.Windows.Markup.MarkupExtensionReturnTypeAttribute" /> .NET Framework attribute is applied.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
index 9307be00bee..b42ea709ebe 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
index 49f308f708d..0a066e43839 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
@@ -27,19 +27,19 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
- When this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is applied to the get accessor for an attached property, this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] specifies that an attached property is browsable when the attached property owner is a parent element of other elements.  
+ When this  .NET Framework attribute is applied to the get accessor for an attached property, this  .NET Framework attribute specifies that an attached property is browsable when the attached property owner is a parent element of other elements.  
   
- When interpreted by a designer that uses type descriptor information, the designer should add this property as a browsable property to all child elements in the logical tree, based on the parent element with this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] applied.  
+ When interpreted by a designer that uses type descriptor information, the designer should add this property as a browsable property to all child elements in the logical tree, based on the parent element with this  .NET Framework attribute applied.  
   
  Generally, the browsable state parallels functionality. For example, <xref:System.Windows.Controls.Canvas.Left%2A?displayProperty=nameWithType> is designated browsable on elements that are child elements of a <xref:System.Windows.Controls.Canvas>, because <xref:System.Windows.Controls.Canvas> includes code for checking any set values of <xref:System.Windows.Controls.Canvas.Left%2A?displayProperty=nameWithType> on child elements.  
   
- This  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] supports two types of tree detection modes for parent element positions:  a shallow mode, and a deep mode. The shallow mode, which is the default mode for an applied <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], requires that the immediate parent element be the owner type of the property in order for the attached property to be browsable. The deep mode is declared by applying the attribute with <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> as `true`. The deep mode is less restrictive because it only requires that the owner type be somewhere in the ancestor direction of the logical tree, and therefore the attached property is browsable on all child elements, not just immediate child elements. The deep mode is applied for attached property usages where intervening elements in the logical tree should not be reported as the true parent element. Implicit collections (for example, the <xref:System.Windows.Controls.UIElementCollection> that is implicit in the <xref:System.Windows.Controls.Panel.Children%2A> of a <xref:System.Windows.Controls.Panel>) are not considered to be parent elements for purposes of how this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] declares the tree detection mode.  
+ This  .NET Framework attribute supports two types of tree detection modes for parent element positions:  a shallow mode, and a deep mode. The shallow mode, which is the default mode for an applied <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute> .NET Framework attribute, requires that the immediate parent element be the owner type of the property in order for the attached property to be browsable. The deep mode is declared by applying the attribute with <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> as `true`. The deep mode is less restrictive because it only requires that the owner type be somewhere in the ancestor direction of the logical tree, and therefore the attached property is browsable on all child elements, not just immediate child elements. The deep mode is applied for attached property usages where intervening elements in the logical tree should not be reported as the true parent element. Implicit collections (for example, the <xref:System.Windows.Controls.UIElementCollection> that is implicit in the <xref:System.Windows.Controls.Panel.Children%2A> of a <xref:System.Windows.Controls.Panel>) are not considered to be parent elements for purposes of how this  .NET Framework attribute declares the tree detection mode.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on child elements, it is the presence and characteristics of the get accessor on the parent element that controls the true behavior.  
+ This .NET Framework attribute should only be applied on the get accessor of attached property definitions. Do not apply this .NET Framework attribute to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on child elements, it is the presence and characteristics of the get accessor on the parent element that controls the true behavior.  
   
- Whether an attached property is browsable on a child element is not an absolute guarantee that the attached property value is really processed by the parent element in some manner. Also, the <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> value is not an absolute guarantee that the processing scope does or does not extend beyond the immediate parent element. All this is implementation specific. However, this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] for reporting the browsable state is the best available mechanism for reporting the usage information and functional information for an attached property. Therefore, you can generally assume that the browsable state of an attached property is analogous to the behavior of how an attached property value on a child element is processed or interpreted by the relevant parent element in your application code.  
+ Whether an attached property is browsable on a child element is not an absolute guarantee that the attached property value is really processed by the parent element in some manner. Also, the <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A> value is not an absolute guarantee that the processing scope does or does not extend beyond the immediate parent element. All this is implementation specific. However, this  .NET Framework attribute for reporting the browsable state is the best available mechanism for reporting the usage information and functional information for an attached property. Therefore, you can generally assume that the browsable state of an attached property is analogous to the behavior of how an attached property value on a child element is processed or interpreted by the relevant parent element in your application code.  
   
  For general information on declaring attached properties, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
@@ -106,14 +106,14 @@
       </Parameters>
       <Docs>
         <param name="obj">The <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> to compare to the current <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" />.</param>
-        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is equal to a specified object.</summary>
+        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> .NET Framework attribute is equal to a specified object.</summary>
         <returns>
           <see langword="true" /> if the specified <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> is equal to the current <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" />; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation supports value equality of the one possible settable value exposed by this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A>.  
+ This implementation supports value equality of the one possible settable value exposed by this .NET Framework attribute, <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A>.  
   
  ]]></format>
         </remarks>
@@ -138,13 +138,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableForChildrenAttribute" /> .NET Framework attribute.</summary>
         <returns>An unsigned 32-bit integer value.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation supports two possible hash values based on the one possible settable value exposed by this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A>.  
+ This implementation supports two possible hash values based on the one possible settable value exposed by this .NET Framework attribute, <xref:System.Windows.AttachedPropertyBrowsableForChildrenAttribute.IncludeDescendants%2A>.  
   
  ]]></format>
         </remarks>
@@ -178,7 +178,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that declares whether to use the deep mode for detection of parent elements on the attached property where this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is applied.</summary>
+        <summary>Gets or sets a value that declares whether to use the deep mode for detection of parent elements on the attached property where this  .NET Framework attribute is applied.</summary>
         <value>
           <see langword="true" /> if the attached property is browsable for all child elements in the logical tree of the parent element that owns the attached property. <see langword="false" /> if the attached property is only browsable for immediate child elements of a parent element that owns the attached property. The default is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
index f13968b650e..f9f8795f2bd 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
@@ -27,13 +27,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
- If more than one type is specified for a <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], the property is browsable if any specified type matches (logical or).  The type can also be an interface.  
+ If more than one type is specified for a <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> .NET Framework attribute, the property is browsable if any specified type matches (logical or).  The type can also be an interface.  
   
- This  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] specifies <xref:System.AttributeUsageAttribute.AllowMultiple%2A> `true`.  
+ This  .NET Framework attribute specifies <xref:System.AttributeUsageAttribute.AllowMultiple%2A> `true`.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
+ This .NET Framework attribute should only be applied on the get accessor of attached property definitions. Do not apply this .NET Framework attribute to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
   
  For general information on declaring attached properties, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
@@ -59,7 +59,7 @@
         <Parameter Name="targetType" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="targetType">The intended type that scopes the use of the attached property where this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] applies.</param>
+        <param name="targetType">The intended type that scopes the use of the attached property where this .NET Framework attribute applies.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> class, using the provided <paramref name="targetType" />.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -86,14 +86,14 @@
       </Parameters>
       <Docs>
         <param name="obj">The <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> to compare to the current <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" />.</param>
-        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is equal to a specified object.</summary>
+        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> .NET Framework attribute is equal to a specified object.</summary>
         <returns>
           <see langword="true" /> if the specified <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> is equal to the current <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" />; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation supports value equality of the one possible settable value exposed by this  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute.TargetType%2A>.  
+ This implementation supports value equality of the one possible settable value exposed by this  .NET Framework attribute, <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute.TargetType%2A>.  
   
  ]]></format>
         </remarks>
@@ -118,13 +118,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> .NET Framework attribute.</summary>
         <returns>An unsigned 32-bit integer value.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation supports multiple possible hash values based on the one possible settable value exposed by this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute.TargetType%2A>.  
+ This implementation supports multiple possible hash values based on the one possible settable value exposed by this .NET Framework attribute, <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute.TargetType%2A>.  
   
  ]]></format>
         </remarks>
@@ -154,13 +154,13 @@
         <ReturnType>System.Type</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the base type that scopes the use of the attached property where this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] applies.</summary>
+        <summary>Gets the base type that scopes the use of the attached property where this .NET Framework attribute applies.</summary>
         <value>The requested <see cref="T:System.Type" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property is settable only via the  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] declaration as exposed by the <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> constructor.  
+ This property is settable only via the  .NET Framework attribute declaration as exposed by the <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> constructor.  
   
  ]]></format>
         </remarks>
@@ -184,13 +184,13 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a unique type identifier for this <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Gets a unique type identifier for this <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" /> .NET Framework attribute.</summary>
         <value>An object that is a unique identifier for the <see cref="T:System.Windows.AttachedPropertyBrowsableForTypeAttribute" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation returns a unique value for each  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)], which is necessary because this  .NET Framework attribute allows multiple usages.  
+ This implementation returns a unique value for each  .NET Framework attribute, which is necessary because this  .NET Framework attribute allows multiple usages.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
index 6135188eb29..9d89c80905a 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
@@ -27,9 +27,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
   
- This [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] should only be applied on the get accessor of attached property definitions. Do not apply this [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
+ This .NET Framework attribute should only be applied on the get accessor of attached property definitions. Do not apply this .NET Framework attribute to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
   
  For general information on declaring attached properties, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
@@ -55,7 +55,7 @@
         <Parameter Name="attributeType" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="attributeType">The <see cref="T:System.Type" /> of the  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] that must also be applied on a class in order for the attached property to be browsable on the class where <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> is applied.</param>
+        <param name="attributeType">The <see cref="T:System.Type" /> of the  .NET Framework attribute that must also be applied on a class in order for the attached property to be browsable on the class where <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> is applied.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> class.</summary>
         <remarks>To be added.</remarks>
       </Docs>
@@ -84,13 +84,13 @@
         <ReturnType>System.Type</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the type of the  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] that must also be applied on a class.</summary>
-        <value>The  [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] type.</value>
+        <summary>Gets the type of the  .NET Framework attribute that must also be applied on a class.</summary>
+        <value>The  .NET Framework attribute type.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute.AttributeType%2A> value can only be set through the `attributeType` parameter of the <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] constructor.  
+ The <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute.AttributeType%2A> value can only be set through the `attributeType` parameter of the <xref:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute> .NET Framework attribute constructor.  
   
  ]]></format>
         </remarks>
@@ -118,7 +118,7 @@
       </Parameters>
       <Docs>
         <param name="obj">The <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> to compare to the current <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" />.</param>
-        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)] is equal to a specified object.</summary>
+        <summary>Determines whether the current <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> .NET Framework attribute is equal to a specified object.</summary>
         <returns>
           <see langword="true" /> if the specified <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> is equal to the current <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" />; otherwise, <see langword="false" />.</returns>
         <remarks>
@@ -150,7 +150,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> [!INCLUDE[TLA#tla_netframewkattr](~/includes/tlasharptla-netframewkattr-md.md)].</summary>
+        <summary>Returns the hash code for this <see cref="T:System.Windows.AttachedPropertyBrowsableWhenAttributePresentAttribute" /> .NET Framework attribute.</summary>
         <returns>An unsigned 32-bit integer value.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 484543b72e35903a1ff2955b1c8ed3a1a8ba894f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:00:16 -0800
Subject: [PATCH 147/236] tlasharptla-opentype

---
 xml/System.Windows.Controls/TextBlock.xml     | 2 +-
 xml/System.Windows.Controls/TextBox.xml       | 2 +-
 xml/System.Windows.Documents/FlowDocument.xml | 2 +-
 xml/System.Windows.Documents/TextElement.xml  | 2 +-
 xml/System.Windows.Documents/Typography.xml   | 2 +-
 xml/System.Windows.Xps.Packaging/XpsFont.xml  | 2 +-
 xml/System.Windows/FontStretch.xml            | 4 ++--
 xml/System.Windows/FontWeight.xml             | 4 ++--
 8 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index c6f6ffbc9bd..d4799fd2319 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -3145,7 +3145,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.TextBlock.Typography%2A> property is applicable only to [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
+ The <xref:System.Windows.Controls.TextBlock.Typography%2A> property is applicable only to OpenType fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
   
    
   
diff --git a/xml/System.Windows.Controls/TextBox.xml b/xml/System.Windows.Controls/TextBox.xml
index 349684b5314..ba1d804f1ab 100644
--- a/xml/System.Windows.Controls/TextBox.xml
+++ b/xml/System.Windows.Controls/TextBox.xml
@@ -1760,7 +1760,7 @@ tbSettingText.Text = "Initial text contents of the TextBox."
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] fonts. A typography variant has no effect on fonts that do not support the variant. For more information about this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
+ The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to OpenType fonts. A typography variant has no effect on fonts that do not support the variant. For more information about this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
   
    
   
diff --git a/xml/System.Windows.Documents/FlowDocument.xml b/xml/System.Windows.Documents/FlowDocument.xml
index 68e5822d0ee..e46355fa381 100644
--- a/xml/System.Windows.Documents/FlowDocument.xml
+++ b/xml/System.Windows.Documents/FlowDocument.xml
@@ -2959,7 +2959,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
+ The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to OpenType fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).  
   
    
   
diff --git a/xml/System.Windows.Documents/TextElement.xml b/xml/System.Windows.Documents/TextElement.xml
index e140223402a..9900794a2a0 100644
--- a/xml/System.Windows.Documents/TextElement.xml
+++ b/xml/System.Windows.Documents/TextElement.xml
@@ -1335,7 +1335,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).
+ The <xref:System.Windows.Documents.FlowDocument.Typography%2A> property is applicable only to OpenType fonts. A typography variant has no effect on fonts that do not support the variant.  For more information on this topic, see [Typography in WPF](/dotnet/framework/wpf/advanced/typography-in-wpf).
   
 ## Examples  
  The following example shows how to set the <xref:System.Windows.Documents.TextElement.Typography%2A> attribute, using <xref:System.Windows.Documents.Paragraph> as the example element.  
diff --git a/xml/System.Windows.Documents/Typography.xml b/xml/System.Windows.Documents/Typography.xml
index 7956a89241e..371d694505b 100644
--- a/xml/System.Windows.Documents/Typography.xml
+++ b/xml/System.Windows.Documents/Typography.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Documents.Typography> object exposes the set of features that an [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] font supports. By setting the properties of <xref:System.Windows.Documents.Typography> in markup or code, you can easily author documents that take advantage of [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] features.  
+ The <xref:System.Windows.Documents.Typography> object exposes the set of features that an OpenType font supports. By setting the properties of <xref:System.Windows.Documents.Typography> in markup or code, you can easily author documents that take advantage of OpenType features.  
   
  The following text displays standard capital letters for the Pescadero font, followed by the letters styled as "SmallCaps" and "AllSmallCaps". In this case, the same font size is used for all three words.  
   
diff --git a/xml/System.Windows.Xps.Packaging/XpsFont.xml b/xml/System.Windows.Xps.Packaging/XpsFont.xml
index abac0b909d5..dcc4a559f44 100644
--- a/xml/System.Windows.Xps.Packaging/XpsFont.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsFont.xml
@@ -154,7 +154,7 @@
 ## Remarks  
  The <xref:System.Windows.Xps.Packaging.XpsFont.ObfuscateFontData%2A> method is provided for use when you are legally obligated to obfuscate licensed proprietary fonts.  
   
- While this method does not provide encryption, the <xref:System.Windows.Xps.Packaging.XpsFont.ObfuscateFontData%2A> method can be used to inhibit users from unzipping proprietary [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] fonts and installing them separately for other uses.  
+ While this method does not provide encryption, the <xref:System.Windows.Xps.Packaging.XpsFont.ObfuscateFontData%2A> method can be used to inhibit users from unzipping proprietary OpenType fonts and installing them separately for other uses.  
   
  For more information about font obfuscation, see Section 2.1.7.3 "Embedded Font Obfuscation" in the *XML Paper Specification (XPS)* available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   
diff --git a/xml/System.Windows/FontStretch.xml b/xml/System.Windows/FontStretch.xml
index 912450bdc38..4695446f6bf 100644
--- a/xml/System.Windows/FontStretch.xml
+++ b/xml/System.Windows/FontStretch.xml
@@ -196,7 +196,7 @@
       </Parameters>
       <Docs>
         <param name="stretchValue">An integer value between one and nine that corresponds to the usStretchValue definition in the OpenType specification.</param>
-        <summary>Creates a new instance of <see cref="T:System.Windows.FontStretch" /> that corresponds to the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] usStretchClass value.</summary>
+        <summary>Creates a new instance of <see cref="T:System.Windows.FontStretch" /> that corresponds to the OpenType usStretchClass value.</summary>
         <returns>A new instance of <see cref="T:System.Windows.FontStretch" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -483,7 +483,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a value that represents the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usStretchClass</c> for this <see cref="T:System.Windows.FontStretch" /> object.</summary>
+        <summary>Returns a value that represents the OpenType <c>usStretchClass</c> for this <see cref="T:System.Windows.FontStretch" /> object.</summary>
         <returns>An integer value between 1 and 999 that corresponds to the <c>usStretchClass</c> definition in the OpenType specification.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows/FontWeight.xml b/xml/System.Windows/FontWeight.xml
index 2ff617399a1..dade39fa95d 100644
--- a/xml/System.Windows/FontWeight.xml
+++ b/xml/System.Windows/FontWeight.xml
@@ -197,7 +197,7 @@
       </Parameters>
       <Docs>
         <param name="weightValue">An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the OpenType specification.</param>
-        <summary>Creates a new instance of <see cref="T:System.Windows.FontWeight" /> that corresponds to the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usWeightClass</c> value.</summary>
+        <summary>Creates a new instance of <see cref="T:System.Windows.FontWeight" /> that corresponds to the OpenType <c>usWeightClass</c> value.</summary>
         <returns>A new instance of <see cref="T:System.Windows.FontWeight" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -526,7 +526,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a value that represents the [!INCLUDE[TLA#tla_opentype](~/includes/tlasharptla-opentype-md.md)] <c>usWeightClass</c> for the <see cref="T:System.Windows.FontWeight" /> object.</summary>
+        <summary>Returns a value that represents the OpenType <c>usWeightClass</c> for the <see cref="T:System.Windows.FontWeight" /> object.</summary>
         <returns>An integer value between 1 and 999 that corresponds to the <c>usWeightClass</c> definition in the OpenType specification.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 7124ec974d2774a9fc9480961ebcbf1b85a38077 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:00:44 -0800
Subject: [PATCH 148/236] tlasharptla-outlook

---
 xml/System.Windows.Automation/MultipleViewPattern.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Automation/MultipleViewPattern.xml b/xml/System.Windows.Automation/MultipleViewPattern.xml
index 0380b3d4a5b..cc1aee14022 100644
--- a/xml/System.Windows.Automation/MultipleViewPattern.xml
+++ b/xml/System.Windows.Automation/MultipleViewPattern.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)] documents (normal, Web layout, print layout, reading layout, outline), [!INCLUDE[TLA#tla_outlook](~/includes/tlasharptla-outlook-md.md)] calendar (year, month, week, day) and [!INCLUDE[TLA#tla_wmp](~/includes/tlasharptla-wmp-md.md)] skins. The supported views are determined by the control developer and are specific to each control.  
+ Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)] documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and [!INCLUDE[TLA#tla_wmp](~/includes/tlasharptla-wmp-md.md)] skins. The supported views are determined by the control developer and are specific to each control.  
   
  ]]></format>
     </remarks>

From 353b7ea70db8959f872e29211b114908ac447993 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:01:04 -0800
Subject: [PATCH 149/236] tlasharptla-passport

---
 xml/System.Security.RightsManagement/AuthenticationType.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Security.RightsManagement/AuthenticationType.xml b/xml/System.Security.RightsManagement/AuthenticationType.xml
index 2722cc07542..7c4c11390de 100644
--- a/xml/System.Security.RightsManagement/AuthenticationType.xml
+++ b/xml/System.Security.RightsManagement/AuthenticationType.xml
@@ -79,7 +79,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[TLA#tla_passport](~/includes/tlasharptla-passport-md.md)] authentication.</summary>
+        <summary>Windows Live ID authentication.</summary>
       </Docs>
     </Member>
     <Member MemberName="Windows">

From 9acaeed61ab60a7cdd03d8d66b6a242cc40ced08 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:01:30 -0800
Subject: [PATCH 150/236] tlasharptla-png

---
 xml/System.Windows.Media.Imaging/BitmapFrame.xml      | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapImage.xml      | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml   | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapSource.xml     | 2 +-
 xml/System.Windows.Media.Imaging/PngBitmapDecoder.xml | 4 ++--
 xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml | 4 ++--
 6 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapFrame.xml b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
index 3cd5c533b15..ea8a94035f8 100644
--- a/xml/System.Windows.Media.Imaging/BitmapFrame.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
@@ -39,7 +39,7 @@
  [!code-csharp[bitmapframeexample#1](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#1)]
  [!code-vb[bitmapframeexample#1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#1)]  
   
- The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapFrame> object to open a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] graphic and write metadata by using the <xref:System.Windows.Media.Imaging.BitmapFrame.CreateInPlaceBitmapMetadataWriter%2A> method.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapFrame> object to open a Portable Network Graphics (PNG) graphic and write metadata by using the <xref:System.Windows.Media.Imaging.BitmapFrame.CreateInPlaceBitmapMetadataWriter%2A> method.  
   
  [!code-cpp[bitmapmetadata#SetQuery](~/samples/snippets/cpp/VS_Snippets_Wpf/BitMapMetadata/CPP/BitmapMetadata.cpp#setquery)]
  [!code-csharp[bitmapmetadata#SetQuery](~/samples/snippets/csharp/VS_Snippets_Wpf/BitMapMetadata/CSharp/BitmapMetadata.cs#setquery)]
@@ -483,7 +483,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapFrame> object to open a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] graphic and write metadata by using the <xref:System.Windows.Media.Imaging.BitmapFrame.CreateInPlaceBitmapMetadataWriter%2A> method.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapFrame> object to open a Portable Network Graphics (PNG) graphic and write metadata by using the <xref:System.Windows.Media.Imaging.BitmapFrame.CreateInPlaceBitmapMetadataWriter%2A> method.  
   
  [!code-cpp[bitmapmetadata#SetQuery](~/samples/snippets/cpp/VS_Snippets_Wpf/BitMapMetadata/CPP/BitmapMetadata.cpp#setquery)]
  [!code-csharp[bitmapmetadata#SetQuery](~/samples/snippets/csharp/VS_Snippets_Wpf/BitMapMetadata/CSharp/BitmapMetadata.cs#setquery)]
diff --git a/xml/System.Windows.Media.Imaging/BitmapImage.xml b/xml/System.Windows.Media.Imaging/BitmapImage.xml
index e03b2331780..9420ed1b7a9 100644
--- a/xml/System.Windows.Media.Imaging/BitmapImage.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapImage.xml
@@ -548,7 +548,7 @@
 ## Remarks  
  If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelWidth%2A> is also set, the aspect ratio of the bitmap is ignored. If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelWidth%2A> is not set, the aspect ratio remains the same.  
   
- The JPEG and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
+ The JPEG and Portable Network Graphics (PNG) codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
   
 <a name="dependencyPropertyInfo_DecodePixelHeight"></a>   
 ## Dependency Property Information  
@@ -619,7 +619,7 @@
 ## Remarks  
  If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelHeight%2A> is also set, the aspect ratio of the bitmap is ignored. If <xref:System.Windows.Media.Imaging.BitmapImage.DecodePixelHeight%2A> is not set, the aspect ratio remains the same.  
   
- The JPEG and [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
+ The JPEG and Portable Network Graphics (PNG) codecs natively decode the image to the specified size; other codecs decode the image at its original size and scale the image to the desired size.  
   
 <a name="dependencyPropertyInfo_DecodePixelWidth"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index 31f7c9bbfee..f55cfd49e18 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -696,7 +696,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapMetadata.SetQuery%2A> method to write metadata to a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] file.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapMetadata.SetQuery%2A> method to write metadata to a Portable Network Graphics (PNG) file.  
   
  [!code-cpp[bitmapmetadata#SetQuery](~/samples/snippets/cpp/VS_Snippets_Wpf/BitMapMetadata/CPP/BitmapMetadata.cpp#setquery)]
  [!code-csharp[bitmapmetadata#SetQuery](~/samples/snippets/csharp/VS_Snippets_Wpf/BitMapMetadata/CSharp/BitmapMetadata.cs#setquery)]
@@ -965,7 +965,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapMetadata.SetQuery%2A> method to write metadata to a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] file.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.BitmapMetadata.SetQuery%2A> method to write metadata to a Portable Network Graphics (PNG) file.  
   
  [!code-cpp[bitmapmetadata#SetQuery](~/samples/snippets/cpp/VS_Snippets_Wpf/BitMapMetadata/CPP/BitmapMetadata.cpp#setquery)]
  [!code-csharp[bitmapmetadata#SetQuery](~/samples/snippets/csharp/VS_Snippets_Wpf/BitMapMetadata/CSharp/BitmapMetadata.cs#setquery)]
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index 937d83b0423..6f6685fbd7b 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)], and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Imaging/PngBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/PngBitmapDecoder.xml
index 3c1b9827b4a..cd65bbf2290 100644
--- a/xml/System.Windows.Media.Imaging/PngBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/PngBitmapDecoder.xml
@@ -78,7 +78,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a Portable Network Graphics (PNG) encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -124,7 +124,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a Portable Network Graphics (PNG) encoded image.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
index 8caacf0d50e..f920962c6a3 100644
--- a/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/PngBitmapEncoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] format bitmaps support frame level metadata. They do not support preview, global thumbnails, frame level thumbnails, global metadata, or multiple frames.  
+ Portable Network Graphics (PNG) format bitmaps support frame level metadata. They do not support preview, global thumbnails, frame level thumbnails, global metadata, or multiple frames.  
   
  Encoding does not work in partial trust. See [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security) for information on partial trust.  
   
@@ -95,7 +95,7 @@
         <ReturnType>System.Windows.Media.Imaging.PngInterlaceOption</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the [!INCLUDE[TLA#tla_png](~/includes/tlasharptla-png-md.md)] bitmap should interlace.</summary>
+        <summary>Gets or sets a value that indicates whether the Portable Network Graphics (PNG) bitmap should interlace.</summary>
         <value>One of the <see cref="P:System.Windows.Media.Imaging.PngBitmapEncoder.Interlace" /> values. The default is <see cref="F:System.Windows.Media.Imaging.PngInterlaceOption.Default" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  

From 51e2fc3844c136507dc26deed79c0944e30c238b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:01:59 -0800
Subject: [PATCH 151/236] tlasharptla-riff

---
 xml/System.Windows/DataFormats.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 1d322a99bab..a1c675aab32 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -39,7 +39,7 @@
 |<xref:System.Windows.DataFormats.OemText>|"OEMText"|Specifies the standard Windows OEM text data format.|  
 |<xref:System.Windows.DataFormats.Palette>|"Palette"|Specifies the Windows palette data format.|  
 |<xref:System.Windows.DataFormats.PenData>|"PenData"|Specifies the Windows pen data format.|  
-|<xref:System.Windows.DataFormats.Riff>|"RiffAudio"|Specifies the [!INCLUDE[TLA#tla_riff](~/includes/tlasharptla-riff-md.md)] audio data format.|  
+|<xref:System.Windows.DataFormats.Riff>|"RiffAudio"|Specifies the Resource Interchange File Format (RIFF) audio data format.|  
 |<xref:System.Windows.DataFormats.Rtf>|"Rich Text Format"|Specifies the [!INCLUDE[TLA#tla_rtf](~/includes/tlasharptla-rtf-md.md)] data format.|  
 |<xref:System.Windows.DataFormats.Serializable>|"PersistentObject"|Specifies a data format that encapsulates any type of serializable data objects.|  
 |<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the common language runtime (CLR) string class data format.|  
@@ -573,7 +573,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_riff](~/includes/tlasharptla-riff-md.md)] audio data format.</summary>
+        <summary>Specifies the Resource Interchange File Format (RIFF) audio data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From de68cedb86c2cd8bb08e15389b02b33e5524edd1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:02:20 -0800
Subject: [PATCH 152/236] tlasharptla-rtf

---
 xml/System.Windows/DataFormats.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index a1c675aab32..efe445995ad 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -40,7 +40,7 @@
 |<xref:System.Windows.DataFormats.Palette>|"Palette"|Specifies the Windows palette data format.|  
 |<xref:System.Windows.DataFormats.PenData>|"PenData"|Specifies the Windows pen data format.|  
 |<xref:System.Windows.DataFormats.Riff>|"RiffAudio"|Specifies the Resource Interchange File Format (RIFF) audio data format.|  
-|<xref:System.Windows.DataFormats.Rtf>|"Rich Text Format"|Specifies the [!INCLUDE[TLA#tla_rtf](~/includes/tlasharptla-rtf-md.md)] data format.|  
+|<xref:System.Windows.DataFormats.Rtf>|"Rich Text Format"|Specifies the Rich Text Format (RTF) data format.|  
 |<xref:System.Windows.DataFormats.Serializable>|"PersistentObject"|Specifies a data format that encapsulates any type of serializable data objects.|  
 |<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the common language runtime (CLR) string class data format.|  
 |<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the Windows symbolic link data format.|  
@@ -606,7 +606,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_rtf](~/includes/tlasharptla-rtf-md.md)] data format.</summary>
+        <summary>Specifies the Rich Text Format (RTF) data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From e25fd54a566cff19311e6c47df0058bdd6d9b0af Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:02:36 -0800
Subject: [PATCH 153/236] tlasharptla-sha1

---
 xml/System.IO.Packaging/PackageDigitalSignatureManager.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
index 26c9e4c718f..54480950a9e 100644
--- a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
+++ b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
@@ -262,7 +262,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default hash algorithm for the standard <xref:System.IO.Packaging.PackageDigitalSignatureManager> class is <xref:System.Security.Cryptography.Xml.SignedXml.XmlDsigSHA1Url> ([!INCLUDE[TLA#tla_sha1](~/includes/tlasharptla-sha1-md.md)]).  
+ The default hash algorithm for the standard <xref:System.IO.Packaging.PackageDigitalSignatureManager> class is <xref:System.Security.Cryptography.Xml.SignedXml.XmlDsigSHA1Url> (Secure Hash Algorithm version 1.0 (SHA1)).  
   
  The <xref:System.IO.Packaging.PackageDigitalSignatureManager.HashAlgorithm%2A> property gets or sets the actual hash algorithm this is used to create and verify signatures.  
   

From c1243566199e9583ea6cd3e072db6415f43a4a67 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:02:53 -0800
Subject: [PATCH 154/236] tlasharptla-tiff

---
 xml/System.Windows.Media.Imaging/BitmapDecoder.xml        | 8 ++++----
 xml/System.Windows.Media.Imaging/BitmapEncoder.xml        | 6 +++---
 xml/System.Windows.Media.Imaging/BitmapFrame.xml          | 2 +-
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml       | 4 ++--
 xml/System.Windows.Media.Imaging/BitmapPalette.xml        | 2 +-
 xml/System.Windows.Media.Imaging/BitmapPalettes.xml       | 2 +-
 xml/System.Windows.Media.Imaging/BitmapSource.xml         | 2 +-
 .../InPlaceBitmapMetadataWriter.xml                       | 2 +-
 .../LateBoundBitmapDecoder.xml                            | 2 +-
 xml/System.Windows.Media.Imaging/TiffBitmapDecoder.xml    | 4 ++--
 xml/System.Windows.Media.Imaging/TiffBitmapEncoder.xml    | 4 ++--
 xml/System.Windows.Media.Imaging/TiffCompressOption.xml   | 2 +-
 xml/System.Windows/DataFormats.xml                        | 4 ++--
 13 files changed, 22 insertions(+), 22 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index ab5eb901454..1432f64db2c 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -26,7 +26,7 @@
   
  Unless a specific codec is selected, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an independent software vendor (ISV) to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
   
- [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) are the only implemented image formats that support multiple frames.  
+ Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) are the only implemented image formats that support multiple frames.  
   
    
   
@@ -36,7 +36,7 @@
  [!code-csharp[imagingsnippetgallery_procedural_snip#BitmapDecoderCreate](~/samples/snippets/csharp/VS_Snippets_Wpf/ImagingSnippetGallery_procedural_snip/CSharp/BitmapDecoderExample.cs#bitmapdecodercreate)]
  [!code-vb[imagingsnippetgallery_procedural_snip#BitmapDecoderCreate](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ImagingSnippetGallery_procedural_snip/VB/BitmapDecoderExample.vb#bitmapdecodercreate)]  
   
- The following code example demonstrates how to use the built in <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> to open and decode a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] bitmap. The resulting <xref:System.Windows.Media.Imaging.BitmapSource> is used as the <xref:System.Windows.Controls.Image.Source%2A> of an <xref:System.Windows.Controls.Image> element.  
+ The following code example demonstrates how to use the built in <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> to open and decode a Tagged Image File Format (TIFF) bitmap. The resulting <xref:System.Windows.Media.Imaging.BitmapSource> is used as the <xref:System.Windows.Controls.Image.Source%2A> of an <xref:System.Windows.Controls.Image> element.  
   
  [!code-csharp[bitmapframeexample#4](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#4)]
  [!code-vb[bitmapframeexample#4](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#4)]  
@@ -486,7 +486,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images support more than one frame.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) images support more than one frame.  
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> objects returned by this property are frozen.  
   
@@ -663,7 +663,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- None of the native formats support global thumbnails. Joint Photographics Experts Group (JPEG), [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
+ None of the native formats support global thumbnails. Joint Photographics Experts Group (JPEG), Tagged Image File Format (TIFF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
   
  The <xref:System.Windows.Media.Imaging.BitmapSource> returned by this property is frozen.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
index 72c3800965f..440d3471edf 100644
--- a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
@@ -196,7 +196,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)], Graphics Interchange Format (GIF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
+ Only Tagged Image File Format (TIFF), Graphics Interchange Format (GIF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
   
 <a name="xamlTextUsage_Frames"></a>   
 ## XAML Text Usage  
@@ -273,12 +273,12 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images (and some older, non-standard bitmap (BMP) images) support palettes.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) images (and some older, non-standard bitmap (BMP) images) support palettes.  
   
    
   
 ## Examples  
- The following example demonstrates how to apply a custom palette to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image and subsequently encode it.  
+ The following example demonstrates how to apply a custom palette to a Tagged Image File Format (TIFF) image and subsequently encode it.  
   
  [!code-csharp[bitmapframeexample#1](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#1)]
  [!code-vb[bitmapframeexample#1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#1)]  
diff --git a/xml/System.Windows.Media.Imaging/BitmapFrame.xml b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
index ea8a94035f8..f66bce8e328 100644
--- a/xml/System.Windows.Media.Imaging/BitmapFrame.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapFrame.xml
@@ -29,7 +29,7 @@
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> returned from a decoder is always frozen. If you require a modifiable copy, you must first create a copy of the <xref:System.Windows.Media.Imaging.BitmapFrame> by using the <xref:System.Windows.Media.Imaging.BitmapSource.Clone%2A> method.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) format images support multiple frames.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) format images support multiple frames.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index f55cfd49e18..a334895b10b 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -40,7 +40,7 @@
    
   
 ## Examples  
- The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and Exif schemas.  
+ The following example demonstrates how to write metadata to a Tagged Image File Format (TIFF) image by using the IFD and Exif schemas.  
   
  [!code-csharp[BitmapFrameExample#7](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#7)]
  [!code-vb[BitmapFrameExample#7](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#7)]  
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example demonstrates how to write metadata to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image by using the IFD and Exif schemas.  
+ The following example demonstrates how to write metadata to a Tagged Image File Format (TIFF) image by using the IFD and Exif schemas.  
   
  [!code-csharp[BitmapFrameExample#7](~/samples/snippets/csharp/VS_Snippets_Wpf/BitmapFrameExample/CSharp/BitmapFrame.cs#7)]
  [!code-vb[BitmapFrameExample#7](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BitmapFrameExample/VB/BitmapFrame.vb#7)]  
diff --git a/xml/System.Windows.Media.Imaging/BitmapPalette.xml b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
index 477d75af2ae..12ae85af49f 100644
--- a/xml/System.Windows.Media.Imaging/BitmapPalette.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) image formats support image palettes. However, other image types can be used to define a <xref:System.Windows.Media.Imaging.BitmapPalette>. Attempting to define a <xref:System.Windows.Media.Imaging.BitmapPalette> for an unsupported bitmap format does not result in an exception; the designated <xref:System.Windows.Media.Imaging.BitmapPalette> is simply ignored.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) image formats support image palettes. However, other image types can be used to define a <xref:System.Windows.Media.Imaging.BitmapPalette>. Attempting to define a <xref:System.Windows.Media.Imaging.BitmapPalette> for an unsupported bitmap format does not result in an exception; the designated <xref:System.Windows.Media.Imaging.BitmapPalette> is simply ignored.  
   
  [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports both custom color palettes and predefined palettes defined by the <xref:System.Windows.Media.Imaging.BitmapPalettes> class.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapPalettes.xml b/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
index 04ff7db155b..1d9ac9ddac9 100644
--- a/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapPalettes.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapPalettes> properties whose names end with "Transparent" have an additional "color" that is fully transparent. In the case of palettes that already have 256 colors, the last color is replaced by the transparent color.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) image formats support palettes.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) image formats support palettes.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index 6f6685fbd7b..9524f10559c 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] images.  
+ [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and Tagged Image File Format (TIFF) images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Imaging/InPlaceBitmapMetadataWriter.xml b/xml/System.Windows.Media.Imaging/InPlaceBitmapMetadataWriter.xml
index a60215975e6..9e106834ae6 100644
--- a/xml/System.Windows.Media.Imaging/InPlaceBitmapMetadataWriter.xml
+++ b/xml/System.Windows.Media.Imaging/InPlaceBitmapMetadataWriter.xml
@@ -235,7 +235,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.InPlaceBitmapMetadataWriter.TrySave%2A> method to determine whether metadata can be written successfully to a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Imaging.InPlaceBitmapMetadataWriter.TrySave%2A> method to determine whether metadata can be written successfully to a Tagged Image File Format (TIFF) image.  
   
  [!code-cpp[bitmapmetadata#SetQuery](~/samples/snippets/cpp/VS_Snippets_Wpf/BitMapMetadata/CPP/BitmapMetadata.cpp#setquery)]
  [!code-csharp[bitmapmetadata#SetQuery](~/samples/snippets/csharp/VS_Snippets_Wpf/BitMapMetadata/CSharp/BitmapMetadata.cs#setquery)]
diff --git a/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
index a121f5801b1..ca1b09d9ac1 100644
--- a/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/LateBoundBitmapDecoder.xml
@@ -155,7 +155,7 @@
   
  Any frame obtained from a <xref:System.Windows.Media.Imaging.LateBoundBitmapDecoder> while the image is downloading will return a width/height of `1,1` until the frames have finished downloading.  
   
- Only [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] and Graphics Interchange Format (GIF) images support more than one frame.  
+ Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) images support more than one frame.  
   
  Any <xref:System.Windows.Media.Imaging.BitmapFrame> objects that this property returns are frozen.  
   
diff --git a/xml/System.Windows.Media.Imaging/TiffBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/TiffBitmapDecoder.xml
index 05462c5d1fc..d8a9189d40a 100644
--- a/xml/System.Windows.Media.Imaging/TiffBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/TiffBitmapDecoder.xml
@@ -78,7 +78,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapStream" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapStream" /> is not a Tagged Image File Format (TIFF) encoded image.</exception>
       </Docs>
     </Member>
     <Member MemberName=".ctor">
@@ -124,7 +124,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentNullException">The <paramref name="bitmapUri" /> value is <see langword="null" />.</exception>
-        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] encoded image.</exception>
+        <exception cref="T:System.IO.FileFormatException">The <paramref name="bitmapUri" /> is not a Tagged Image File Format (TIFF) encoded image.</exception>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Windows.Media.Imaging/TiffBitmapEncoder.xml b/xml/System.Windows.Media.Imaging/TiffBitmapEncoder.xml
index efb95ff4c78..6ac18c8b3c3 100644
--- a/xml/System.Windows.Media.Imaging/TiffBitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/TiffBitmapEncoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] bitmap format supports frame level thumbnails, multiple frames, and frame level metadata. It does not support global preview, global thumbnails, or global metadata.  
+ The Tagged Image File Format (TIFF) bitmap format supports frame level thumbnails, multiple frames, and frame level metadata. It does not support global preview, global thumbnails, or global metadata.  
   
  Encoding does not work in partial trust. See [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security) for information on partial trust.  
   
@@ -95,7 +95,7 @@
         <ReturnType>System.Windows.Media.Imaging.TiffCompressOption</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates the type of compression that is used by this [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image.</summary>
+        <summary>Gets or sets a value that indicates the type of compression that is used by this Tagged Image File Format (TIFF) image.</summary>
         <value>One of the <see cref="T:System.Windows.Media.Imaging.TiffCompressOption" /> values. The default is <see cref="F:System.Windows.Media.Imaging.TiffCompressOption.Default" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Media.Imaging/TiffCompressOption.xml b/xml/System.Windows.Media.Imaging/TiffCompressOption.xml
index 4fc149cab26..ae89c4aaf34 100644
--- a/xml/System.Windows.Media.Imaging/TiffCompressOption.xml
+++ b/xml/System.Windows.Media.Imaging/TiffCompressOption.xml
@@ -143,7 +143,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] image is not compressed.</summary>
+        <summary>The Tagged Image File Format (TIFF) image is not compressed.</summary>
       </Docs>
     </Member>
     <Member MemberName="Rle">
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index efe445995ad..addc0bacca5 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -45,7 +45,7 @@
 |<xref:System.Windows.DataFormats.StringFormat>|"System.String"|Specifies the common language runtime (CLR) string class data format.|  
 |<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the Windows symbolic link data format.|  
 |<xref:System.Windows.DataFormats.Text>|"Text"|Specifies the ANSI text data format.|  
-|<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] data format.|  
+|<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the Tagged Image File Format (TIFF) data format.|  
 |<xref:System.Windows.DataFormats.UnicodeText>|"UnicodeText"|Specifies the [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] text data format.|  
 |<xref:System.Windows.DataFormats.WaveAudio>|"WaveAudio"|Specifies the wave audio data format.|  
 |<xref:System.Windows.DataFormats.Xaml>|"Xaml"|Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] data format.|  
@@ -765,7 +765,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_tiff](~/includes/tlasharptla-tiff-md.md)] data format.</summary>
+        <summary>Specifies the Tagged Image File Format (TIFF) data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From 699c3720adac0f1d5f8c046240c3416b3c991c19 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:03:11 -0800
Subject: [PATCH 155/236] tlasharptla-titlewinclient

---
 xml/System.Windows.Input/Touch.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Input/Touch.xml b/xml/System.Windows.Input/Touch.xml
index b9cf288cc68..878740554a0 100644
--- a/xml/System.Windows.Input/Touch.xml
+++ b/xml/System.Windows.Input/Touch.xml
@@ -69,7 +69,7 @@
 ## Remarks  
  A frame is one in a series of multitouch messages or touch points. You can respond to touches by handling the <xref:System.Windows.Input.Touch.FrameReported> event and accessing the details of the <xref:System.Windows.Input.TouchPoint> from the <xref:System.Windows.Input.TouchFrameEventArgs> event data.  
   
- The <xref:System.Windows.Input.Touch.FrameReported> event does not use the same event model as other [!INCLUDE[TLA#tla_titlewinclient](~/includes/tlasharptla-titlewinclient-md.md)] input events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>. Instead of being exposed as an element-specific event that potentially routes through the object tree of a UI, the <xref:System.Windows.Input.Touch.FrameReported> event is a single event that is handled at the application level. Therefore, you cannot use the `sender` parameter of the event handler to determine what element is touched.  
+ The <xref:System.Windows.Input.Touch.FrameReported> event does not use the same event model as other WPF input events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>. Instead of being exposed as an element-specific event that potentially routes through the object tree of a UI, the <xref:System.Windows.Input.Touch.FrameReported> event is a single event that is handled at the application level. Therefore, you cannot use the `sender` parameter of the event handler to determine what element is touched.  
   
    
   

From 8dab232dc6072843ecf112242e1557602cfc485e Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:03:35 -0800
Subject: [PATCH 156/236] tlasharptla-titlexaml

---
 .../AnnotationService.xml                      | 12 ++++++------
 xml/System.Windows.Controls/Page.xml           |  4 ++--
 .../BlockUIContainer.xml                       |  2 +-
 .../InlineUIContainer.xml                      |  2 +-
 xml/System.Windows.Documents/List.xml          |  4 ++--
 xml/System.Windows.Documents/ListItem.xml      |  4 ++--
 xml/System.Windows.Documents/TextPointer.xml   |  2 +-
 xml/System.Windows.Input/RoutedCommand.xml     |  2 +-
 xml/System.Windows.Media/FontFamily.xml        |  2 +-
 xml/System.Windows/Application.xml             | 18 +++++++++---------
 10 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/xml/System.Windows.Annotations/AnnotationService.xml b/xml/System.Windows.Annotations/AnnotationService.xml
index 41f3895e6df..0e69fe145ba 100644
--- a/xml/System.Windows.Annotations/AnnotationService.xml
+++ b/xml/System.Windows.Annotations/AnnotationService.xml
@@ -205,7 +205,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to assign routed commands to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to assign routed commands to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
@@ -240,7 +240,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to assign routed commands to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to assign routed commands to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
@@ -275,7 +275,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how routed commands are assigned to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how routed commands are assigned to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
@@ -310,7 +310,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how routed commands are assigned to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how routed commands are assigned to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
@@ -345,7 +345,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to assign routed commands to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to assign routed commands to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
@@ -381,7 +381,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how routed commands are assigned to menu items in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how routed commands are assigned to menu items in XAML.  
   
  [!code-xaml[DocViewerAnnotationsXps#CreateDeleteAnnotations](~/samples/snippets/csharp/VS_Snippets_Wpf/DocViewerAnnotationsXps/CSharp/Window1.xaml#createdeleteannotations)]  
   
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 34aaaf9413a..c4fd21cda50 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -589,7 +589,7 @@
    
   
 ## Examples  
- The following example shows how to use [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] to retain an instance of the <xref:System.Windows.Controls.Page> class across multiple navigations.  
+ The following example shows how to use XAML to retain an instance of the <xref:System.Windows.Controls.Page> class across multiple navigations.  
   
  [!code-xaml[PageKeepAliveSnippets#SetPageKeepAliveXAML1](~/samples/snippets/xaml/VS_Snippets_Wpf/PageKeepAliveSnippets/XAML/HomePage.xaml#setpagekeepalivexaml1)]  
 [!code-xaml[PageKeepAliveSnippets#SetPageKeepAliveXAML2](~/samples/snippets/xaml/VS_Snippets_Wpf/PageKeepAliveSnippets/XAML/HomePage.xaml#setpagekeepalivexaml2)]  
@@ -1014,7 +1014,7 @@
    
   
 ## Examples  
- The following example shows how to use [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] to hide the navigation UI of a <xref:System.Windows.Navigation.NavigationWindow>.  
+ The following example shows how to use XAML to hide the navigation UI of a <xref:System.Windows.Navigation.NavigationWindow>.  
   
  [!code-xaml[PageShowsNavigationUISnippets#SetPageShowsNavigationUIXAML1](~/samples/snippets/xaml/VS_Snippets_Wpf/PageShowsNavigationUISnippets/XAML/HomePage.xaml#setpageshowsnavigationuixaml1)]  
 [!code-xaml[PageShowsNavigationUISnippets#SetPageShowsNavigationUIXAML2](~/samples/snippets/xaml/VS_Snippets_Wpf/PageShowsNavigationUISnippets/XAML/HomePage.xaml#setpageshowsnavigationuixaml2)]  
diff --git a/xml/System.Windows.Documents/BlockUIContainer.xml b/xml/System.Windows.Documents/BlockUIContainer.xml
index 2960a2efd2c..f44fcd5eb8f 100644
--- a/xml/System.Windows.Documents/BlockUIContainer.xml
+++ b/xml/System.Windows.Documents/BlockUIContainer.xml
@@ -140,7 +140,7 @@
 ## Remarks  
  An <xref:System.Windows.Documents.BlockUIContainer> may directly host no more than one <xref:System.Windows.UIElement> child.  However, the child element hosted by an <xref:System.Windows.Documents.BlockUIContainer> may host children of its own.  
   
- In [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)], wrapping a <xref:System.Windows.UIElement> in an <xref:System.Windows.Documents.BlockUIContainer> is equivalent to setting that <xref:System.Windows.UIElement> as the value of the <xref:System.Windows.Documents.BlockUIContainer.Child%2A> property.  
+ In XAML, wrapping a <xref:System.Windows.UIElement> in an <xref:System.Windows.Documents.BlockUIContainer> is equivalent to setting that <xref:System.Windows.UIElement> as the value of the <xref:System.Windows.Documents.BlockUIContainer.Child%2A> property.  
   
    
   
diff --git a/xml/System.Windows.Documents/InlineUIContainer.xml b/xml/System.Windows.Documents/InlineUIContainer.xml
index 67a6177e0c8..d6050de04c4 100644
--- a/xml/System.Windows.Documents/InlineUIContainer.xml
+++ b/xml/System.Windows.Documents/InlineUIContainer.xml
@@ -185,7 +185,7 @@
 ## Remarks  
  An <xref:System.Windows.Documents.InlineUIContainer> may directly host no more than one <xref:System.Windows.UIElement> child.  However, the child element hosted by an <xref:System.Windows.Documents.InlineUIContainer> may host children of its own.  
   
- In [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)], wrapping a <xref:System.Windows.UIElement> in an <xref:System.Windows.Documents.InlineUIContainer> is equivalent to setting that <xref:System.Windows.UIElement> as the value of the <xref:System.Windows.Documents.InlineUIContainer.Child%2A> property.  
+ In XAML, wrapping a <xref:System.Windows.UIElement> in an <xref:System.Windows.Documents.InlineUIContainer> is equivalent to setting that <xref:System.Windows.UIElement> as the value of the <xref:System.Windows.Documents.InlineUIContainer.Child%2A> property.  
   
    
   
diff --git a/xml/System.Windows.Documents/List.xml b/xml/System.Windows.Documents/List.xml
index 906a9a30904..b77a948246e 100644
--- a/xml/System.Windows.Documents/List.xml
+++ b/xml/System.Windows.Documents/List.xml
@@ -37,7 +37,7 @@
    
   
 ## Examples  
- The following example shows how to define a <xref:System.Windows.Documents.List> using [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to define a <xref:System.Windows.Documents.List> using XAML.  
   
  [!code-xaml[ListSnippets#_ListXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/ListSnippets/CSharp/Window1.xaml#_listxaml)]  
   
@@ -50,7 +50,7 @@
   
  ![Screenshot: Ordered list](~/add/media/ordered-list.png "Screenshot: Ordered list")  
   
- The following example shows how to define a nested <xref:System.Windows.Documents.List> (lists within lists) using [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to define a nested <xref:System.Windows.Documents.List> (lists within lists) using XAML.  
   
  [!code-xaml[ListSnippets#_NestedListXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/ListSnippets/CSharp/Window1.xaml#_nestedlistxaml)]  
   
diff --git a/xml/System.Windows.Documents/ListItem.xml b/xml/System.Windows.Documents/ListItem.xml
index 841f2eaf950..caa564150f3 100644
--- a/xml/System.Windows.Documents/ListItem.xml
+++ b/xml/System.Windows.Documents/ListItem.xml
@@ -34,7 +34,7 @@
    
   
 ## Examples  
- The following example shows how to define a <xref:System.Windows.Documents.List> using [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to define a <xref:System.Windows.Documents.List> using XAML.  
   
  [!code-xaml[ListSnippets#_ListXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/ListSnippets/CSharp/Window1.xaml#_listxaml)]  
   
@@ -47,7 +47,7 @@
   
  ![Screenshot: Ordered list](~/add/media/ordered-list.png "Screenshot: Ordered list")  
   
- The following example shows how to define a nested <xref:System.Windows.Documents.List> (lists within lists) using [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ The following example shows how to define a nested <xref:System.Windows.Documents.List> (lists within lists) using XAML.  
   
  [!code-xaml[ListSnippets#_NestedListXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/ListSnippets/CSharp/Window1.xaml#_nestedlistxaml)]  
   
diff --git a/xml/System.Windows.Documents/TextPointer.xml b/xml/System.Windows.Documents/TextPointer.xml
index 7ed7dc584f6..26a459cb748 100644
--- a/xml/System.Windows.Documents/TextPointer.xml
+++ b/xml/System.Windows.Documents/TextPointer.xml
@@ -494,7 +494,7 @@
 ## Examples  
  The following example demonstrates a use for this method.  The example uses the <xref:System.Windows.Documents.TextPointer.GetNextContextPosition%2A> method in conjunction with the <xref:System.Windows.Documents.TextPointer.GetPointerContext%2A> method to traverse and extract the symbols in a specified <xref:System.Windows.Documents.TextElement>.  
   
- While the example can be used to extract a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] structure for the contents of a given <xref:System.Windows.Documents.TextElement>, it is intended for illustrative purposes only, and should not be used in production code.  See the <xref:System.Xml> namespace for a rich set of types designed for working with and processing XML.  
+ While the example can be used to extract a XAML structure for the contents of a given <xref:System.Windows.Documents.TextElement>, it is intended for illustrative purposes only, and should not be used in production code.  See the <xref:System.Xml> namespace for a rich set of types designed for working with and processing XML.  
   
  [!code-csharp[TextPointer_Snippets#_TextPointer_GetNextContextPosition](~/samples/snippets/csharp/VS_Snippets_Wpf/TextPointer_Snippets/CSharp/Window1.xaml.cs#_textpointer_getnextcontextposition)]
  [!code-vb[TextPointer_Snippets#_TextPointer_GetNextContextPosition](~/samples/snippets/visualbasic/VS_Snippets_Wpf/TextPointer_Snippets/visualbasic/window1.xaml.vb#_textpointer_getnextcontextposition)]  
diff --git a/xml/System.Windows.Input/RoutedCommand.xml b/xml/System.Windows.Input/RoutedCommand.xml
index 34dd477af6d..8bd1e7160a5 100644
--- a/xml/System.Windows.Input/RoutedCommand.xml
+++ b/xml/System.Windows.Input/RoutedCommand.xml
@@ -420,7 +420,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property can be used when referencing a <xref:System.Windows.Input.RoutedCommand> in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)].  
+ This property can be used when referencing a <xref:System.Windows.Input.RoutedCommand> in XAML.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index d36dfa338eb..071285b28fc 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -65,7 +65,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  [!code-csharp[FontSnippets#FontPackageSnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml.cs#fontpackagesnippet2)]
  [!code-vb[FontSnippets#FontPackageSnippet2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontpackagesnippets.xaml.vb#fontpackagesnippet2)]  
   
- When a <xref:System.Windows.Media.FontFamily> is specified as an attribute in markup, the base URI value is always implied - its value is the URI of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] page. The implied base URI value is used with the relative URI value in the friendly name string to obtain the location of the font. In the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] example, notice that the relative URI value uses the "./" notation, which means "in the current folder" of the base URI value.  
+ When a <xref:System.Windows.Media.FontFamily> is specified as an attribute in markup, the base URI value is always implied - its value is the URI of the XAML page. The implied base URI value is used with the relative URI value in the friendly name string to obtain the location of the font. In the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] example, notice that the relative URI value uses the "./" notation, which means "in the current folder" of the base URI value.  
   
  [!code-xaml[FontSnippets#FontPackageSnippet1](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml#fontpackagesnippet1)]  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index ae96938450c..53ecf366d09 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -699,7 +699,7 @@
         <AssemblyVersion>4.0.0.0</AssemblyVersion>
       </AssemblyInfo>
       <Docs>
-        <summary>Loads a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file that is located at the specified uniform resource identifier (URI).</summary>
+        <summary>Loads a XAML file that is located at the specified uniform resource identifier (URI).</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -738,13 +738,13 @@
       </Parameters>
       <Docs>
         <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative XAML file.</param>
-        <summary>Loads a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file that is located at the specified uniform resource identifier (URI), and converts it to an instance of the object that is specified by the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.</summary>
+        <summary>Loads a XAML file that is located at the specified uniform resource identifier (URI), and converts it to an instance of the object that is specified by the root element of the XAML file.</summary>
         <returns>An instance of the root element specified by the XAML file loaded.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You must explicitly convert the return value to the same type as the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.  
+ You must explicitly convert the return value to the same type as the root element of the XAML file.  
   
  The XAML file can be an application code file (configured as an Microsoft build engine (MSBuild) Page item) or an application data file (a resource file, content file, or site-of-origin file; see [WPF Application Resource, Content, and Data Files](/dotnet/framework/wpf/app-development/wpf-application-resource-content-and-data-files)).  
   
@@ -792,7 +792,7 @@
       <Docs>
         <param name="component">An object of the same type as the root element of the XAML file.</param>
         <param name="resourceLocator">A <see cref="T:System.Uri" /> that maps to a relative XAML file.</param>
-        <summary>Loads a [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file that is located at the specified uniform resource identifier (URI) and converts it to an instance of the object that is specified by the root element of the [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] file.</summary>
+        <summary>Loads a XAML file that is located at the specified uniform resource identifier (URI) and converts it to an instance of the object that is specified by the root element of the XAML file.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -844,7 +844,7 @@
   
  If the <xref:System.Windows.Application.ShutdownMode%2A> property of the <xref:System.Windows.Application> object is set to <xref:System.Windows.ShutdownMode.OnMainWindowClose>, closing the main window causes the application to shut down.  
   
- It is possible to set the <xref:System.Windows.Application.MainWindow%2A> property from [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)], if an application's main window is not the window that is produced by setting the <xref:System.Windows.Application.StartupUri%2A> property in XAML. The two limitations of the XAML approach are:  
+ It is possible to set the <xref:System.Windows.Application.MainWindow%2A> property from XAML, if an application's main window is not the window that is produced by setting the <xref:System.Windows.Application.StartupUri%2A> property in XAML. The two limitations of the XAML approach are:  
   
 -   You can specify either a XAML-only <xref:System.Windows.Window> or a XAML-only <xref:System.Windows.Navigation.NavigationWindow> as the main window.  
   
@@ -1697,7 +1697,7 @@
   
  Consequently, [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements can bind to application-scope resources. Additionally, if resources change, the resource system ensures that element properties which are bound to those resources are automatically updated to reflect the change.  
   
- Application-scope resources provide a simple way to support a consistent theme across your application. You can easily create a theme in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] by using the `Application.Resources` tag. However, if your application supports multiple themes, which may contain a large number of theme elements, it might be easier to manage them using one <xref:System.Windows.ResourceDictionary> instance for each theme. In this way, a new theme can be applied by setting the Resources property to the appropriate <xref:System.Windows.ResourceDictionary>.  
+ Application-scope resources provide a simple way to support a consistent theme across your application. You can easily create a theme in XAML by using the `Application.Resources` tag. However, if your application supports multiple themes, which may contain a large number of theme elements, it might be easier to manage them using one <xref:System.Windows.ResourceDictionary> instance for each theme. In this way, a new theme can be applied by setting the Resources property to the appropriate <xref:System.Windows.ResourceDictionary>.  
   
  There are two considerations to make when using <xref:System.Windows.Application.Resources%2A>. First, the dictionary *key* is an object, so you need to use exactly the same object instance when both setting and getting a property value (note that the key is case-sensitive when using a string). Second, the dictionary *value* is an object, so you will need to convert the value to the desired type when getting a property value.  
   
@@ -2091,7 +2091,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
  The lifetime of some applications may not be dependent on when the main window or last window is closed, or may not be dependent on windows at all. For these scenarios you need to set the <xref:System.Windows.Application.ShutdownMode%2A> property to <xref:System.Windows.ShutdownMode.OnExplicitShutdown>, which requires an explicit <xref:System.Windows.Application.Shutdown%2A> method call to stop the application. Otherwise, the application continues running in the background.  
   
- <xref:System.Windows.Application.ShutdownMode%2A> can be configured declaratively from [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] or programmatically from code.  
+ <xref:System.Windows.Application.ShutdownMode%2A> can be configured declaratively from XAML or programmatically from code.  
   
  This property is available only from the thread that created the <xref:System.Windows.Application> object.  
   
@@ -2141,7 +2141,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
 -   Initializing application-scope properties.  
   
- You can declaratively specify the main window and application-scope resources using [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)] (<xref:System.Windows.Application.StartupUri%2A> and <xref:System.Windows.Application.Resources%2A>, respectively). Sometimes, however, the resources or main window of your application can only be determined programmatically at run time. Additionally, application-scope properties and command-line parameters can only be used programmatically. Programmatic initialization can be performed by handling the <xref:System.Windows.Application.Startup> event, including the following:  
+ You can declaratively specify the main window and application-scope resources using XAML (<xref:System.Windows.Application.StartupUri%2A> and <xref:System.Windows.Application.Resources%2A>, respectively). Sometimes, however, the resources or main window of your application can only be determined programmatically at run time. Additionally, application-scope properties and command-line parameters can only be used programmatically. Programmatic initialization can be performed by handling the <xref:System.Windows.Application.Startup> event, including the following:  
   
 -   Acquire and process command-line parameters, which are available from the <xref:System.Windows.StartupEventArgs.Args%2A> property of the <xref:System.Windows.StartupEventArgs> class that is passed to the <xref:System.Windows.Application.Startup> event handler.  
   
@@ -2216,7 +2216,7 @@ This example illustrates how to use XAML together with application-scope resourc
 |<xref:System.Windows.Documents.FlowDocument>|<xref:System.Windows.Navigation.NavigationWindow>|Standalone/browser-hosted|  
 |<xref:System.Windows.Navigation.PageFunction%601>|<xref:System.Windows.Navigation.NavigationWindow>|Standalone/browser-hosted|  
   
- Typically, you set the <xref:System.Windows.Application.StartupUri%2A> property declaratively in [!INCLUDE[TLA#tla_titlexaml](~/includes/tlasharptla-titlexaml-md.md)]. However, you can set <xref:System.Windows.Application.StartupUri%2A> programmatically, such as from a <xref:System.Windows.Application.Startup> event handler, which is useful if for applications that can only load the necessary UI resources at run time. For example, an application might wait until run time to load its resources if the name of the UI resource is stored in a configuration file.  
+ Typically, you set the <xref:System.Windows.Application.StartupUri%2A> property declaratively in XAML. However, you can set <xref:System.Windows.Application.StartupUri%2A> programmatically, such as from a <xref:System.Windows.Application.Startup> event handler, which is useful if for applications that can only load the necessary UI resources at run time. For example, an application might wait until run time to load its resources if the name of the UI resource is stored in a configuration file.  
   
  Whether you set <xref:System.Windows.Application.StartupUri%2A> declaratively or programmatically, the corresponding UI resource is not loaded until after the <xref:System.Windows.Application.Startup> event is handled. Consequently, you won't have access to the resulting window from either the <xref:System.Windows.Application.Windows%2A> property or the <xref:System.Windows.Application.MainWindow%2A> property when handling <xref:System.Windows.Application.Startup>.  
   

From ac333a014f2c7898907643ec2634e3a2d31708f6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:03:53 -0800
Subject: [PATCH 157/236] tlasharptla-tpc

---
 xml/System.Windows.Controls/StickyNoteType.xml | 2 +-
 xml/System.Windows/SystemParameters.xml        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Controls/StickyNoteType.xml b/xml/System.Windows.Controls/StickyNoteType.xml
index deca7cffff9..fe48519765e 100644
--- a/xml/System.Windows.Controls/StickyNoteType.xml
+++ b/xml/System.Windows.Controls/StickyNoteType.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  Use this enumeration primarily to provide values for the <xref:System.Windows.Controls.StickyNoteControl.StickyNoteType%2A> property of a <xref:System.Windows.Controls.StickyNoteControl>.  
   
- An ink <xref:System.Windows.Controls.StickyNoteControl> can be handwritten on a [!INCLUDE[TLA#tla_tpc](~/includes/tlasharptla-tpc-md.md)] or other hardware that supports handwritten input.  
+ An ink <xref:System.Windows.Controls.StickyNoteControl> can be handwritten on a Tablet PC or other hardware that supports handwritten input.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index c1d5094b6d5..000f48f5482 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -3445,7 +3445,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the current operating system is Microsoft Windows XP [!INCLUDE[TLA#tla_tpc](~/includes/tlasharptla-tpc-md.md)] Edition.</summary>
+        <summary>Gets a value that indicates whether the current operating system is Microsoft Windows XP Tablet PC Edition.</summary>
         <value>
           <see langword="true" /> if the current operating system is Windows XP Tablet PC Edition; otherwise, <see langword="false" />.</value>
         <remarks>

From b457aebc41556cddfdfa1a2661e1db586c2d1aec Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:04:13 -0800
Subject: [PATCH 158/236] tlasharptla-ui

---
 xml/System.IO.Packaging/PackageProperties.xml |  2 +-
 xml/System.Printing/PrintSystemJobInfo.xml    |  4 +--
 .../TabItemWrapperAutomationPeer.xml          |  2 +-
 xml/System.Windows.Automation/Automation.xml  |  4 +--
 ...onElement+AutomationElementInformation.xml |  6 ++--
 .../AutomationElement.xml                     | 34 +++++++++----------
 .../AutomationElementIdentifiers.xml          |  2 +-
 .../AutomationElementMode.xml                 |  2 +-
 .../AutomationFocusChangedEventArgs.xml       |  2 +-
 .../CacheRequest.xml                          |  4 +--
 xml/System.Windows.Automation/TreeWalker.xml  | 28 +++++++--------
 .../ItemsChangedEventArgs.xml                 |  2 +-
 .../ToggleButton.xml                          |  2 +-
 xml/System.Windows.Controls/AccessText.xml    |  4 +--
 .../FlowDocumentPageViewer.xml                | 10 +++---
 .../FlowDocumentReader.xml                    | 22 ++++++------
 .../FlowDocumentScrollViewer.xml              |  4 +--
 xml/System.Windows.Controls/ItemsControl.xml  |  2 +-
 xml/System.Windows.Controls/Panel.xml         |  2 +-
 xml/System.Windows.Controls/PrintDialog.xml   |  4 +--
 .../StickyNoteControl.xml                     |  2 +-
 xml/System.Windows.Controls/TextBlock.xml     |  2 +-
 xml/System.Windows.Controls/Validation.xml    |  2 +-
 .../VirtualizationCacheLength.xml             |  4 +--
 .../VirtualizingPanel.xml                     |  4 +--
 .../VirtualizingStackPanel.xml                |  2 +-
 xml/System.Windows.Data/BindingGroup.xml      |  4 +--
 xml/System.Windows.Data/CollectionView.xml    |  6 ++--
 xml/System.Windows.Input/InputMethod.xml      | 18 +++++-----
 xml/System.Windows.Input/Mouse.xml            |  2 +-
 xml/System.Windows.Media/FontFamily.xml       |  2 +-
 xml/System.Windows.Media/MediaPlayer.xml      |  2 +-
 .../NavigationService.xml                     |  2 +-
 .../DispatcherTimer.xml                       |  2 +-
 xml/System.Windows/Application.xml            |  6 ++--
 xml/System.Windows/ContentElement.xml         |  4 +--
 xml/System.Windows/DragDrop.xml               |  2 +-
 xml/System.Windows/EventTrigger.xml           |  4 +--
 .../FrameworkContentElement.xml               |  8 ++---
 xml/System.Windows/FrameworkElement.xml       | 14 ++++----
 xml/System.Windows/IInputElement.xml          |  2 +-
 xml/System.Windows/SystemParameters.xml       |  2 +-
 xml/System.Windows/UIElement.xml              | 14 ++++----
 xml/System.Windows/UIElement3D.xml            | 10 +++---
 xml/System.Windows/WindowStyle.xml            |  2 +-
 45 files changed, 132 insertions(+), 132 deletions(-)

diff --git a/xml/System.IO.Packaging/PackageProperties.xml b/xml/System.IO.Packaging/PackageProperties.xml
index 53b8a6fe6ad..decb3babcf8 100644
--- a/xml/System.IO.Packaging/PackageProperties.xml
+++ b/xml/System.IO.Packaging/PackageProperties.xml
@@ -103,7 +103,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Packaging.PackageProperties.Category%2A> value is typically used as part of the application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] to create labels for navigation controls.  
+ The <xref:System.IO.Packaging.PackageProperties.Category%2A> value is typically used as part of the application user interface (UI) to create labels for navigation controls.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Printing/PrintSystemJobInfo.xml b/xml/System.Printing/PrintSystemJobInfo.xml
index 472e397389c..c532b93cedc 100644
--- a/xml/System.Printing/PrintSystemJobInfo.xml
+++ b/xml/System.Printing/PrintSystemJobInfo.xml
@@ -1183,7 +1183,7 @@
 ## Remarks  
  This value is propagated to each <xref:System.Printing.PrintSystemJobInfo> object from the <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> property of the hosting <xref:System.Printing.PrintQueue> at the time the job enters the queue. If <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> is changed, then any <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A?displayProperty=nameWithType> value that is earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> is changed to the value of <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
   
- After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], provided that it is not earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
+ After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] user interface (UI), provided that it is not earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
   
  If you are not in the UTC time zone, you must add or subtract multiples of 60 to get the correct time for your time zone. For example, if you are in the Pacific Time Zone of North America and daylight savings time is not in effect, then your local time is 8 hours earlier than UTC. If <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> returns 960, that means 16:00 (4:00 PM) in UTC (because 960/60 = 16). To convert this to Pacific Time, you must subtract 480 (= 8 * 60) minutes.  
   
@@ -1318,7 +1318,7 @@
 ## Remarks  
  This value is propagated to each <xref:System.Printing.PrintSystemJobInfo> object from the <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> property of the hosting <xref:System.Printing.PrintQueue> at the time the job enters the queue. If <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> is changed, then any <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A?displayProperty=nameWithType> value that is later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> is changed to the value of <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
   
- After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], provided that it is not later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
+ After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] user interface (UI), provided that it is not later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
   
  If you are not in the UTC time zone, you must add or subtract multiples of 60 to get the correct time for your time zone. For example, if you are in the Pacific Time Zone of North America and daylight savings time is not in effect, then your local time is 8 hours earlier than UTC. If <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> returns 960, that means 16:00 (4:00 PM) in UTC (because 960/60 = 16). To convert this to Pacific Time, you must subtract 480 (= 8 * 60) minutes.  
   
diff --git a/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
index 9739b42a70f..5bba3b55a14 100644
--- a/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TabItemWrapperAutomationPeer.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When data items are shown in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], the system creates a <xref:System.Windows.UIElement> subtree for the data items. The system also creates an <xref:System.Windows.Automation.Peers.ItemAutomationPeer> for each data item. When the UI for the data item is created, this <xref:System.Windows.Automation.Peers.TabItemWrapperAutomationPeer> is also created. The two peers then merge to form a single peer.  
+ When data items are shown in the user interface (UI), the system creates a <xref:System.Windows.UIElement> subtree for the data items. The system also creates an <xref:System.Windows.Automation.Peers.ItemAutomationPeer> for each data item. When the UI for the data item is created, this <xref:System.Windows.Automation.Peers.TabItemWrapperAutomationPeer> is also created. The two peers then merge to form a single peer.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Automation/Automation.xml b/xml/System.Windows.Automation/Automation.xml
index df7c51f722b..49029a16b0f 100644
--- a/xml/System.Windows.Automation/Automation.xml
+++ b/xml/System.Windows.Automation/Automation.xml
@@ -156,7 +156,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item specified by the supplied UI Automation element might not support the properties specified by the `properties` parameter.  
+ The user interface (UI) item specified by the supplied UI Automation element might not support the properties specified by the `properties` parameter.  
   
  `eventHandler` can be an instance of the method, or a reference to the method (`AddressOf` in Visual Basic).  
   
@@ -268,7 +268,7 @@
         <param name="runtimeId2">The second run-time ID to compare.</param>
         <summary>Compares two integer arrays containing run-time identifiers (IDs) to determine whether their content is the same.</summary>
         <returns>
-          <see langword="true" /> if the compared run-time IDs refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element; otherwise <see langword="false" />.</returns>
+          <see langword="true" /> if the compared run-time IDs refer to the same user interface (UI) element; otherwise <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
index 1153f3af379..cdc59df33ee 100644
--- a/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
+++ b/xml/System.Windows.Automation/AutomationElement+AutomationElementInformation.xml
@@ -162,7 +162,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The returned rectangle can contain points that are not clickable. Instances where this could happen are when the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item has an irregular shape or clickable region, or it is obscured by other UI elements.  
+ The returned rectangle can contain points that are not clickable. Instances where this could happen are when the user interface (UI) item has an irregular shape or clickable region, or it is obscured by other UI elements.  
   
  ]]></format>
         </remarks>
@@ -418,7 +418,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the UI Automation element is enabled.</summary>
+        <summary>Gets a value that indicates whether the user interface (UI) item referenced by the UI Automation element is enabled.</summary>
         <value>
           <see langword="true" /> if the control is enabled; otherwise <see langword="false" />.</value>
         <remarks>
@@ -716,7 +716,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the name of the element.</summary>
-        <value>The name of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</value>
+        <value>The name of the user interface (UI) element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 7c6638b8c1c..631d9981642 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], regardless of underlying implementation (such as [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] or [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)]).  
+ An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of user interface (UI), regardless of underlying implementation (such as [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] or [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)]).  
   
  ]]></format>
     </remarks>
@@ -222,7 +222,7 @@
   
  While support of an <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A> is always recommended for better testability, this property is not mandatory. Where it is supported, an <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A> is useful for creating test automation scripts that run regardless of UI language. Clients should make no assumptions regarding the <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A>s exposed by other applications. An <xref:System.Windows.Automation.AutomationElement.AutomationElementInformation.AutomationId%2A> is not necessarily guaranteed to be stable across different releases or builds of an application.  
   
- Instances of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are uniquely identified on the desktop by their <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty> properties.  
+ Instances of user interface (UI) elements are uniquely identified on the desktop by their <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty> properties.  
   
 > [!NOTE]
 >  <xref:System.Windows.Automation.AutomationElement.AutomationIdProperty> is supported by all UI Automation elements in the control view except top-level application windows, UI Automation elements derived from [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] controls that do not have an ID or x:Uid, and UI Automation elements derived from Win32 controls that do not have a control ID.  
@@ -304,7 +304,7 @@
   
  This property can also be retrieved from the <xref:System.Windows.Automation.AutomationElement.Current%2A> or <xref:System.Windows.Automation.AutomationElement.Cached%2A> properties.  
   
- Bounding rectangles are of type <xref:System.Windows.Rect>. The returned rectangle is in physical screen coordinates. The default value is <xref:System.Windows.Rect.Empty%2A>. <xref:System.Windows.Rect.Empty%2A> is returned if the item is not currently displaying a [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ Bounding rectangles are of type <xref:System.Windows.Rect>. The returned rectangle is in physical screen coordinates. The default value is <xref:System.Windows.Rect.Empty%2A>. <xref:System.Windows.Rect.Empty%2A> is returned if the item is not currently displaying a user interface (UI).  
   
  The returned rectangle can contain points that are not clickable. Instances where this could happen include when the UI item has an irregular shape or clickable region, or it is obscured by other UI elements.  
   
@@ -946,7 +946,7 @@
       </Parameters>
       <Docs>
         <param name="hwnd">The handle of the UI element.</param>
-        <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the specified window handle.</summary>
+        <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the user interface (UI) item referenced by the specified window handle.</summary>
         <returns>An <see cref="T:System.Windows.Automation.AutomationElement" /> for the UI item identified by <paramref name="hwnd" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Automation.AutomationElement.FromPoint(System.Windows.Point)" />
@@ -1010,7 +1010,7 @@
       </Parameters>
       <Docs>
         <param name="pt">The physical screen coordinates on the desktop at which to locate the UI element.</param>
-        <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item at specified point on the desktop.</summary>
+        <summary>Retrieves a new <see cref="T:System.Windows.Automation.AutomationElement" /> object for the user interface (UI) item at specified point on the desktop.</summary>
         <returns>The UI item at the specified point.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1133,7 +1133,7 @@
       </Parameters>
       <Docs>
         <param name="property">The identifier of the property to retrieve.</param>
-        <summary>Retrieves the value of the specified property from the cache of this <see cref="T:System.Windows.Automation.AutomationElement" />. An appropriate default value for the property type is returned for properties not explicitly supported by the target [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</summary>
+        <summary>Retrieves the value of the specified property from the cache of this <see cref="T:System.Windows.Automation.AutomationElement" />. An appropriate default value for the property type is returned for properties not explicitly supported by the target user interface (UI) element.</summary>
         <returns>An object containing the value of the specified property.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1156,7 +1156,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">The requested property is not in the cache.</exception>
-        <exception cref="T:System.Windows.Automation.ElementNotAvailableException">The [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] for the <see cref="T:System.Windows.Automation.AutomationElement" /> no longer exists.</exception>
+        <exception cref="T:System.Windows.Automation.ElementNotAvailableException">The user interface (UI) for the <see cref="T:System.Windows.Automation.AutomationElement" /> no longer exists.</exception>
       </Docs>
     </Member>
     <Member MemberName="GetCachedPropertyValue">
@@ -1329,7 +1329,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the user interface (UI).  
   
  For some forms of UI, this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
@@ -1368,7 +1368,7 @@
       </Parameters>
       <Docs>
         <param name="property">The UI Automation property identifier specifying which property to retrieve.</param>
-        <summary>Retrieves the value of the specified property on this <see cref="T:System.Windows.Automation.AutomationElement" />. An appropriate default value for the property type is returned for properties not explicitly supported by the target [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</summary>
+        <summary>Retrieves the value of the specified property on this <see cref="T:System.Windows.Automation.AutomationElement" />. An appropriate default value for the property type is returned for properties not explicitly supported by the target user interface (UI) element.</summary>
         <returns>An object containing the value of the specified property.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1427,7 +1427,7 @@
   
  If the UI Automation provider for the element itself supports the property, the value of the property is returned. Otherwise, if `ignoreDefaultValue` is `false`, a default property specified by UI Automation is returned. For information on default properties, see the property identifier fields of <xref:System.Windows.Automation.AutomationElement>, such as <xref:System.Windows.Automation.AutomationElement.AcceleratorKeyProperty>.  
   
- The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ The value returned by the <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> method is current at the time it is called. The value can subsequently change by other applications interacting with the user interface (UI).  
   
  For some forms of UI, this method will incur cross-process performance overhead. Applications can concentrate overhead by caching properties and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPropertyValue%2A>.  
   
@@ -1487,7 +1487,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Retrieves the unique identifier assigned to the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item.</summary>
+        <summary>Retrieves the unique identifier assigned to the user interface (UI) item.</summary>
         <returns>An array of integers representing the run-time identifier.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1618,7 +1618,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The original <xref:System.Windows.Automation.AutomationElement> is unchanged. <xref:System.Windows.Automation.AutomationElement.GetUpdatedCache%2A> returns a new <xref:System.Windows.Automation.AutomationElement>, that refers to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] and has the same <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty>.  
+ The original <xref:System.Windows.Automation.AutomationElement> is unchanged. <xref:System.Windows.Automation.AutomationElement.GetUpdatedCache%2A> returns a new <xref:System.Windows.Automation.AutomationElement>, that refers to the same user interface (UI) and has the same <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty>.  
   
    
   
@@ -1886,7 +1886,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled" /> property, which specifies whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the <see cref="T:System.Windows.Automation.AutomationElement" /> is enabled.</summary>
+        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled" /> property, which specifies whether the user interface (UI) item referenced by the <see cref="T:System.Windows.Automation.AutomationElement" /> is enabled.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2195,7 +2195,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsOffscreen" /> property, which indicates whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item is visible on the screen.</summary>
+        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsOffscreen" /> property, which indicates whether the user interface (UI) item is visible on the screen.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3268,7 +3268,7 @@
       <Docs>
         <param name="left">The first <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
         <param name="right">The second <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
-        <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element.</summary>
+        <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same user interface (UI) element.</summary>
         <returns>
           <see langword="true" /> if the two <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to the same UI element; otherwise <see langword="false" />.</returns>
         <remarks>
@@ -3308,7 +3308,7 @@
       <Docs>
         <param name="left">The first <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
         <param name="right">The second <see cref="T:System.Windows.Automation.AutomationElement" /> to compare.</param>
-        <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to different [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements.</summary>
+        <summary>Returns a value indicating whether the specified <see cref="T:System.Windows.Automation.AutomationElement" /> objects refer to different user interface (UI) elements.</summary>
         <returns>
           <see langword="true" /> if the two objects refer to different UI elements; otherwise <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
@@ -3793,7 +3793,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For some forms of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], this method will incur cross-process performance overhead. Applications can concentrate overhead by caching patterns and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPattern%2A>.  
+ For some forms of user interface (UI), this method will incur cross-process performance overhead. Applications can concentrate overhead by caching patterns and then retrieving them by using <xref:System.Windows.Automation.AutomationElement.GetCachedPattern%2A>.  
   
    
   
diff --git a/xml/System.Windows.Automation/AutomationElementIdentifiers.xml b/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
index 8e5bae35b88..603074399c4 100644
--- a/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
+++ b/xml/System.Windows.Automation/AutomationElementIdentifiers.xml
@@ -580,7 +580,7 @@
         <ReturnType>System.Windows.Automation.AutomationProperty</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled" /> property, which specifies whether the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] item referenced by the <see cref="T:System.Windows.Automation.AutomationElement" /> is enabled.</summary>
+        <summary>Identifies the <see cref="P:System.Windows.Automation.AutomationElement.AutomationElementInformation.IsEnabled" /> property, which specifies whether the user interface (UI) item referenced by the <see cref="T:System.Windows.Automation.AutomationElement" /> is enabled.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElementMode.xml b/xml/System.Windows.Automation/AutomationElementMode.xml
index f204133c114..31070367d36 100644
--- a/xml/System.Windows.Automation/AutomationElementMode.xml
+++ b/xml/System.Windows.Automation/AutomationElementMode.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Full is the default, and specifies that returned elements contain a full reference to the underlying [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. None specifies that the returned elements have no reference to the underlying UI, and contain only cached information.  
+ Full is the default, and specifies that returned elements contain a full reference to the underlying user interface (UI). None specifies that the returned elements have no reference to the underlying UI, and contain only cached information.  
   
  Certain operations on elements, such as <xref:System.Windows.Automation.AutomationElement.GetCurrentPropertyValue%2A> or <xref:System.Windows.Automation.AutomationElement.SetFocus%2A>, require a full reference; attempting to perform these on an element that has none results in an <xref:System.InvalidOperationException>.  
   
diff --git a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
index 93d8b24a44b..207fdc8cb4c 100644
--- a/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
+++ b/xml/System.Windows.Automation/AutomationFocusChangedEventArgs.xml
@@ -119,7 +119,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets the identifier (ID) of the Microsoft Active Accessibility object that generated the event.</summary>
-        <value>The ID of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] element that is receiving focus. For possible values, see <see href="/windows/win32/winauto/object-identifiers">Object Identifiers</see>.</value>
+        <value>The ID of the user interface (UI) element that is receiving focus. For possible values, see <see href="/windows/win32/winauto/object-identifiers">Object Identifiers</see>.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/CacheRequest.xml b/xml/System.Windows.Automation/CacheRequest.xml
index 021478fb437..26093ca77a2 100644
--- a/xml/System.Windows.Automation/CacheRequest.xml
+++ b/xml/System.Windows.Automation/CacheRequest.xml
@@ -257,9 +257,9 @@
         <ReturnType>System.Windows.Automation.AutomationElementMode</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies whether returned elements should contain full references to the underlying [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], or only cached information.</summary>
+        <summary>Gets or sets a value that specifies whether returned elements should contain full references to the underlying user interface (UI), or only cached information.</summary>
         <value>
-          <see cref="F:System.Windows.Automation.AutomationElementMode.Full" /> if the returned elements have a full reference to the underlying [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]; otherwise <see cref="F:System.Windows.Automation.AutomationElementMode.None" />.</value>
+          <see cref="F:System.Windows.Automation.AutomationElementMode.Full" /> if the returned elements have a full reference to the underlying user interface (UI); otherwise <see cref="F:System.Windows.Automation.AutomationElementMode.None" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/TreeWalker.xml b/xml/System.Windows.Automation/TreeWalker.xml
index cdc890bb551..3228207975c 100644
--- a/xml/System.Windows.Automation/TreeWalker.xml
+++ b/xml/System.Windows.Automation/TreeWalker.xml
@@ -205,7 +205,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -241,7 +241,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
   
    
   
@@ -290,7 +290,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the first child element will be returned as the first child on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -312,7 +312,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -348,7 +348,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -389,7 +389,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional child elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the last child element will be returned as the last child on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -411,7 +411,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -447,7 +447,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
   
    
   
@@ -496,7 +496,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the next sibling element will be returned as the next sibling on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -516,7 +516,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the parent element will be returned as the parent on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the parent element will be returned as the parent on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -592,7 +592,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the parent element will be returned as the parent on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the parent element will be returned as the parent on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -614,7 +614,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -650,7 +650,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  An <xref:System.Windows.Automation.AutomationElement> can have additional sibling elements that do not match the current view condition and thus are not returned when navigating the element tree.  
   
- The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
+ The structure of the <xref:System.Windows.Automation.AutomationElement> tree changes as the visible user interface (UI) elements on the desktop change. It is not guaranteed that an element returned as the previous sibling element will be returned as the previous sibling on subsequent passes.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls.Primitives/ItemsChangedEventArgs.xml b/xml/System.Windows.Controls.Primitives/ItemsChangedEventArgs.xml
index e3f9b4b990b..f75d25b7cf6 100644
--- a/xml/System.Windows.Controls.Primitives/ItemsChangedEventArgs.xml
+++ b/xml/System.Windows.Controls.Primitives/ItemsChangedEventArgs.xml
@@ -109,7 +109,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the number of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements involved in the change.</summary>
+        <summary>Gets the number of user interface (UI) elements involved in the change.</summary>
         <value>Integer that represents the number of UI elements involved in the change.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls.Primitives/ToggleButton.xml b/xml/System.Windows.Controls.Primitives/ToggleButton.xml
index 42932aa3761..4f05f393980 100644
--- a/xml/System.Windows.Controls.Primitives/ToggleButton.xml
+++ b/xml/System.Windows.Controls.Primitives/ToggleButton.xml
@@ -258,7 +258,7 @@
 |Unchecked|`false`|  
 |Indeterminate|`null`|  
   
- If <xref:System.Windows.Controls.Primitives.ToggleButton.IsThreeState%2A> is false, you can still programmatically set this property to `null` to put the <xref:System.Windows.Controls.CheckBox> in an indeterminate state, but the user cannot set the <xref:System.Windows.Controls.CheckBox> to the indeterminate state through the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ If <xref:System.Windows.Controls.Primitives.ToggleButton.IsThreeState%2A> is false, you can still programmatically set this property to `null` to put the <xref:System.Windows.Controls.CheckBox> in an indeterminate state, but the user cannot set the <xref:System.Windows.Controls.CheckBox> to the indeterminate state through the user interface (UI).  
   
 ## RadioButton  
  If you set this property to `null` on a <xref:System.Windows.Controls.RadioButton>, the <xref:System.Windows.Controls.RadioButton> is unchecked.  
diff --git a/xml/System.Windows.Controls/AccessText.xml b/xml/System.Windows.Controls/AccessText.xml
index 30464115c32..0a13da06856 100644
--- a/xml/System.Windows.Controls/AccessText.xml
+++ b/xml/System.Windows.Controls/AccessText.xml
@@ -1184,7 +1184,7 @@
   
  This property is not typically set, either by using markup or code.  
   
- This property exposes the default decoration for an access key (an underline in the same text color as the text) for possible styling or programmatic change. Because users expect access key identifiers to have a certain appearance in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], a better choice is to change this property by using application-wide mechanisms, such as application styles or custom themes.  
+ This property exposes the default decoration for an access key (an underline in the same text color as the text) for possible styling or programmatic change. Because users expect access key identifiers to have a certain appearance in the user interface (UI), a better choice is to change this property by using application-wide mechanisms, such as application styles or custom themes.  
   
 <a name="xamlPropertyElementUsage_TextDecorations"></a>   
 ## XAML Property Element Usage  
@@ -1265,7 +1265,7 @@
   
  This property exposes the default effects for an access key for possible styling or programmatic change.  
   
- Because users expect access key identifiers to have a certain appearance in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], a better choice is to change this property by using application-wide mechanisms, such as application styles or custom themes.  
+ Because users expect access key identifiers to have a certain appearance in the user interface (UI), a better choice is to change this property by using application-wide mechanisms, such as application styles or custom themes.  
   
 <a name="xamlPropertyElementUsage_TextEffects"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
index 2654976a774..84280a2c62c 100644
--- a/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentPageViewer.xml
@@ -32,7 +32,7 @@
   
  <xref:System.Windows.Controls.FlowDocumentPageViewer> shows content in page-at-a-time viewing mode. A similar control, <xref:System.Windows.Controls.FlowDocumentScrollViewer>, shows content in continuous scrolling mode. Both <xref:System.Windows.Controls.FlowDocumentPageViewer> and <xref:System.Windows.Controls.FlowDocumentScrollViewer> are fixed to a particular viewing mode. On the other hand, <xref:System.Windows.Controls.FlowDocumentReader> includes features that enable the user to dynamically choose between various viewing modes (as provided by the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> enumeration), at the cost of being poorer performing than <xref:System.Windows.Controls.FlowDocumentPageViewer> or <xref:System.Windows.Controls.FlowDocumentScrollViewer>.  
   
- The following illustration shows a <xref:System.Windows.Controls.FlowDocumentPageViewer> control with its default [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ The following illustration shows a <xref:System.Windows.Controls.FlowDocumentPageViewer> control with its default user interface (UI).  
   
  ![Screenshot: FlowDocumentPageViewer](~/add/media/flowdocpageviewer-main.png "Screenshot: FlowDocumentPageViewer")  
   
@@ -297,7 +297,7 @@
 ## Remarks  
  This method decreases the current <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level by the value specified by the <xref:System.Windows.Controls.FlowDocumentPageViewer.ZoomIncrement%2A> property.  
   
- Default <xref:System.Windows.Controls.FlowDocumentPageViewer>[!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a button to decrease the zoom.  
+ Default <xref:System.Windows.Controls.FlowDocumentPageViewer>user interface (UI) includes a button to decrease the zoom.  
   
  Calling this method has no effect if the <xref:System.Windows.Controls.FlowDocumentPageViewer.CanDecreaseZoom%2A> property returns `false`.  
   
@@ -392,7 +392,7 @@
 ## Remarks  
  This method increases the current <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level by the value specified by the <xref:System.Windows.Controls.FlowDocumentPageViewer.ZoomIncrement%2A> property.  
   
- Default <xref:System.Windows.Controls.FlowDocumentPageViewer>[!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a button to increase the zoom.  
+ Default <xref:System.Windows.Controls.FlowDocumentPageViewer>user interface (UI) includes a button to increase the zoom.  
   
  Calling this method has no effect if the <xref:System.Windows.Controls.FlowDocumentPageViewer.CanIncreaseZoom%2A> property returns `false`.  
   
@@ -548,7 +548,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentPageViewer> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level. This property specifies the upper-limit value for the slider.  
+ The default <xref:System.Windows.Controls.FlowDocumentPageViewer> user interface (UI) includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level. This property specifies the upper-limit value for the slider.  
   
 <a name="dependencyPropertyInfo_MaxZoom"></a>   
 ## Dependency Property Information  
@@ -624,7 +624,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentPageViewer> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level. This property specifies the lower-limit value for the slider.  
+ The default <xref:System.Windows.Controls.FlowDocumentPageViewer> user interface (UI) includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentPageViewer.Zoom%2A> level. This property specifies the lower-limit value for the slider.  
   
 <a name="dependencyPropertyInfo_MinZoom"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Controls/FlowDocumentReader.xml b/xml/System.Windows.Controls/FlowDocumentReader.xml
index 44444087dc1..c7ac5a1aae4 100644
--- a/xml/System.Windows.Controls/FlowDocumentReader.xml
+++ b/xml/System.Windows.Controls/FlowDocumentReader.xml
@@ -42,7 +42,7 @@
 ## Remarks  
  <xref:System.Windows.Controls.FlowDocumentReader> includes features that enable the user to dynamically choose between various viewing modes, including a single-page (page-at-a-time) viewing mode, a two-page-at-a-time (book reading format) viewing mode, and a continuous scrolling (bottomless) viewing mode.  If you do not need the ability to dynamically switch between different viewing modes, there are lighter-weight flow content viewers that are fixed in a particular viewing mode.  <xref:System.Windows.Controls.FlowDocumentPageViewer> displays flow content in single-page viewing mode, and <xref:System.Windows.Controls.FlowDocumentScrollViewer> displays flow content in continuous-scrolling mode.  For more information about available display modes, see <xref:System.Windows.Controls.FlowDocumentReaderViewingMode>.  
   
- The following figure shows a <xref:System.Windows.Controls.FlowDocumentReader> control with its default [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ The following figure shows a <xref:System.Windows.Controls.FlowDocumentReader> control with its default user interface (UI).  
   
  ![Screenshot with callouts: FlowDocumentReader](~/add/media/flowdocrdr-main.png "Screenshot with callouts: FlowDocumentReader")  
   
@@ -454,7 +454,7 @@
 ## Remarks  
  The <xref:System.Windows.Controls.FlowDocumentReader.DecreaseZoom%2A> method decreases the current <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level by the value specified by the <xref:System.Windows.Controls.FlowDocumentReader.ZoomIncrement%2A> property.  
   
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a button to decrease the zoom.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a button to decrease the zoom.  
   
  Calling this method has no effect if the <xref:System.Windows.Controls.FlowDocumentReader.CanDecreaseZoom%2A> property is `false`.  
   
@@ -555,7 +555,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a **Find** button that toggles the Find dialog.  The following figure shows the Find dialog on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a **Find** button that toggles the Find dialog.  The following figure shows the Find dialog on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
   
  ![Screenshot with callouts: FlowDocumentReader](~/add/media/flowdocrdr-find.png "Screenshot with callouts: FlowDocumentReader")  
   
@@ -609,7 +609,7 @@
 ## Remarks  
  The <xref:System.Windows.Controls.FlowDocumentReader.IncreaseZoom%2A> method increases the current <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level by the value specified by the <xref:System.Windows.Controls.FlowDocumentReader.ZoomIncrement%2A> property.  
   
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a button to increase the zoom.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a button to increase the zoom.  
   
  Calling this method has no effect if the <xref:System.Windows.Controls.FlowDocumentReader.CanIncreaseZoom%2A> property is `false`.  
   
@@ -646,7 +646,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a **Find** button that toggles the Find dialog.  The following figure shows the Find dialog on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a **Find** button that toggles the Find dialog.  The following figure shows the Find dialog on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
   
  ![Screenshot with callouts: FlowDocumentReader](~/add/media/flowdocrdr-find.png "Screenshot with callouts: FlowDocumentReader")  
   
@@ -1135,7 +1135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level.  This property specifies the upper-limit value for the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> slider.  
+ The default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level.  This property specifies the upper-limit value for the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> slider.  
   
 <a name="dependencyPropertyInfo_MaxZoom"></a>   
 ## Dependency Property Information  
@@ -1213,7 +1213,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level.  This property specifies the lower-limit value for the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> slider.  
+ The default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a slider that can be used to adjust the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level.  This property specifies the lower-limit value for the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> slider.  
   
 <a name="dependencyPropertyInfo_MinZoom"></a>   
 ## Dependency Property Information  
@@ -1843,7 +1843,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] does not provide a **Print** button.  
+ The default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) does not provide a **Print** button.  
   
  The following figure shows an example of a standard Print dialog.  Note that the specific appearance of the Print dialog may vary depending on the hosting computer's configuration.  
   
@@ -2210,7 +2210,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes buttons for selecting the viewing mode.  The following figure shows the viewing mode selection buttons on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes buttons for selecting the viewing mode.  The following figure shows the viewing mode selection buttons on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
   
  ![Screenshot: FlowDocumentReader ViewMode](~/add/media/flowdocrdr-viewmode.png "Screenshot: FlowDocumentReader ViewMode")  
   
@@ -2277,7 +2277,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a zoom control that provides buttons for increasing or decreasing the zoom, as well as a slider for adjusting the zoom level.  The following figure shows the zoom controls on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a zoom control that provides buttons for increasing or decreasing the zoom, as well as a slider for adjusting the zoom level.  The following figure shows the zoom controls on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
   
  ![FlowDocumentReader content zoom](~/add/media/flowdocrdr-zoom.png "FlowDocumentReader content zoom")  
   
@@ -2337,7 +2337,7 @@
 ## Remarks  
  The zoom increment is the percentage by which the <xref:System.Windows.Controls.FlowDocumentReader.Zoom%2A> level is increased or decreased when the <xref:System.Windows.Input.NavigationCommands.IncreaseZoom%2A> or <xref:System.Windows.Input.NavigationCommands.DecreaseZoom%2A> commands are executed, respectively.  
   
- Default <xref:System.Windows.Controls.FlowDocumentReader> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] includes a zoom control that provides buttons for increasing or decreasing the zoom, as well as a slider for adjusting the zoom level.  The following figure shows the zoom controls on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
+ Default <xref:System.Windows.Controls.FlowDocumentReader> user interface (UI) includes a zoom control that provides buttons for increasing or decreasing the zoom, as well as a slider for adjusting the zoom level.  The following figure shows the zoom controls on a <xref:System.Windows.Controls.FlowDocumentReader> with default UI.  
   
  ![FlowDocumentReader content zoom](~/add/media/flowdocrdr-zoom.png "FlowDocumentReader content zoom")  
   
diff --git a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
index 212aaec05e9..4d51674e7d6 100644
--- a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
@@ -50,7 +50,7 @@
 ## Remarks  
  <xref:System.Windows.Controls.FlowDocumentScrollViewer> shows content in continuous scrolling mode.  A similar control, <xref:System.Windows.Controls.FlowDocumentPageViewer>, shows content in page-at-a-time viewing mode.  Both <xref:System.Windows.Controls.FlowDocumentPageViewer> and <xref:System.Windows.Controls.FlowDocumentScrollViewer> are fixed to a particular viewing mode.  On the other hand, <xref:System.Windows.Controls.FlowDocumentReader> includes features that enable the user to dynamically choose between various viewing modes (as provided by the <xref:System.Windows.Controls.FlowDocumentReaderViewingMode> enumeration), at the cost of being heavier weight than <xref:System.Windows.Controls.FlowDocumentPageViewer> or <xref:System.Windows.Controls.FlowDocumentScrollViewer>.  
   
- The following figure shows a <xref:System.Windows.Controls.FlowDocumentScrollViewer> control with its default [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ The following figure shows a <xref:System.Windows.Controls.FlowDocumentScrollViewer> control with its default user interface (UI).  
   
  ![Screenshot: Basic FlowDocumentScrollViewer](~/add/media/flowdocscrollviewer-main.png "Screenshot: Basic FlowDocumentScrollViewer")  
   
@@ -1336,7 +1336,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default <xref:System.Windows.Controls.FlowDocumentScrollViewer> [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] does not provide a **Print** button.  
+ The default <xref:System.Windows.Controls.FlowDocumentScrollViewer> user interface (UI) does not provide a **Print** button.  
   
  The following figure shows an example of a standard **Print** dialog.  Note that the specific appearance of the **Print** dialog may vary depending on the hosting computer's configuration.  
   
diff --git a/xml/System.Windows.Controls/ItemsControl.xml b/xml/System.Windows.Controls/ItemsControl.xml
index cc34bc08fde..2a91790341d 100644
--- a/xml/System.Windows.Controls/ItemsControl.xml
+++ b/xml/System.Windows.Controls/ItemsControl.xml
@@ -1260,7 +1260,7 @@ ListBox that contains multiple types of objects
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An <xref:System.Windows.Controls.ItemsControl.ItemContainerGenerator%2A> is responsible for generating the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] for its host, such as an <xref:System.Windows.Controls.ItemsControl>. It maintains the association between the items in the data view of the control and the corresponding <xref:System.Windows.UIElement> objects. Every <xref:System.Windows.Controls.ItemsControl> has an associated item container that contains a data item in the item collection. You can use the <xref:System.Windows.Controls.ItemsControl.ItemContainerGenerator%2A> property to access the item container that is associated with your <xref:System.Windows.Controls.ItemsControl>. For example, if you have a data-bound <xref:System.Windows.Controls.TreeView> control and you want to get a <xref:System.Windows.Controls.TreeViewItem> based on its index or its associated data item, you can use the <xref:System.Windows.Controls.ItemContainerGenerator.ContainerFromIndex%2A?displayProperty=nameWithType> or the <xref:System.Windows.Controls.ItemContainerGenerator.ContainerFromItem%2A?displayProperty=nameWithType> method. Alternatively, you can use the <xref:System.Windows.Controls.ItemContainerGenerator.IndexFromContainer%2A?displayProperty=nameWithType> or the <xref:System.Windows.Controls.ItemContainerGenerator.ItemFromContainer%2A?displayProperty=nameWithType> method to get the index or data item that is associated with a given generated container element.  
+ An <xref:System.Windows.Controls.ItemsControl.ItemContainerGenerator%2A> is responsible for generating the user interface (UI) for its host, such as an <xref:System.Windows.Controls.ItemsControl>. It maintains the association between the items in the data view of the control and the corresponding <xref:System.Windows.UIElement> objects. Every <xref:System.Windows.Controls.ItemsControl> has an associated item container that contains a data item in the item collection. You can use the <xref:System.Windows.Controls.ItemsControl.ItemContainerGenerator%2A> property to access the item container that is associated with your <xref:System.Windows.Controls.ItemsControl>. For example, if you have a data-bound <xref:System.Windows.Controls.TreeView> control and you want to get a <xref:System.Windows.Controls.TreeViewItem> based on its index or its associated data item, you can use the <xref:System.Windows.Controls.ItemContainerGenerator.ContainerFromIndex%2A?displayProperty=nameWithType> or the <xref:System.Windows.Controls.ItemContainerGenerator.ContainerFromItem%2A?displayProperty=nameWithType> method. Alternatively, you can use the <xref:System.Windows.Controls.ItemContainerGenerator.IndexFromContainer%2A?displayProperty=nameWithType> or the <xref:System.Windows.Controls.ItemContainerGenerator.ItemFromContainer%2A?displayProperty=nameWithType> method to get the index or data item that is associated with a given generated container element.  
   
  The <xref:System.Windows.Controls.Primitives.IItemContainerGenerator> interface is also used in advanced scenarios. Typically, advanced applications that have their own implementation of a virtualizing panel call members of the interface.  
   
diff --git a/xml/System.Windows.Controls/Panel.xml b/xml/System.Windows.Controls/Panel.xml
index 0bbee2c1694..37708e0025f 100644
--- a/xml/System.Windows.Controls/Panel.xml
+++ b/xml/System.Windows.Controls/Panel.xml
@@ -415,7 +415,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates that this <see cref="T:System.Windows.Controls.Panel" /> is a container for [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] items that are generated by an <see cref="T:System.Windows.Controls.ItemsControl" />.</summary>
+        <summary>Gets or sets a value that indicates that this <see cref="T:System.Windows.Controls.Panel" /> is a container for user interface (UI) items that are generated by an <see cref="T:System.Windows.Controls.ItemsControl" />.</summary>
         <value>
           <see langword="true" /> if this instance of <see cref="T:System.Windows.Controls.Panel" /> is an items host; otherwise, <see langword="false" />. The default value is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Controls/PrintDialog.xml b/xml/System.Windows.Controls/PrintDialog.xml
index 50b2b0ad626..bfc59c57865 100644
--- a/xml/System.Windows.Controls/PrintDialog.xml
+++ b/xml/System.Windows.Controls/PrintDialog.xml
@@ -345,7 +345,7 @@
       </Parameters>
       <Docs>
         <param name="documentPaginator">The <see cref="T:System.Windows.Documents.DocumentPaginator" /> object to print.</param>
-        <param name="description">A description of the job that is to be printed. This text appears in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of the printer.</param>
+        <param name="description">A description of the job that is to be printed. This text appears in the user interface (UI) of the printer.</param>
         <summary>Prints a <see cref="T:System.Windows.Documents.DocumentPaginator" /> object to the <see cref="T:System.Printing.PrintQueue" /> that is currently selected.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
@@ -456,7 +456,7 @@
       </Parameters>
       <Docs>
         <param name="visual">The <see cref="T:System.Windows.Media.Visual" /> to print.</param>
-        <param name="description">A description of the job that is to be printed. This text appears in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of the printer.</param>
+        <param name="description">A description of the job that is to be printed. This text appears in the user interface (UI) of the printer.</param>
         <summary>Prints a visual (non-text) object, which is derived from the <see cref="T:System.Windows.Media.Visual" /> class, to the <see cref="T:System.Printing.PrintQueue" /> that is currently selected.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
diff --git a/xml/System.Windows.Controls/StickyNoteControl.xml b/xml/System.Windows.Controls/StickyNoteControl.xml
index 8667d226649..0986a72ee69 100644
--- a/xml/System.Windows.Controls/StickyNoteControl.xml
+++ b/xml/System.Windows.Controls/StickyNoteControl.xml
@@ -74,7 +74,7 @@
   
 -   **Ink** sticky notes have an <xref:System.Windows.Controls.InkCanvas> content area and it can be edited like other ink canvasses. For example, strokes can be erased. With a tablet PC or other suitable hardware, users can enter handwritten notes.  
   
- The [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of the <xref:System.Windows.Controls.StickyNoteControl> makes it a more powerful way to annotate material than marking up a hardcopy or using physical handwritten notes.  It is also more flexible than simply adding to, or striking through, the text of a document.  
+ The user interface (UI) of the <xref:System.Windows.Controls.StickyNoteControl> makes it a more powerful way to annotate material than marking up a hardcopy or using physical handwritten notes.  It is also more flexible than simply adding to, or striking through, the text of a document.  
   
 -   Sticky notes can be resized.  
   
diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index d4799fd2319..b57c68944ee 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -45,7 +45,7 @@
 ## Remarks  
  A <xref:System.Windows.Controls.TextBlock> can contain a string in its <xref:System.Windows.Controls.TextBlock.Text%2A> property or <xref:System.Windows.Documents.Inline> flow content elements, such as <xref:System.Windows.Documents.Bold>, <xref:System.Windows.Documents.Hyperlink>, and <xref:System.Windows.Documents.InlineUIContainer>, in its <xref:System.Windows.Controls.TextBlock.Inlines%2A> property.  
   
- <xref:System.Windows.Controls.TextBlock> is designed to be lightweight, and is geared specifically at integrating small portions of flow content into a [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  <xref:System.Windows.Controls.TextBlock> is optimized for single-line display, and provides good performance for displaying up to a few lines of content.  
+ <xref:System.Windows.Controls.TextBlock> is designed to be lightweight, and is geared specifically at integrating small portions of flow content into a user interface (UI).  <xref:System.Windows.Controls.TextBlock> is optimized for single-line display, and provides good performance for displaying up to a few lines of content.  
   
  <xref:System.Windows.Controls.TextBlock> is not optimized for scenarios that need to display more than a few lines of content; for such scenarios, a <xref:System.Windows.Documents.FlowDocument> coupled with an appropriate viewing control is a better choice than <xref:System.Windows.Controls.TextBlock>, in terms of performance.  After <xref:System.Windows.Controls.TextBlock>, <xref:System.Windows.Controls.FlowDocumentScrollViewer> is the next lightest-weight control for displaying flow content, and simply provides a scrolling content area with minimal UI.  <xref:System.Windows.Controls.FlowDocumentPageViewer> is optimized around "page-at-a-time" viewing mode for flow content.  Finally, <xref:System.Windows.Controls.FlowDocumentReader> supports the richest set functionality for viewing flow content, but is correspondingly heavier-weight.  
   
diff --git a/xml/System.Windows.Controls/Validation.xml b/xml/System.Windows.Controls/Validation.xml
index 3489363560c..ffc7e7950f0 100644
--- a/xml/System.Windows.Controls/Validation.xml
+++ b/xml/System.Windows.Controls/Validation.xml
@@ -256,7 +256,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The WPF data binding model allows you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. If the user enters an invalid value, you may want to provide some feedback about the error on the application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. One way to provide such feedback is to set the <xref:System.Windows.Controls.Validation>.<xref:System.Windows.Controls.Validation.ErrorTemplate%2A> attached property to a custom <xref:System.Windows.Controls.ControlTemplate>.  
+ The WPF data binding model allows you to associate <xref:System.Windows.Data.Binding.ValidationRules%2A> with your <xref:System.Windows.Data.Binding> object. If the user enters an invalid value, you may want to provide some feedback about the error on the application user interface (UI). One way to provide such feedback is to set the <xref:System.Windows.Controls.Validation>.<xref:System.Windows.Controls.Validation.ErrorTemplate%2A> attached property to a custom <xref:System.Windows.Controls.ControlTemplate>.  
   
  For a detailed discussion of validation, see the Data Validation section of the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Controls/VirtualizationCacheLength.xml b/xml/System.Windows.Controls/VirtualizationCacheLength.xml
index 1a3f360dd85..dfd1687ec98 100644
--- a/xml/System.Windows.Controls/VirtualizationCacheLength.xml
+++ b/xml/System.Windows.Controls/VirtualizationCacheLength.xml
@@ -114,7 +114,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
+ In this context, "virtualize" refers to a technique by which a subset of user interface (UI) elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
   
  ]]></format>
         </remarks>
@@ -143,7 +143,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
+ In this context, "virtualize" refers to a technique by which a subset of user interface (UI) elements are generated from a larger number of data items based on which items are visible on the screen. Use a cache to avoid generating UI elements as they're scrolled into view.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/VirtualizingPanel.xml b/xml/System.Windows.Controls/VirtualizingPanel.xml
index 40e235539d9..0b0ee351edd 100644
--- a/xml/System.Windows.Controls/VirtualizingPanel.xml
+++ b/xml/System.Windows.Controls/VirtualizingPanel.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. It is intensive, both in terms of memory and processor, to generate a large number of UI elements when only a few may be on the screen at a given time. A panel that inherits from <xref:System.Windows.Controls.VirtualizingPanel>, such as the <xref:System.Windows.Controls.VirtualizingStackPanel>, calculates visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to only create UI elements for visible items.  
+ In this context, "virtualize" refers to a technique by which a subset of user interface (UI) elements are generated from a larger number of data items based on which items are visible on the screen. It is intensive, both in terms of memory and processor, to generate a large number of UI elements when only a few may be on the screen at a given time. A panel that inherits from <xref:System.Windows.Controls.VirtualizingPanel>, such as the <xref:System.Windows.Controls.VirtualizingStackPanel>, calculates visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to only create UI elements for visible items.  
   
  The following lists describes cases when the <xref:System.Windows.Controls.VirtualizingPanel> cannot virtualize item containers:  
   
@@ -744,7 +744,7 @@ The following example shows how to bind to an XML data source and virtualize the
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. In this context, "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on the screen. It is intensive, both in terms of memory and processor, to generate a large number of UI elements when only a few may be on the screen at a given time.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. In this context, "virtualize" refers to a technique by which a subset of user interface (UI) elements are generated from a larger number of data items based on which items are visible on the screen. It is intensive, both in terms of memory and processor, to generate a large number of UI elements when only a few may be on the screen at a given time.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/VirtualizingStackPanel.xml b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
index 9057f316d18..191621a4ada 100644
--- a/xml/System.Windows.Controls/VirtualizingStackPanel.xml
+++ b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
+ The standard layout system creates item containers and computes layout for each item associated with a list control. The word "virtualize" refers to a technique by which a subset of user interface (UI) elements are generated from a larger number of data items based on which items are visible on-screen. Generating many UI elements when only a few elements might be on the screen can adversely affect the performance of your application. The <xref:System.Windows.Controls.VirtualizingStackPanel> calculates the number of visible items and works with the <xref:System.Windows.Controls.ItemContainerGenerator> from an <xref:System.Windows.Controls.ItemsControl> (such as <xref:System.Windows.Controls.ListBox> or <xref:System.Windows.Controls.ListView>) to create UI elements only for visible items.  
   
  Virtualization in a <xref:System.Windows.Controls.StackPanel> only occurs when the items control contained in the panel creates its own item containers. You can ensure this happens by using data binding. In scenarios where item containers are created and added to the items control, a <xref:System.Windows.Controls.VirtualizingStackPanel> offers no performance advantage over a <xref:System.Windows.Controls.StackPanel>.  
   
diff --git a/xml/System.Windows.Data/BindingGroup.xml b/xml/System.Windows.Data/BindingGroup.xml
index 3d4f5cbf9df..5d4b1a95f45 100644
--- a/xml/System.Windows.Data/BindingGroup.xml
+++ b/xml/System.Windows.Data/BindingGroup.xml
@@ -42,13 +42,13 @@
   
  The application does the following to achieve this behavior.  
   
--   Creates a <xref:System.Windows.Data.BindingGroup> and adds it the root <xref:System.Windows.Controls.StackPanel> when it creates the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of the application.  
+-   Creates a <xref:System.Windows.Data.BindingGroup> and adds it the root <xref:System.Windows.Controls.StackPanel> when it creates the user interface (UI) of the application.  
   
 -   Calls <xref:System.Windows.Data.BindingGroup.BeginEdit%2A>, <xref:System.Windows.Data.BindingGroup.CommitEdit%2A>, and <xref:System.Windows.Data.BindingGroup.CancelEdit%2A> in the application's logic to enable rolling back changes.  
   
 -   Calls <xref:System.Windows.Data.BindingGroup.TryGetValue%2A> in a <xref:System.Windows.Controls.ValidationRule.Validate%2A> method to get the user's input and then check that an item over 100 dollars is available for at least seven days.  
   
- The following example creates the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of the application. The root <xref:System.Windows.Controls.StackPanel> has a <xref:System.Windows.Data.BindingGroup> that contains a <xref:System.Windows.Controls.ValidationRule> that validates the item, as described previously. The binding objects on the `Price` property and the `OfferExpires` property become part of the <xref:System.Windows.Data.BindingGroup> and each binding has a <xref:System.Windows.Controls.ValidationRule> to make sure that price and date, respectively, are valid values. The validation rules for the individual properties run before the <xref:System.Windows.Controls.ValidationRule> on the <xref:System.Windows.Data.BindingGroup>.  
+ The following example creates the user interface (UI) of the application. The root <xref:System.Windows.Controls.StackPanel> has a <xref:System.Windows.Data.BindingGroup> that contains a <xref:System.Windows.Controls.ValidationRule> that validates the item, as described previously. The binding objects on the `Price` property and the `OfferExpires` property become part of the <xref:System.Windows.Data.BindingGroup> and each binding has a <xref:System.Windows.Controls.ValidationRule> to make sure that price and date, respectively, are valid values. The validation rules for the individual properties run before the <xref:System.Windows.Controls.ValidationRule> on the <xref:System.Windows.Data.BindingGroup>.  
   
  [!code-xaml[BindingGroupSnippets#WindowLayout](~/samples/snippets/csharp/VS_Snippets_Wpf/BindingGroupSnippets/CSharp/Window1.xaml#windowlayout)]  
   
diff --git a/xml/System.Windows.Data/CollectionView.xml b/xml/System.Windows.Data/CollectionView.xml
index 05b2d51acd5..f55cde0c2d9 100644
--- a/xml/System.Windows.Data/CollectionView.xml
+++ b/xml/System.Windows.Data/CollectionView.xml
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The instance of <xref:System.Windows.Data.CollectionView> is bound to the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread dispatcher of the caller of this constructor.  
+ The instance of <xref:System.Windows.Data.CollectionView> is bound to the user interface (UI) thread dispatcher of the caller of this constructor.  
   
  ]]></format>
         </remarks>
@@ -2064,9 +2064,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether it has been necessary to update the change log because a <see cref="E:System.Windows.Data.CollectionView.CollectionChanged" /> notification has been received on a different thread without first entering the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread dispatcher.</summary>
+        <summary>Gets a value that indicates whether it has been necessary to update the change log because a <see cref="E:System.Windows.Data.CollectionView.CollectionChanged" /> notification has been received on a different thread without first entering the user interface (UI) thread dispatcher.</summary>
         <value>
-          <see langword="true" /> if it has been necessary to update the change log because a <see cref="E:System.Windows.Data.CollectionView.CollectionChanged" /> notification has been received on a different thread without first entering the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread dispatcher; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if it has been necessary to update the change log because a <see cref="E:System.Windows.Data.CollectionView.CollectionChanged" /> notification has been received on a different thread without first entering the user interface (UI) thread dispatcher; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Data.CollectionView.OnBeginChangeLogging(System.Collections.Specialized.NotifyCollectionChangedEventArgs)" />
       </Docs>
diff --git a/xml/System.Windows.Input/InputMethod.xml b/xml/System.Windows.Input/InputMethod.xml
index 966743251bd..4c004f8635f 100644
--- a/xml/System.Windows.Input/InputMethod.xml
+++ b/xml/System.Windows.Input/InputMethod.xml
@@ -59,7 +59,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether or not this input method can display configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets a value that indicates whether or not this input method can display configuration user interface (UI).</summary>
         <value>
           <see langword="true" /> if configuration UI can be displayed; otherwise, <see langword="false" />.  
   
@@ -103,7 +103,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether this input method can display word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets a value that indicates whether this input method can display word registration user interface (UI).</summary>
         <value>
           <see langword="true" /> if word registration UI can be displayed; otherwise, <see langword="false" />.  
   
@@ -1081,7 +1081,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Displays configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.</summary>
+        <summary>Displays configuration user interface (UI) associated with the currently active keyboard text service.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Input.InputMethod.CanShowConfigurationUI" />
         <altmember cref="M:System.Windows.Input.InputMethod.ShowConfigureUI(System.Windows.UIElement)" />
@@ -1110,7 +1110,7 @@
       </Parameters>
       <Docs>
         <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the configuration UI.  This parameter can be <see langword="null" />.</param>
-        <summary>Displays configuration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service, using a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
+        <summary>Displays configuration user interface (UI) associated with the currently active keyboard text service, using a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Input.InputMethod.CanShowConfigurationUI" />
         <altmember cref="M:System.Windows.Input.InputMethod.ShowConfigureUI" />
@@ -1153,7 +1153,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Displays word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.</summary>
+        <summary>Displays word registration user interface (UI) associated with the currently active keyboard text service.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Input.InputMethod.CanShowRegisterWordUI" />
         <altmember cref="M:System.Windows.Input.InputMethod.ShowRegisterWordUI(System.String)" />
@@ -1189,12 +1189,12 @@
       </Parameters>
       <Docs>
         <param name="registeredText">A string that specifies a value to register.</param>
-        <summary>Displays word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.  Accepts a specified string as the default value to register.</summary>
+        <summary>Displays word registration user interface (UI) associated with the currently active keyboard text service.  Accepts a specified string as the default value to register.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Typically the value specified by *registeredText* is used to pre-populate the word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ Typically the value specified by *registeredText* is used to pre-populate the word registration user interface (UI).  
   
  ]]></format>
         </remarks>
@@ -1228,12 +1228,12 @@
       <Docs>
         <param name="element">A <see cref="T:System.Windows.UIElement" /> that will be used as the parent element for the word registration UI.  This parameter can be <see langword="null" />.</param>
         <param name="registeredText">A string that specifies a value to register.</param>
-        <summary>Displays word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] associated with the currently active keyboard text service.  Accepts a specified string as the default value to register, and a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
+        <summary>Displays word registration user interface (UI) associated with the currently active keyboard text service.  Accepts a specified string as the default value to register, and a specified <see cref="T:System.Windows.UIElement" /> as the parent element for the configuration UI.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Typically the value specified by *registeredText* is used to pre-populate the word registration [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ Typically the value specified by *registeredText* is used to pre-populate the word registration user interface (UI).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 34d5a1302ca..9d785227153 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -1444,7 +1444,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Which mouse button was depressed is determined by checking the arguments of the event. This is an attached event (using tunneling routing strategy) that is intended through attached event syntax to be referenced by existing [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements that take input.  
+ Which mouse button was depressed is determined by checking the arguments of the event. This is an attached event (using tunneling routing strategy) that is intended through attached event syntax to be referenced by existing user interface (UI) elements that take input.  
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index 071285b28fc..cbfda359680 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -40,7 +40,7 @@
  ![Fonts](~/add/media/fonts.PNG "Fonts")  
 Example of typefaces that are members of the "Times New Roman" font family  
   
- Most [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBlock>, provide a <xref:System.Windows.Controls.Control.FontFamily%2A> property that can be used to specify a font for the text content of a control. You define the font by setting that property with a <xref:System.Windows.Media.FontFamily> value. The following examples show how to reference a font, in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and in code.  
+ Most user interface (UI) elements, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBlock>, provide a <xref:System.Windows.Controls.Control.FontFamily%2A> property that can be used to specify a font for the text content of a control. You define the font by setting that property with a <xref:System.Windows.Media.FontFamily> value. The following examples show how to reference a font, in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and in code.  
   
  [!code-csharp[FontSnippets#FontFallbackSnippet3](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontFamilySnippets.xaml.cs#fontfallbacksnippet3)]
  [!code-vb[FontSnippets#FontFallbackSnippet3](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontfamilysnippets.xaml.vb#fontfallbacksnippet3)]
diff --git a/xml/System.Windows.Media/MediaPlayer.xml b/xml/System.Windows.Media/MediaPlayer.xml
index a95f8b5a792..0e55fecf701 100644
--- a/xml/System.Windows.Media/MediaPlayer.xml
+++ b/xml/System.Windows.Media/MediaPlayer.xml
@@ -28,7 +28,7 @@
   
  <xref:System.Windows.Media.MediaPlayer> can be used in two different modes, depending on what is driving the player: independent mode or clock mode. In independent mode, the <xref:System.Windows.Media.MediaPlayer> is analogous to an image and the media opened through the <xref:System.Windows.Media.MediaPlayer.Open%2A> method drives playback. In Clock mode, the <xref:System.Windows.Media.MediaPlayer> can be thought of as a target for an animation, and thus it will have corresponding <xref:System.Windows.Media.Animation.Timeline> and <xref:System.Windows.Media.Animation.Clock> entries in the Timing tree which controls playback. For more information on media modes, see the [Multimedia Overview](/dotnet/framework/wpf/graphics-multimedia/multimedia-overview).  
   
- <xref:System.Windows.Media.MediaPlayer> is different from a <xref:System.Windows.Controls.MediaElement> in that it is not a control that can be added directly to the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] of an application. To display media loaded using <xref:System.Windows.Media.MediaPlayer>, a <xref:System.Windows.Media.VideoDrawing> or <xref:System.Windows.Media.DrawingContext> must be used.  
+ <xref:System.Windows.Media.MediaPlayer> is different from a <xref:System.Windows.Controls.MediaElement> in that it is not a control that can be added directly to the user interface (UI) of an application. To display media loaded using <xref:System.Windows.Media.MediaPlayer>, a <xref:System.Windows.Media.VideoDrawing> or <xref:System.Windows.Media.DrawingContext> must be used.  
   
    
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 539a8428b29..48bf05032a3 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -863,7 +863,7 @@
 ## Remarks  
  You handle <xref:System.Windows.Navigation.NavigationService.Navigated> if you need to discover pertinent information regarding the navigation request when downloading commences. This information is available from the <xref:System.Windows.Navigation.NavigationEventArgs> object that is passed to the <xref:System.Windows.Navigation.NavigationService.Navigated> event handler, and includes:  
   
--   The source page. When <xref:System.Windows.Navigation.NavigationService.Navigated> is raised, at least part of the source page's [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] tree has been parsed, and attached to target content control.  
+-   The source page. When <xref:System.Windows.Navigation.NavigationService.Navigated> is raised, at least part of the source page's user interface (UI) tree has been parsed, and attached to target content control.  
   
 -   The requested URI.  
   
diff --git a/xml/System.Windows.Threading/DispatcherTimer.xml b/xml/System.Windows.Threading/DispatcherTimer.xml
index 13df62c1e94..9ebba0adb07 100644
--- a/xml/System.Windows.Threading/DispatcherTimer.xml
+++ b/xml/System.Windows.Threading/DispatcherTimer.xml
@@ -25,7 +25,7 @@
   
  Timers are not guaranteed to execute exactly when the time interval occurs, but they are guaranteed to not execute before the time interval occurs.  This is because <xref:System.Windows.Threading.DispatcherTimer> operations are placed on the <xref:System.Windows.Threading.Dispatcher> queue like other operations.  When the <xref:System.Windows.Threading.DispatcherTimer> operation executes is dependent on the other jobs in the queue and their priorities.  
   
- If a <xref:System.Timers.Timer?displayProperty=nameWithType> is used in a WPF application, it is worth noting that the <xref:System.Timers.Timer?displayProperty=nameWithType> runs on a different thread than the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread.  In order to access objects on the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread, it is necessary to post the operation onto the <xref:System.Windows.Threading.Dispatcher> of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread using <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. Reasons for using a <xref:System.Windows.Threading.DispatcherTimer> as opposed to a <xref:System.Timers.Timer?displayProperty=nameWithType> are that the <xref:System.Windows.Threading.DispatcherTimer> runs on the same thread as the <xref:System.Windows.Threading.Dispatcher> and a <xref:System.Windows.Threading.DispatcherPriority> can be set on the <xref:System.Windows.Threading.DispatcherTimer>.  
+ If a <xref:System.Timers.Timer?displayProperty=nameWithType> is used in a WPF application, it is worth noting that the <xref:System.Timers.Timer?displayProperty=nameWithType> runs on a different thread than the user interface (UI) thread.  In order to access objects on the user interface (UI) thread, it is necessary to post the operation onto the <xref:System.Windows.Threading.Dispatcher> of the user interface (UI) thread using <xref:System.Windows.Threading.Dispatcher.Invoke%2A> or <xref:System.Windows.Threading.Dispatcher.BeginInvoke%2A>. Reasons for using a <xref:System.Windows.Threading.DispatcherTimer> as opposed to a <xref:System.Timers.Timer?displayProperty=nameWithType> are that the <xref:System.Windows.Threading.DispatcherTimer> runs on the same thread as the <xref:System.Windows.Threading.Dispatcher> and a <xref:System.Windows.Threading.DispatcherPriority> can be set on the <xref:System.Windows.Threading.DispatcherTimer>.  
   
  A <xref:System.Windows.Threading.DispatcherTimer> will keep an object alive whenever the object's methods are bound to the timer.  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 53ecf366d09..fa416634214 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -411,7 +411,7 @@
       </Parameters>
       <Docs>
         <param name="resourceKey">The name of the resource to find.</param>
-        <summary>Searches for a [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] resource, such as a <see cref="T:System.Windows.Style" /> or <see cref="T:System.Windows.Media.Brush" />, with the specified key, and throws an exception if the requested resource is not found (see <see href="/dotnet/framework/wpf/advanced/xaml-resources">XAML Resources</see>).</summary>
+        <summary>Searches for a user interface (UI) resource, such as a <see cref="T:System.Windows.Style" /> or <see cref="T:System.Windows.Media.Brush" />, with the specified key, and throws an exception if the requested resource is not found (see <see href="/dotnet/framework/wpf/advanced/xaml-resources">XAML Resources</see>).</summary>
         <returns>The requested resource object. If the requested resource is not found, a <see cref="T:System.Windows.ResourceReferenceKeyNotFoundException" /> is thrown.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1695,7 +1695,7 @@
   
 4.  System  
   
- Consequently, [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements can bind to application-scope resources. Additionally, if resources change, the resource system ensures that element properties which are bound to those resources are automatically updated to reflect the change.  
+ Consequently, user interface (UI) elements can bind to application-scope resources. Additionally, if resources change, the resource system ensures that element properties which are bound to those resources are automatically updated to reflect the change.  
   
  Application-scope resources provide a simple way to support a consistent theme across your application. You can easily create a theme in XAML by using the `Application.Resources` tag. However, if your application supports multiple themes, which may contain a large number of theme elements, it might be easier to manage them using one <xref:System.Windows.ResourceDictionary> instance for each theme. In this way, a new theme can be applied by setting the Resources property to the appropriate <xref:System.Windows.ResourceDictionary>.  
   
@@ -2339,7 +2339,7 @@ This example illustrates how to use XAML together with application-scope resourc
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Window> reference is automatically added to <xref:System.Windows.Application.Windows%2A> as soon as a window is instantiated on the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] thread; windows that are created by worker threads are not added. A <xref:System.Windows.Window> reference is automatically removed after its <xref:System.Windows.Window.Closing> event has been handled and before its <xref:System.Windows.Window.Closed> event is raised.  
+ A <xref:System.Windows.Window> reference is automatically added to <xref:System.Windows.Application.Windows%2A> as soon as a window is instantiated on the user interface (UI) thread; windows that are created by worker threads are not added. A <xref:System.Windows.Window> reference is automatically removed after its <xref:System.Windows.Window.Closing> event has been handled and before its <xref:System.Windows.Window.Closed> event is raised.  
   
  By default, the first item added to the <xref:System.Windows.Application.Windows%2A> property becomes the <xref:System.Windows.Application.MainWindow%2A>.  
   
diff --git a/xml/System.Windows/ContentElement.xml b/xml/System.Windows/ContentElement.xml
index 45145ea3779..ea8b747af82 100644
--- a/xml/System.Windows/ContentElement.xml
+++ b/xml/System.Windows/ContentElement.xml
@@ -1390,7 +1390,7 @@ where `myElement` is the class name of the type that you are overriding the meta
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>When overridden in a derived class, returns an alternative [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] parent for this element if no visual parent exists.</summary>
+        <summary>When overridden in a derived class, returns an alternative user interface (UI) parent for this element if no visual parent exists.</summary>
         <returns>An object, if implementation of a derived class has an alternate parent connection to report.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1967,7 +1967,7 @@ where `myElement` is the class name of the type that you are overriding the meta
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether this element is enabled in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets or sets a value that indicates whether this element is enabled in the user interface (UI).</summary>
         <value>
           <see langword="true" /> if the element is enabled; otherwise, <see langword="false" />. The default value is <see langword="true" />.</value>
         <remarks>
diff --git a/xml/System.Windows/DragDrop.xml b/xml/System.Windows/DragDrop.xml
index 5ace07717c8..67c94e7cb1a 100644
--- a/xml/System.Windows/DragDrop.xml
+++ b/xml/System.Windows/DragDrop.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Drag-and-drop commonly refers to a method of data transfer that involves using a mouse (or some other pointing device) to select one or more objects, dragging these objects over some desired drop target in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], and dropping them. A drag-and-drop operation is analogous to a copy (or cut)-and-paste operation that is used to transfer data from one object or application to another. Drag-and-drop operations typically involve two parties: a drag source from which the dragged data originates and a drop target which receives the dropped data. The events and methods required for drag-and-drop operations are defined in the <xref:System.Windows.DragDrop> class. The drag-and-drop events are attached events that can be attached to any <xref:System.Windows.UIElement> or <xref:System.Windows.ContentElement>. The drag source and drop target may be UI elements in the same application or in different applications. However, the drop target must know how to process the data being passed by the drag source.  
+ Drag-and-drop commonly refers to a method of data transfer that involves using a mouse (or some other pointing device) to select one or more objects, dragging these objects over some desired drop target in the user interface (UI), and dropping them. A drag-and-drop operation is analogous to a copy (or cut)-and-paste operation that is used to transfer data from one object or application to another. Drag-and-drop operations typically involve two parties: a drag source from which the dragged data originates and a drop target which receives the dropped data. The events and methods required for drag-and-drop operations are defined in the <xref:System.Windows.DragDrop> class. The drag-and-drop events are attached events that can be attached to any <xref:System.Windows.UIElement> or <xref:System.Windows.ContentElement>. The drag source and drop target may be UI elements in the same application or in different applications. However, the drop target must know how to process the data being passed by the drag source.  
   
 > [!NOTE]
 >  The <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement> classes contain aliases for the drag-and-drop events so that the events appear in the class members list when these classes are inherited as a base class. When you attach an event handler to a drag-and-drop event on one of these classes, the handler is attached to the underlying <xref:System.Windows.DragDrop> event and they receive the same instance of event data. For example, see <xref:System.Windows.UIElement.Drop?displayProperty=nameWithType>.  
diff --git a/xml/System.Windows/EventTrigger.xml b/xml/System.Windows/EventTrigger.xml
index a97092959b7..a706fd4d3d5 100644
--- a/xml/System.Windows/EventTrigger.xml
+++ b/xml/System.Windows/EventTrigger.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Trigger> objects have the <xref:System.Windows.Trigger.Setters%2A>, <xref:System.Windows.TriggerBase.EnterActions%2A>, and <xref:System.Windows.TriggerBase.ExitActions%2A> properties that apply changes or actions based on the state of certain properties, while <xref:System.Windows.EventTrigger> objects start a set of <xref:System.Windows.EventTrigger.Actions%2A> when a specified routed event occurs. For example, you may want to use an <xref:System.Windows.EventTrigger> to start a set of animations when the mouse pointer is over a certain [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] control. Unlike <xref:System.Windows.Trigger>, <xref:System.Windows.EventTrigger> has no concept of termination of state, so the action will not be undone once the condition that raised the event is no longer true.  
+ <xref:System.Windows.Trigger> objects have the <xref:System.Windows.Trigger.Setters%2A>, <xref:System.Windows.TriggerBase.EnterActions%2A>, and <xref:System.Windows.TriggerBase.ExitActions%2A> properties that apply changes or actions based on the state of certain properties, while <xref:System.Windows.EventTrigger> objects start a set of <xref:System.Windows.EventTrigger.Actions%2A> when a specified routed event occurs. For example, you may want to use an <xref:System.Windows.EventTrigger> to start a set of animations when the mouse pointer is over a certain user interface (UI) control. Unlike <xref:System.Windows.Trigger>, <xref:System.Windows.EventTrigger> has no concept of termination of state, so the action will not be undone once the condition that raised the event is no longer true.  
   
  Note that when using an <xref:System.Windows.EventTrigger>, you need to choose events that do not interfere with the inherent behavior of your control. Controls such as <xref:System.Windows.Controls.Button> or <xref:System.Windows.Controls.TextBox> perform specific actions on user input events such as mouse clicks and keyboard events. For example, if you are styling a button and try to set the <xref:System.Windows.Input.Mouse.MouseDown> event as the <xref:System.Windows.EventTrigger.RoutedEvent%2A> of an <xref:System.Windows.EventTrigger>, the <xref:System.Windows.EventTrigger> never gets applied because the event first gets handled by the button. Instead, you can use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event or a different event.  
   
@@ -256,7 +256,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.EventTrigger>s apply a set of actions when the specified routed event occurs. For example, you may want to use <xref:System.Windows.EventTrigger>s to start a set of animations when the mouse pointer is over a certain [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] control.  
+ <xref:System.Windows.EventTrigger>s apply a set of actions when the specified routed event occurs. For example, you may want to use <xref:System.Windows.EventTrigger>s to start a set of animations when the mouse pointer is over a certain user interface (UI) control.  
   
  If the template or style that contains this <xref:System.Windows.EventTrigger> does not have the `TargetType` property specified, then you need to quality the event name with the class name using the `ClassName.EventName` syntax.  
   
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 9e8658f10cd..6d1f6d21c33 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -60,7 +60,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.FrameworkContentElement> does not yet define its own rendering behavior; instantiating an actual <xref:System.Windows.FrameworkContentElement> class instance in code or markup is possible but displays nothing in a WPF application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. Rendering logic must be provided by classes that take <xref:System.Windows.FrameworkContentElement> child elements as part of their content model, or in <xref:System.Windows.FrameworkContentElement> derived classes.  
+ <xref:System.Windows.FrameworkContentElement> does not yet define its own rendering behavior; instantiating an actual <xref:System.Windows.FrameworkContentElement> class instance in code or markup is possible but displays nothing in a WPF application user interface (UI). Rendering logic must be provided by classes that take <xref:System.Windows.FrameworkContentElement> child elements as part of their content model, or in <xref:System.Windows.FrameworkContentElement> derived classes.  
   
  <xref:System.Windows.FrameworkContentElement> deliberately parallels many of the same APIs as <xref:System.Windows.FrameworkElement>. Note that certain APIs found on <xref:System.Windows.FrameworkElement> will not have a <xref:System.Windows.FrameworkContentElement> equivalent. Several of the <xref:System.Windows.FrameworkElement> APIs are for functionality such as geometry representation or layout, which are not relevant for a <xref:System.Windows.FrameworkContentElement>.  
   
@@ -437,7 +437,7 @@
         <ReturnType>System.Windows.Controls.ContextMenu</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the context menu element that should appear whenever the context menu is requested via [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] from within this element.</summary>
+        <summary>Gets or sets the context menu element that should appear whenever the context menu is requested via user interface (UI) from within this element.</summary>
         <value>The context menu that this element uses.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1180,7 +1180,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether this <see cref="T:System.Windows.FrameworkContentElement" /> should force the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] to render the cursor as declared by this instance's <see cref="P:System.Windows.FrameworkContentElement.Cursor" /> property.</summary>
+        <summary>Gets or sets a value indicating whether this <see cref="T:System.Windows.FrameworkContentElement" /> should force the user interface (UI) to render the cursor as declared by this instance's <see cref="P:System.Windows.FrameworkContentElement.Cursor" /> property.</summary>
         <value>
           <see langword="true" /> to force cursor presentation while over this element to use this instance's setting for the cursor (including on all child elements); otherwise <see langword="false" />. The default value is <see langword="false" />.</value>
         <remarks>
@@ -2888,7 +2888,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the tool-tip object that is displayed for this element in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets or sets the tool-tip object that is displayed for this element in the user interface (UI).</summary>
         <value>The tooltip object.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 8d81e7659f8..376cf9e672e 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -77,7 +77,7 @@
   
  As can be seen from the class hierarchy, many WPF classes derive from <xref:System.Windows.FrameworkElement>, either directly or through intermediate base classes such as <xref:System.Windows.Controls.Panel> or <xref:System.Windows.Controls.Control>.  
   
- If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create XAML child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
+ If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create user interface (UI) in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create XAML child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
   
  ]]></format>
     </remarks>
@@ -824,7 +824,7 @@
         <ReturnType>System.Windows.Controls.ContextMenu</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the context menu element that should appear whenever the context menu is requested through [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] from within this element.</summary>
+        <summary>Gets or sets the context menu element that should appear whenever the context menu is requested through user interface (UI) from within this element.</summary>
         <value>The context menu assigned to this element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1520,7 +1520,7 @@
         <ReturnType>System.Windows.FlowDirection</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the direction that text and other [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] elements flow within any parent element that controls their layout.</summary>
+        <summary>Gets or sets the direction that text and other user interface (UI) elements flow within any parent element that controls their layout.</summary>
         <value>The direction that text and other UI elements flow within their parent element, as a value of the enumeration. The default value is <see cref="F:System.Windows.FlowDirection.LeftToRight" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1680,7 +1680,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether this <see cref="T:System.Windows.FrameworkElement" /> should force the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] to render the cursor as declared by the <see cref="P:System.Windows.FrameworkElement.Cursor" /> property.</summary>
+        <summary>Gets or sets a value that indicates whether this <see cref="T:System.Windows.FrameworkElement" /> should force the user interface (UI) to render the cursor as declared by the <see cref="P:System.Windows.FrameworkElement.Cursor" /> property.</summary>
         <value>
           <see langword="true" /> if cursor presentation while over this element is forced to use current <see cref="P:System.Windows.FrameworkElement.Cursor" /> settings for the cursor (including on all child elements); otherwise <see langword="false" />. The default value is <see langword="false" />.</value>
         <remarks>
@@ -2462,7 +2462,7 @@
   
  Setting a transform provides powerful capabilities of scaling and rotating. However, <xref:System.Windows.FrameworkElement.LayoutTransform%2A> ignores <xref:System.Windows.Media.TranslateTransform> operations. This is because the layout system behavior for child elements of a <xref:System.Windows.FrameworkElement> auto-corrects any offsets to the position of a scaled or rotated element into the layout and coordinate system of the parent element.  
   
- <xref:System.Windows.FrameworkElement.LayoutTransform%2A> can lead to poor application performance if you invoke it in a scenario that does not require a full pass by the layout system. When you apply a <xref:System.Windows.FrameworkElement.LayoutTransform%2A> to the <xref:System.Windows.Controls.Panel.Children%2A> collection of the <xref:System.Windows.Controls.Panel>, it triggers a new pass by the layout system and forces all on-screen objects to be remeasured and rearranged. If you are updating the complete application [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)], this functionality might be exactly what you need. However, if you do not need a full layout pass, use the <xref:System.Windows.UIElement.RenderTransform%2A> property, which does not invoke the layout system, and therefore, is typically a better choice for this scenario.  
+ <xref:System.Windows.FrameworkElement.LayoutTransform%2A> can lead to poor application performance if you invoke it in a scenario that does not require a full pass by the layout system. When you apply a <xref:System.Windows.FrameworkElement.LayoutTransform%2A> to the <xref:System.Windows.Controls.Panel.Children%2A> collection of the <xref:System.Windows.Controls.Panel>, it triggers a new pass by the layout system and forces all on-screen objects to be remeasured and rearranged. If you are updating the complete application user interface (UI), this functionality might be exactly what you need. However, if you do not need a full layout pass, use the <xref:System.Windows.UIElement.RenderTransform%2A> property, which does not invoke the layout system, and therefore, is typically a better choice for this scenario.  
   
  Example scenarios where <xref:System.Windows.FrameworkElement.LayoutTransform%2A> would be useful include: rotating elements such as menu components from horizontal to vertical or vice versa, scaling elements (zooming in) on focus, providing editing behavior, etc.  
   
@@ -2644,7 +2644,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The margin is the space between this element and other elements that will be adjacent when layout creates the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)]. Shared elements might be peer elements (such as other elements in the collection of a common parent control), or might also be this element's parent.  
+ The margin is the space between this element and other elements that will be adjacent when layout creates the user interface (UI). Shared elements might be peer elements (such as other elements in the collection of a common parent control), or might also be this element's parent.  
   
  <xref:System.Windows.FrameworkElement.Margin%2A> is set as a <xref:System.Windows.Thickness> structure rather than as a number so that the margin can be set asymmetrically. The <xref:System.Windows.Thickness> structure itself supports string type conversion so that you can specify an asymmetric <xref:System.Windows.FrameworkElement.Margin%2A> in XAML attribute syntax also.  
   
@@ -4943,7 +4943,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the tool-tip object that is displayed for this element in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets or sets the tool-tip object that is displayed for this element in the user interface (UI).</summary>
         <value>The tooltip object.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/IInputElement.xml b/xml/System.Windows/IInputElement.xml
index 150fb72f264..e84b2e96cad 100644
--- a/xml/System.Windows/IInputElement.xml
+++ b/xml/System.Windows/IInputElement.xml
@@ -334,7 +334,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether this element is enabled in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets a value that indicates whether this element is enabled in the user interface (UI).</summary>
         <value>
           <see langword="true" /> if the element is enabled; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index 000f48f5482..bf2dae31a78 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -7975,7 +7975,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether all [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] effects are enabled.</summary>
+        <summary>Gets a value that indicates whether all user interface (UI) effects are enabled.</summary>
         <value>
           <see langword="true" /> if all UI effects are enabled; <see langword="false" /> if they are disabled.</value>
         <remarks>
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 1d7bddab221..4e92a2658d2 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -2090,7 +2090,7 @@ Image with an Elliptical Clip Region
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>When overridden in a derived class, returns an alternative [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] parent for this element if no visual parent exists.</summary>
+        <summary>When overridden in a derived class, returns an alternative user interface (UI) parent for this element if no visual parent exists.</summary>
         <returns>An object, if implementation of a derived class has an alternate parent connection to report.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2959,7 +2959,7 @@ Image with an Elliptical Clip Region
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether this element is enabled in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  This is a dependency property.</summary>
+        <summary>Gets or sets a value indicating whether this element is enabled in the user interface (UI).  This is a dependency property.</summary>
         <value>
           <see langword="true" /> if the element is enabled; otherwise, <see langword="false" />. The default value is <see langword="true" />.</value>
         <remarks>
@@ -3043,7 +3043,7 @@ Image with an Elliptical Clip Region
           <see langword="true" /> if the element is enabled; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
-          <para>The default implementation of this property caches the value and also calculates whether the parent element of this element is enabled. (If the parent is not enabled, the child element cannot be effectively enabled in practical [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].) If you choose to override this implementation, make certain that you call the base implementation to preserve this behavior.  
+          <para>The default implementation of this property caches the value and also calculates whether the parent element of this element is enabled. (If the parent is not enabled, the child element cannot be effectively enabled in practical user interface (UI).) If you choose to override this implementation, make certain that you call the base implementation to preserve this behavior.  
   
  The <see cref="T:System.Windows.Controls.Primitives.ScrollBar" /> class provides an existing override implementation of this property. This override determines whether the content inside the content presentation area exceeds the available area. If the content does exceed the area, the scrollbar portion is enabled. Otherwise, the scrollbar is not enabled.</para>
         </block>
@@ -4356,7 +4356,7 @@ Image with an Elliptical Clip Region
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether this element is visible in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  This is a dependency property.</summary>
+        <summary>Gets a value indicating whether this element is visible in the user interface (UI).  This is a dependency property.</summary>
         <value>
           <see langword="true" /> if the element is visible; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -9938,7 +9938,7 @@ Image with an Elliptical Clip Region
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the opacity factor applied to the entire <see cref="T:System.Windows.UIElement" /> when it is rendered in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  This is a dependency property.</summary>
+        <summary>Gets or sets the opacity factor applied to the entire <see cref="T:System.Windows.UIElement" /> when it is rendered in the user interface (UI).  This is a dependency property.</summary>
         <value>The opacity factor. Default opacity is 1.0. Expected values are between 0.0 and 1.0.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -12954,7 +12954,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A render transform does not regenerate layout size or render size information. Render transforms are typically intended for animating or applying a temporary effect to an element. For example, the element might zoom when focused or moused over, or might jitter on load to draw the eye to that part of the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].  
+ A render transform does not regenerate layout size or render size information. Render transforms are typically intended for animating or applying a temporary effect to an element. For example, the element might zoom when focused or moused over, or might jitter on load to draw the eye to that part of the user interface (UI).  
   
 <a name="dependencyPropertyInfo_RenderTransform"></a>   
 ## Dependency Property Information  
@@ -14794,7 +14794,7 @@ Image with an Elliptical Clip Region
         <ReturnType>System.Windows.Visibility</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] visibility of this element.  This is a dependency property.</summary>
+        <summary>Gets or sets the user interface (UI) visibility of this element.  This is a dependency property.</summary>
         <value>A value of the enumeration. The default value is <see cref="F:System.Windows.Visibility.Visible" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 9c0a0d12505..37bb3f512d3 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -1180,7 +1180,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>When overridden in a derived class, returns an alternative [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] parent for this element if no visual parent exists.</summary>
+        <summary>When overridden in a derived class, returns an alternative user interface (UI) parent for this element if no visual parent exists.</summary>
         <returns>An object, if implementation of a derived class has an alternate parent connection to report.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1797,7 +1797,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether this element is enabled in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets or sets a value indicating whether this element is enabled in the user interface (UI).</summary>
         <value>
           <see langword="true" /> if the element is enabled; otherwise, <see langword="false" />. The default value is <see langword="true" />.</value>
         <remarks>
@@ -1885,7 +1885,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>The default implementation of this property caches the value and also calculates whether the parent element of this element is enabled. (If the parent is not enabled, the child element cannot be effectively enabled in practical [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].) If you choose to override this implementation, make certain that you call the base implementation to preserve this behavior.</para>
+          <para>The default implementation of this property caches the value and also calculates whether the parent element of this element is enabled. (If the parent is not enabled, the child element cannot be effectively enabled in practical user interface (UI).) If you choose to override this implementation, make certain that you call the base implementation to preserve this behavior.</para>
         </block>
         <altmember cref="E:System.Windows.UIElement3D.IsEnabledChanged" />
         <altmember cref="P:System.Windows.UIElement3D.IsEnabled" />
@@ -3216,7 +3216,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether this element is visible in the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Gets a value indicating whether this element is visible in the user interface (UI).</summary>
         <value>
           <see langword="true" /> if the element is visible; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -12626,7 +12626,7 @@
         <ReturnType>System.Windows.Visibility</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)] visibility of this element.</summary>
+        <summary>Gets or sets the user interface (UI) visibility of this element.</summary>
         <value>A value of the enumeration. The default value is <see cref="F:System.Windows.Visibility.Visible" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/WindowStyle.xml b/xml/System.Windows/WindowStyle.xml
index 81a23a3bf39..c7c1b2a2f66 100644
--- a/xml/System.Windows/WindowStyle.xml
+++ b/xml/System.Windows/WindowStyle.xml
@@ -38,7 +38,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Only the client area is visible - the title bar and border are not shown. A <see cref="T:System.Windows.Navigation.NavigationWindow" /> with a <see cref="P:System.Windows.Window.WindowStyle" /> of <see cref="F:System.Windows.WindowStyle.None" /> will still display the navigation [!INCLUDE[TLA#tla_ui](~/includes/tlasharptla-ui-md.md)].</summary>
+        <summary>Only the client area is visible - the title bar and border are not shown. A <see cref="T:System.Windows.Navigation.NavigationWindow" /> with a <see cref="P:System.Windows.Window.WindowStyle" /> of <see cref="F:System.Windows.WindowStyle.None" /> will still display the navigation user interface (UI).</summary>
       </Docs>
     </Member>
     <Member MemberName="SingleBorderWindow">

From 5310f019803fef659130576047d62d4d55ff756a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:05:34 -0800
Subject: [PATCH 159/236] tlasharptla-uiautomation

---
 xml/System.Windows.Automation/InvokePattern.xml         | 2 +-
 xml/System.Windows.Automation/PropertyCondition.xml     | 2 +-
 xml/System.Windows.Automation/WindowClosedEventArgs.xml | 2 +-
 xml/System.Windows.Controls/Label.xml                   | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.Windows.Automation/InvokePattern.xml b/xml/System.Windows.Automation/InvokePattern.xml
index fcf71f21eb8..4b45255810c 100644
--- a/xml/System.Windows.Automation/InvokePattern.xml
+++ b/xml/System.Windows.Automation/InvokePattern.xml
@@ -58,7 +58,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Calls to <xref:System.Windows.Automation.InvokePattern.Invoke%2A> should return immediately without blocking. However, this behavior is entirely dependent on the [!INCLUDE[TLA#tla_uiautomation](~/includes/tlasharptla-uiautomation-md.md)] provider implementation. In scenarios where calling <xref:System.Windows.Automation.InvokePattern.Invoke%2A> causes a blocking issue (such as a modal dialog) a separate helper thread may be required to call the method.  
+ Calls to <xref:System.Windows.Automation.InvokePattern.Invoke%2A> should return immediately without blocking. However, this behavior is entirely dependent on the Microsoft UI Automation provider implementation. In scenarios where calling <xref:System.Windows.Automation.InvokePattern.Invoke%2A> causes a blocking issue (such as a modal dialog) a separate helper thread may be required to call the method.  
   
    
   
diff --git a/xml/System.Windows.Automation/PropertyCondition.xml b/xml/System.Windows.Automation/PropertyCondition.xml
index 76f78ce9cea..9c26abe1da0 100644
--- a/xml/System.Windows.Automation/PropertyCondition.xml
+++ b/xml/System.Windows.Automation/PropertyCondition.xml
@@ -99,7 +99,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example uses a <xref:System.Windows.Automation.PropertyCondition> to retrieve the [!INCLUDE[TLA#tla_uiautomation](~/includes/tlasharptla-uiautomation-md.md)] element representing the main form of an application. The form is located by a case-insensitive search for its string identifier.  
+ The following example uses a <xref:System.Windows.Automation.PropertyCondition> to retrieve the Microsoft UI Automation element representing the main form of an application. The form is located by a case-insensitive search for its string identifier.  
   
  [!code-csharp[UIAClient_snip#110](~/samples/snippets/csharp/VS_Snippets_Wpf/UIAClient_snip/CSharp/ClientForm.cs#110)]
  [!code-vb[UIAClient_snip#110](~/samples/snippets/visualbasic/VS_Snippets_Wpf/UIAClient_snip/VisualBasic/ClientForm.vb#110)]  
diff --git a/xml/System.Windows.Automation/WindowClosedEventArgs.xml b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
index 43ab29bda9f..86e33d6622a 100644
--- a/xml/System.Windows.Automation/WindowClosedEventArgs.xml
+++ b/xml/System.Windows.Automation/WindowClosedEventArgs.xml
@@ -84,7 +84,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When your application receives a window-closed event, the `sender` parameter of the event handler cannot be used to obtain information about the window that has closed, because the corresponding [!INCLUDE[TLA#tla_uiautomation](~/includes/tlasharptla-uiautomation-md.md)] element is no longer valid. Use <xref:System.Windows.Automation.WindowClosedEventArgs.GetRuntimeId%2A> to match the window with a known identifier.  
+ When your application receives a window-closed event, the `sender` parameter of the event handler cannot be used to obtain information about the window that has closed, because the corresponding Microsoft UI Automation element is no longer valid. Use <xref:System.Windows.Automation.WindowClosedEventArgs.GetRuntimeId%2A> to match the window with a known identifier.  
   
    
   
diff --git a/xml/System.Windows.Controls/Label.xml b/xml/System.Windows.Controls/Label.xml
index 180207a39f3..5766a6dc1db 100644
--- a/xml/System.Windows.Controls/Label.xml
+++ b/xml/System.Windows.Controls/Label.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class provides both functional and visual support for access keys (also known as mnemonics). It is frequently used to enable quick keyboard access to controls such as a <xref:System.Windows.Controls.TextBox>. To assign a <xref:System.Windows.Controls.Label> to a <xref:System.Windows.Controls.Control>, set the <xref:System.Windows.Controls.Label.Target%2A> property to the control that should get focus when the user presses the access key. Setting the target also causes [!INCLUDE[TLA#tla_uiautomation](~/includes/tlasharptla-uiautomation-md.md)] to use the text of the label as the name of the targeted control. For more information, see [Accessibility](/dotnet/framework/ui-automation/).  
+ This class provides both functional and visual support for access keys (also known as mnemonics). It is frequently used to enable quick keyboard access to controls such as a <xref:System.Windows.Controls.TextBox>. To assign a <xref:System.Windows.Controls.Label> to a <xref:System.Windows.Controls.Control>, set the <xref:System.Windows.Controls.Label.Target%2A> property to the control that should get focus when the user presses the access key. Setting the target also causes Microsoft UI Automation to use the text of the label as the name of the targeted control. For more information, see [Accessibility](/dotnet/framework/ui-automation/).  
   
  To set the access key, add an underscore before the character that should be the access key. If your content has multiple underscore characters, only the first one is converted into an access key; the other underscores appear as normal text. If the underscore that you want converted to the access key is not the first underscore, use two consecutive underscores for any underscores that precede the one that you want to convert. For example, the following code contains an access key and displays as _Hello**W**orld:  
   

From a25626b553267623ef5cbd1b48bc1c964751a2e4 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:05:58 -0800
Subject: [PATCH 160/236] tlasharptla-uiautomationsharpinitcap

---
 xml/System.Windows.Controls/DataGridCell.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Controls/DataGridCell.xml b/xml/System.Windows.Controls/DataGridCell.xml
index 29d873a4e68..941eec95127 100644
--- a/xml/System.Windows.Controls/DataGridCell.xml
+++ b/xml/System.Windows.Controls/DataGridCell.xml
@@ -355,7 +355,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Automation.Peers.DataGridCellAutomationPeer> exposes the <xref:System.Windows.Controls.DataGrid> to [!INCLUDE[TLA#tla_uiautomation#initcap](~/includes/tlasharptla-uiautomationsharpinitcap-md.md)].  
+ The <xref:System.Windows.Automation.Peers.DataGridCellAutomationPeer> exposes the <xref:System.Windows.Controls.DataGrid> to UI Automation.  
   
  ]]></format>
         </remarks>

From efbcc0ed0a83ccf43786ea6266f7700c29851b25 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:06:18 -0800
Subject: [PATCH 161/236] tlasharptla-unc

---
 xml/System.Windows.Documents/Hyperlink.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Documents/Hyperlink.xml b/xml/System.Windows.Documents/Hyperlink.xml
index 9c41ca4755f..77ec1ac0f0b 100644
--- a/xml/System.Windows.Documents/Hyperlink.xml
+++ b/xml/System.Windows.Documents/Hyperlink.xml
@@ -691,7 +691,7 @@
  This method navigates to the uniform resource identifier (URI) specified by the <xref:System.Windows.Documents.Hyperlink.NavigateUri%2A> property, and marks the URI as visited.  
   
 > [!IMPORTANT]
->  Depending on the host computer's security configuration, certain forms of navigation (for example, navigating to a [!INCLUDE[TLA#tla_unc](~/includes/tlasharptla-unc-md.md)] path) are not allowed in the Internet zone.  In such cases, this method will demand full trust.  For more information, see [Code Access Security](/dotnet/framework/misc/code-access-security).  
+>  Depending on the host computer's security configuration, certain forms of navigation (for example, navigating to a Universal Naming Convention (UNC) path) are not allowed in the Internet zone.  In such cases, this method will demand full trust.  For more information, see [Code Access Security](/dotnet/framework/misc/code-access-security).  
   
  ]]></format>
         </remarks>

From 406d77d2746658f8deae05d1c1c3df4b818b1f49 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:06:35 -0800
Subject: [PATCH 162/236] tlasharptla-unicode

---
 xml/System.Windows.Controls/TextChange.xml   |  2 +-
 xml/System.Windows.Documents/TextPointer.xml | 12 ++++++------
 xml/System.Windows/DataFormats.xml           |  4 ++--
 3 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Windows.Controls/TextChange.xml b/xml/System.Windows.Controls/TextChange.xml
index 729436ef3b1..8951f931917 100644
--- a/xml/System.Windows.Controls/TextChange.xml
+++ b/xml/System.Windows.Controls/TextChange.xml
@@ -27,7 +27,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained within an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   Each 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   Each 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
  <xref:System.Windows.Controls.TextChange> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
diff --git a/xml/System.Windows.Documents/TextPointer.xml b/xml/System.Windows.Documents/TextPointer.xml
index 26a459cb748..8a6eae2a869 100644
--- a/xml/System.Windows.Documents/TextPointer.xml
+++ b/xml/System.Windows.Documents/TextPointer.xml
@@ -35,7 +35,7 @@
   
     -   A <xref:System.Windows.UIElement> element contained within an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
-    -   Each 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+    -   Each 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
 -   Text Container - A *text container* is the element that forms the ultimate border for the flow content at hand; the position indicated by a <xref:System.Windows.Documents.TextPointer> always falls within a text container.  Currently, a text container must be either a <xref:System.Windows.Documents.FlowDocument> or a <xref:System.Windows.Controls.TextBlock>.  Generally speaking, operations between <xref:System.Windows.Documents.TextPointer> instances in different text containers are not supported.  
   
@@ -483,7 +483,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained in an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   A 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   A 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
  If the next symbol is categorized as <xref:System.Windows.Documents.TextPointerContext.EmbeddedElement>, <xref:System.Windows.Documents.TextPointerContext.ElementStart>, or <xref:System.Windows.Documents.TextPointerContext.ElementEnd> (as identified by the <xref:System.Windows.Documents.TextPointer.GetPointerContext%2A> method), then the <xref:System.Windows.Documents.TextPointer> returned by this method is advanced by exactly one symbol from the current position.  
   
@@ -580,7 +580,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained in an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   A 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   A 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
    
   
@@ -678,7 +678,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained in an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   A 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   A 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
    
   
@@ -729,7 +729,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained in an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   A 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   A 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
  ]]></format>
         </remarks>
@@ -873,7 +873,7 @@
   
 -   A <xref:System.Windows.UIElement> element contained in an <xref:System.Windows.Documents.InlineUIContainer> or <xref:System.Windows.Documents.BlockUIContainer>.  Note that such a <xref:System.Windows.UIElement> is always counted as exactly one symbol; any additional content or elements contained by the <xref:System.Windows.UIElement> are not counted as symbols.  
   
--   A 16-bit [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] character inside of a text <xref:System.Windows.Documents.Run> element.  
+-   A 16-bit Unicode character inside of a text <xref:System.Windows.Documents.Run> element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index addc0bacca5..fa7feeae25b 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -46,7 +46,7 @@
 |<xref:System.Windows.DataFormats.SymbolicLink>|"SymbolicLink"|Specifies the Windows symbolic link data format.|  
 |<xref:System.Windows.DataFormats.Text>|"Text"|Specifies the ANSI text data format.|  
 |<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the Tagged Image File Format (TIFF) data format.|  
-|<xref:System.Windows.DataFormats.UnicodeText>|"UnicodeText"|Specifies the [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] text data format.|  
+|<xref:System.Windows.DataFormats.UnicodeText>|"UnicodeText"|Specifies the Unicode text data format.|  
 |<xref:System.Windows.DataFormats.WaveAudio>|"WaveAudio"|Specifies the wave audio data format.|  
 |<xref:System.Windows.DataFormats.Xaml>|"Xaml"|Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] data format.|  
 |<xref:System.Windows.DataFormats.XamlPackage>|"XamlPackage"|Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] package data format.|  
@@ -798,7 +798,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_unicode](~/includes/tlasharptla-unicode-md.md)] text data format.</summary>
+        <summary>Specifies the Unicode text data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   

From 7a88e0ebbe6b86cd2fef9a4261d187141d116be8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:06:52 -0800
Subject: [PATCH 163/236] tlasharptla-url

---
 xml/System.Windows.Automation/ControlType.xml       | 2 +-
 xml/System.Windows.Navigation/NavigationService.xml | 2 +-
 xml/System.Windows/Application.xml                  | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Automation/ControlType.xml b/xml/System.Windows.Automation/ControlType.xml
index 2ad5db4a5a1..27539764a56 100644
--- a/xml/System.Windows.Automation/ControlType.xml
+++ b/xml/System.Windows.Automation/ControlType.xml
@@ -516,7 +516,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A hyperlink control navigates to a specified [!INCLUDE[TLA#tla_url](~/includes/tlasharptla-url-md.md)] when a user clicks on the control.  
+ A hyperlink control navigates to a specified URL when a user clicks on the control.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 48bf05032a3..7e3a9dbdbfb 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -646,7 +646,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The value of `source` can be a Web [!INCLUDE[TLA#tla_url](~/includes/tlasharptla-url-md.md)] or a valid pack URI (see [Pack URIs in WPF](/dotnet/framework/wpf/app-development/pack-uris-in-wpf)).  
+ The value of `source` can be a Web URL or a valid pack URI (see [Pack URIs in WPF](/dotnet/framework/wpf/app-development/pack-uris-in-wpf)).  
   
  <xref:System.Windows.Navigation.NavigationService.Navigate%2A> will navigate to the URI specified by `source` if the following conditions are true:  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index fa416634214..2476360d19c 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -2159,7 +2159,7 @@ This example illustrates how to use XAML together with application-scope resourc
 > [!NOTE]
 >  If your application uses <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> to specify a credential policy, you need to set <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> after <xref:System.Windows.Application.Startup> is raised; otherwise, WPF sets it to a default internal policy directly after the <xref:System.Windows.Application.Startup> event has been raised.  
   
- The command-line arguments that are passed to the <xref:System.Windows.Application.Startup> event handler are not the same as the [!INCLUDE[TLA#tla_url](~/includes/tlasharptla-url-md.md)] query string parameters that are passed to an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)].  
+ The command-line arguments that are passed to the <xref:System.Windows.Application.Startup> event handler are not the same as the URL query string parameters that are passed to an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)].  
   
    
   

From 4751166db1bd0cb66256b13962a2d5c28629ba57 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:07:20 -0800
Subject: [PATCH 164/236] tlasharptla-visualstu

---
 xml/System.Windows.Controls/Page.xml | 2 +-
 xml/System.Windows.Forms/Form.xml    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index c4fd21cda50..4269b17d26b 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -50,7 +50,7 @@
   
 -   It can alter the title, width, height, and navigation UI of its host window (<xref:System.Windows.Controls.Page.WindowTitle%2A>, <xref:System.Windows.Controls.Page.WindowWidth%2A>, <xref:System.Windows.Controls.Page.WindowHeight%2A>, <xref:System.Windows.Controls.Page.ShowsNavigationUI%2A>).  
   
--   It has designer support in [!INCLUDE[TLA#tla_visualstu](~/includes/tlasharptla-visualstu-md.md)].  
+-   It has designer support in Microsoft Visual Studio.  
   
  A page can be hosted from <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Frame>, or from a browser. To be hosted, a page can be:  
   
diff --git a/xml/System.Windows.Forms/Form.xml b/xml/System.Windows.Forms/Form.xml
index c2e493c2498..ef403933856 100644
--- a/xml/System.Windows.Forms/Form.xml
+++ b/xml/System.Windows.Forms/Form.xml
@@ -78,7 +78,7 @@
   
  You can use a form as the starting class in your application by placing a method called `Main` in the class. In the `Main` method add code to create and show the form. You will also need to add the `STAThread` attribute to the `Main` method in order for the form to run. When the starting form is closed, the application is also closed.  
   
- If you set the <xref:System.Windows.Forms.Control.Enabled%2A> property to `false` before the <xref:System.Windows.Forms.Form> is visible (for example, setting <xref:System.Windows.Forms.Control.Enabled%2A> to false in the [!INCLUDE[TLA#tla_visualstu](~/includes/tlasharptla-visualstu-md.md)] designer), the minimize, maximize, close, and system buttons remain enabled. If you set <xref:System.Windows.Forms.Control.Enabled%2A> to `false` after the <xref:System.Windows.Forms.Form> is visible (for example, when the Load event occurs), the buttons are disabled.  
+ If you set the <xref:System.Windows.Forms.Control.Enabled%2A> property to `false` before the <xref:System.Windows.Forms.Form> is visible (for example, setting <xref:System.Windows.Forms.Control.Enabled%2A> to false in the Microsoft Visual Studio designer), the minimize, maximize, close, and system buttons remain enabled. If you set <xref:System.Windows.Forms.Control.Enabled%2A> to `false` after the <xref:System.Windows.Forms.Form> is visible (for example, when the Load event occurs), the buttons are disabled.  
   
    
   

From c1ceca065c125dc506be16b1ff234b54485f0624 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:07:38 -0800
Subject: [PATCH 165/236] tlasharptla-wdp

---
 xml/System.Windows.Media.Imaging/BitmapDecoder.xml    | 2 +-
 xml/System.Windows.Media.Imaging/BitmapEncoder.xml    | 2 +-
 xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index 1432f64db2c..dbb3397f691 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -663,7 +663,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- None of the native formats support global thumbnails. Joint Photographics Experts Group (JPEG), Tagged Image File Format (TIFF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
+ None of the native formats support global thumbnails. Joint Photographics Experts Group (JPEG), Tagged Image File Format (TIFF), and Microsoft Windows Media Photo support frame-level thumbnails that can be accessed using the <xref:System.Windows.Media.Imaging.BitmapFrame.Thumbnail%2A> property.  
   
  The <xref:System.Windows.Media.Imaging.BitmapSource> returned by this property is frozen.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
index 440d3471edf..f8a10a65c7f 100644
--- a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
@@ -196,7 +196,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Only Tagged Image File Format (TIFF), Graphics Interchange Format (GIF), and [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
+ Only Tagged Image File Format (TIFF), Graphics Interchange Format (GIF), and Microsoft Windows Media Photo images support more than one frame. Attempts to add additional frames to formats that do not support them will result in only the first frame being encoded.  
   
 <a name="xamlTextUsage_Frames"></a>   
 ## XAML Text Usage  
diff --git a/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml b/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
index 1c6c15865ef..f15d62a0834 100644
--- a/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/WmpBitmapDecoder.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_wdp](~/includes/tlasharptla-wdp-md.md)] is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. Windows Media Photo images achieve lossy and lossless compression by using a single algorithm. Windows Media Photo images support existing metadata standards. For additional information about this format, see the [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
+ Microsoft Windows Media Photo is a new codec that provides better image fidelity than JPEG with smaller file sizes and more features. Windows Media Photo images achieve lossy and lossless compression by using a single algorithm. Windows Media Photo images support existing metadata standards. For additional information about this format, see the [Windows Media Photo Specification](https://www.microsoft.com/whdc/xps/wmphoto.mspx).  
   
  ]]></format>
     </remarks>

From a9d0efdcc7e8a513fe3a71f70d364ec821cbec3f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:07:54 -0800
Subject: [PATCH 166/236] tlasharptla-win

---
 xml/System.Printing/PrintQueue.xml                  | 8 ++++----
 xml/System.Printing/PrintQueueStream.xml            | 2 +-
 xml/System.Printing/PrintServer.xml                 | 2 +-
 xml/System.Printing/PrintSystemJobInfo.xml          | 4 ++--
 xml/System.Windows.Interop/HwndSourceParameters.xml | 4 ++--
 xml/System.Windows.Interop/IKeyboardInputSink.xml   | 2 +-
 xml/System.Windows/DataFormats.xml                  | 4 ++--
 xml/System.Windows/SystemParameters.xml             | 2 +-
 8 files changed, 14 insertions(+), 14 deletions(-)

diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index 5fb8cfd8cb4..6c60e5bf463 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -424,7 +424,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
@@ -481,7 +481,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
@@ -3513,7 +3513,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the earliest time of day, expressed as the number of minutes after midnight Coordinated Universal Time (UTC) (also called Greenwich Mean Time [GMT]), that the printer will print a job.</summary>
-        <value>The time of day that the printer first becomes available, expressed as the number of minutes after midnight (UTC). The maximum value is 1439. When a printer is first installed by using the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] Add Printer Wizard, the printer defaults to being available all the time, and this property returns 0 in all time zones.</value>
+        <value>The time of day that the printer first becomes available, expressed as the number of minutes after midnight (UTC). The maximum value is 1439. When a printer is first installed by using the Microsoft Windows Add Printer Wizard, the printer defaults to being available all the time, and this property returns 0 in all time zones.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3558,7 +3558,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the latest time, expressed as the number of minutes after midnight Coordinated Universal Time (UTC) (also called Greenwich Mean Time [GMT]), that the printer will print a job.</summary>
-        <value>The time of day that the printer is no longer available, expressed as the number of minutes after midnight (UTC). The maximum value is 1439. When a printer is first installed by using the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] Add Printer Wizard, the printer defaults to being available all the time, and this property returns 0 in all time zones.</value>
+        <value>The time of day that the printer is no longer available, expressed as the number of minutes after midnight (UTC). The maximum value is 1439. When a printer is first installed by using the Microsoft Windows Add Printer Wizard, the printer defaults to being available all the time, and this property returns 0 in all time zones.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Printing/PrintQueueStream.xml b/xml/System.Printing/PrintQueueStream.xml
index ef1bd673323..5e9460503c7 100644
--- a/xml/System.Printing/PrintQueueStream.xml
+++ b/xml/System.Printing/PrintQueueStream.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this class to write device specific information to a spool file that is not automatically included by the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
+ Use this class to write device specific information to a spool file that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
   
 > [!CAUTION]
 >  Classes within the <xref:System.Printing> namespace are not supported for use within a Windows service or ASP.NET application or service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.  
diff --git a/xml/System.Printing/PrintServer.xml b/xml/System.Printing/PrintServer.xml
index b3f45e27db8..e2d47d9106c 100644
--- a/xml/System.Printing/PrintServer.xml
+++ b/xml/System.Printing/PrintServer.xml
@@ -980,7 +980,7 @@
         <param name="printProcessorName">The name of the print processor.</param>
         <param name="printQueueAttributes">The attributes, as flags, of the new queue.</param>
         <param name="printQueueShareName">The share name of the new queue.</param>
-        <param name="printQueueComment">A comment about the queue that is visible to users in the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] UI.</param>
+        <param name="printQueueComment">A comment about the queue that is visible to users in the Microsoft Windows UI.</param>
         <param name="printQueueLocation">The location of the new queue.</param>
         <param name="printQueueSeparatorFile">The path of a file that is inserted at the beginning of each print job.</param>
         <param name="printQueuePriority">A value from 1 through 99 that specifies the priority of the queue relative to other queues that are hosted by the print server.</param>
diff --git a/xml/System.Printing/PrintSystemJobInfo.xml b/xml/System.Printing/PrintSystemJobInfo.xml
index c532b93cedc..35daf190607 100644
--- a/xml/System.Printing/PrintSystemJobInfo.xml
+++ b/xml/System.Printing/PrintSystemJobInfo.xml
@@ -1183,7 +1183,7 @@
 ## Remarks  
  This value is propagated to each <xref:System.Printing.PrintSystemJobInfo> object from the <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> property of the hosting <xref:System.Printing.PrintQueue> at the time the job enters the queue. If <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> is changed, then any <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A?displayProperty=nameWithType> value that is earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType> is changed to the value of <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
   
- After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] user interface (UI), provided that it is not earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
+ After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> value through the Microsoft Windows user interface (UI), provided that it is not earlier than <xref:System.Printing.PrintQueue.StartTimeOfDay%2A?displayProperty=nameWithType>.  
   
  If you are not in the UTC time zone, you must add or subtract multiples of 60 to get the correct time for your time zone. For example, if you are in the Pacific Time Zone of North America and daylight savings time is not in effect, then your local time is 8 hours earlier than UTC. If <xref:System.Printing.PrintSystemJobInfo.StartTimeOfDay%2A> returns 960, that means 16:00 (4:00 PM) in UTC (because 960/60 = 16). To convert this to Pacific Time, you must subtract 480 (= 8 * 60) minutes.  
   
@@ -1318,7 +1318,7 @@
 ## Remarks  
  This value is propagated to each <xref:System.Printing.PrintSystemJobInfo> object from the <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> property of the hosting <xref:System.Printing.PrintQueue> at the time the job enters the queue. If <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> is changed, then any <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A?displayProperty=nameWithType> value that is later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType> is changed to the value of <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
   
- After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> value through the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] user interface (UI), provided that it is not later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
+ After the job is added to the queue, it can be given a new <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> value through the Microsoft Windows user interface (UI), provided that it is not later than <xref:System.Printing.PrintQueue.UntilTimeOfDay%2A?displayProperty=nameWithType>.  
   
  If you are not in the UTC time zone, you must add or subtract multiples of 60 to get the correct time for your time zone. For example, if you are in the Pacific Time Zone of North America and daylight savings time is not in effect, then your local time is 8 hours earlier than UTC. If <xref:System.Printing.PrintSystemJobInfo.UntilTimeOfDay%2A> returns 960, that means 16:00 (4:00 PM) in UTC (because 960/60 = 16). To convert this to Pacific Time, you must subtract 480 (= 8 * 60) minutes.  
   
diff --git a/xml/System.Windows.Interop/HwndSourceParameters.xml b/xml/System.Windows.Interop/HwndSourceParameters.xml
index d500a4a5f6b..54d99961d8a 100644
--- a/xml/System.Windows.Interop/HwndSourceParameters.xml
+++ b/xml/System.Windows.Interop/HwndSourceParameters.xml
@@ -285,7 +285,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the extended [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] styles for the window.</summary>
+        <summary>Gets or sets the extended Microsoft Windows styles for the window.</summary>
         <value>The extended window styles. See [CreateWindowEx](https://go.microsoft.com/fwlink/?LinkId=98462) for a list of these styles. The default is 0 (no extended window styles).</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Interop.HwndSource" />
@@ -899,7 +899,7 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] class style for the window.</summary>
+        <summary>Gets or sets the Microsoft Windows class style for the window.</summary>
         <value>The window class style. See [Window Class Styles](https://go.microsoft.com/fwlink/?LinkId=178417) for detailed information. The default is 0 (no window class style).</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Interop.HwndSource" />
diff --git a/xml/System.Windows.Interop/IKeyboardInputSink.xml b/xml/System.Windows.Interop/IKeyboardInputSink.xml
index 938a26241c4..2510f9b1890 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSink.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSink.xml
@@ -142,7 +142,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] message must be WM_CHAR, WM_SYSCHAR, WM_DEADCHAR or WM_SYSDEADCHAR.  
+ The Microsoft Windows message must be WM_CHAR, WM_SYSCHAR, WM_DEADCHAR or WM_SYSDEADCHAR.  
   
  If the component has contained components, the message must be passed in your implementation by calling each contained component's <xref:System.Windows.Interop.IKeyboardInputSink.OnMnemonic%2A> method.  
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index fa7feeae25b..044bb0c97df 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -27,7 +27,7 @@
   
 |Field|Field Value|Description|  
 |-----------|-----------------|-----------------|  
-|<xref:System.Windows.DataFormats.Bitmap>|"Bitmap"|Specifies a [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] bitmap data format.|  
+|<xref:System.Windows.DataFormats.Bitmap>|"Bitmap"|Specifies a Microsoft Windows bitmap data format.|  
 |<xref:System.Windows.DataFormats.CommaSeparatedValue>|"CSV"|Specifies a comma-separated value (CSV) data format.|  
 |<xref:System.Windows.DataFormats.Dib>|"DeviceIndependentBitmap"|Specifies the device-independent bitmap (DIB) data format.|  
 |<xref:System.Windows.DataFormats.Dif>|"DataInterchangeFormat"|Specifies the Windows Data Interchange Format (DIF) data format.|  
@@ -73,7 +73,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies a [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] bitmap data format.</summary>
+        <summary>Specifies a Microsoft Windows bitmap data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/SystemParameters.xml b/xml/System.Windows/SystemParameters.xml
index bf2dae31a78..72079056587 100644
--- a/xml/System.Windows/SystemParameters.xml
+++ b/xml/System.Windows/SystemParameters.xml
@@ -3145,7 +3145,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether [!INCLUDE[TLA#tla_win](~/includes/tlasharptla-win-md.md)] for Pen Computing extensions are installed.</summary>
+        <summary>Gets a value that indicates whether Microsoft Windows for Pen Computing extensions are installed.</summary>
         <value>
           <see langword="true" /> if Pen Computing extensions are installed; otherwise, <see langword="false" />.</value>
         <remarks>

From 2e7612430026fedb6bc54db23fab3b326492bcec Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:08:12 -0800
Subject: [PATCH 167/236] tlasharptla-win32

---
 xml/Microsoft.Win32/CommonDialog.xml                |  2 +-
 xml/Microsoft.Win32/FileDialog.xml                  |  6 +++---
 xml/System.Windows.Automation/AutomationElement.xml |  2 +-
 xml/System.Windows.Input/Mouse.xml                  |  2 +-
 xml/System.Windows.Interop/CursorInteropHelper.xml  |  4 ++--
 xml/System.Windows.Interop/HwndHost.xml             |  8 ++++----
 xml/System.Windows.Interop/HwndSource.xml           | 10 +++++-----
 xml/System.Windows.Interop/HwndSourceParameters.xml |  2 +-
 xml/System.Windows.Interop/IKeyboardInputSink.xml   |  2 +-
 xml/System.Windows.Interop/MSG.xml                  |  2 +-
 xml/System.Windows.Media/FontFamily.xml             |  2 +-
 xml/System.Windows.Media/Visual.xml                 |  2 +-
 xml/System.Windows/Application.xml                  |  4 ++--
 xml/System.Windows/UIElement.xml                    |  2 +-
 xml/System.Windows/Window.xml                       |  2 +-
 15 files changed, 26 insertions(+), 26 deletions(-)

diff --git a/xml/Microsoft.Win32/CommonDialog.xml b/xml/Microsoft.Win32/CommonDialog.xml
index 958f5b1d02b..5ab19c9ba6e 100644
--- a/xml/Microsoft.Win32/CommonDialog.xml
+++ b/xml/Microsoft.Win32/CommonDialog.xml
@@ -170,7 +170,7 @@
       </Parameters>
       <Docs>
         <param name="hwndOwner">Handle to the window that owns the dialog box.</param>
-        <summary>When overridden in a derived class, is called to display a particular type of [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] common dialog.</summary>
+        <summary>When overridden in a derived class, is called to display a particular type of Win32 common dialog.</summary>
         <returns>If the user clicks the **OK** button of the dialog that is displayed (e.g. <see cref="T:Microsoft.Win32.OpenFileDialog" />, <see cref="T:Microsoft.Win32.SaveFileDialog" />), <see langword="true" /> is returned; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/Microsoft.Win32/FileDialog.xml b/xml/Microsoft.Win32/FileDialog.xml
index 3e529341f93..1975edd779d 100644
--- a/xml/Microsoft.Win32/FileDialog.xml
+++ b/xml/Microsoft.Win32/FileDialog.xml
@@ -530,7 +530,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This index is 1-based, not 0-based, due to compatibility requirements with the underlying [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] API.  
+ This index is 1-based, not 0-based, due to compatibility requirements with the underlying Win32 API.  
   
  ]]></format>
         </remarks>
@@ -664,8 +664,8 @@
         <ReturnType>System.Int32</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] common file dialog flags that are used by file dialogs for initialization.</summary>
-        <value>A <see cref="T:System.Int32" /> that contains the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] common file dialog flags that are used by file dialogs for initialization.</value>
+        <summary>Gets the Win32 common file dialog flags that are used by file dialogs for initialization.</summary>
+        <value>A <see cref="T:System.Int32" /> that contains the Win32 common file dialog flags that are used by file dialogs for initialization.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 631d9981642..55253deb936 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of user interface (UI), regardless of underlying implementation (such as [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] or [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)]).  
+ An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of user interface (UI), regardless of underlying implementation (such as [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] or Win32).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 9d785227153..316f759c0ea 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -711,7 +711,7 @@
 ## Remarks  
  The position of the mouse pointer is calculated relative to the specified element with the upper-left corner of element being the point of origin, 0,0.  
   
- During drag-and-drop operations, the position of the mouse cannot be reliably determined through <xref:System.Windows.Input.Mouse.GetPosition%2A>. This is because control of the mouse (possibly including capture) is held by the originating element of the drag until the drop is completed, with much of the behavior controlled by underlying [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] calls. Try the following approaches instead:  
+ During drag-and-drop operations, the position of the mouse cannot be reliably determined through <xref:System.Windows.Input.Mouse.GetPosition%2A>. This is because control of the mouse (possibly including capture) is held by the originating element of the drag until the drop is completed, with much of the behavior controlled by underlying Win32 calls. Try the following approaches instead:  
   
 -   Call the <xref:System.Windows.DragEventArgs.GetPosition%2A> method of the <xref:System.Windows.DragEventArgs> that is passed to the drag events (<xref:System.Windows.ContentElement.DragEnter>, <xref:System.Windows.ContentElement.DragOver>, <xref:System.Windows.ContentElement.DragLeave>).  
   
diff --git a/xml/System.Windows.Interop/CursorInteropHelper.xml b/xml/System.Windows.Interop/CursorInteropHelper.xml
index 159a93356df..364be3804b3 100644
--- a/xml/System.Windows.Interop/CursorInteropHelper.xml
+++ b/xml/System.Windows.Interop/CursorInteropHelper.xml
@@ -48,8 +48,8 @@
       </Parameters>
       <Docs>
         <param name="cursorHandle">Cursor reference to use for interoperation.</param>
-        <summary>Returns a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] <see cref="T:System.Windows.Input.Cursor" /> object based on a provided [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] cursor handle.</summary>
-        <returns>The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] cursor object based on the provided [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] cursor handle.</returns>
+        <summary>Returns a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] <see cref="T:System.Windows.Input.Cursor" /> object based on a provided Win32 cursor handle.</summary>
+        <returns>The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] cursor object based on the provided Win32 cursor handle.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Interop/HwndHost.xml b/xml/System.Windows.Interop/HwndHost.xml
index 776a25d29e8..7edc49fe653 100644
--- a/xml/System.Windows.Interop/HwndHost.xml
+++ b/xml/System.Windows.Interop/HwndHost.xml
@@ -36,7 +36,7 @@
  To host a Win32 window, create a class that derives from <xref:System.Windows.Interop.HwndHost>. Override the <xref:System.Windows.Interop.HwndHost.BuildWindowCore%2A> method and create your Win32 window as a child of the parent window that is passed into the method.  
   
 > [!IMPORTANT]
->  Although <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement>, various properties of <xref:System.Windows.Interop.HwndHost> that come from <xref:System.Windows.FrameworkElement> and other intermediate classes such as <xref:System.Windows.UIElement> are not generally mapped to possible [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] equivalents. Also, not all <xref:System.Windows.FrameworkElement> / <xref:System.Windows.UIElement> input events transfer across the interoperation boundary. <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement> primarily so that an <xref:System.Windows.Interop.HwndHost> instance can be inserted into the widest variety of possible content models, and so that default <xref:System.Windows.FrameworkElement> layout characteristics can apply. For more details on <xref:System.Windows.Interop.HwndHost>, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
+>  Although <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement>, various properties of <xref:System.Windows.Interop.HwndHost> that come from <xref:System.Windows.FrameworkElement> and other intermediate classes such as <xref:System.Windows.UIElement> are not generally mapped to possible Win32 equivalents. Also, not all <xref:System.Windows.FrameworkElement> / <xref:System.Windows.UIElement> input events transfer across the interoperation boundary. <xref:System.Windows.Interop.HwndHost> derives from <xref:System.Windows.FrameworkElement> primarily so that an <xref:System.Windows.Interop.HwndHost> instance can be inserted into the widest variety of possible content models, and so that default <xref:System.Windows.FrameworkElement> layout characteristics can apply. For more details on <xref:System.Windows.Interop.HwndHost>, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
   
  ]]></format>
     </remarks>
@@ -450,7 +450,7 @@
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>In [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)], a window is expected to be the size requested by layout at the time the window is created. Derived classes should override this method only if they have additional information regarding required window size.  
+          <para>In Win32, a window is expected to be the size requested by layout at the time the window is created. Derived classes should override this method only if they have additional information regarding required window size.  
   
  The specific implementation here is already an override of the <see cref="T:System.Windows.FrameworkElement" /> virtual member, which bases size constraints on the window handle and treats a zero value in one or more dimensions as a non-constraint. The <see cref="T:System.Windows.Forms.Integration.WindowsFormsHost" /> class also overrides a <see cref="M:System.Windows.Forms.Integration.WindowsFormsHost.MeasureOverride(System.Windows.Size)" /> implementation that will result in a clip of the form if it is too large.</para>
         </block>
@@ -604,7 +604,7 @@
 > [!IMPORTANT]
 >  This type or member is not available in the Internet security zone.  
 >   
->  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyDown%2A> and provides the behavior of translating the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
+>  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyDown%2A> and provides the behavior of translating the Win32 message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
   
  ]]></format>
         </remarks>
@@ -651,7 +651,7 @@
 > [!IMPORTANT]
 >  This type or member is not available in the Internet security zone.  
 >   
->  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyUp%2A> and provides the behavior of translating the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
+>  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyUp%2A> and provides the behavior of translating the Win32 message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Interop/HwndSource.xml b/xml/System.Windows.Interop/HwndSource.xml
index dc88d940822..f042e2b4507 100644
--- a/xml/System.Windows.Interop/HwndSource.xml
+++ b/xml/System.Windows.Interop/HwndSource.xml
@@ -77,7 +77,7 @@
   
  For more information about <xref:System.Windows.Interop.HwndSource> and other interoperation classes, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
   
- Notice how the constructors for <xref:System.Windows.Interop.HwndSource> take parameters that resemble the parameters for [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] functions such as [CreateWindowEx](https://go.microsoft.com/fwlink/?LinkID=98462).  
+ Notice how the constructors for <xref:System.Windows.Interop.HwndSource> take parameters that resemble the parameters for Win32 functions such as [CreateWindowEx](https://go.microsoft.com/fwlink/?LinkID=98462).  
   
  Scale transformations should not be applied to the <xref:System.Windows.Interop.HwndSource.RootVisual%2A> of an <xref:System.Windows.Interop.HwndSource>. See Remarks for <xref:System.Windows.Interop.HwndSource.RootVisual%2A>.  
   
@@ -178,7 +178,7 @@
         <Parameter Name="parent" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
+        <param name="classStyle">The Win32 class styles for the window.</param>
         <param name="style">The Win32 styles for the window.</param>
         <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
@@ -230,7 +230,7 @@
         <Parameter Name="parent" Type="System.IntPtr" />
       </Parameters>
       <Docs>
-        <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
+        <param name="classStyle">The Win32 class styles for the window.</param>
         <param name="style">The Win32 styles for the window.</param>
         <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
@@ -285,7 +285,7 @@
         <Parameter Name="adjustSizingForNonClientArea" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="classStyle">The [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] class styles for the window.</param>
+        <param name="classStyle">The Win32 class styles for the window.</param>
         <param name="style">The Win32 styles for the window.</param>
         <param name="exStyle">The extended Win32 styles for the window.</param>
         <param name="x">The position of the window's left edge.</param>
@@ -384,7 +384,7 @@
 > [!IMPORTANT]
 >  This method is not available in the Internet security zone.  
   
- Most [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] messages that reach the <xref:System.Windows.Interop.HwndSource> have an approximate WPF equivalent. You use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to handle the cases where the message has no WPF equivalent.  
+ Most Win32 messages that reach the <xref:System.Windows.Interop.HwndSource> have an approximate WPF equivalent. You use <xref:System.Windows.Interop.HwndSource.AddHook%2A> to handle the cases where the message has no WPF equivalent.  
   
  The <xref:System.Windows.Interop.HwndSourceHook> delegate resembles the parameter profile of a Win32 main window procedure. All window messages that the main window procedure of the <xref:System.Windows.Interop.HwndSource> parent window receives are also forwarded to the <xref:System.Windows.Interop.HwndSourceHook> delegates.  
   
diff --git a/xml/System.Windows.Interop/HwndSourceParameters.xml b/xml/System.Windows.Interop/HwndSourceParameters.xml
index 54d99961d8a..2a4147521ac 100644
--- a/xml/System.Windows.Interop/HwndSourceParameters.xml
+++ b/xml/System.Windows.Interop/HwndSourceParameters.xml
@@ -169,7 +169,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Window> class sets this parameter to `true` when using this structure internally, as part of its [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] window-creation process.  
+ The <xref:System.Windows.Window> class sets this parameter to `true` when using this structure internally, as part of its Win32 window-creation process.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Interop/IKeyboardInputSink.xml b/xml/System.Windows.Interop/IKeyboardInputSink.xml
index 2510f9b1890..aed60559929 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSink.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSink.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A keyboard sink handles input from particular subsets of the overall keyboard input model for [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] and [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], and enables some keyboard input to be processed and directed to HWNDs other than the one with current keyboard focus.  
+ A keyboard sink handles input from particular subsets of the overall keyboard input model for Win32 and [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], and enables some keyboard input to be processed and directed to HWNDs other than the one with current keyboard focus.  
   
  If your component contains other components, and maintains a tab order, your component must also implement <xref:System.Windows.Interop.IKeyboardInputSite> and keep track of which component has focus.  
   
diff --git a/xml/System.Windows.Interop/MSG.xml b/xml/System.Windows.Interop/MSG.xml
index 42a180fdf18..339726fd395 100644
--- a/xml/System.Windows.Interop/MSG.xml
+++ b/xml/System.Windows.Interop/MSG.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This type provides similar information to the unmanaged [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] [MSG structure](/windows/win32/api/winuser/ns-winuser-msg).  
+ This type provides similar information to the unmanaged Win32 [MSG structure](/windows/win32/api/winuser/ns-winuser-msg).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index cbfda359680..7c50a51a478 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -80,7 +80,7 @@ Example of typefaces that are members of the "Times New Roman" font family
   
  InWPF, the font fallback mechanism uses the default fallback font family, "Global User Interface", as the substitute font. This font is defined as a composite font, whose file name is "GlobalUserInterface.CompositeFont". For more information about composite fonts, see the Composite Fonts section in this topic.  
   
- The WPF font fallback mechanism replaces previous [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] font substitution technologies.  
+ The WPF font fallback mechanism replaces previous Win32 font substitution technologies.  
   
 ## Defining a Font Fallback Sequence in Code  
  You can define a font fallback sequence in your code, which lets you define an alternate font. When you create a <xref:System.Windows.Media.FontFamily> object, provide multiple font family names, separated by commas, for the <xref:System.String> parameter, such as "Comic Sans MS, Verdana". In this case, if the glyphs from the "Comic Sans MS" typeface are not available, glyphs from the "Verdana" typeface are used. If neither "Comic Sans MS" nor "Verdana" have the required glyphs, the fallback font family of the typeface is used, which is "Global User Interface" by default.  
diff --git a/xml/System.Windows.Media/Visual.xml b/xml/System.Windows.Media/Visual.xml
index 4b881b18d67..928ce7df34e 100644
--- a/xml/System.Windows.Media/Visual.xml
+++ b/xml/System.Windows.Media/Visual.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Media.Visual> class is the basic abstraction from which every <xref:System.Windows.FrameworkElement> object derives. It also serves as the entry point for writing new controls in WPF, and in many ways can be thought of as an equivalent of a window handle (HWND) in the [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] application model.  
+ The <xref:System.Windows.Media.Visual> class is the basic abstraction from which every <xref:System.Windows.FrameworkElement> object derives. It also serves as the entry point for writing new controls in WPF, and in many ways can be thought of as an equivalent of a window handle (HWND) in the Win32 application model.  
   
  The <xref:System.Windows.Media.Visual> object is a core WPF object, whose primary role is to provide rendering support. User interface controls, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBox>, derive from the <xref:System.Windows.Media.Visual> class, and use the <xref:System.Windows.Media.Visual> defined properties for persisting their rendering data. The <xref:System.Windows.Media.Visual> object provides support for the following:  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 2476360d19c..394185e7e4a 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -557,7 +557,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.ComponentModel.Win32Exception">A [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] error is raised by the <see langword="InternetGetCookie" /> function (called by <see cref="M:System.Windows.Application.GetCookie(System.Uri)" />) if a problem occurs when attempting to retrieve the specified cookie.</exception>
+        <exception cref="T:System.ComponentModel.Win32Exception">A Win32 error is raised by the <see langword="InternetGetCookie" /> function (called by <see cref="M:System.Windows.Application.GetCookie(System.Uri)" />) if a problem occurs when attempting to retrieve the specified cookie.</exception>
         <altmember cref="M:System.Windows.Application.SetCookie(System.Uri,System.String)" />
       </Docs>
     </Member>
@@ -1947,7 +1947,7 @@ This example illustrates how to use XAML together with application-scope resourc
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.ComponentModel.Win32Exception">A [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] error is raised by the <see langword="InternetSetCookie" /> function (called by <see cref="M:System.Windows.Application.SetCookie(System.Uri,System.String)" />) if a problem occurs when attempting to create the specified cookie.</exception>
+        <exception cref="T:System.ComponentModel.Win32Exception">A Win32 error is raised by the <see langword="InternetSetCookie" /> function (called by <see cref="M:System.Windows.Application.SetCookie(System.Uri,System.String)" />) if a problem occurs when attempting to create the specified cookie.</exception>
         <altmember cref="M:System.Windows.Application.GetCookie(System.Uri)" />
       </Docs>
     </Member>
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 4e92a2658d2..700c655331b 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -43,7 +43,7 @@
   
  <xref:System.Windows.UIElement> also includes APIs that relate to the WPF event model, including methods that can raise specified routed events that are sourced from an element instance.  
   
- In terms of architecture, <xref:System.Windows.UIElement> can be considered roughly equivalent to a window handle in [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)] programming, or an Element in Dynamic HTML (DHTML) programming. <xref:System.Windows.UIElement> is a base element at the WPF core level.  
+ In terms of architecture, <xref:System.Windows.UIElement> can be considered roughly equivalent to a window handle in Win32 programming, or an Element in Dynamic HTML (DHTML) programming. <xref:System.Windows.UIElement> is a base element at the WPF core level.  
   
  A <xref:System.Windows.UIElement> has the following capabilities that are specifically defined by the <xref:System.Windows.UIElement> class:  
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index c93ac8b0507..c4e98e4dd42 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2264,7 +2264,7 @@
         <ReturnType>System.EventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This event is raised to support interoperation with [!INCLUDE[TLA#tla_win32](~/includes/tlasharptla-win32-md.md)]. See <see cref="T:System.Windows.Interop.HwndSource" />.</summary>
+        <summary>This event is raised to support interoperation with Win32. See <see cref="T:System.Windows.Interop.HwndSource" />.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

From 0dcae57bb37f600ab6b84355d195e126c574ad54 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:08:38 -0800
Subject: [PATCH 168/236] tlasharptla-winclient

---
 .../ObservableCollection`1.xml                |  2 +-
 .../IEditableCollectionView.xml               |  2 +-
 .../PresentationTraceSources.xml              |  2 +-
 .../PackWebRequestFactory.xml                 |  2 +-
 xml/System.IO.Packaging/Package.xml           |  2 +-
 xml/System.Printing/PrintQueue.xml            |  8 +++----
 .../PrintingCanceledException.xml             |  2 +-
 .../AutomationPeer.xml                        | 14 ++++++------
 .../ButtonAutomationPeer.xml                  |  2 +-
 .../ComboBoxAutomationPeer.xml                | 12 +++++-----
 .../ExpanderAutomationPeer.xml                |  6 ++---
 .../GridSplitterAutomationPeer.xml            | 12 +++++-----
 .../GridViewColumnHeaderAutomationPeer.xml    | 14 ++++++------
 .../HyperlinkAutomationPeer.xml               |  2 +-
 .../ListBoxItemAutomationPeer.xml             |  2 +-
 .../MenuItemAutomationPeer.xml                | 12 +++++-----
 .../PasswordBoxAutomationPeer.xml             |  6 ++---
 .../ProgressBarAutomationPeer.xml             |  8 +++----
 .../RadioButtonAutomationPeer.xml             | 10 ++++-----
 .../RangeBaseAutomationPeer.xml               | 14 ++++++------
 .../RepeatButtonAutomationPeer.xml            |  2 +-
 .../ScrollViewerAutomationPeer.xml            | 16 +++++++-------
 .../SelectorAutomationPeer.xml                |  6 ++---
 .../SelectorItemAutomationPeer.xml            | 10 ++++-----
 .../TabControlAutomationPeer.xml              |  2 +-
 .../TabItemAutomationPeer.xml                 |  2 +-
 .../TextBoxAutomationPeer.xml                 |  6 ++---
 .../ToggleButtonAutomationPeer.xml            |  4 ++--
 .../TreeViewItemAutomationPeer.xml            | 18 +++++++--------
 .../AutomationElement.xml                     |  4 ++--
 .../DocumentPageView.xml                      |  4 ++--
 .../DocumentViewerBase.xml                    |  6 ++---
 .../GridViewRowPresenterBase.xml              |  2 +-
 .../Selector.xml                              |  2 +-
 .../AdornedElementPlaceholder.xml             |  4 ++--
 .../ContentControl.xml                        |  4 ++--
 xml/System.Windows.Controls/Decorator.xml     |  4 ++--
 .../FlowDocumentReader.xml                    |  4 ++--
 .../FlowDocumentScrollViewer.xml              |  6 ++---
 xml/System.Windows.Controls/Grid.xml          |  4 ++--
 xml/System.Windows.Controls/Image.xml         |  2 +-
 .../ItemCollection.xml                        |  8 +++----
 .../ItemContainerGenerator.xml                |  6 ++---
 xml/System.Windows.Controls/ItemsControl.xml  |  4 ++--
 xml/System.Windows.Controls/ListView.xml      |  2 +-
 xml/System.Windows.Controls/MediaElement.xml  |  2 +-
 xml/System.Windows.Controls/Panel.xml         |  4 ++--
 xml/System.Windows.Controls/RichTextBox.xml   |  4 ++--
 xml/System.Windows.Controls/ScrollViewer.xml  |  2 +-
 xml/System.Windows.Controls/TextBlock.xml     | 14 ++++++------
 xml/System.Windows.Controls/ToolBarTray.xml   |  4 ++--
 .../ToolTipService.xml                        |  2 +-
 .../UIElementCollection.xml                   | 16 +++++++-------
 xml/System.Windows.Controls/UserControl.xml   |  2 +-
 xml/System.Windows.Controls/Viewport3D.xml    |  4 ++--
 xml/System.Windows.Data/Binding.xml           |  2 +-
 xml/System.Windows.Data/BindingExpression.xml |  2 +-
 .../BindingExpressionBase.xml                 |  2 +-
 .../BindingListCollectionView.xml             |  2 +-
 .../CollectionContainer.xml                   |  2 +-
 .../CompositeCollection.xml                   | 12 +++++-----
 .../DataSourceProvider.xml                    |  6 ++---
 .../ListCollectionView.xml                    |  2 +-
 xml/System.Windows.Data/PriorityBinding.xml   |  4 ++--
 xml/System.Windows.Data/RelativeSource.xml    |  4 ++--
 xml/System.Windows.Data/XmlDataProvider.xml   |  2 +-
 .../XmlNamespaceMapping.xml                   |  4 ++--
 .../ListItemStructure.xml                     |  2 +-
 xml/System.Windows.Documents/FlowDocument.xml |  2 +-
 xml/System.Windows.Documents/Section.xml      |  2 +-
 .../TableCellCollection.xml                   |  6 ++---
 .../TableColumnCollection.xml                 |  6 ++---
 .../TableRowCollection.xml                    |  6 ++---
 .../TableRowGroupCollection.xml               |  6 ++---
 .../TextElementCollection`1.xml               |  2 +-
 xml/System.Windows.Documents/TextPointer.xml  |  4 ++--
 .../ElementHost.xml                           | 18 +++++++--------
 .../PropertyMap.xml                           |  2 +-
 .../WindowsFormsHost.xml                      |  2 +-
 xml/System.Windows.Input/ICommand.xml         |  2 +-
 xml/System.Windows.Input/InputManager.xml     |  4 ++--
 xml/System.Windows.Input/InputScopePhrase.xml |  6 ++---
 xml/System.Windows.Input/Keyboard.xml         |  2 +-
 xml/System.Windows.Input/KeyboardDevice.xml   |  4 ++--
 .../ManipulationDelta.xml                     |  2 +-
 xml/System.Windows.Input/ModifierKeys.xml     |  2 +-
 xml/System.Windows.Input/Mouse.xml            | 10 ++++-----
 xml/System.Windows.Input/MouseDevice.xml      |  2 +-
 xml/System.Windows.Input/Touch.xml            |  2 +-
 .../TouchFrameEventArgs.xml                   |  2 +-
 .../BrowserInteropHelper.xml                  |  2 +-
 .../CursorInteropHelper.xml                   |  4 ++--
 xml/System.Windows.Interop/DocObjHost.xml     |  4 ++--
 xml/System.Windows.Interop/HwndHost.xml       |  4 ++--
 .../HwndSourceParameters.xml                  |  6 ++---
 .../IKeyboardInputSink.xml                    |  2 +-
 .../WindowInteropHelper.xml                   |  8 +++----
 .../RuntimeNamePropertyAttribute.xml          |  2 +-
 xml/System.Windows.Markup/XamlWriterState.xml |  2 +-
 .../ByteAnimation.xml                         |  2 +-
 .../ColorAnimation.xml                        |  2 +-
 .../DecimalAnimation.xml                      |  2 +-
 .../DoubleAnimation.xml                       |  2 +-
 .../IAnimatable.xml                           |  2 +-
 .../Int16Animation.xml                        |  2 +-
 .../Int32Animation.xml                        |  2 +-
 .../Int64Animation.xml                        |  2 +-
 .../Point3DAnimation.xml                      |  2 +-
 .../PointAnimation.xml                        |  2 +-
 .../QuaternionAnimation.xml                   |  2 +-
 .../RectAnimation.xml                         |  2 +-
 .../Rotation3DAnimation.xml                   |  2 +-
 .../SingleAnimation.xml                       |  2 +-
 .../SizeAnimation.xml                         |  2 +-
 .../ThicknessAnimation.xml                    |  2 +-
 .../TimelineCollection+Enumerator.xml         |  4 ++--
 .../Vector3DAnimation.xml                     |  2 +-
 .../BitmapEffectCollection+Enumerator.xml     |  4 ++--
 .../BitmapCodecInfo.xml                       |  2 +-
 .../BitmapDecoder.xml                         |  2 +-
 .../BitmapMetadata.xml                        | 10 ++++-----
 .../BitmapMetadataBlob.xml                    |  2 +-
 .../BitmapPalette.xml                         |  2 +-
 .../BitmapSource.xml                          |  4 ++--
 .../MaterialCollection+Enumerator.xml         |  4 ++--
 .../Model3DCollection+Enumerator.xml          |  4 ++--
 xml/System.Windows.Media.Media3D/Point3D.xml  |  2 +-
 .../Point3DCollection+Enumerator.xml          |  4 ++--
 xml/System.Windows.Media.Media3D/Point4D.xml  |  2 +-
 .../Quaternion.xml                            |  2 +-
 xml/System.Windows.Media.Media3D/Rect3D.xml   |  2 +-
 .../RotateTransform3D.xml                     |  2 +-
 xml/System.Windows.Media.Media3D/Size3D.xml   |  2 +-
 .../Transform3DCollection+Enumerator.xml      |  4 ++--
 xml/System.Windows.Media.Media3D/Vector3D.xml |  2 +-
 .../Vector3DCollection+Enumerator.xml         |  4 ++--
 .../Visual3DCollection+Enumerator.xml         |  4 ++--
 .../CompositionTarget.xml                     |  4 ++--
 .../DoubleCollection+Enumerator.xml           |  4 ++--
 .../DrawingCollection+Enumerator.xml          |  4 ++--
 xml/System.Windows.Media/DrawingContext.xml   |  2 +-
 xml/System.Windows.Media/FontFamily.xml       |  2 +-
 .../GeneralTransformCollection+Enumerator.xml |  4 ++--
 .../GeometryCollection+Enumerator.xml         |  4 ++--
 .../GeometryHitTestParameters.xml             |  2 +-
 .../GradientStopCollection+Enumerator.xml     |  4 ++--
 .../Int32Collection+Enumerator.xml            |  4 ++--
 xml/System.Windows.Media/Matrix.xml           |  6 ++---
 xml/System.Windows.Media/MatrixTransform.xml  |  2 +-
 .../PathFigureCollection+Enumerator.xml       |  4 ++--
 .../PathSegmentCollection+Enumerator.xml      |  4 ++--
 .../PointCollection+Enumerator.xml            |  4 ++--
 .../StreamGeometryContext.xml                 |  2 +-
 xml/System.Windows.Media/TileBrush.xml        |  2 +-
 xml/System.Windows.Media/Transform.xml        |  2 +-
 .../TransformCollection+Enumerator.xml        |  4 ++--
 .../VectorCollection+Enumerator.xml           |  4 ++--
 xml/System.Windows.Media/VisualBrush.xml      |  4 ++--
 .../JournalEntryListConverter.xml             |  4 ++--
 .../XpsDocument.xml                           |  2 +-
 .../BasePackagingPolicy.xml                   |  2 +-
 xml/System.Windows/Clipboard.xml              |  4 ++--
 xml/System.Windows/DataFormats.xml            |  2 +-
 xml/System.Windows/DependencyObject.xml       |  2 +-
 xml/System.Windows/DependencyProperty.xml     |  2 +-
 xml/System.Windows/EventManager.xml           |  2 +-
 xml/System.Windows/EventRoute.xml             |  2 +-
 .../FrameworkContentElement.xml               |  4 ++--
 xml/System.Windows/FrameworkElement.xml       |  8 +++----
 xml/System.Windows/Freezable.xml              |  2 +-
 .../FreezableCollection`1+Enumerator.xml      |  4 ++--
 xml/System.Windows/IInputElement.xml          | 20 ++++++++---------
 xml/System.Windows/Point.xml                  |  2 +-
 xml/System.Windows/Size.xml                   |  2 +-
 xml/System.Windows/Style.xml                  |  2 +-
 xml/System.Windows/TemplateKey.xml            |  4 ++--
 .../TriggerActionCollection.xml               | 22 +++++++++----------
 xml/System.Windows/UIElement.xml              | 12 +++++-----
 xml/System.Windows/UIElement3D.xml            |  8 +++----
 xml/System.Windows/UIPropertyMetadata.xml     |  2 +-
 xml/System.Windows/Vector.xml                 |  2 +-
 xml/System.Windows/VisualStateManager.xml     |  2 +-
 xml/System.Windows/Window.xml                 |  2 +-
 xml/System.Xaml/XamlServices.xml              |  6 ++---
 184 files changed, 397 insertions(+), 397 deletions(-)

diff --git a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
index bb88ac1ffcb..1fc6bc1f24f 100644
--- a/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
+++ b/xml/System.Collections.ObjectModel/ObservableCollection`1.xml
@@ -90,7 +90,7 @@
  For more information, see "Binding to Collections" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
 ## Notes on XAML Usage  
- <xref:System.Collections.ObjectModel.ObservableCollection%601> can be used as a XAML object element in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], in versions 3.0 and 3.5. However, the usage has substantial limitations.  
+ <xref:System.Collections.ObjectModel.ObservableCollection%601> can be used as a XAML object element in Windows Presentation Foundation (WPF), in versions 3.0 and 3.5. However, the usage has substantial limitations.  
   
 -   <xref:System.Collections.ObjectModel.ObservableCollection%601> must be the root element, because the `x:TypeArguments` attribute that must be used to specify the constrained type of the generic <xref:System.Collections.ObjectModel.ObservableCollection%601> is only supported on the object element for the root element.  
   
diff --git a/xml/System.ComponentModel/IEditableCollectionView.xml b/xml/System.ComponentModel/IEditableCollectionView.xml
index 7ec53228716..b5f6a1d45ff 100644
--- a/xml/System.ComponentModel/IEditableCollectionView.xml
+++ b/xml/System.ComponentModel/IEditableCollectionView.xml
@@ -20,7 +20,7 @@
 ## Remarks  
  When a collection view implements the <xref:System.ComponentModel.IEditableCollectionView> interface, you can directly change the underlying collection, if it allows changes to be made, by using the methods and properties that <xref:System.ComponentModel.IEditableCollectionView> exposes, regardless of the collection's type.  
   
- The types <xref:System.Windows.Controls.ItemCollection>, <xref:System.Windows.Data.BindingListCollectionView>, and <xref:System.Windows.Data.ListCollectionView> are the types that ship with [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] that inherit from <xref:System.Windows.Data.CollectionView>.  These types also implement the <xref:System.ComponentModel.IEditableCollectionView>, so you can edit a collection that uses one of those types.  <xref:System.Windows.Controls.ItemCollection>, in particular, is often used because the <xref:System.Windows.Controls.ItemsControl.Items%2A?displayProperty=nameWithType> property is an <xref:System.Windows.Controls.ItemCollection>.  
+ The types <xref:System.Windows.Controls.ItemCollection>, <xref:System.Windows.Data.BindingListCollectionView>, and <xref:System.Windows.Data.ListCollectionView> are the types that ship with Windows Presentation Foundation (WPF) that inherit from <xref:System.Windows.Data.CollectionView>.  These types also implement the <xref:System.ComponentModel.IEditableCollectionView>, so you can edit a collection that uses one of those types.  <xref:System.Windows.Controls.ItemCollection>, in particular, is often used because the <xref:System.Windows.Controls.ItemsControl.Items%2A?displayProperty=nameWithType> property is an <xref:System.Windows.Controls.ItemCollection>.  
   
    
   
diff --git a/xml/System.Diagnostics/PresentationTraceSources.xml b/xml/System.Diagnostics/PresentationTraceSources.xml
index c6fe858df44..6eb2574c187 100644
--- a/xml/System.Diagnostics/PresentationTraceSources.xml
+++ b/xml/System.Diagnostics/PresentationTraceSources.xml
@@ -29,7 +29,7 @@
   
 -   To configure trace sources, create an application config file. This file has a .config extension, for example, XamlPad.exe.config.  
   
- Achieving optimal application performance requires forethought in application design and an understanding of best practices for [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application development. For more information, see [Optimizing WPF Application Performance](/dotnet/framework/wpf/advanced/optimizing-wpf-application-performance).  
+ Achieving optimal application performance requires forethought in application design and an understanding of best practices for Windows Presentation Foundation (WPF) application development. For more information, see [Optimizing WPF Application Performance](/dotnet/framework/wpf/advanced/optimizing-wpf-application-performance).  
   
    
   
diff --git a/xml/System.IO.Packaging/PackWebRequestFactory.xml b/xml/System.IO.Packaging/PackWebRequestFactory.xml
index ba0cd38039c..eb27622decb 100644
--- a/xml/System.IO.Packaging/PackWebRequestFactory.xml
+++ b/xml/System.IO.Packaging/PackWebRequestFactory.xml
@@ -86,7 +86,7 @@
       </Parameters>
       <Docs>
         <param name="uri">The URI to create the Web request.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="T:System.IO.Packaging.PackUriHelper" /> method instead.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="T:System.IO.Packaging.PackUriHelper" /> method instead.</summary>
         <returns>The pack URI Web request.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.IO.Packaging/Package.xml b/xml/System.IO.Packaging/Package.xml
index a6a187227d8..48cd3aeeb02 100644
--- a/xml/System.IO.Packaging/Package.xml
+++ b/xml/System.IO.Packaging/Package.xml
@@ -2065,7 +2065,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended for application use.  Use the type-safe <see cref="M:System.IO.Packaging.Package.Dispose(System.Boolean)" /> method instead.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended for application use.  Use the type-safe <see cref="M:System.IO.Packaging.Package.Dispose(System.Boolean)" /> method instead.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[
 
diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index 6c60e5bf463..925b39eb469 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -387,7 +387,7 @@
 ## Remarks  
  Unless the queue is paused or in an error state, the job prints when it reaches the top of the queue, so this is a printing function.  
   
- Other ways to print in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
+ Other ways to print in Windows Presentation Foundation (WPF) include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
   
  ]]></format>
         </remarks>
@@ -433,7 +433,7 @@
   
  In the print queue's graphical user interface (GUI), the job has the name "Print System Document". To give the job a different name, use the <xref:System.Printing.PrintQueue.AddJob%28System.String%29> overload.  
   
- Other ways to print in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
+ Other ways to print in Windows Presentation Foundation (WPF) include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
   
    
   
@@ -488,7 +488,7 @@
 > [!CAUTION]
 >  If the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> is not closed with <xref:System.IO.Stream.Close%2A> before the end of the thread in which <xref:System.Printing.PrintQueue.AddJob%2A> is called, then an <xref:System.InvalidOperationException> is thrown when that thread ends because the spooler thread cannot gain control over the <xref:System.IO.Stream> object.  
   
- Other ways to print in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
+ Other ways to print in Windows Presentation Foundation (WPF) include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
   
    
   
@@ -593,7 +593,7 @@
 > [!NOTE]
 >  You cannot apply the <xref:System.STAThreadAttribute> to any method except `Main` and you cannot use <xref:System.Threading.Thread.SetApartmentState%2A> for the `Main` thread.  
   
- Other ways to print in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
+ Other ways to print in Windows Presentation Foundation (WPF) include the <xref:System.Windows.Controls.PrintDialog.PrintDocument%2A?displayProperty=nameWithType> method, which can be used with or without opening the dialog, and the many <xref:System.Windows.Xps.XpsDocumentWriter.Write%2A> and <xref:System.Windows.Xps.XpsDocumentWriter.WriteAsync%2A> methods of the <xref:System.Windows.Xps.XpsDocumentWriter>.  
   
    
   
diff --git a/xml/System.Printing/PrintingCanceledException.xml b/xml/System.Printing/PrintingCanceledException.xml
index 2ef59f33a11..33102d2157f 100644
--- a/xml/System.Printing/PrintingCanceledException.xml
+++ b/xml/System.Printing/PrintingCanceledException.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If you are creating a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application that includes printing functionality and allows print jobs to be canceled, be sure to correctly handle this exception. An unhandled exception of this type can cause a Windows Presentation Foundation application to stop responding.  
+ If you are creating a Windows Presentation Foundation (WPF) application that includes printing functionality and allows print jobs to be canceled, be sure to correctly handle this exception. An unhandled exception of this type can cause a Windows Presentation Foundation application to stop responding.  
   
 > [!CAUTION]
 >  Classes within the <xref:System.Printing> namespace are not supported for use within a Windows service or ASP.NET application or service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.  
diff --git a/xml/System.Windows.Automation.Peers/AutomationPeer.xml b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
index 159c170bd08..5215189a1a0 100644
--- a/xml/System.Windows.Automation.Peers/AutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/AutomationPeer.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When UI Automation queries the root of a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application about an element, the root returns the UI Automation peer for that element. The peer also responds to UI Automation queries about its corresponding element.  
+ When UI Automation queries the root of a Windows Presentation Foundation (WPF) application about an element, the root returns the UI Automation peer for that element. The peer also responds to UI Automation queries about its corresponding element.  
   
  ]]></format>
     </remarks>
@@ -663,7 +663,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Tells UI Automation where in the UI Automation tree to place the <see langword="hwnd" /> being hosted by a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
+        <summary>Tells UI Automation where in the UI Automation tree to place the <see langword="hwnd" /> being hosted by a Windows Presentation Foundation (WPF) element.</summary>
         <returns>This method returns the hosted <see langword="hwnd" /> to UI Automation for controls that host <see langword="hwnd" /> objects.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -673,7 +673,7 @@
   
  The <xref:System.Windows.Automation.Peers.AutomationPeer> that is associated with an element that immediately hosts an `hwnd` must override this method.  
   
- If this method is not overridden, UI Automation places the `hwnd` as a child element of the <xref:System.Windows.Interop.HwndSource> that hosts the whole application. Typically, you want to override this default behavior and set UI Automation to position the hosted `hwnd` parallel to the place where it is located in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] logical tree.  
+ If this method is not overridden, UI Automation places the `hwnd` as a child element of the <xref:System.Windows.Interop.HwndSource> that hosts the whole application. Typically, you want to override this default behavior and set UI Automation to position the hosted `hwnd` parallel to the place where it is located in the Windows Presentation Foundation (WPF) logical tree.  
   
  Except in hosting scenarios, do not allow <xref:System.Windows.Automation.Peers.AutomationPeer> types to override this method.  
   
@@ -1380,7 +1380,7 @@ This method calls the derived implementation of <xref:System.Windows.Automation.
 ## Remarks  
  Examples of main properties include, but are not limited to, <xref:System.Windows.Controls.ContentControl.LogicalChildren%2A> and <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.BoundingRectangle%2A>.  
   
- Typically, updates and notifications happen automatically after the update of the layout in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)]. (The update occurs in response to the <xref:System.Windows.UIElement.LayoutUpdated> event.) Sometimes, however, properties change without raising the <xref:System.Windows.UIElement.LayoutUpdated> event. For example, when the whole <xref:System.Windows.Window> moves, the <xref:System.Windows.UIElement.LayoutUpdated> event is not raised. In this example, the set of <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.BoundingRectangle%2A> objects change because the objects are expressed in screen coordinates. Therefore, the <xref:System.Windows.Window> must call <xref:System.Windows.Automation.Peers.AutomationPeer.InvalidatePeer%2A> on its peer on <xref:System.Windows.Automation.Peers.WindowAutomationPeer>.  
+ Typically, updates and notifications happen automatically after the update of the layout in Windows Presentation Foundation (WPF). (The update occurs in response to the <xref:System.Windows.UIElement.LayoutUpdated> event.) Sometimes, however, properties change without raising the <xref:System.Windows.UIElement.LayoutUpdated> event. For example, when the whole <xref:System.Windows.Window> moves, the <xref:System.Windows.UIElement.LayoutUpdated> event is not raised. In this example, the set of <xref:System.Windows.Automation.Provider.IRawElementProviderFragment.BoundingRectangle%2A> objects change because the objects are expressed in screen coordinates. Therefore, the <xref:System.Windows.Window> must call <xref:System.Windows.Automation.Peers.AutomationPeer.InvalidatePeer%2A> on its peer on <xref:System.Windows.Automation.Peers.WindowAutomationPeer>.  
   
  ]]></format>
         </remarks>
@@ -1578,14 +1578,14 @@ This method calls the derived implementation of <xref:System.Windows.Automation.
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether the element that is associated with this <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> hosts <see langword="hwnds" /> in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)].</summary>
+        <summary>Gets a value that indicates whether the element that is associated with this <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> hosts <see langword="hwnds" /> in Windows Presentation Foundation (WPF).</summary>
         <value>
-          <see langword="true" /> if the element that is associated with this <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> hosts <see langword="hwnds" /> in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)]; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the element that is associated with this <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> hosts <see langword="hwnds" /> in Windows Presentation Foundation (WPF); otherwise, <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Two examples of elements that host `hwnds` in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] are <xref:System.Windows.Forms.Integration.WindowsFormsHost> and <xref:System.Windows.Controls.Primitives.Popup>.  
+ Two examples of elements that host `hwnds` in Windows Presentation Foundation (WPF) are <xref:System.Windows.Forms.Integration.WindowsFormsHost> and <xref:System.Windows.Controls.Primitives.Popup>.  
   
  These peers must also override <xref:System.Windows.Automation.Peers.AutomationPeer.GetHostRawElementProviderCore%2A>.  
   
diff --git a/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
index 00f1d15c188..26fc332277e 100644
--- a/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ButtonAutomationPeer.xml
@@ -152,7 +152,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/ComboBoxAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ComboBoxAutomationPeer.xml
index 12ba4e945ca..7b3a84ff4fa 100644
--- a/xml/System.Windows.Automation.Peers/ComboBoxAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ComboBoxAutomationPeer.xml
@@ -231,7 +231,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -257,7 +257,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -282,7 +282,7 @@
         <ReturnType>System.Windows.Automation.ExpandCollapseState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The <see cref="T:System.Windows.Automation.ExpandCollapseState" /> for the current element.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -308,7 +308,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the value is read-only; <see langword="false" /> if it can be modified.</value>
         <remarks>To be added.</remarks>
@@ -339,7 +339,7 @@
       </Parameters>
       <Docs>
         <param name="val">The string value of a control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -364,7 +364,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>A string value of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/ExpanderAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ExpanderAutomationPeer.xml
index fdd7194c535..4a3028a2fbf 100644
--- a/xml/System.Windows.Automation.Peers/ExpanderAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ExpanderAutomationPeer.xml
@@ -205,7 +205,7 @@ The expander should have automation keyboard focus whenever the actual focus is
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -231,7 +231,7 @@ The expander should have automation keyboard focus whenever the actual focus is
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -256,7 +256,7 @@ The expander should have automation keyboard focus whenever the actual focus is
         <ReturnType>System.Windows.Automation.ExpandCollapseState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The state (expanded or collapsed) of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/GridSplitterAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GridSplitterAutomationPeer.xml
index 2f28160cc84..756fb7fcc64 100644
--- a/xml/System.Windows.Automation.Peers/GridSplitterAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GridSplitterAutomationPeer.xml
@@ -126,7 +126,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can be moved; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -153,7 +153,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can be resized; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -180,7 +180,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can rotate; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -213,7 +213,7 @@
       <Docs>
         <param name="x">Absolute screen coordinates of the left side of the control.</param>
         <param name="y">Absolute screen coordinates of the top of the control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -244,7 +244,7 @@
       <Docs>
         <param name="width">The new width of the window, in pixels.</param>
         <param name="height">The new height of the window, in pixels.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -273,7 +273,7 @@
       </Parameters>
       <Docs>
         <param name="degrees">The number of degrees to rotate the control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/GridViewColumnHeaderAutomationPeer.xml b/xml/System.Windows.Automation.Peers/GridViewColumnHeaderAutomationPeer.xml
index b8fe785373b..7d6f75861c8 100644
--- a/xml/System.Windows.Automation.Peers/GridViewColumnHeaderAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/GridViewColumnHeaderAutomationPeer.xml
@@ -179,7 +179,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -204,7 +204,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can be moved; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -231,7 +231,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can be resized; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -258,7 +258,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element can rotate; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -291,7 +291,7 @@
       <Docs>
         <param name="x">Absolute screen coordinates of the left side of the control.</param>
         <param name="y">Absolute screen coordinates of the top of the control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -322,7 +322,7 @@
       <Docs>
         <param name="width">The new width of the window, in pixels.</param>
         <param name="height">The new height of the window, in pixels.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -351,7 +351,7 @@
       </Parameters>
       <Docs>
         <param name="degrees">The number of degrees to rotate the control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
index f966a6eb13c..6234cf65cae 100644
--- a/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/HyperlinkAutomationPeer.xml
@@ -208,7 +208,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/ListBoxItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ListBoxItemAutomationPeer.xml
index b8b65850d57..5a7ca41f3fb 100644
--- a/xml/System.Windows.Automation.Peers/ListBoxItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ListBoxItemAutomationPeer.xml
@@ -152,7 +152,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
index af42598d331..7b419ca37b5 100644
--- a/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/MenuItemAutomationPeer.xml
@@ -328,7 +328,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -354,7 +354,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -379,7 +379,7 @@ In some circumstances, the element can be on the screen but still not be visible
         <ReturnType>System.Windows.Automation.ExpandCollapseState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The state (expanded or collapsed) of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -406,7 +406,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -432,7 +432,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -457,7 +457,7 @@ In some circumstances, the element can be on the screen but still not be visible
         <ReturnType>System.Windows.Automation.ToggleState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The toggle state of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/PasswordBoxAutomationPeer.xml b/xml/System.Windows.Automation.Peers/PasswordBoxAutomationPeer.xml
index 6ba54e2edc5..fee39725f63 100644
--- a/xml/System.Windows.Automation.Peers/PasswordBoxAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/PasswordBoxAutomationPeer.xml
@@ -187,7 +187,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the value is read-only; <see langword="false" /> if it can be modified.</value>
         <remarks>To be added.</remarks>
@@ -218,7 +218,7 @@
       </Parameters>
       <Docs>
         <param name="value">The value of a control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -243,7 +243,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>A string value of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/ProgressBarAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ProgressBarAutomationPeer.xml
index 556e95df182..7ebb92b0e12 100644
--- a/xml/System.Windows.Automation.Peers/ProgressBarAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ProgressBarAutomationPeer.xml
@@ -153,7 +153,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the value is read-only; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -180,7 +180,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The large-change value.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -210,7 +210,7 @@
       </Parameters>
       <Docs>
         <param name="val">The value to set.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -235,7 +235,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The small-change value.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/RadioButtonAutomationPeer.xml b/xml/System.Windows.Automation.Peers/RadioButtonAutomationPeer.xml
index 34b33a58d9d..db23da9f64a 100644
--- a/xml/System.Windows.Automation.Peers/RadioButtonAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/RadioButtonAutomationPeer.xml
@@ -162,7 +162,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -187,7 +187,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element is selected; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -215,7 +215,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -241,7 +241,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -266,7 +266,7 @@
         <ReturnType>System.Windows.Automation.Provider.IRawElementProviderSimple</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The selection container.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/RangeBaseAutomationPeer.xml b/xml/System.Windows.Automation.Peers/RangeBaseAutomationPeer.xml
index 0b5766a45be..e8895b575fc 100644
--- a/xml/System.Windows.Automation.Peers/RangeBaseAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/RangeBaseAutomationPeer.xml
@@ -104,7 +104,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the range value is read-only; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -131,7 +131,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The large-change value.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -157,7 +157,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The maximum range value supported by the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -183,7 +183,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The minimum range value supported by the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -213,7 +213,7 @@
       </Parameters>
       <Docs>
         <param name="val">The value to set.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -238,7 +238,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The small-change value.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -264,7 +264,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The value of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/RepeatButtonAutomationPeer.xml b/xml/System.Windows.Automation.Peers/RepeatButtonAutomationPeer.xml
index 8e61e3cf7a8..75e101451ac 100644
--- a/xml/System.Windows.Automation.Peers/RepeatButtonAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/RepeatButtonAutomationPeer.xml
@@ -156,7 +156,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
index 67cecb43372..e7e600de0fc 100644
--- a/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ScrollViewerAutomationPeer.xml
@@ -184,7 +184,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Value indicating whether control is can be scrolled in the horizontal direction.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -210,7 +210,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The horizontal scroll position as a percentage of the total content area within the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -236,7 +236,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Returns <see langword="S_OK" /> if successful, or an error value otherwise.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -268,7 +268,7 @@
       <Docs>
         <param name="horizontalAmount">The horizontal increment specific to the control.</param>
         <param name="verticalAmount">The vertical increment specific to the control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -299,7 +299,7 @@
       <Docs>
         <param name="horizontalPercent">Percent scrolled horizontally.</param>
         <param name="verticalPercent">Percent scrolled vertically.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -330,7 +330,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the control can scroll vertically; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -357,7 +357,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The vertical scroll position as a percentage of the total content area within the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -383,7 +383,7 @@
         <ReturnType>System.Double</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Returns <see langword="S_OK" /> if successful, or an error value otherwise.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/SelectorAutomationPeer.xml b/xml/System.Windows.Automation.Peers/SelectorAutomationPeer.xml
index c5932c6d697..54a754e17fb 100644
--- a/xml/System.Windows.Automation.Peers/SelectorAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/SelectorAutomationPeer.xml
@@ -130,7 +130,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if multiple selection is allowed; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -158,7 +158,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A collection of UI Automation providers. true if multiple selection is allowed; otherwise <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -184,7 +184,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Returns <see langword="S_OK" /> if successful, or an error value otherwise.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/SelectorItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/SelectorItemAutomationPeer.xml
index 3fe06cbfbce..d3e0c5f6318 100644
--- a/xml/System.Windows.Automation.Peers/SelectorItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/SelectorItemAutomationPeer.xml
@@ -108,7 +108,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -133,7 +133,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element is selected; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -161,7 +161,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -187,7 +187,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -212,7 +212,7 @@
         <ReturnType>System.Windows.Automation.Provider.IRawElementProviderSimple</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The selection container.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/TabControlAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TabControlAutomationPeer.xml
index e40a33e9a72..5ae3a8f5adf 100644
--- a/xml/System.Windows.Automation.Peers/TabControlAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TabControlAutomationPeer.xml
@@ -179,7 +179,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Returns <see langword="S_OK" /> if successful, or an error value otherwise.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
index 27035809b84..99c200bd032 100644
--- a/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TabItemAutomationPeer.xml
@@ -186,7 +186,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Automation.Peers/TextBoxAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TextBoxAutomationPeer.xml
index 2785e61598d..2e34e917207 100644
--- a/xml/System.Windows.Automation.Peers/TextBoxAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TextBoxAutomationPeer.xml
@@ -167,7 +167,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the value is read-only; <see langword="false" /> if it can be modified.</value>
         <remarks>To be added.</remarks>
@@ -198,7 +198,7 @@
       </Parameters>
       <Docs>
         <param name="value">The value of a control.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -223,7 +223,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>A string value of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/ToggleButtonAutomationPeer.xml b/xml/System.Windows.Automation.Peers/ToggleButtonAutomationPeer.xml
index e5f6e6f7fc7..e889e2f63a9 100644
--- a/xml/System.Windows.Automation.Peers/ToggleButtonAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/ToggleButtonAutomationPeer.xml
@@ -160,7 +160,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -185,7 +185,7 @@
         <ReturnType>System.Windows.Automation.ToggleState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>the toggle state of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation.Peers/TreeViewItemAutomationPeer.xml b/xml/System.Windows.Automation.Peers/TreeViewItemAutomationPeer.xml
index b9fe8e8b94a..d564101b204 100644
--- a/xml/System.Windows.Automation.Peers/TreeViewItemAutomationPeer.xml
+++ b/xml/System.Windows.Automation.Peers/TreeViewItemAutomationPeer.xml
@@ -297,7 +297,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -323,7 +323,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -348,7 +348,7 @@ In some circumstances, the element can be on the screen but still not be visible
         <ReturnType>System.Windows.Automation.ExpandCollapseState</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The state (expanded or collapsed) of the control.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -375,7 +375,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -401,7 +401,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -426,7 +426,7 @@ In some circumstances, the element can be on the screen but still not be visible
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the element is selected; otherwise <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -454,7 +454,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -480,7 +480,7 @@ In some circumstances, the element can be on the screen but still not be visible
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -505,7 +505,7 @@ In some circumstances, the element can be on the screen but still not be visible
         <ReturnType>System.Windows.Automation.Provider.IRawElementProviderSimple</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The selection container.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Automation/AutomationElement.xml b/xml/System.Windows.Automation/AutomationElement.xml
index 55253deb936..a5d14ec6964 100644
--- a/xml/System.Windows.Automation/AutomationElement.xml
+++ b/xml/System.Windows.Automation/AutomationElement.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of user interface (UI), regardless of underlying implementation (such as [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] or Win32).  
+ An <xref:System.Windows.Automation.AutomationElement> corresponds to a piece of user interface (UI), regardless of underlying implementation (such as Windows Presentation Foundation (WPF) or Win32).  
   
  ]]></format>
     </remarks>
@@ -225,7 +225,7 @@
  Instances of user interface (UI) elements are uniquely identified on the desktop by their <xref:System.Windows.Automation.AutomationElement.RuntimeIdProperty> properties.  
   
 > [!NOTE]
->  <xref:System.Windows.Automation.AutomationElement.AutomationIdProperty> is supported by all UI Automation elements in the control view except top-level application windows, UI Automation elements derived from [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] controls that do not have an ID or x:Uid, and UI Automation elements derived from Win32 controls that do not have a control ID.  
+>  <xref:System.Windows.Automation.AutomationElement.AutomationIdProperty> is supported by all UI Automation elements in the control view except top-level application windows, UI Automation elements derived from Windows Presentation Foundation (WPF) controls that do not have an ID or x:Uid, and UI Automation elements derived from Win32 controls that do not have a control ID.  
   
    
   
diff --git a/xml/System.Windows.Controls.Primitives/DocumentPageView.xml b/xml/System.Windows.Controls.Primitives/DocumentPageView.xml
index f3d83d5d9e5..f60c4aac4c9 100644
--- a/xml/System.Windows.Controls.Primitives/DocumentPageView.xml
+++ b/xml/System.Windows.Controls.Primitives/DocumentPageView.xml
@@ -622,7 +622,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.Primitives.DocumentPageView.Dispose" /> method instead.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.Primitives.DocumentPageView.Dispose" /> method instead.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -657,7 +657,7 @@
       </Parameters>
       <Docs>
         <param name="serviceType">An object that specifies the type of service object to get.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.Primitives.DocumentPageView.GetService(System.Type)" /> method instead.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.Primitives.DocumentPageView.GetService(System.Type)" /> method instead.</summary>
         <returns>A service object of type <paramref name="serviceType" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls.Primitives/DocumentViewerBase.xml b/xml/System.Windows.Controls.Primitives/DocumentViewerBase.xml
index 6c88d412099..3e6f76aa897 100644
--- a/xml/System.Windows.Controls.Primitives/DocumentViewerBase.xml
+++ b/xml/System.Windows.Controls.Primitives/DocumentViewerBase.xml
@@ -1608,7 +1608,7 @@
       </Parameters>
       <Docs>
         <param name="serviceType">An object that specifies the type of service object to get.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A service object of type <paramref name="serviceType" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.IServiceProvider" />
@@ -1639,7 +1639,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1668,7 +1668,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls.Primitives/GridViewRowPresenterBase.xml b/xml/System.Windows.Controls.Primitives/GridViewRowPresenterBase.xml
index 5a2c9b620fa..714026275ac 100644
--- a/xml/System.Windows.Controls.Primitives/GridViewRowPresenterBase.xml
+++ b/xml/System.Windows.Controls.Primitives/GridViewRowPresenterBase.xml
@@ -212,7 +212,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="args">Event data.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Controls.Primitives/Selector.xml b/xml/System.Windows.Controls.Primitives/Selector.xml
index 46b9ab8396a..ebba6ac3837 100644
--- a/xml/System.Windows.Controls.Primitives/Selector.xml
+++ b/xml/System.Windows.Controls.Primitives/Selector.xml
@@ -233,7 +233,7 @@
 ## Remarks  
  Use the <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A> attached property to select an item in the <xref:System.Windows.Controls.Primitives.Selector> when you do not explicitly create the item container. An item container is a class that represents an item in the <xref:System.Windows.Controls.Primitives.Selector>.  <xref:System.Windows.Controls.TabItem>, <xref:System.Windows.Controls.ListBoxItem>, and <xref:System.Windows.Controls.ComboBoxItem> are item containers for the controls that inherit from <xref:System.Windows.Controls.Primitives.Selector>, and each defines an **IsSelected** property.  
   
- If you do not explicitly create an item container, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] implicitly creates one and sets the **IsSelected** property on the item container to the value of <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType>. This is the only time <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType> is read.  <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType> is not updated if the selection on the item changes.  
+ If you do not explicitly create an item container, Windows Presentation Foundation (WPF) implicitly creates one and sets the **IsSelected** property on the item container to the value of <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType>. This is the only time <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType> is read.  <xref:System.Windows.Controls.Primitives.Selector.IsSelected%2A?displayProperty=nameWithType> is not updated if the selection on the item changes.  
   
  If you explicitly create an item container, you should use the **IsSelected** property on that class.  
   
diff --git a/xml/System.Windows.Controls/AdornedElementPlaceholder.xml b/xml/System.Windows.Controls/AdornedElementPlaceholder.xml
index 95554e8a682..3d0d94f87a4 100644
--- a/xml/System.Windows.Controls/AdornedElementPlaceholder.xml
+++ b/xml/System.Windows.Controls/AdornedElementPlaceholder.xml
@@ -310,7 +310,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -339,7 +339,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/ContentControl.xml b/xml/System.Windows.Controls/ContentControl.xml
index 7046e29b7ef..327e01e2a5e 100644
--- a/xml/System.Windows.Controls/ContentControl.xml
+++ b/xml/System.Windows.Controls/ContentControl.xml
@@ -813,7 +813,7 @@ Four buttons with different types of content
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -848,7 +848,7 @@ Four buttons with different types of content
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/Decorator.xml b/xml/System.Windows.Controls/Decorator.xml
index 046c2ec6025..d07d9647572 100644
--- a/xml/System.Windows.Controls/Decorator.xml
+++ b/xml/System.Windows.Controls/Decorator.xml
@@ -268,7 +268,7 @@ Border around a TextBox
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -297,7 +297,7 @@ Border around a TextBox
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/FlowDocumentReader.xml b/xml/System.Windows.Controls/FlowDocumentReader.xml
index c7ac5a1aae4..72100db273a 100644
--- a/xml/System.Windows.Controls/FlowDocumentReader.xml
+++ b/xml/System.Windows.Controls/FlowDocumentReader.xml
@@ -2153,7 +2153,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. Use the <see cref="P:System.Windows.Controls.FlowDocumentReader.Document" /> property to add a <see cref="T:System.Windows.Documents.FlowDocument" /> as the content child for the <see cref="T:System.Windows.Controls.FlowDocumentReader" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. Use the <see cref="P:System.Windows.Controls.FlowDocumentReader.Document" /> property to add a <see cref="T:System.Windows.Documents.FlowDocument" /> as the content child for the <see cref="T:System.Windows.Controls.FlowDocumentReader" />.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -2182,7 +2182,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
index 4d51674e7d6..fd68f066942 100644
--- a/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
+++ b/xml/System.Windows.Controls/FlowDocumentScrollViewer.xml
@@ -1525,7 +1525,7 @@
       </Parameters>
       <Docs>
         <param name="serviceType">An object that specifies the type of service object to get.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A service object of type <paramref name="serviceType" />, or <see langword="null" /> if there is no service object of type <paramref name="serviceType" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -1555,7 +1555,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. Use the <see cref="P:System.Windows.Controls.FlowDocumentScrollViewer.Document" /> property to add a <see cref="T:System.Windows.Documents.FlowDocument" /> as the content child for the <see cref="T:System.Windows.Controls.FlowDocumentScrollViewer" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. Use the <see cref="P:System.Windows.Controls.FlowDocumentScrollViewer.Document" /> property to add a <see cref="T:System.Windows.Documents.FlowDocument" /> as the content child for the <see cref="T:System.Windows.Controls.FlowDocumentScrollViewer" />.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1584,7 +1584,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/Grid.xml b/xml/System.Windows.Controls/Grid.xml
index 47397bcff7e..8a23e0a138e 100644
--- a/xml/System.Windows.Controls/Grid.xml
+++ b/xml/System.Windows.Controls/Grid.xml
@@ -1091,7 +1091,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1120,7 +1120,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/Image.xml b/xml/System.Windows.Controls/Image.xml
index 78a5215b504..f5000c71485 100644
--- a/xml/System.Windows.Controls/Image.xml
+++ b/xml/System.Windows.Controls/Image.xml
@@ -612,7 +612,7 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The base URI of the current context.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/ItemCollection.xml b/xml/System.Windows.Controls/ItemCollection.xml
index 1608f60f547..1540e327bca 100644
--- a/xml/System.Windows.Controls/ItemCollection.xml
+++ b/xml/System.Windows.Controls/ItemCollection.xml
@@ -1400,7 +1400,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if access to the <see cref="T:System.Collections.ICollection" /> is synchronized (thread safe); otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -1427,7 +1427,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the <see cref="T:System.Collections.ICollection" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -1459,7 +1459,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Collections.IList" /> has a fixed size; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -1492,7 +1492,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Collections.IList" /> is read only; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Controls/ItemContainerGenerator.xml b/xml/System.Windows.Controls/ItemContainerGenerator.xml
index 793cf853c0a..5a34e3ce592 100644
--- a/xml/System.Windows.Controls/ItemContainerGenerator.xml
+++ b/xml/System.Windows.Controls/ItemContainerGenerator.xml
@@ -571,7 +571,7 @@
       <Docs>
         <param name="position">Removes one or more generated (realized) items.</param>
         <param name="count">The Int32 number of elements to remove, starting at <paramref name="position" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -709,7 +709,7 @@
       <Docs>
         <param name="position">The index of the first element to reuse. <paramref name="position" /> must refer to a previously generated (realized) item.</param>
         <param name="count">The number of elements to reuse, starting at <paramref name="position" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -742,7 +742,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="e">Event data.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Controls/ItemsControl.xml b/xml/System.Windows.Controls/ItemsControl.xml
index 2a91790341d..024e989191b 100644
--- a/xml/System.Windows.Controls/ItemsControl.xml
+++ b/xml/System.Windows.Controls/ItemsControl.xml
@@ -2797,7 +2797,7 @@ ListBox that contains multiple types of objects
       </Parameters>
       <Docs>
         <param name="value">The object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -2832,7 +2832,7 @@ ListBox that contains multiple types of objects
       </Parameters>
       <Docs>
         <param name="text">The text to add.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/ListView.xml b/xml/System.Windows.Controls/ListView.xml
index 2c9f9f39b04..53fbe6f57b2 100644
--- a/xml/System.Windows.Controls/ListView.xml
+++ b/xml/System.Windows.Controls/ListView.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Controls.ListView> is an <xref:System.Windows.Controls.ItemsControl>, which means it can contain a collection of objects of any type (such as string, image, or panel). For more information, see the <xref:System.Windows.Controls.ItemsControl> class.  
   
- The presentation of the data items in a <xref:System.Windows.Controls.ListView> is defined by its view mode, which is specified by the <xref:System.Windows.Controls.ListView.View%2A> property. [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] provides a <xref:System.Windows.Controls.GridView> view mode that partitions the <xref:System.Windows.Controls.ListView> data item content into columns. The properties and methods on <xref:System.Windows.Controls.GridView> and its related classes style and specify the content of the columns.  
+ The presentation of the data items in a <xref:System.Windows.Controls.ListView> is defined by its view mode, which is specified by the <xref:System.Windows.Controls.ListView.View%2A> property. Windows Presentation Foundation (WPF) provides a <xref:System.Windows.Controls.GridView> view mode that partitions the <xref:System.Windows.Controls.ListView> data item content into columns. The properties and methods on <xref:System.Windows.Controls.GridView> and its related classes style and specify the content of the columns.  
   
  The following illustration shows a <xref:System.Windows.Controls.ListView> with a <xref:System.Windows.Controls.GridView> view.  
   
diff --git a/xml/System.Windows.Controls/MediaElement.xml b/xml/System.Windows.Controls/MediaElement.xml
index 6569b5a7289..3d116060585 100644
--- a/xml/System.Windows.Controls/MediaElement.xml
+++ b/xml/System.Windows.Controls/MediaElement.xml
@@ -1466,7 +1466,7 @@ Different gradient spread methods
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The base URI of the current context.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Controls/Panel.xml b/xml/System.Windows.Controls/Panel.xml
index 37708e0025f..7ad42ac1c67 100644
--- a/xml/System.Windows.Controls/Panel.xml
+++ b/xml/System.Windows.Controls/Panel.xml
@@ -750,7 +750,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -779,7 +779,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/RichTextBox.xml b/xml/System.Windows.Controls/RichTextBox.xml
index 58ac6991347..30f230acd86 100644
--- a/xml/System.Windows.Controls/RichTextBox.xml
+++ b/xml/System.Windows.Controls/RichTextBox.xml
@@ -652,7 +652,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -681,7 +681,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/ScrollViewer.xml b/xml/System.Windows.Controls/ScrollViewer.xml
index 61fa28b6f18..d3f3a2799ac 100644
--- a/xml/System.Windows.Controls/ScrollViewer.xml
+++ b/xml/System.Windows.Controls/ScrollViewer.xml
@@ -1292,7 +1292,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control, as part of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] automation infrastructure.</summary>
+        <summary>Provides an appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control, as part of the Windows Presentation Foundation (WPF) automation infrastructure.</summary>
         <returns>The appropriate <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation for this control.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Automation.Peers.AutomationPeer" />
diff --git a/xml/System.Windows.Controls/TextBlock.xml b/xml/System.Windows.Controls/TextBlock.xml
index b57c68944ee..cfba1d2eba5 100644
--- a/xml/System.Windows.Controls/TextBlock.xml
+++ b/xml/System.Windows.Controls/TextBlock.xml
@@ -2482,7 +2482,7 @@
       </Parameters>
       <Docs>
         <param name="serviceType">An object that specifies the type of service object to get.</param>
-        <summary>This method supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This method supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A service object of type <paramref name="serviceType" />, or <see langword="null" /> if there is no service object of type <paramref name="serviceType" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -2518,7 +2518,7 @@
       </Parameters>
       <Docs>
         <param name="child">A <see cref="T:System.Windows.ContentElement" /> for which to generate and return a collection of bounding rectangles.</param>
-        <summary>This method supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.GetRectanglesCore(System.Windows.ContentElement)" /> method instead.</summary>
+        <summary>This method supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.GetRectanglesCore(System.Windows.ContentElement)" /> method instead.</summary>
         <returns>A read-only collection of bounding rectangles for the specified <see cref="T:System.Windows.ContentElement" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -2550,7 +2550,7 @@
         <ReturnType>System.Collections.Generic.IEnumerator&lt;System.Windows.IInputElement&gt;</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="P:System.Windows.Controls.TextBlock.HostedElementsCore" /> property instead.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="P:System.Windows.Controls.TextBlock.HostedElementsCore" /> property instead.</summary>
         <value>Elements hosted by the content host.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -2586,7 +2586,7 @@
       </Parameters>
       <Docs>
         <param name="point">Mouse coordinates relative to the content host.</param>
-        <summary>This method supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.InputHitTestCore(System.Windows.Point)" /> method instead.</summary>
+        <summary>This method supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.InputHitTestCore(System.Windows.Point)" /> method instead.</summary>
         <returns>The element that has been hit.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -2622,7 +2622,7 @@
       </Parameters>
       <Docs>
         <param name="child">The child <see cref="T:System.Windows.UIElement" /> element whose <see cref="P:System.Windows.UIElement.DesiredSize" /> has changed.</param>
-        <summary>This method supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.OnChildDesiredSizeChangedCore(System.Windows.UIElement)" /> method instead.</summary>
+        <summary>This method supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Controls.TextBlock.OnChildDesiredSizeChangedCore(System.Windows.UIElement)" /> method instead.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -2651,7 +2651,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -2680,7 +2680,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/ToolBarTray.xml b/xml/System.Windows.Controls/ToolBarTray.xml
index ff5e0211411..4d0af9b1551 100644
--- a/xml/System.Windows.Controls/ToolBarTray.xml
+++ b/xml/System.Windows.Controls/ToolBarTray.xml
@@ -496,7 +496,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -525,7 +525,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Controls/ToolTipService.xml b/xml/System.Windows.Controls/ToolTipService.xml
index 11e8c507a16..524190da36c 100644
--- a/xml/System.Windows.Controls/ToolTipService.xml
+++ b/xml/System.Windows.Controls/ToolTipService.xml
@@ -1993,7 +1993,7 @@ This is an attached property. For information about how to get the value of this
 ## Remarks  
  Tooltip content can range from a simple text string to more complex objects such as a <xref:System.Windows.Controls.StackPanel> element that has embedded controls and images. However, tooltip content cannot take focus. For example, a <xref:System.Windows.Controls.Button> inside a tooltip cannot receive a <xref:System.Windows.Controls.Primitives.ButtonBase.Click> event.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] provides a <xref:System.Windows.Controls.ToolTipService.ToolTip%2A> control that defines a tooltip and provides properties that you can use to specify tooltip behavior. However, a tooltip can be any element, such as a <xref:System.Windows.Controls.DockPanel> or an <xref:System.Windows.Controls.Image>.  
+ Windows Presentation Foundation (WPF) provides a <xref:System.Windows.Controls.ToolTipService.ToolTip%2A> control that defines a tooltip and provides properties that you can use to specify tooltip behavior. However, a tooltip can be any element, such as a <xref:System.Windows.Controls.DockPanel> or an <xref:System.Windows.Controls.Image>.  
   
  This property is an attached property. For information about how to get or set the value of this property in code, see the <xref:System.Windows.Controls.ToolTipService.GetToolTip%2A> and <xref:System.Windows.Controls.ToolTipService.SetToolTip%2A> methods.  
   
diff --git a/xml/System.Windows.Controls/UIElementCollection.xml b/xml/System.Windows.Controls/UIElementCollection.xml
index 2a7ec1657a5..02c1967cab0 100644
--- a/xml/System.Windows.Controls/UIElementCollection.xml
+++ b/xml/System.Windows.Controls/UIElementCollection.xml
@@ -678,7 +678,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to add.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Add(System.Object)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Add(System.Object)" />.</summary>
         <returns>The position into which the new element was inserted.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Controls.UIElementCollection.Add(System.Windows.UIElement)" />
@@ -709,7 +709,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to locate in the list.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Contains(System.Object)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Contains(System.Object)" />.</summary>
         <returns>
           <see langword="true" /> if the object was found in the list; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
@@ -741,7 +741,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to locate in the list.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.IndexOf(System.Object)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.IndexOf(System.Object)" />.</summary>
         <returns>The index of <paramref name="value" /> if found in the list; otherwise, -1.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Controls.UIElementCollection.IndexOf(System.Windows.UIElement)" />
@@ -774,7 +774,7 @@
       <Docs>
         <param name="index">The zero-based index at which <paramref name="value" /> should be inserted.</param>
         <param name="value">The object to insert to the list.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Insert(System.Int32,System.Object)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Insert(System.Int32,System.Object)" />.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Controls.UIElementCollection.Insert(System.Int32,System.Windows.UIElement)" />
       </Docs>
@@ -800,7 +800,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.IsFixedSize" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.IsFixedSize" />.</summary>
         <value>
           <see langword="true" /> if the list has a fixed size; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -827,7 +827,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.IsReadOnly" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.IsReadOnly" />.</summary>
         <value>
           <see langword="true" /> if the list is read-only; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -864,7 +864,7 @@
       </Parameters>
       <Docs>
         <param name="index">The zero-based index of the element to get or set.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.Item(System.Int32)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="P:System.Collections.IList.Item(System.Int32)" />.</summary>
         <value>The element at the specified index.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -894,7 +894,7 @@
       </Parameters>
       <Docs>
         <param name="value">The object to remove from the list.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Remove(System.Object)" />.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.Collections.IList.Remove(System.Object)" />.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Controls.UIElementCollection.Remove(System.Windows.UIElement)" />
       </Docs>
diff --git a/xml/System.Windows.Controls/UserControl.xml b/xml/System.Windows.Controls/UserControl.xml
index 222164d9978..524a833fb55 100644
--- a/xml/System.Windows.Controls/UserControl.xml
+++ b/xml/System.Windows.Controls/UserControl.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Controls in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] support rich content, styles, triggers, and templates. In many cases, these features allow you to create custom and consistent experiences without having to create a new control. For more information, see [Styling and Templating](/dotnet/framework/wpf/controls/styling-and-templating).  
+ Controls in Windows Presentation Foundation (WPF) support rich content, styles, triggers, and templates. In many cases, these features allow you to create custom and consistent experiences without having to create a new control. For more information, see [Styling and Templating](/dotnet/framework/wpf/controls/styling-and-templating).  
   
  If you do need to create a new control, the simplest way is to create a class that derives from <xref:System.Windows.Controls.UserControl>. Before you do so, consider that your control will not support templates and therefore will not support complex customization. However, deriving from <xref:System.Windows.Controls.UserControl> is a suitable model if you want to build your control by adding existing elements to it, similar to how you build an application, and if you do not need to support complex customization. (If you want to use templates with your control, derive from <xref:System.Windows.Controls.Control> instead.) For more information about the different models for authoring controls, see [Control Authoring Overview](/dotnet/framework/wpf/controls/control-authoring-overview).  
   
diff --git a/xml/System.Windows.Controls/Viewport3D.xml b/xml/System.Windows.Controls/Viewport3D.xml
index 6ebad564d60..8ed1a4d1c5c 100644
--- a/xml/System.Windows.Controls/Viewport3D.xml
+++ b/xml/System.Windows.Controls/Viewport3D.xml
@@ -324,7 +324,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -353,7 +353,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 54a35b8b036..5a668ba3bb0 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] data binding provides a simple and consistent way for applications to present and interact with data. Data binding enables you to synchronize the values of the properties of two different objects.  
+ Windows Presentation Foundation (WPF) data binding provides a simple and consistent way for applications to present and interact with data. Data binding enables you to synchronize the values of the properties of two different objects.  
   
  To establish a binding, use the <xref:System.Windows.Data.Binding> class or one of the other classes that inherit <xref:System.Windows.Data.BindingBase>. Regardless of what object you are binding and the nature of your data source, each binding follows the model illustrated by the following figure.  
   
diff --git a/xml/System.Windows.Data/BindingExpression.xml b/xml/System.Windows.Data/BindingExpression.xml
index 083e8f0fc7b..b0046154a54 100644
--- a/xml/System.Windows.Data/BindingExpression.xml
+++ b/xml/System.Windows.Data/BindingExpression.xml
@@ -171,7 +171,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method. This only recognizes manager objects of type <see cref="T:System.Collections.Specialized.CollectionChangedEventManager" />.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="e">Event data.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Data/BindingExpressionBase.xml b/xml/System.Windows.Data/BindingExpressionBase.xml
index e33fc38c5b7..5c1e81c64fd 100644
--- a/xml/System.Windows.Data/BindingExpressionBase.xml
+++ b/xml/System.Windows.Data/BindingExpressionBase.xml
@@ -240,7 +240,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method. This only recognizes manager objects of type <see cref="T:System.Collections.Specialized.CollectionChangedEventManager" />.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="e">Event data.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Data/BindingListCollectionView.xml b/xml/System.Windows.Data/BindingListCollectionView.xml
index 44e0e228ea1..c778a630a17 100644
--- a/xml/System.Windows.Data/BindingListCollectionView.xml
+++ b/xml/System.Windows.Data/BindingListCollectionView.xml
@@ -1601,7 +1601,7 @@
       <Docs>
         <param name="o1">First object to compare.</param>
         <param name="o2">Second object to compare.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>Less than zero means <paramref name="o1" /> is less than <paramref name="o2" />, a value of zero means they are equal, and over zero means <paramref name="o1" /> is greater than <paramref name="o2" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Data/CollectionContainer.xml b/xml/System.Windows.Data/CollectionContainer.xml
index 71df648ac70..caaa8bae5e0 100644
--- a/xml/System.Windows.Data/CollectionContainer.xml
+++ b/xml/System.Windows.Data/CollectionContainer.xml
@@ -302,7 +302,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method. This only recognizes manager objects of type <see cref="T:System.Collections.Specialized.CollectionChangedEventManager" />.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="e">Event data.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Data/CompositeCollection.xml b/xml/System.Windows.Data/CompositeCollection.xml
index d13377096b3..6af2eec9ccd 100644
--- a/xml/System.Windows.Data/CompositeCollection.xml
+++ b/xml/System.Windows.Data/CompositeCollection.xml
@@ -495,7 +495,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>true if access to the <see cref="T:System.Collections.ICollection" /> is synchronized (thread safe); otherwise, false.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -521,7 +521,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the <see cref="T:System.Collections.ICollection" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -574,7 +574,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Collections.IList" /> has a fixed size; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -601,7 +601,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Collections.IList" /> is read-only; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -653,7 +653,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The view created.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -693,7 +693,7 @@
         <param name="managerType">The type of the <see cref="T:System.Windows.WeakEventManager" /> calling this method. This only recognizes manager objects of type <see cref="T:System.Collections.Specialized.CollectionChangedEventManager" />.</param>
         <param name="sender">Object that originated the event.</param>
         <param name="e">Event data.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the listener handled the event; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Data/DataSourceProvider.xml b/xml/System.Windows.Data/DataSourceProvider.xml
index 69bae005f1c..a8b9b9d8952 100644
--- a/xml/System.Windows.Data/DataSourceProvider.xml
+++ b/xml/System.Windows.Data/DataSourceProvider.xml
@@ -30,7 +30,7 @@
 ## Remarks  
  <xref:System.Windows.Data.DataSourceProvider> is a convenience wrapper around an existing data model; it does not replace any data model. A data provider does not attempt to condense the complexity and versatility of a data model such as ADO into one single object with a few properties.  
   
- <xref:System.Windows.Data.DataSourceProvider> is an abstract class. Use one of the derived classes, which are <xref:System.Windows.Data.XmlDataProvider> and <xref:System.Windows.Data.ObjectDataProvider>. The <xref:System.Windows.Data.DataSourceProvider> is aware of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] threading and dispatcher model. It assumes the thread at creation time to be the UI thread. Events will get marshaled from a worker thread to the UI thread of the application.  
+ <xref:System.Windows.Data.DataSourceProvider> is an abstract class. Use one of the derived classes, which are <xref:System.Windows.Data.XmlDataProvider> and <xref:System.Windows.Data.ObjectDataProvider>. The <xref:System.Windows.Data.DataSourceProvider> is aware of the Windows Presentation Foundation (WPF) threading and dispatcher model. It assumes the thread at creation time to be the UI thread. Events will get marshaled from a worker thread to the UI thread of the application.  
   
  ]]></format>
     </remarks>
@@ -627,7 +627,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -659,7 +659,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Data/ListCollectionView.xml b/xml/System.Windows.Data/ListCollectionView.xml
index 7bd9e3f74c9..bb595f02c3d 100644
--- a/xml/System.Windows.Data/ListCollectionView.xml
+++ b/xml/System.Windows.Data/ListCollectionView.xml
@@ -1946,7 +1946,7 @@
       <Docs>
         <param name="o1">The first object to compare.</param>
         <param name="o2">The second object to compare.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A value that is less than zero means <paramref name="o1" /> is less than <paramref name="o2;" /> a value of zero means the objects are equal; and a value that is over zero means <paramref name="o1" /> is greater than <paramref name="o2" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Data/PriorityBinding.xml b/xml/System.Windows.Data/PriorityBinding.xml
index 98dc93299d7..bf85c701fa9 100644
--- a/xml/System.Windows.Data/PriorityBinding.xml
+++ b/xml/System.Windows.Data/PriorityBinding.xml
@@ -193,7 +193,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -222,7 +222,7 @@
       </Parameters>
       <Docs>
         <param name="text">A string to add to the object.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Data/RelativeSource.xml b/xml/System.Windows.Data/RelativeSource.xml
index 0aa0ee5a807..53bec353e24 100644
--- a/xml/System.Windows.Data/RelativeSource.xml
+++ b/xml/System.Windows.Data/RelativeSource.xml
@@ -512,7 +512,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -538,7 +538,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index 6b216798928..a2feafe8577 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -460,7 +460,7 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The base URI.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Data/XmlNamespaceMapping.xml b/xml/System.Windows.Data/XmlNamespaceMapping.xml
index 919fcd0ca51..cdd590075f8 100644
--- a/xml/System.Windows.Data/XmlNamespaceMapping.xml
+++ b/xml/System.Windows.Data/XmlNamespaceMapping.xml
@@ -267,7 +267,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -293,7 +293,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Documents.DocumentStructures/ListItemStructure.xml b/xml/System.Windows.Documents.DocumentStructures/ListItemStructure.xml
index c9e34ee447c..0996abec93e 100644
--- a/xml/System.Windows.Documents.DocumentStructures/ListItemStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/ListItemStructure.xml
@@ -207,7 +207,7 @@
       </Parameters>
       <Docs>
         <param name="value">The child <see cref="T:System.Object" /> that is added.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Documents/FlowDocument.xml b/xml/System.Windows.Documents/FlowDocument.xml
index e46355fa381..e7c3553088e 100644
--- a/xml/System.Windows.Documents/FlowDocument.xml
+++ b/xml/System.Windows.Documents/FlowDocument.xml
@@ -2264,7 +2264,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>When overridden in a derived class, provides specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>When overridden in a derived class, provides specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the Windows Presentation Foundation (WPF) infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Documents/Section.xml b/xml/System.Windows.Documents/Section.xml
index bbaf78440ce..78055db1938 100644
--- a/xml/System.Windows.Documents/Section.xml
+++ b/xml/System.Windows.Documents/Section.xml
@@ -221,7 +221,7 @@
       </Parameters>
       <Docs>
         <param name="manager">A serialization service manager object for this object.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the <see cref="P:System.Windows.Documents.Section.Blocks" /> property should be serialized; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Windows.Documents/TableCellCollection.xml b/xml/System.Windows.Documents/TableCellCollection.xml
index 62df3f5fd40..e6cf8eaec90 100644
--- a/xml/System.Windows.Documents/TableCellCollection.xml
+++ b/xml/System.Windows.Documents/TableCellCollection.xml
@@ -394,7 +394,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -420,7 +420,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -604,7 +604,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the collection.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Documents/TableColumnCollection.xml b/xml/System.Windows.Documents/TableColumnCollection.xml
index 14308e6e08b..697d9ccf7d2 100644
--- a/xml/System.Windows.Documents/TableColumnCollection.xml
+++ b/xml/System.Windows.Documents/TableColumnCollection.xml
@@ -395,7 +395,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -421,7 +421,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -605,7 +605,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the collection.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Documents/TableRowCollection.xml b/xml/System.Windows.Documents/TableRowCollection.xml
index 7fd635e118e..3b72bb0d0dc 100644
--- a/xml/System.Windows.Documents/TableRowCollection.xml
+++ b/xml/System.Windows.Documents/TableRowCollection.xml
@@ -395,7 +395,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -421,7 +421,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -605,7 +605,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the collection.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Documents/TableRowGroupCollection.xml b/xml/System.Windows.Documents/TableRowGroupCollection.xml
index ad3844738df..76ed73993fd 100644
--- a/xml/System.Windows.Documents/TableRowGroupCollection.xml
+++ b/xml/System.Windows.Documents/TableRowGroupCollection.xml
@@ -395,7 +395,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -421,7 +421,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>Currently, this property always returns <see langword="false" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -605,7 +605,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the collection.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Documents/TextElementCollection`1.xml b/xml/System.Windows.Documents/TextElementCollection`1.xml
index df236b4b21c..4808c64b069 100644
--- a/xml/System.Windows.Documents/TextElementCollection`1.xml
+++ b/xml/System.Windows.Documents/TextElementCollection`1.xml
@@ -612,7 +612,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Documents.TextElementCollection`1.Clear" /> method instead.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  Use the type-safe <see cref="M:System.Windows.Documents.TextElementCollection`1.Clear" /> method instead.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Documents/TextPointer.xml b/xml/System.Windows.Documents/TextPointer.xml
index 8a6eae2a869..f7a7737a939 100644
--- a/xml/System.Windows.Documents/TextPointer.xml
+++ b/xml/System.Windows.Documents/TextPointer.xml
@@ -41,7 +41,7 @@
   
 -   Document - The content in a text container is referred to as a *document*, as in the <xref:System.Windows.Documents.TextPointer.IsInSameDocument%2A> method and the <xref:System.Windows.Documents.TextPointer.DocumentStart%2A> and <xref:System.Windows.Documents.TextPointer.DocumentEnd%2A> properties.  
   
- The <xref:System.Windows.Documents.TextPointer> class is intended to facilitate traversal and manipulation of content that is represented by [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] flow content elements; in general, such elements derive from <xref:System.Windows.Documents.TextElement>.  Some of the operations that <xref:System.Windows.Documents.TextPointer> facilitates include the following:  
+ The <xref:System.Windows.Documents.TextPointer> class is intended to facilitate traversal and manipulation of content that is represented by Windows Presentation Foundation (WPF) flow content elements; in general, such elements derive from <xref:System.Windows.Documents.TextElement>.  Some of the operations that <xref:System.Windows.Documents.TextPointer> facilitates include the following:  
   
 -   Perform an ordinal comparison of the current position with a second specified position.  See the <xref:System.Windows.Documents.TextPointer.CompareTo%2A> method.  
   
@@ -1217,7 +1217,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The string that represents the object.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Forms.Integration/ElementHost.xml b/xml/System.Windows.Forms.Integration/ElementHost.xml
index 1fa86ec995b..7ec0d343c61 100644
--- a/xml/System.Windows.Forms.Integration/ElementHost.xml
+++ b/xml/System.Windows.Forms.Integration/ElementHost.xml
@@ -265,7 +265,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the <see cref="T:System.Windows.UIElement" /> hosted by the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control.</summary>
-        <value>The hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</value>
+        <value>The hosted Windows Presentation Foundation (WPF) element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -804,7 +804,7 @@
         <Parameter Name="window" Type="System.Windows.Window" />
       </Parameters>
       <Docs>
-        <param name="window">The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window to be opened modelessly.</param>
+        <param name="window">The Windows Presentation Foundation (WPF) window to be opened modelessly.</param>
         <summary>Enables a <see cref="T:System.Windows.Window" /> to receive keyboard messages correctly when it is opened modelessly from [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)].</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -984,7 +984,7 @@
       </Parameters>
       <Docs>
         <param name="proposedSize">The custom-sized area for a WPF element.</param>
-        <summary>Overrides the base class implementation <see cref="M:System.Windows.Forms.Control.GetPreferredSize(System.Drawing.Size)" /> to provide correct layout behavior for the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] elements.</summary>
+        <summary>Overrides the base class implementation <see cref="M:System.Windows.Forms.Control.GetPreferredSize(System.Drawing.Size)" /> to provide correct layout behavior for the hosted Windows Presentation Foundation (WPF) elements.</summary>
         <returns>The <see cref="T:System.Drawing.Size" /> computed by the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control, given the constraints specified by <paramref name="proposedSize" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Forms.Integration.WindowsFormsHost" />
@@ -1102,7 +1102,7 @@
         <ReturnType>System.Windows.Controls.Panel</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the parent container of the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
+        <summary>Gets the parent container of the hosted Windows Presentation Foundation (WPF) element.</summary>
         <value>The parent container.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1207,7 +1207,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element does not process `charCode`, the <xref:System.Windows.Forms.Integration.ElementHost> control processes it with the <xref:System.Windows.Forms.Control.ProcessDialogChar%2A> method.  
+ If the hosted Windows Presentation Foundation (WPF) element does not process `charCode`, the <xref:System.Windows.Forms.Integration.ElementHost> control processes it with the <xref:System.Windows.Forms.Control.ProcessDialogChar%2A> method.  
   
  ]]></format>
         </remarks>
@@ -2323,7 +2323,7 @@
         <param name="keyData">One of the <see cref="T:System.Windows.Forms.Keys" /> values representing the key to process.</param>
         <summary>Processes a command key, ensuring that the hosted element has an opportunity to handle the command before normal [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] processing.</summary>
         <returns>
-          <see langword="true" /> if the character is a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] shortcut key; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the character is a Windows Presentation Foundation (WPF) shortcut key; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2359,7 +2359,7 @@
         <param name="charCode">The character to process.</param>
         <summary>Processes a mnemonic character, ensuring that the hosted element has an opportunity to handle the mnemonic before normal [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] processing.</summary>
         <returns>
-          <see langword="true" /> if the character is a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] shortcut key; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the character is a Windows Presentation Foundation (WPF) shortcut key; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -2399,7 +2399,7 @@
         <ReturnType>System.Windows.Forms.Integration.PropertyMap</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the property map, which determines how setting properties on the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control affects the hosted [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] element.</summary>
+        <summary>Gets the property map, which determines how setting properties on the <see cref="T:System.Windows.Forms.Integration.ElementHost" /> control affects the hosted Windows Presentation Foundation (WPF) element.</summary>
         <value>A <see cref="T:System.Windows.Forms.Integration.PropertyMap" /> that maps <see cref="T:System.Windows.Forms.Integration.ElementHost" /> to properties on the hosted WPF element.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2604,7 +2604,7 @@
   
  Repeated calls to the <xref:System.Windows.Forms.Integration.ElementHost.Select%2A> method do not traverse the hosted elements. To select subsequent elements, call the <xref:System.Windows.FrameworkElement.MoveFocus%2A> method on the <xref:System.Windows.Forms.Integration.ElementHost.HostContainer%2A> property.  
   
- This implementation forwards tab keys from [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] to [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)].  
+ This implementation forwards tab keys from [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] to Windows Presentation Foundation (WPF).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms.Integration/PropertyMap.xml b/xml/System.Windows.Forms.Integration/PropertyMap.xml
index 768cdb6b5b0..6e10e4251f8 100644
--- a/xml/System.Windows.Forms.Integration/PropertyMap.xml
+++ b/xml/System.Windows.Forms.Integration/PropertyMap.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Windows.Forms.Integration.PropertyMap> class to define translations between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] properties and [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] properties in a hybrid application. The <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A?displayProperty=nameWithType> and <xref:System.Windows.Forms.Integration.WindowsFormsHost.PropertyMap%2A?displayProperty=nameWithType> properties on the <xref:System.Windows.Forms.Integration.ElementHost> and <xref:System.Windows.Forms.Integration.WindowsFormsHost> classes define mappings from one technology to the other.  
+ Use the <xref:System.Windows.Forms.Integration.PropertyMap> class to define translations between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] properties and Windows Presentation Foundation (WPF) properties in a hybrid application. The <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A?displayProperty=nameWithType> and <xref:System.Windows.Forms.Integration.WindowsFormsHost.PropertyMap%2A?displayProperty=nameWithType> properties on the <xref:System.Windows.Forms.Integration.ElementHost> and <xref:System.Windows.Forms.Integration.WindowsFormsHost> classes define mappings from one technology to the other.  
   
  For more information, see [Walkthrough: Mapping Properties Using the ElementHost Control](/dotnet/desktop/wpf/advanced/walkthrough-mapping-properties-using-the-elementhost-control?view=netframeworkdesktop-4.8) and [Walkthrough: Mapping Properties Using the WindowsFormsHost Element](/dotnet/desktop/wpf/advanced/walkthrough-mapping-properties-using-the-windowsformshost-element?view=netframeworkdesktop-4.8).  
   
diff --git a/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml b/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
index 02b603f23d3..65a08674b36 100644
--- a/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
+++ b/xml/System.Windows.Forms.Integration/WindowsFormsHost.xml
@@ -45,7 +45,7 @@
  To host a WPF element in a Windows Forms control or form, use the <xref:System.Windows.Forms.Integration.ElementHost> control.  
   
 > [!NOTE]
->  WindowsFormsIntegration.dll is installed with the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] assemblies. The default location for the assembly is %programfiles%\Reference Assemblies\Microsoft\Framework\v3.0\WindowsFormsIntegration.dll.  
+>  WindowsFormsIntegration.dll is installed with the Windows Presentation Foundation (WPF) assemblies. The default location for the assembly is %programfiles%\Reference Assemblies\Microsoft\Framework\v3.0\WindowsFormsIntegration.dll.  
   
  To host a Windows Forms control in a WPF element, you must assign the Windows Forms control to the <xref:System.Windows.Forms.Integration.WindowsFormsHost.Child%2A> property.  
   
diff --git a/xml/System.Windows.Input/ICommand.xml b/xml/System.Windows.Input/ICommand.xml
index 8d0d6f25f51..d8d1011a579 100644
--- a/xml/System.Windows.Input/ICommand.xml
+++ b/xml/System.Windows.Input/ICommand.xml
@@ -72,7 +72,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Input.RoutedCommand> and <xref:System.Windows.Input.RoutedUICommand> are two implementations of the <xref:System.Windows.Input.ICommand> interface in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)].  
+ <xref:System.Windows.Input.RoutedCommand> and <xref:System.Windows.Input.RoutedUICommand> are two implementations of the <xref:System.Windows.Input.ICommand> interface in Windows Presentation Foundation (WPF).  
   
 ## ICommand in Windows Runtime apps  
  The <xref:System.Windows.Input.ICommand> interface is the code contract for commands that are written in .NET for Windows Runtime apps. These commands provide the commanding behavior for UI elements such as a Windows Runtime XAML `Button` and in particular an `AppBarButton`. If you're defining commands for Windows Runtime apps you use basically the same techniques you'd use for defining commands for a .NET app. Implement the command by defining a class that implements <xref:System.Windows.Input.ICommand> and specifically implement the <xref:System.Windows.Input.ICommand.Execute%2A> method.  
diff --git a/xml/System.Windows.Input/InputManager.xml b/xml/System.Windows.Input/InputManager.xml
index 6c332e929f2..1fc5e612c5e 100644
--- a/xml/System.Windows.Input/InputManager.xml
+++ b/xml/System.Windows.Input/InputManager.xml
@@ -27,7 +27,7 @@
   
  A monitor is any code that listens to <xref:System.Windows.Input.InputManager.PreNotifyInput> or <xref:System.Windows.Input.InputManager.PostNotifyInput>.  Monitors cannot modify the input staging area.  
   
- The <xref:System.Windows.Input.InputManager> controls the input staging area.  The input staging area processes input into [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] events.  
+ The <xref:System.Windows.Input.InputManager> controls the input staging area.  The input staging area processes input into Windows Presentation Foundation (WPF) events.  
   
  Input is processed in WPF in the follow stages:  
   
@@ -334,7 +334,7 @@
         <ReturnType>System.Windows.Input.NotifyInputEventHandler</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Occurs after the <see cref="E:System.Windows.Input.InputManager.PreNotifyInput" /> handlers have finished processing the input and the corresponding [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] events have been raised.</summary>
+        <summary>Occurs after the <see cref="E:System.Windows.Input.InputManager.PreNotifyInput" /> handlers have finished processing the input and the corresponding Windows Presentation Foundation (WPF) events have been raised.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Input/InputScopePhrase.xml b/xml/System.Windows.Input/InputScopePhrase.xml
index 9851da37649..6c6d18a537d 100644
--- a/xml/System.Windows.Input/InputScopePhrase.xml
+++ b/xml/System.Windows.Input/InputScopePhrase.xml
@@ -68,7 +68,7 @@
       </Attributes>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -128,7 +128,7 @@
       </Parameters>
       <Docs>
         <param name="value">An object to add as a child.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -157,7 +157,7 @@
       </Parameters>
       <Docs>
         <param name="name">A string to add.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Input/Keyboard.xml b/xml/System.Windows.Input/Keyboard.xml
index 071af963219..202c25cd8bc 100644
--- a/xml/System.Windows.Input/Keyboard.xml
+++ b/xml/System.Windows.Input/Keyboard.xml
@@ -443,7 +443,7 @@
         <ReturnType>System.Windows.Input.RestoreFocusMode</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the behavior of [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] when restoring focus.</summary>
+        <summary>Gets or sets the behavior of Windows Presentation Foundation (WPF) when restoring focus.</summary>
         <value>An enumeration value that specifies the behavior of WPF when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Input/KeyboardDevice.xml b/xml/System.Windows.Input/KeyboardDevice.xml
index 4ab996593d2..289aebcb340 100644
--- a/xml/System.Windows.Input/KeyboardDevice.xml
+++ b/xml/System.Windows.Input/KeyboardDevice.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.KeyboardDevice> supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  
+ The <xref:System.Windows.Input.KeyboardDevice> supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  
   
  For keyboard related input, use the <xref:System.Windows.Input.Keyboard> class. The <xref:System.Windows.Input.Keyboard> class represents the keyboard to an application and provides methods, properties, and events that reflect the state of the keyboard.  
   
@@ -158,7 +158,7 @@
         <ReturnType>System.Windows.Input.RestoreFocusMode</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the behavior of [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] when restoring focus.</summary>
+        <summary>Gets or sets the behavior of Windows Presentation Foundation (WPF) when restoring focus.</summary>
         <value>An enumeration value that specifies the behavior of WPF when restoring focus. The default in <see cref="F:System.Windows.Input.RestoreFocusMode.Auto" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Input/ManipulationDelta.xml b/xml/System.Windows.Input/ManipulationDelta.xml
index 645f8039a16..d708e825b7c 100644
--- a/xml/System.Windows.Input/ManipulationDelta.xml
+++ b/xml/System.Windows.Input/ManipulationDelta.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.ManipulationDelta> class contains information about the changes in the position of a manipulation.  [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] interprets the changes as a <xref:System.Windows.Input.ManipulationDelta.Translation%2A>, <xref:System.Windows.Input.ManipulationDelta.Expansion%2A>, or <xref:System.Windows.Input.ManipulationDelta.Rotation%2A>. When the <xref:System.Windows.UIElement.ManipulationDelta> event occurs on a <xref:System.Windows.UIElement>, use the properties on a <xref:System.Windows.Input.ManipulationDelta> object to transform the object that should be manipulated.  The <xref:System.Windows.Input.ManipulationDeltaEventArgs> class provides two properties of type <xref:System.Windows.Input.ManipulationDelta>: <xref:System.Windows.Input.ManipulationDeltaEventArgs.DeltaManipulation%2A> and <xref:System.Windows.Input.ManipulationDeltaEventArgs.CumulativeManipulation%2A>.  
+ The <xref:System.Windows.Input.ManipulationDelta> class contains information about the changes in the position of a manipulation.  Windows Presentation Foundation (WPF) interprets the changes as a <xref:System.Windows.Input.ManipulationDelta.Translation%2A>, <xref:System.Windows.Input.ManipulationDelta.Expansion%2A>, or <xref:System.Windows.Input.ManipulationDelta.Rotation%2A>. When the <xref:System.Windows.UIElement.ManipulationDelta> event occurs on a <xref:System.Windows.UIElement>, use the properties on a <xref:System.Windows.Input.ManipulationDelta> object to transform the object that should be manipulated.  The <xref:System.Windows.Input.ManipulationDeltaEventArgs> class provides two properties of type <xref:System.Windows.Input.ManipulationDelta>: <xref:System.Windows.Input.ManipulationDeltaEventArgs.DeltaManipulation%2A> and <xref:System.Windows.Input.ManipulationDeltaEventArgs.CumulativeManipulation%2A>.  
   
  For more information about manipulations, see the [Input Overview](/dotnet/framework/wpf/advanced/input-overview).  For an example of an application that responds to manipulations, see [Walkthrough: Creating Your First Touch Application](/dotnet/framework/wpf/advanced/walkthrough-creating-your-first-touch-application).  
   
diff --git a/xml/System.Windows.Input/ModifierKeys.xml b/xml/System.Windows.Input/ModifierKeys.xml
index 93354a9b6e6..b27dc22e928 100644
--- a/xml/System.Windows.Input/ModifierKeys.xml
+++ b/xml/System.Windows.Input/ModifierKeys.xml
@@ -36,7 +36,7 @@
 ## Remarks  
  The <xref:System.Windows.Input.Keyboard.Modifiers%2A> property on the <xref:System.Windows.Input.Keyboard> class is the set of the modifier keys that are currently pressed.  
   
- Some APIs in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] that make use of the <xref:System.Windows.Input.ModifierKeys> enumeration are the <xref:System.Windows.Input.Keyboard.Modifiers%2A> properties on the <xref:System.Windows.Input.Keyboard>, <xref:System.Windows.Input.KeyBinding>, <xref:System.Windows.Input.KeyGesture>, and <xref:System.Windows.Input.MouseGesture> classes.  
+ Some APIs in Windows Presentation Foundation (WPF) that make use of the <xref:System.Windows.Input.ModifierKeys> enumeration are the <xref:System.Windows.Input.Keyboard.Modifiers%2A> properties on the <xref:System.Windows.Input.Keyboard>, <xref:System.Windows.Input.KeyBinding>, <xref:System.Windows.Input.KeyGesture>, and <xref:System.Windows.Input.MouseGesture> classes.  
   
 <a name="xamlAttributeUsage_ModifierKeys"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Input/Mouse.xml b/xml/System.Windows.Input/Mouse.xml
index 316f759c0ea..ad69e8c650b 100644
--- a/xml/System.Windows.Input/Mouse.xml
+++ b/xml/System.Windows.Input/Mouse.xml
@@ -959,7 +959,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
+ The Windows Presentation Foundation (WPF) framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement> and <xref:System.Windows.ContentElement>: <xref:System.Windows.UIElement.MouseLeftButtonDown> and <xref:System.Windows.UIElement.MouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For a three-button mouse, there is no framework-level event support for the center button. You should use the <xref:System.Windows.Input.Mouse.MouseDown> event and check the <xref:System.Windows.Input.MouseEventArgs.MiddleButton%2A> state in the event arguments.  
   
 > [!IMPORTANT]
 >  A few <xref:System.Windows.ContentElement> derived classes that have control-like behavior, for example, <xref:System.Windows.Documents.Hyperlink>, might have inherent class handling for mouse button events. The left mouse button down event is the most likely event to have class handling in a control. The class handling often marks the underlying <xref:System.Windows.Input.Mouse> class event as handled. Once the event is marked handled, other instance handlers that are attached to that element are not ordinarily raised. Any other class or instance handlers that are attached to elements in the bubbling direction towards the root in the UI tree are also not ordinarily raised.  
@@ -1236,7 +1236,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
+ The Windows Presentation Foundation (WPF) framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.MouseLeftButtonUp> and <xref:System.Windows.UIElement.MouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.MouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.MouseUp> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. The difficulty in making the appropriate choices about whether parent elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events all along the route.  
   
@@ -1347,7 +1347,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In the current [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], the value of this field is 120. The intention of the field exposure is to allow for vendors to build finer-resolution mouse wheels in the future, that perhaps would include a freely rotating wheel without notches. The expectation is that such a device would send more messages per rotation, but with a smaller value in each message. To support this possibility, you should either add the incoming delta values until the <xref:System.Windows.Input.Mouse.MouseWheelDeltaForOneLine> amount is reached (so for a delta-rotation you get the same response), or scroll partial lines in response to the more frequent messages. You could also choose your own scroll granularity and accumulate deltas of your own choosing until that delta is reached, or perhaps reference user-controllable system parameters for mouse sensitivity and extrapolate these to mouse wheel delta thresholds.  
+ In the current Windows Presentation Foundation (WPF), the value of this field is 120. The intention of the field exposure is to allow for vendors to build finer-resolution mouse wheels in the future, that perhaps would include a freely rotating wheel without notches. The expectation is that such a device would send more messages per rotation, but with a smaller value in each message. To support this possibility, you should either add the incoming delta values until the <xref:System.Windows.Input.Mouse.MouseWheelDeltaForOneLine> amount is reached (so for a delta-rotation you get the same response), or scroll partial lines in response to the more frequent messages. You could also choose your own scroll granularity and accumulate deltas of your own choosing until that delta is reached, or perhaps reference user-controllable system parameters for mouse sensitivity and extrapolate these to mouse wheel delta thresholds.  
   
  ]]></format>
         </remarks>
@@ -1448,7 +1448,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
+ The Windows Presentation Foundation (WPF) framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonDown> and <xref:System.Windows.UIElement.PreviewMouseRightButtonDown>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseDown> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and handling it by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
@@ -1651,7 +1651,7 @@
   
  This is an attached event. WPF implements attached events as routed events. Attached events are fundamentally a XAML language concept for referencing events that can be handled on objects that do not define that event, which WPF expands upon by also enabling the event to traverse a route. Attached events do not have a direct handling syntax in code; to attach handlers for a routed event in code, you use a designated Add*Handler method. For details, see [Attached Events Overview](/dotnet/framework/wpf/advanced/attached-events-overview).  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
+ The Windows Presentation Foundation (WPF) framework builds on this attached event by surfacing it as two different common language runtime (CLR) events on <xref:System.Windows.UIElement>: <xref:System.Windows.UIElement.PreviewMouseLeftButtonUp> and <xref:System.Windows.UIElement.PreviewMouseRightButtonUp>. These implementations handle the underlying <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and read the arguments of the event to determine whether the left or right mouse button was involved. For three-button, there is no framework-level event support for the center button, and you should use the <xref:System.Windows.Input.Mouse.PreviewMouseUp> event and check for the center button condition in the event arguments.  
   
  For routed events that relate to the mouse, be careful about how or when you mark them handled. Handling the event near the root and not handling by a child further toward the source may not be appropriate for composited controls, where the compositing pieces might have expected mouse behaviors. The difficulty in making the appropriate choices about whether other elements should also be informed about any given mouse action is in fact why the WPF framework chose the model of having the underlying <xref:System.Windows.Input.Mouse> routed event be surfaced as CLR events along the route.  
   
diff --git a/xml/System.Windows.Input/MouseDevice.xml b/xml/System.Windows.Input/MouseDevice.xml
index a4f484ae27e..f86c796e511 100644
--- a/xml/System.Windows.Input/MouseDevice.xml
+++ b/xml/System.Windows.Input/MouseDevice.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.MouseDevice> supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.  
+ The <xref:System.Windows.Input.MouseDevice> supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.  
   
  For mouse related input, use the <xref:System.Windows.Input.Mouse> class.  The <xref:System.Windows.Input.Mouse> class represents the mouse to an application and provides methods, properties, and events that reflect the state of the mouse.  
   
diff --git a/xml/System.Windows.Input/Touch.xml b/xml/System.Windows.Input/Touch.xml
index 878740554a0..dfc28e3443a 100644
--- a/xml/System.Windows.Input/Touch.xml
+++ b/xml/System.Windows.Input/Touch.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.Touch.FrameReported> event is included in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] to support compatibility with Silverlight. If you do not have to ensure compatibility with Silverlight, use the touch events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>, on <xref:System.Windows.UIElement>, <xref:System.Windows.UIElement3D>, or <xref:System.Windows.ContentElement>.  
+ The <xref:System.Windows.Input.Touch.FrameReported> event is included in Windows Presentation Foundation (WPF) to support compatibility with Silverlight. If you do not have to ensure compatibility with Silverlight, use the touch events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>, on <xref:System.Windows.UIElement>, <xref:System.Windows.UIElement3D>, or <xref:System.Windows.ContentElement>.  
   
  The <xref:System.Windows.Input.Touch.FrameReported> event does not use the same event model as other WPF input events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>. Instead of being exposed as an element-specific event that potentially routes through the object tree of a UI, the <xref:System.Windows.Input.Touch.FrameReported> event is a single event that is handled at the application level. Therefore, you cannot use the `sender` parameter of the event handler to determine what element is touched.  
   
diff --git a/xml/System.Windows.Input/TouchFrameEventArgs.xml b/xml/System.Windows.Input/TouchFrameEventArgs.xml
index cbe1025eb1b..eca9c9b8797 100644
--- a/xml/System.Windows.Input/TouchFrameEventArgs.xml
+++ b/xml/System.Windows.Input/TouchFrameEventArgs.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Input.Touch.FrameReported> event is included in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] to support compatibility with Silverlight. If you do not have to ensure compatibility with Silverlight, use the touch events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>, on <xref:System.Windows.UIElement>, <xref:System.Windows.UIElement3D>, or <xref:System.Windows.ContentElement>.  
+ The <xref:System.Windows.Input.Touch.FrameReported> event is included in Windows Presentation Foundation (WPF) to support compatibility with Silverlight. If you do not have to ensure compatibility with Silverlight, use the touch events, such as <xref:System.Windows.UIElement.TouchDown> and <xref:System.Windows.UIElement.TouchMove>, on <xref:System.Windows.UIElement>, <xref:System.Windows.UIElement3D>, or <xref:System.Windows.ContentElement>.  
   
  Use the <xref:System.Windows.Input.TouchFrameEventArgs> to get the <xref:System.Windows.Input.TouchPoint> values that are relevant to the touch event. From the <xref:System.Windows.Input.TouchPoint>, you can get the <xref:System.Windows.Input.TouchPoint.Position%2A> of the touch and determine whether the <xref:System.Windows.Input.TouchAction> was a <xref:System.Windows.Input.TouchAction.Down>, <xref:System.Windows.Input.TouchAction.Move>, or <xref:System.Windows.Input.TouchAction.Up> action. You can also use the <xref:System.Windows.Input.TouchPoint> to get the <xref:System.Windows.Input.TouchDevice>. From the <xref:System.Windows.Input.TouchDevice>, you can determine the device <xref:System.Windows.Input.TouchDevice.Id%2A> and get information about the element that is touched.  
   
diff --git a/xml/System.Windows.Interop/BrowserInteropHelper.xml b/xml/System.Windows.Interop/BrowserInteropHelper.xml
index ecd5e449d6b..987a988e724 100644
--- a/xml/System.Windows.Interop/BrowserInteropHelper.xml
+++ b/xml/System.Windows.Interop/BrowserInteropHelper.xml
@@ -122,7 +122,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that specifies whether the current [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application is browser hosted.</summary>
+        <summary>Gets a value that specifies whether the current Windows Presentation Foundation (WPF) application is browser hosted.</summary>
         <value>
           <see langword="true" /> if the application is browser hosted; otherwise, <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Interop/CursorInteropHelper.xml b/xml/System.Windows.Interop/CursorInteropHelper.xml
index 364be3804b3..7934e06c1de 100644
--- a/xml/System.Windows.Interop/CursorInteropHelper.xml
+++ b/xml/System.Windows.Interop/CursorInteropHelper.xml
@@ -48,8 +48,8 @@
       </Parameters>
       <Docs>
         <param name="cursorHandle">Cursor reference to use for interoperation.</param>
-        <summary>Returns a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] <see cref="T:System.Windows.Input.Cursor" /> object based on a provided Win32 cursor handle.</summary>
-        <returns>The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] cursor object based on the provided Win32 cursor handle.</returns>
+        <summary>Returns a Windows Presentation Foundation (WPF) <see cref="T:System.Windows.Input.Cursor" /> object based on a provided Win32 cursor handle.</summary>
+        <returns>The Windows Presentation Foundation (WPF) cursor object based on the provided Win32 cursor handle.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Interop/DocObjHost.xml b/xml/System.Windows.Interop/DocObjHost.xml
index 23636094d23..c553380cf67 100644
--- a/xml/System.Windows.Interop/DocObjHost.xml
+++ b/xml/System.Windows.Interop/DocObjHost.xml
@@ -53,7 +53,7 @@
       </Attributes>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -81,7 +81,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A new <see cref="T:System.Runtime.Remoting.Lifetime.ILease" /> object.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Interop/HwndHost.xml b/xml/System.Windows.Interop/HwndHost.xml
index 7edc49fe653..d20acc0b579 100644
--- a/xml/System.Windows.Interop/HwndHost.xml
+++ b/xml/System.Windows.Interop/HwndHost.xml
@@ -604,7 +604,7 @@
 > [!IMPORTANT]
 >  This type or member is not available in the Internet security zone.  
 >   
->  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyDown%2A> and provides the behavior of translating the Win32 message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
+>  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyDown%2A> and provides the behavior of translating the Win32 message into a Windows Presentation Foundation (WPF) event, marking the event as handled whenever appropriate.  
   
  ]]></format>
         </remarks>
@@ -651,7 +651,7 @@
 > [!IMPORTANT]
 >  This type or member is not available in the Internet security zone.  
 >   
->  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyUp%2A> and provides the behavior of translating the Win32 message into a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event, marking the event as handled whenever appropriate.  
+>  This is an override of the class handler <xref:System.Windows.UIElement.OnKeyUp%2A> and provides the behavior of translating the Win32 message into a Windows Presentation Foundation (WPF) event, marking the event as handled whenever appropriate.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Interop/HwndSourceParameters.xml b/xml/System.Windows.Interop/HwndSourceParameters.xml
index 2a4147521ac..338af0b1808 100644
--- a/xml/System.Windows.Interop/HwndSourceParameters.xml
+++ b/xml/System.Windows.Interop/HwndSourceParameters.xml
@@ -392,7 +392,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Unlike most methods that take rectangle screen-region measures in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you specify this window size in device pixels, not the typical device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
+ Unlike most methods that take rectangle screen-region measures in Windows Presentation Foundation (WPF), you specify this window size in device pixels, not the typical device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
   
  Do not set <xref:System.Windows.Interop.HwndSourceParameters.Height%2A> to 0 (zero). Doing so incurs a significant performance penalty in rendering.  
   
@@ -706,7 +706,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Unlike most methods that take rectangle screen-region measures in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you specify this window size in device pixels, not in the typical device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
+ Unlike most methods that take rectangle screen-region measures in Windows Presentation Foundation (WPF), you specify this window size in device pixels, not in the typical device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
   
  Do not pass 0 (zero) for either the `width` or `height` parameters. Although the method eventually succeeds even if you do pass 0, a substantial performance penalty occurs.  
   
@@ -862,7 +862,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Unlike most methods that take rectangle screen region measures in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you specify this window's size in device pixels, not in the usual device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
+ Unlike most methods that take rectangle screen region measures in Windows Presentation Foundation (WPF), you specify this window's size in device pixels, not in the usual device-independent units. If you need to size your window to its content, set <xref:System.Windows.Interop.HwndSource.SizeToContent%2A> to `true`.  
   
  Do not set <xref:System.Windows.Interop.HwndSourceParameters.Width%2A> to 0 (zero). Doing so incurs a substantial performance penalty in rendering.  
   
diff --git a/xml/System.Windows.Interop/IKeyboardInputSink.xml b/xml/System.Windows.Interop/IKeyboardInputSink.xml
index aed60559929..ebf7512ee47 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSink.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSink.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A keyboard sink handles input from particular subsets of the overall keyboard input model for Win32 and [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], and enables some keyboard input to be processed and directed to HWNDs other than the one with current keyboard focus.  
+ A keyboard sink handles input from particular subsets of the overall keyboard input model for Win32 and Windows Presentation Foundation (WPF), and enables some keyboard input to be processed and directed to HWNDs other than the one with current keyboard focus.  
   
  If your component contains other components, and maintains a tab order, your component must also implement <xref:System.Windows.Interop.IKeyboardInputSite> and keep track of which component has focus.  
   
diff --git a/xml/System.Windows.Interop/WindowInteropHelper.xml b/xml/System.Windows.Interop/WindowInteropHelper.xml
index d72beec5dca..32d047ffeb4 100644
--- a/xml/System.Windows.Interop/WindowInteropHelper.xml
+++ b/xml/System.Windows.Interop/WindowInteropHelper.xml
@@ -58,7 +58,7 @@
       </Parameters>
       <Docs>
         <param name="window">A WPF window object.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Windows.Interop.WindowInteropHelper" /> class for a specified [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.Windows.Interop.WindowInteropHelper" /> class for a specified Windows Presentation Foundation (WPF) window.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -139,8 +139,8 @@
         <ReturnType>System.IntPtr</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the window handle for a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window that is used to create this <see cref="T:System.Windows.Interop.WindowInteropHelper" />.</summary>
-        <value>The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window handle (HWND).</value>
+        <summary>Gets the window handle for a Windows Presentation Foundation (WPF) window that is used to create this <see cref="T:System.Windows.Interop.WindowInteropHelper" />.</summary>
+        <value>The Windows Presentation Foundation (WPF) window handle (HWND).</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Window" />
       </Docs>
@@ -173,7 +173,7 @@
         <ReturnType>System.IntPtr</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the handle of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] owner window.</summary>
+        <summary>Gets or sets the handle of the Windows Presentation Foundation (WPF) owner window.</summary>
         <value>The owner window handle (HWND).</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml b/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
index 3721b5f3d57..3fa83b2bc3b 100644
--- a/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
+++ b/xml/System.Windows.Markup/RuntimeNamePropertyAttribute.xml
@@ -47,7 +47,7 @@
  In previous versions of the .NET Framework, this class existed in the WPF-specific assembly WindowsBase. In .NET Framework 4, <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is in the System.Xaml assembly. For more information, see [Types Migrated from WPF to System.Xaml](/dotnet/framework/xaml-services/types-migrated-from-wpf-to-system-xaml).  
   
 ## WPF Usage Notes  
- An example of an existing class in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] where the <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is applied is <xref:System.Windows.FrameworkElement>.  The <xref:System.Windows.FrameworkElement.Name%2A> property on <xref:System.Windows.FrameworkElement> is attributed with <xref:System.Windows.Markup.RuntimeNamePropertyAttribute>, which results in any <xref:System.Windows.FrameworkElement> derived class also using <xref:System.Windows.FrameworkElement.Name%2A> as its run-time name property.  
+ An example of an existing class in Windows Presentation Foundation (WPF) where the <xref:System.Windows.Markup.RuntimeNamePropertyAttribute> is applied is <xref:System.Windows.FrameworkElement>.  The <xref:System.Windows.FrameworkElement.Name%2A> property on <xref:System.Windows.FrameworkElement> is attributed with <xref:System.Windows.Markup.RuntimeNamePropertyAttribute>, which results in any <xref:System.Windows.FrameworkElement> derived class also using <xref:System.Windows.FrameworkElement.Name%2A> as its run-time name property.  
   
  In general, you do not typically need to apply this attribute in WPF unless you are implementing a new or <xref:System.Windows.FrameworkElement>-parallel framework-level class. `x:Name` should take precedence over the run-time name property if both exist as attributes on an element, and a XAML processor implementation generally throws in this case.  
   
diff --git a/xml/System.Windows.Markup/XamlWriterState.xml b/xml/System.Windows.Markup/XamlWriterState.xml
index 02217e485e5..c0fe47a6fdf 100644
--- a/xml/System.Windows.Markup/XamlWriterState.xml
+++ b/xml/System.Windows.Markup/XamlWriterState.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- No existing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] API uses this enumeration for its values. It could be used for a custom XAML writer.  
+ No existing Windows Presentation Foundation (WPF) API uses this enumeration for its values. It could be used for a custom XAML writer.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Animation/ByteAnimation.xml b/xml/System.Windows.Media.Animation/ByteAnimation.xml
index fa05a7080be..c5df52e5a7c 100644
--- a/xml/System.Windows.Media.Animation/ByteAnimation.xml
+++ b/xml/System.Windows.Media.Animation/ByteAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.ByteAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.ByteAnimation.From%2A>, <xref:System.Windows.Media.Animation.ByteAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ByteAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.ByteAnimation.From%2A>, <xref:System.Windows.Media.Animation.ByteAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ByteAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/ColorAnimation.xml b/xml/System.Windows.Media.Animation/ColorAnimation.xml
index 4243c4b79ce..2d9977132a0 100644
--- a/xml/System.Windows.Media.Animation/ColorAnimation.xml
+++ b/xml/System.Windows.Media.Animation/ColorAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.ColorAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.ColorAnimation.From%2A>, <xref:System.Windows.Media.Animation.ColorAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ColorAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.ColorAnimation.From%2A>, <xref:System.Windows.Media.Animation.ColorAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ColorAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/DecimalAnimation.xml b/xml/System.Windows.Media.Animation/DecimalAnimation.xml
index 58b983f84e3..bbc66e2043a 100644
--- a/xml/System.Windows.Media.Animation/DecimalAnimation.xml
+++ b/xml/System.Windows.Media.Animation/DecimalAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.DecimalAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.DecimalAnimation.From%2A>, <xref:System.Windows.Media.Animation.DecimalAnimation.To%2A>, and <xref:System.Windows.Media.Animation.DecimalAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.DecimalAnimation.From%2A>, <xref:System.Windows.Media.Animation.DecimalAnimation.To%2A>, and <xref:System.Windows.Media.Animation.DecimalAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/DoubleAnimation.xml b/xml/System.Windows.Media.Animation/DoubleAnimation.xml
index 450c4eabfcc..ec9d401211a 100644
--- a/xml/System.Windows.Media.Animation/DoubleAnimation.xml
+++ b/xml/System.Windows.Media.Animation/DoubleAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.DoubleAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.DoubleAnimation.From%2A>, <xref:System.Windows.Media.Animation.DoubleAnimation.To%2A>, and <xref:System.Windows.Media.Animation.DoubleAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.DoubleAnimation.From%2A>, <xref:System.Windows.Media.Animation.DoubleAnimation.To%2A>, and <xref:System.Windows.Media.Animation.DoubleAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/IAnimatable.xml b/xml/System.Windows.Media.Animation/IAnimatable.xml
index 476b673a136..c85fea5b750 100644
--- a/xml/System.Windows.Media.Animation/IAnimatable.xml
+++ b/xml/System.Windows.Media.Animation/IAnimatable.xml
@@ -208,7 +208,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method instead of <xref:System.Windows.DependencyObject.GetValue%2A> when you want to retrieve the non-animated value of an animated property. This method takes advantage of the fact that [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] animations do not remove the target property's original value. For more information, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
+ Use this method instead of <xref:System.Windows.DependencyObject.GetValue%2A> when you want to retrieve the non-animated value of an animated property. This method takes advantage of the fact that Windows Presentation Foundation (WPF) animations do not remove the target property's original value. For more information, see [Dependency Property Value Precedence](/dotnet/framework/wpf/advanced/dependency-property-value-precedence).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media.Animation/Int16Animation.xml b/xml/System.Windows.Media.Animation/Int16Animation.xml
index 33cb2a3188b..f59b969915a 100644
--- a/xml/System.Windows.Media.Animation/Int16Animation.xml
+++ b/xml/System.Windows.Media.Animation/Int16Animation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Int16Animation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Int16Animation.From%2A>, <xref:System.Windows.Media.Animation.Int16Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int16Animation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Int16Animation.From%2A>, <xref:System.Windows.Media.Animation.Int16Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int16Animation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/Int32Animation.xml b/xml/System.Windows.Media.Animation/Int32Animation.xml
index 4713dc0d49b..32704b3ea68 100644
--- a/xml/System.Windows.Media.Animation/Int32Animation.xml
+++ b/xml/System.Windows.Media.Animation/Int32Animation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Int32Animation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Int32Animation.From%2A>, <xref:System.Windows.Media.Animation.Int32Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int32Animation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Int32Animation.From%2A>, <xref:System.Windows.Media.Animation.Int32Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int32Animation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/Int64Animation.xml b/xml/System.Windows.Media.Animation/Int64Animation.xml
index 1fbb5881db7..e25bfd1ed64 100644
--- a/xml/System.Windows.Media.Animation/Int64Animation.xml
+++ b/xml/System.Windows.Media.Animation/Int64Animation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Int64Animation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Int64Animation.From%2A>, <xref:System.Windows.Media.Animation.Int64Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int64Animation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Int64Animation.From%2A>, <xref:System.Windows.Media.Animation.Int64Animation.To%2A>, and <xref:System.Windows.Media.Animation.Int64Animation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/Point3DAnimation.xml b/xml/System.Windows.Media.Animation/Point3DAnimation.xml
index 01c9940215d..ac2034b4c64 100644
--- a/xml/System.Windows.Media.Animation/Point3DAnimation.xml
+++ b/xml/System.Windows.Media.Animation/Point3DAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Point3DAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Point3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Point3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Point3DAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Point3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Point3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Point3DAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/PointAnimation.xml b/xml/System.Windows.Media.Animation/PointAnimation.xml
index dd910192f1d..cba5e2d182c 100644
--- a/xml/System.Windows.Media.Animation/PointAnimation.xml
+++ b/xml/System.Windows.Media.Animation/PointAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you must associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you must associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.PointAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.PointAnimation.From%2A>, <xref:System.Windows.Media.Animation.PointAnimation.To%2A>, and <xref:System.Windows.Media.Animation.PointAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.PointAnimation.From%2A>, <xref:System.Windows.Media.Animation.PointAnimation.To%2A>, and <xref:System.Windows.Media.Animation.PointAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/QuaternionAnimation.xml b/xml/System.Windows.Media.Animation/QuaternionAnimation.xml
index 348bd9474cd..36d4e3d30ee 100644
--- a/xml/System.Windows.Media.Animation/QuaternionAnimation.xml
+++ b/xml/System.Windows.Media.Animation/QuaternionAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.QuaternionAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.QuaternionAnimation.From%2A>, <xref:System.Windows.Media.Animation.QuaternionAnimation.To%2A>, and <xref:System.Windows.Media.Animation.QuaternionAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.QuaternionAnimation.From%2A>, <xref:System.Windows.Media.Animation.QuaternionAnimation.To%2A>, and <xref:System.Windows.Media.Animation.QuaternionAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/RectAnimation.xml b/xml/System.Windows.Media.Animation/RectAnimation.xml
index a4f51eab89f..441d19517ad 100644
--- a/xml/System.Windows.Media.Animation/RectAnimation.xml
+++ b/xml/System.Windows.Media.Animation/RectAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time. An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time. An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.RectAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.RectAnimation.From%2A>, <xref:System.Windows.Media.Animation.RectAnimation.To%2A>, and <xref:System.Windows.Media.Animation.RectAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.RectAnimation.From%2A>, <xref:System.Windows.Media.Animation.RectAnimation.To%2A>, and <xref:System.Windows.Media.Animation.RectAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/Rotation3DAnimation.xml b/xml/System.Windows.Media.Animation/Rotation3DAnimation.xml
index efb15783b01..4d04d30f0d6 100644
--- a/xml/System.Windows.Media.Animation/Rotation3DAnimation.xml
+++ b/xml/System.Windows.Media.Animation/Rotation3DAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Rotation3DAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Rotation3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Rotation3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Rotation3DAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Rotation3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Rotation3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Rotation3DAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/SingleAnimation.xml b/xml/System.Windows.Media.Animation/SingleAnimation.xml
index eb6f7373dca..c4c6c3f8955 100644
--- a/xml/System.Windows.Media.Animation/SingleAnimation.xml
+++ b/xml/System.Windows.Media.Animation/SingleAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.SingleAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.SingleAnimation.From%2A>, <xref:System.Windows.Media.Animation.SingleAnimation.To%2A>, and <xref:System.Windows.Media.Animation.SingleAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.SingleAnimation.From%2A>, <xref:System.Windows.Media.Animation.SingleAnimation.To%2A>, and <xref:System.Windows.Media.Animation.SingleAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/SizeAnimation.xml b/xml/System.Windows.Media.Animation/SizeAnimation.xml
index 76cf89acae9..08dad44bff8 100644
--- a/xml/System.Windows.Media.Animation/SizeAnimation.xml
+++ b/xml/System.Windows.Media.Animation/SizeAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you must associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you must associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.SizeAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.SizeAnimation.From%2A>, <xref:System.Windows.Media.Animation.SizeAnimation.To%2A>, and <xref:System.Windows.Media.Animation.SizeAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.SizeAnimation.From%2A>, <xref:System.Windows.Media.Animation.SizeAnimation.To%2A>, and <xref:System.Windows.Media.Animation.SizeAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/ThicknessAnimation.xml b/xml/System.Windows.Media.Animation/ThicknessAnimation.xml
index 6ebcc2eef51..5312cb8eb2c 100644
--- a/xml/System.Windows.Media.Animation/ThicknessAnimation.xml
+++ b/xml/System.Windows.Media.Animation/ThicknessAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.ThicknessAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.ThicknessAnimation.From%2A>, <xref:System.Windows.Media.Animation.ThicknessAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ThicknessAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.ThicknessAnimation.From%2A>, <xref:System.Windows.Media.Animation.ThicknessAnimation.To%2A>, and <xref:System.Windows.Media.Animation.ThicknessAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Animation/TimelineCollection+Enumerator.xml b/xml/System.Windows.Media.Animation/TimelineCollection+Enumerator.xml
index 0e9bca9df80..94e75843457 100644
--- a/xml/System.Windows.Media.Animation/TimelineCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Animation/TimelineCollection+Enumerator.xml
@@ -147,7 +147,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -174,7 +174,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Animation/Vector3DAnimation.xml b/xml/System.Windows.Media.Animation/Vector3DAnimation.xml
index 9a34c7cbb38..cea1dac1a05 100644
--- a/xml/System.Windows.Media.Animation/Vector3DAnimation.xml
+++ b/xml/System.Windows.Media.Animation/Vector3DAnimation.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], you associate an animation with an object's property value.  
+ An animation updates the value of a property over a period of time.  An animation effect can be subtle, such as moving a <xref:System.Windows.Shapes.Shape> a few pixels left and right, or dramatic, such as enlarging an object to 200 times its original size while spinning it and changing its color. To create an animation in Windows Presentation Foundation (WPF), you associate an animation with an object's property value.  
   
 ## Target Values  
  The <xref:System.Windows.Media.Animation.Vector3DAnimation> class creates a transition between two target values. To set its target values, use its <xref:System.Windows.Media.Animation.Vector3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Vector3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Vector3DAnimation.By%2A> properties.  The following table summarizes how the <xref:System.Windows.Media.Animation.Vector3DAnimation.From%2A>, <xref:System.Windows.Media.Animation.Vector3DAnimation.To%2A>, and <xref:System.Windows.Media.Animation.Vector3DAnimation.By%2A> properties may be used together or separately to determine an animation's target values.  
diff --git a/xml/System.Windows.Media.Effects/BitmapEffectCollection+Enumerator.xml b/xml/System.Windows.Media.Effects/BitmapEffectCollection+Enumerator.xml
index 736f003919f..6c0d1637e40 100644
--- a/xml/System.Windows.Media.Effects/BitmapEffectCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Effects/BitmapEffectCollection+Enumerator.xml
@@ -139,7 +139,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.Effect" />. This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.Effect" />. This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -166,7 +166,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.Effect" />. This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>**Note: This API is now obsolete.** The non-obsolete alternative is <see cref="T:System.Windows.Media.Effects.Effect" />. This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml b/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
index 478e1f91a12..e25d5c3b48e 100644
--- a/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapCodecInfo.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Media.Imaging.BitmapCodecInfo> can be obtain for each codec in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] by using the <xref:System.Windows.Media.Imaging.BitmapDecoder.CodecInfo%2A> or the <xref:System.Windows.Media.Imaging.BitmapEncoder.CodecInfo%2A> properties.  
+ A <xref:System.Windows.Media.Imaging.BitmapCodecInfo> can be obtain for each codec in Windows Presentation Foundation (WPF) by using the <xref:System.Windows.Media.Imaging.BitmapDecoder.CodecInfo%2A> or the <xref:System.Windows.Media.Imaging.BitmapEncoder.CodecInfo%2A> properties.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
index dbb3397f691..8a8d1850560 100644
--- a/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapDecoder.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  <xref:System.Windows.Media.Imaging.BitmapDecoder> is not a <xref:System.Windows.Media.Imaging.BitmapFrame> itself; rather, it is a container for <xref:System.Windows.Media.Imaging.BitmapFrame> objects. Each <xref:System.Windows.Media.Imaging.BitmapFrame> in the container can potentially have different attributes, including different sizes, resolutions, or palettes.  
   
- Unless a specific codec is selected, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an independent software vendor (ISV) to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
+ Unless a specific codec is selected, Windows Presentation Foundation (WPF) uses automatic run-time discovery to identify the format of an image and match it with the appropriate codec. This discovery process allows a codec developed by an independent software vendor (ISV) to be automatically discoverable by the system. To select a specific codec, the derived <xref:System.Windows.Media.Imaging.BitmapDecoder> or <xref:System.Windows.Media.Imaging.BitmapEncoder>, such as the <xref:System.Windows.Media.Imaging.TiffBitmapDecoder> class, should be used.  
   
  Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) are the only implemented image formats that support multiple frames.  
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index a334895b10b..66409ccceee 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index b0a83f0dcca..87609b91ee7 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Imaging/BitmapPalette.xml b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
index 12ae85af49f..73f94e98c16 100644
--- a/xml/System.Windows.Media.Imaging/BitmapPalette.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapPalette.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  Only Tagged Image File Format (TIFF) and Graphics Interchange Format (GIF) image formats support image palettes. However, other image types can be used to define a <xref:System.Windows.Media.Imaging.BitmapPalette>. Attempting to define a <xref:System.Windows.Media.Imaging.BitmapPalette> for an unsupported bitmap format does not result in an exception; the designated <xref:System.Windows.Media.Imaging.BitmapPalette> is simply ignored.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] supports both custom color palettes and predefined palettes defined by the <xref:System.Windows.Media.Imaging.BitmapPalettes> class.  
+ Windows Presentation Foundation (WPF) supports both custom color palettes and predefined palettes defined by the <xref:System.Windows.Media.Imaging.BitmapPalettes> class.  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapSource.xml b/xml/System.Windows.Media.Imaging/BitmapSource.xml
index 9524f10559c..bae9c22d461 100644
--- a/xml/System.Windows.Media.Imaging/BitmapSource.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapSource.xml
@@ -28,9 +28,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
+ <xref:System.Windows.Media.Imaging.BitmapSource> is the basic building block of the Windows Presentation Foundation (WPF) imaging pipeline, conceptually representing a single, constant set of pixels at a certain size and resolution. A <xref:System.Windows.Media.Imaging.BitmapSource> could be a single frame in an image file that a decoder provides, or it could be the result of a transform that operates on a <xref:System.Windows.Media.Imaging.BitmapSource> of its own. <xref:System.Windows.Media.Imaging.BitmapSource> is not used to represent a multi-frame image or an animation.  
   
- [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and Tagged Image File Format (TIFF) images.  
+ Windows Presentation Foundation (WPF) natively supports compression and decompression of bitmap (BMP), Graphics Interchange Format (GIF), Joint Photographics Experts Group (JPEG), Portable Network Graphics (PNG), and Tagged Image File Format (TIFF) images.  
   
  For bitmap decoding scenarios, <xref:System.Windows.Media.Imaging.BitmapSource> uses automatic codec discovery, based on the installed codecs on the user's system.  
   
diff --git a/xml/System.Windows.Media.Media3D/MaterialCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/MaterialCollection+Enumerator.xml
index ecf2bc68e8f..b56e509c6fc 100644
--- a/xml/System.Windows.Media.Media3D/MaterialCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/MaterialCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Media3D/Model3DCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/Model3DCollection+Enumerator.xml
index b951dc03c43..abf422f3b15 100644
--- a/xml/System.Windows.Media.Media3D/Model3DCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/Model3DCollection+Enumerator.xml
@@ -138,7 +138,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -165,7 +165,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Media3D/Point3D.xml b/xml/System.Windows.Media.Media3D/Point3D.xml
index 689c7908cdd..ba314cdf432 100644
--- a/xml/System.Windows.Media.Media3D/Point3D.xml
+++ b/xml/System.Windows.Media.Media3D/Point3D.xml
@@ -906,7 +906,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/Point3DCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/Point3DCollection+Enumerator.xml
index 09e52442ac2..e4c17edf087 100644
--- a/xml/System.Windows.Media.Media3D/Point3DCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/Point3DCollection+Enumerator.xml
@@ -141,7 +141,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -168,7 +168,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Media3D/Point4D.xml b/xml/System.Windows.Media.Media3D/Point4D.xml
index f48bad1cef6..4fd36731341 100644
--- a/xml/System.Windows.Media.Media3D/Point4D.xml
+++ b/xml/System.Windows.Media.Media3D/Point4D.xml
@@ -741,7 +741,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/Quaternion.xml b/xml/System.Windows.Media.Media3D/Quaternion.xml
index 9cdf751a895..da162d7a829 100644
--- a/xml/System.Windows.Media.Media3D/Quaternion.xml
+++ b/xml/System.Windows.Media.Media3D/Quaternion.xml
@@ -945,7 +945,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/Rect3D.xml b/xml/System.Windows.Media.Media3D/Rect3D.xml
index f2d3f90af3c..9cfa469281d 100644
--- a/xml/System.Windows.Media.Media3D/Rect3D.xml
+++ b/xml/System.Windows.Media.Media3D/Rect3D.xml
@@ -1089,7 +1089,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
index 96f2f3f1bd0..eca2958c340 100644
--- a/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
+++ b/xml/System.Windows.Media.Media3D/RotateTransform3D.xml
@@ -26,7 +26,7 @@
   
  Rotations in 3-D become more complicated when they are animated.  To animate a 3-D rotation using <xref:System.Windows.Media.Media3D.RotateTransform3D>, you can animate the <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Angle%2A> or <xref:System.Windows.Media.Media3D.AxisAngleRotation3D.Axis%2A> properties of an <xref:System.Windows.Media.Media3D.AxisAngleRotation3D>, or specify a <xref:System.Windows.Media.Media3D.QuaternionRotation3D> for the transform. 
   
- Axis/angle rotations in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] 3-D are specified in degrees, not radians.  
+ Axis/angle rotations in Windows Presentation Foundation (WPF) 3-D are specified in degrees, not radians.  
   
    
   
diff --git a/xml/System.Windows.Media.Media3D/Size3D.xml b/xml/System.Windows.Media.Media3D/Size3D.xml
index 2705246c5b0..c2702872fe3 100644
--- a/xml/System.Windows.Media.Media3D/Size3D.xml
+++ b/xml/System.Windows.Media.Media3D/Size3D.xml
@@ -595,7 +595,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/Transform3DCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/Transform3DCollection+Enumerator.xml
index a52bfe70d3d..d5e4f5046c9 100644
--- a/xml/System.Windows.Media.Media3D/Transform3DCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/Transform3DCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Media3D/Vector3D.xml b/xml/System.Windows.Media.Media3D/Vector3D.xml
index 09534c91c8e..2ff1f9bda37 100644
--- a/xml/System.Windows.Media.Media3D/Vector3D.xml
+++ b/xml/System.Windows.Media.Media3D/Vector3D.xml
@@ -1539,7 +1539,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member is part of the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly by your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member is part of the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly by your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>String representation of this object.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Media.Media3D/Vector3DCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/Vector3DCollection+Enumerator.xml
index dfd45895eb6..b7706238e9f 100644
--- a/xml/System.Windows.Media.Media3D/Vector3DCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/Vector3DCollection+Enumerator.xml
@@ -140,7 +140,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -167,7 +167,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media.Media3D/Visual3DCollection+Enumerator.xml b/xml/System.Windows.Media.Media3D/Visual3DCollection+Enumerator.xml
index 0301a913393..bbce8196af3 100644
--- a/xml/System.Windows.Media.Media3D/Visual3DCollection+Enumerator.xml
+++ b/xml/System.Windows.Media.Media3D/Visual3DCollection+Enumerator.xml
@@ -138,7 +138,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -165,7 +165,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/CompositionTarget.xml b/xml/System.Windows.Media/CompositionTarget.xml
index 044c2c3304e..5a985a00835 100644
--- a/xml/System.Windows.Media/CompositionTarget.xml
+++ b/xml/System.Windows.Media/CompositionTarget.xml
@@ -88,12 +88,12 @@
    
   
 ## Examples  
- The <xref:System.Windows.Media.CompositionTarget.Rendering> event is raised during the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] rendering process. The following example shows how you register an <xref:System.EventHandler> delegate to the static <xref:System.Windows.Media.CompositionTarget.Rendering> method on <xref:System.Windows.Media.CompositionTarget>.  
+ The <xref:System.Windows.Media.CompositionTarget.Rendering> event is raised during the Windows Presentation Foundation (WPF) rendering process. The following example shows how you register an <xref:System.EventHandler> delegate to the static <xref:System.Windows.Media.CompositionTarget.Rendering> method on <xref:System.Windows.Media.CompositionTarget>.  
   
  [!code-csharp[CompositionTargetSample#CompositionTarget1](~/samples/snippets/csharp/VS_Snippets_Wpf/CompositionTargetSample/CSharp/Window1.xaml.cs#compositiontarget1)]
  [!code-vb[CompositionTargetSample#CompositionTarget1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CompositionTargetSample/visualbasic/window1.xaml.vb#compositiontarget1)]  
   
- You can use your rendering event handler to create custom drawing content. This event handler gets called once per frame. Each time that [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] marshals the persisted rendering data in the visual tree across to the composition tree, your event handler is called. In addition, if changes to the visual tree force updates to the composition tree, your event handler is also called. Note that your event handler is called after layout has been computed. However, you can modify layout in your event handler, which means that layout will be computed once more before rendering.  
+ You can use your rendering event handler to create custom drawing content. This event handler gets called once per frame. Each time that Windows Presentation Foundation (WPF) marshals the persisted rendering data in the visual tree across to the composition tree, your event handler is called. In addition, if changes to the visual tree force updates to the composition tree, your event handler is also called. Note that your event handler is called after layout has been computed. However, you can modify layout in your event handler, which means that layout will be computed once more before rendering.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/DoubleCollection+Enumerator.xml b/xml/System.Windows.Media/DoubleCollection+Enumerator.xml
index 179884cd6c6..89ceb9ed26d 100644
--- a/xml/System.Windows.Media/DoubleCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/DoubleCollection+Enumerator.xml
@@ -140,7 +140,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -167,7 +167,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/DrawingCollection+Enumerator.xml b/xml/System.Windows.Media/DrawingCollection+Enumerator.xml
index ae5e96dd28b..52f3f6608e6 100644
--- a/xml/System.Windows.Media/DrawingCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/DrawingCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/DrawingContext.xml b/xml/System.Windows.Media/DrawingContext.xml
index cc478ef40aa..88d89331a04 100644
--- a/xml/System.Windows.Media/DrawingContext.xml
+++ b/xml/System.Windows.Media/DrawingContext.xml
@@ -1059,7 +1059,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index 7c50a51a478..092b80c4914 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -49,7 +49,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  In the preceding example, the font that is referenced, "Comic Sans MS", is referred to by its *friendly name*. Also, in this example the font is assumed to be in the system font collection.  
   
 ## Specifying Fonts in Alternate Directories  
- A [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application can specify a directory, other than the directory that contains the systems font collection, for resolving font references. The friendly name of the font can specify an absolute uniform resource identifier (URI) value to resolve the font reference, as shown in the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code examples.  
+ A Windows Presentation Foundation (WPF) application can specify a directory, other than the directory that contains the systems font collection, for resolving font references. The friendly name of the font can specify an absolute uniform resource identifier (URI) value to resolve the font reference, as shown in the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code examples.  
   
  [!code-csharp[FontSnippets#FontPackageSnippet6](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml.cs#fontpackagesnippet6)]
  [!code-vb[FontSnippets#FontPackageSnippet6](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontpackagesnippets.xaml.vb#fontpackagesnippet6)]
diff --git a/xml/System.Windows.Media/GeneralTransformCollection+Enumerator.xml b/xml/System.Windows.Media/GeneralTransformCollection+Enumerator.xml
index f2154aef636..6c13b522ef3 100644
--- a/xml/System.Windows.Media/GeneralTransformCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/GeneralTransformCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/GeometryCollection+Enumerator.xml b/xml/System.Windows.Media/GeometryCollection+Enumerator.xml
index f9a115cdd59..6a5cf7d2e87 100644
--- a/xml/System.Windows.Media/GeometryCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/GeometryCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/GeometryHitTestParameters.xml b/xml/System.Windows.Media/GeometryHitTestParameters.xml
index 4d3d9af62e4..cb4b138221d 100644
--- a/xml/System.Windows.Media/GeometryHitTestParameters.xml
+++ b/xml/System.Windows.Media/GeometryHitTestParameters.xml
@@ -26,7 +26,7 @@
  You can also hit test with a <xref:System.Windows.Point> value by creating a <xref:System.Windows.Media.PointHitTestParameters> object.  
   
 > [!NOTE]
->  [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] hit testing only considers the filled area of a geometry during a hit test. If you create a point <xref:System.Windows.Media.Geometry>, the hit test would not intersect anything because a point has no area.  
+>  Windows Presentation Foundation (WPF) hit testing only considers the filled area of a geometry during a hit test. If you create a point <xref:System.Windows.Media.Geometry>, the hit test would not intersect anything because a point has no area.  
   
    
   
diff --git a/xml/System.Windows.Media/GradientStopCollection+Enumerator.xml b/xml/System.Windows.Media/GradientStopCollection+Enumerator.xml
index 9d959759797..a33de2ed053 100644
--- a/xml/System.Windows.Media/GradientStopCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/GradientStopCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/Int32Collection+Enumerator.xml b/xml/System.Windows.Media/Int32Collection+Enumerator.xml
index 21d4dc66ab1..f3c31daf799 100644
--- a/xml/System.Windows.Media/Int32Collection+Enumerator.xml
+++ b/xml/System.Windows.Media/Int32Collection+Enumerator.xml
@@ -140,7 +140,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -167,7 +167,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/Matrix.xml b/xml/System.Windows.Media/Matrix.xml
index 63d24a52f89..eed6513ad63 100644
--- a/xml/System.Windows.Media/Matrix.xml
+++ b/xml/System.Windows.Media/Matrix.xml
@@ -455,7 +455,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses for the <xref:System.Windows.Media.Matrix>, structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
+ An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that Windows Presentation Foundation (WPF) uses for the <xref:System.Windows.Media.Matrix>, structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
   
 ||||  
 |-|-|-|  
@@ -536,7 +536,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses for the <xref:System.Windows.Media.Matrix> structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
+ An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that Windows Presentation Foundation (WPF) uses for the <xref:System.Windows.Media.Matrix> structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
   
 ||||  
 |-|-|-|  
@@ -1415,7 +1415,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] uses for the <xref:System.Windows.Media.Matrix> structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
+ An identity matrix has a value of 1 in coefficients [1,1],[2,2],[3,3] and a value of 0 in the rest of the coefficients. This correlates to setting <xref:System.Windows.Media.Matrix.M11%2A> and <xref:System.Windows.Media.Matrix.M22%2A> to 1 and <xref:System.Windows.Media.Matrix.M12%2A>, <xref:System.Windows.Media.Matrix.M21%2A>, <xref:System.Windows.Media.Matrix.OffsetX%2A>, and <xref:System.Windows.Media.Matrix.OffsetY%2A> to 0. In an affine matrix, which is the implementation that Windows Presentation Foundation (WPF) uses for the <xref:System.Windows.Media.Matrix> structure, coefficients [3,1],[3,2],[3.3] are implied to always have the values 0,0,1 respectively.  
   
 ||||  
 |-|-|-|  
diff --git a/xml/System.Windows.Media/MatrixTransform.xml b/xml/System.Windows.Media/MatrixTransform.xml
index bc7a0d5fab8..e8e5a1371d0 100644
--- a/xml/System.Windows.Media/MatrixTransform.xml
+++ b/xml/System.Windows.Media/MatrixTransform.xml
@@ -28,7 +28,7 @@
   
  An affine matrix transformation has its final column equal to (0, 0, 1); therefore, you only have to specify the members in the first two columns.  
   
- A [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] <xref:System.Windows.Media.Matrix> has the following structure:  
+ A Windows Presentation Foundation (WPF) <xref:System.Windows.Media.Matrix> has the following structure:  
   
 ||||  
 |-|-|-|  
diff --git a/xml/System.Windows.Media/PathFigureCollection+Enumerator.xml b/xml/System.Windows.Media/PathFigureCollection+Enumerator.xml
index a5fe08dca9d..a1991ef812e 100644
--- a/xml/System.Windows.Media/PathFigureCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/PathFigureCollection+Enumerator.xml
@@ -146,7 +146,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/PathSegmentCollection+Enumerator.xml b/xml/System.Windows.Media/PathSegmentCollection+Enumerator.xml
index 7733b7fb361..24ce52191a1 100644
--- a/xml/System.Windows.Media/PathSegmentCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/PathSegmentCollection+Enumerator.xml
@@ -154,7 +154,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Media.PathSegmentCollection.Enumerator.Current" />
@@ -182,7 +182,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/PointCollection+Enumerator.xml b/xml/System.Windows.Media/PointCollection+Enumerator.xml
index 940d9e1f4c4..9f3290b6994 100644
--- a/xml/System.Windows.Media/PointCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/PointCollection+Enumerator.xml
@@ -148,7 +148,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -175,7 +175,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/StreamGeometryContext.xml b/xml/System.Windows.Media/StreamGeometryContext.xml
index fd20c0806d7..4706779765c 100644
--- a/xml/System.Windows.Media/StreamGeometryContext.xml
+++ b/xml/System.Windows.Media/StreamGeometryContext.xml
@@ -518,7 +518,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/TileBrush.xml b/xml/System.Windows.Media/TileBrush.xml
index 1ca28a54748..0e10be3f131 100644
--- a/xml/System.Windows.Media/TileBrush.xml
+++ b/xml/System.Windows.Media/TileBrush.xml
@@ -24,7 +24,7 @@
 ## Remarks  
  The derived classes of <xref:System.Windows.Media.TileBrush> define the contents of the tiles that you use to paint a region. For example, use the <xref:System.Windows.Media.ImageBrush> class to paint an area by using an image.  
   
- Use a <xref:System.Windows.Media.TileBrush> to control how you paint an area. For example, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] provides several types of brushes:  
+ Use a <xref:System.Windows.Media.TileBrush> to control how you paint an area. For example, Windows Presentation Foundation (WPF) provides several types of brushes:  
   
 -   To paint by using an image, use the <xref:System.Windows.Media.ImageBrush>.  
   
diff --git a/xml/System.Windows.Media/Transform.xml b/xml/System.Windows.Media/Transform.xml
index a281d9a55fb..ca5f3ac8770 100644
--- a/xml/System.Windows.Media/Transform.xml
+++ b/xml/System.Windows.Media/Transform.xml
@@ -42,7 +42,7 @@
   
  An affine transformation matrix has its final column equal to (0, 0, 1); therefore, you only have to specify the members in the first two columns.  
   
- A [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] <xref:System.Windows.Media.Matrix> has the following structure:  
+ A Windows Presentation Foundation (WPF) <xref:System.Windows.Media.Matrix> has the following structure:  
   
 ||||  
 |-|-|-|  
diff --git a/xml/System.Windows.Media/TransformCollection+Enumerator.xml b/xml/System.Windows.Media/TransformCollection+Enumerator.xml
index 78a7381328b..e71471f4d57 100644
--- a/xml/System.Windows.Media/TransformCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/TransformCollection+Enumerator.xml
@@ -154,7 +154,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Media.TransformCollection.Enumerator.Current" />
@@ -182,7 +182,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/VectorCollection+Enumerator.xml b/xml/System.Windows.Media/VectorCollection+Enumerator.xml
index 9ec58180712..9c35b73d34c 100644
--- a/xml/System.Windows.Media/VectorCollection+Enumerator.xml
+++ b/xml/System.Windows.Media/VectorCollection+Enumerator.xml
@@ -153,7 +153,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -180,7 +180,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Media/VisualBrush.xml b/xml/System.Windows.Media/VisualBrush.xml
index eef0a7852b0..c73231d6ab9 100644
--- a/xml/System.Windows.Media/VisualBrush.xml
+++ b/xml/System.Windows.Media/VisualBrush.xml
@@ -28,7 +28,7 @@
   
 -   Use an existing <xref:System.Windows.Media.Visual>, which creates a duplicate image of the target <xref:System.Windows.Media.Visual>. You can then use the <xref:System.Windows.Media.VisualBrush> to create interesting effects, such as reflection and magnification.  
   
- When you define a new <xref:System.Windows.Media.VisualBrush.Visual%2A> for a <xref:System.Windows.Media.VisualBrush> and that <xref:System.Windows.Media.Visual> is a <xref:System.Windows.UIElement> (such as a panel or control), the layout system runs on the <xref:System.Windows.UIElement> and its child elements when the <xref:System.Windows.Media.VisualBrush.AutoLayoutContent%2A> property is set to `true`. However, the root <xref:System.Windows.UIElement> is essentially isolated from the rest of the system; styles, storyboards, and external layout can't permeate this boundary. Therefore, you should explicitly specify the size of the root <xref:System.Windows.UIElement>, because its only parent is the <xref:System.Windows.Media.VisualBrush> and therefore it cannot automatically size itself to the area being painted. For more information about layout in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], see the [Layout](/dotnet/framework/wpf/advanced/layout).  
+ When you define a new <xref:System.Windows.Media.VisualBrush.Visual%2A> for a <xref:System.Windows.Media.VisualBrush> and that <xref:System.Windows.Media.Visual> is a <xref:System.Windows.UIElement> (such as a panel or control), the layout system runs on the <xref:System.Windows.UIElement> and its child elements when the <xref:System.Windows.Media.VisualBrush.AutoLayoutContent%2A> property is set to `true`. However, the root <xref:System.Windows.UIElement> is essentially isolated from the rest of the system; styles, storyboards, and external layout can't permeate this boundary. Therefore, you should explicitly specify the size of the root <xref:System.Windows.UIElement>, because its only parent is the <xref:System.Windows.Media.VisualBrush> and therefore it cannot automatically size itself to the area being painted. For more information about layout in Windows Presentation Foundation (WPF), see the [Layout](/dotnet/framework/wpf/advanced/layout).  
   
  Updates to the visual tree of a <xref:System.Windows.Media.VisualBrush> will not propagate if a <xref:System.Windows.Media.Effects.BitmapEffect> is in the brush's parent chain. You can workaround this limitation by forcing an update of the scene on the object above the effect. You can call <xref:System.Windows.UIElement.InvalidateVisual%2A> or include an animation to force a scene update.  
   
@@ -355,7 +355,7 @@
   
  <xref:System.Windows.Media.Visual> is quite high in the overall WPF class hierarchy, so a very large number of objects could possibly serve as the visual that you use for a <xref:System.Windows.Media.VisualBrush>; the entire list cannot be shown here. See <xref:System.Windows.Media.Visual>; refer to the "Inheritance Hierarchy" section, which will show the immediately derived classes. You can then click on the immediately derived classes and traverse the hierarchies to get a sense of the full range of possibilities. At a top level, the two most common categories of objects you might use for a <xref:System.Windows.Media.VisualBrush> are <xref:System.Windows.UIElement> or <xref:System.Windows.Media.ContainerVisual>. <xref:System.Windows.UIElement> encompasses basically any UI element that can otherwise participate in the UI for a WPF application. <xref:System.Windows.Media.ContainerVisual> contains a <xref:System.Windows.Media.DrawingGroup> that includes one or more <xref:System.Windows.Media.Drawing>-derived objects.  
   
- When you define a new <xref:System.Windows.Media.VisualBrush.Visual%2A> for a <xref:System.Windows.Media.VisualBrush> and that <xref:System.Windows.Media.Visual> is a <xref:System.Windows.UIElement> (such as a panel or control), the layout system runs on the <xref:System.Windows.UIElement> and its child elements when the <xref:System.Windows.Media.VisualBrush.AutoLayoutContent%2A> property is set to `true`. However, the root <xref:System.Windows.UIElement> is essentially isolated from the rest of the system; styles, storyboards, and external layout dictated by the parent where the brush is applied cannot permeate this boundary. Therefore, you should explicitly specify the size of the root <xref:System.Windows.UIElement>, because its only parent is the <xref:System.Windows.Media.VisualBrush> and therefore it cannot automatically size itself to the area being painted. For more information about layout in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], see the [Layout](/dotnet/framework/wpf/advanced/layout).  
+ When you define a new <xref:System.Windows.Media.VisualBrush.Visual%2A> for a <xref:System.Windows.Media.VisualBrush> and that <xref:System.Windows.Media.Visual> is a <xref:System.Windows.UIElement> (such as a panel or control), the layout system runs on the <xref:System.Windows.UIElement> and its child elements when the <xref:System.Windows.Media.VisualBrush.AutoLayoutContent%2A> property is set to `true`. However, the root <xref:System.Windows.UIElement> is essentially isolated from the rest of the system; styles, storyboards, and external layout dictated by the parent where the brush is applied cannot permeate this boundary. Therefore, you should explicitly specify the size of the root <xref:System.Windows.UIElement>, because its only parent is the <xref:System.Windows.Media.VisualBrush> and therefore it cannot automatically size itself to the area being painted. For more information about layout in Windows Presentation Foundation (WPF), see the [Layout](/dotnet/framework/wpf/advanced/layout).  
   
  Updates to the visual tree of a <xref:System.Windows.Media.VisualBrush> will not propagate if a <xref:System.Windows.Media.Effects.BitmapEffect> is in the brush's parent chain. You can workaround this limitation by forcing an update of the scene on the object above the effect. You can call <xref:System.Windows.UIElement.InvalidateVisual%2A> or include an animation to force a scene update.  
   
diff --git a/xml/System.Windows.Navigation/JournalEntryListConverter.xml b/xml/System.Windows.Navigation/JournalEntryListConverter.xml
index 41eed5de5c7..bc3046f9dea 100644
--- a/xml/System.Windows.Navigation/JournalEntryListConverter.xml
+++ b/xml/System.Windows.Navigation/JournalEntryListConverter.xml
@@ -80,7 +80,7 @@
         <param name="targetType">The type of the binding target property.</param>
         <param name="parameter">The converter parameter to use.</param>
         <param name="culture">The culture to use in the converter.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A converted value.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -116,7 +116,7 @@
         <param name="targetType">The type of the binding source property.</param>
         <param name="parameter">The converter parameter to use.</param>
         <param name="culture">The culture to use in the converter.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>A converted value.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows.Xps.Packaging/XpsDocument.xml b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
index bf14b3c39f4..8a98503d818 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDocument.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
@@ -910,7 +910,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. Use the type-safe <see cref="M:System.Windows.Xps.Packaging.XpsDocument.Dispose(System.Boolean)" /> method instead.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. Use the type-safe <see cref="M:System.Windows.Xps.Packaging.XpsDocument.Dispose(System.Boolean)" /> method instead.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
index 76613ad32a4..6e35c3924ca 100644
--- a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
+++ b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
@@ -743,7 +743,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/Clipboard.xml b/xml/System.Windows/Clipboard.xml
index 733d3814b6c..9f333247bad 100644
--- a/xml/System.Windows/Clipboard.xml
+++ b/xml/System.Windows/Clipboard.xml
@@ -33,7 +33,7 @@
   
 -   On copy or cut, partial trust code puts plaintext and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] on to the clipboard. Plaintext includes text, Unicode text, OEM (Object Exchange Model) text, and CSV (Comma-separated values).  
   
--   On paste, [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] will paste in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] if the source of that content is from a equally trusted or more trusted site. Specifically:  
+-   On paste, Windows Presentation Foundation (WPF) will paste in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] if the source of that content is from a equally trusted or more trusted site. Specifically:  
   
     -   A partial trust application can paste [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] from a full trust application.  
   
@@ -41,7 +41,7 @@
   
     -   A full trust application can paste XAML only from another fully trusted application.  
   
-    -   A non-[!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] full trust application can examine the ApplicationTrust format on the clipboard and sanitize the XAML if appropriate.  
+    -   A non-Windows Presentation Foundation (WPF) full trust application can examine the ApplicationTrust format on the clipboard and sanitize the XAML if appropriate.  
   
    
   
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 044bb0c97df..9d260789789 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -867,7 +867,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any Microsoft .NET programming language. In [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)], XAML is typically used to describe user interfaces (UI), documents, and media experiences.  
+ XAML is an XML-based language used to represent a tree of objects. Events generated by these objects can be handled using any Microsoft .NET programming language. In Windows Presentation Foundation (WPF), XAML is typically used to describe user interfaces (UI), documents, and media experiences.  
   
  This field is used by the <xref:System.Windows.DataObject> class and other classes that implement the <xref:System.Windows.IDataObject> interface to describe an available data format.  
   
diff --git a/xml/System.Windows/DependencyObject.xml b/xml/System.Windows/DependencyObject.xml
index 87884f5edf0..ddc2a53833d 100644
--- a/xml/System.Windows/DependencyObject.xml
+++ b/xml/System.Windows/DependencyObject.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.DependencyObject> class enables [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] property system services on its many derived classes.  
+ The <xref:System.Windows.DependencyObject> class enables Windows Presentation Foundation (WPF) property system services on its many derived classes.  
   
  The property system's primary function is to compute the values of properties, and to provide system notification about values that have changed. Another key class that participates in the property system is <xref:System.Windows.DependencyProperty>. <xref:System.Windows.DependencyProperty> enables the registration of dependency properties into the property system, and provides identification and information about each dependency property, whereas <xref:System.Windows.DependencyObject> as a base class enables objects to use the dependency properties.  
   
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index 63152d776e6..bd49f8808ad 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -35,7 +35,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.DependencyProperty> supports the following capabilities in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)]:  
+ A <xref:System.Windows.DependencyProperty> supports the following capabilities in Windows Presentation Foundation (WPF):  
   
 -   The property can be set in a style. For more information, see [Styling and Templating](/dotnet/framework/wpf/controls/styling-and-templating).  
   
diff --git a/xml/System.Windows/EventManager.xml b/xml/System.Windows/EventManager.xml
index 3d5c250b1cd..649461a1fd9 100644
--- a/xml/System.Windows/EventManager.xml
+++ b/xml/System.Windows/EventManager.xml
@@ -239,7 +239,7 @@
         <param name="routingStrategy">The routing strategy of the event as a value of the enumeration.</param>
         <param name="handlerType">The type of the event handler. This must be a delegate type and cannot be <see langword="null" />.</param>
         <param name="ownerType">The owner class type of the routed event. This cannot be <see langword="null" />.</param>
-        <summary>Registers a new routed event with the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] event system.</summary>
+        <summary>Registers a new routed event with the Windows Presentation Foundation (WPF) event system.</summary>
         <returns>The identifier for the newly registered routed event. This identifier object can now be stored as a static field in a class and then used as a parameter for methods that attach handlers to the event. The routed event identifier is also used for other event system APIs.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows/EventRoute.xml b/xml/System.Windows/EventRoute.xml
index 17009d5208a..81a8cc4368d 100644
--- a/xml/System.Windows/EventRoute.xml
+++ b/xml/System.Windows/EventRoute.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class corresponds to a valid <xref:System.Windows.RoutedEvent>, and contains an ordered list of target object and handler list pairs that refer to the event route for that event. <xref:System.Windows.EventRoute> supports adding new entries to the list and also allows for the handlers in the list to be invoked.  
   
- Most normal operations for adding handlers for [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] events do not require working with this class (for instance, use <xref:System.Windows.EventManager> methods to add class handling, or query for existing handlers of an event). This class is mainly for use when elements have particular knowledge about child elements or parent elements that make it practical to either add elements to or remove elements from the default calculated event route.  
+ Most normal operations for adding handlers for Windows Presentation Foundation (WPF) events do not require working with this class (for instance, use <xref:System.Windows.EventManager> methods to add class handling, or query for existing handlers of an event). This class is mainly for use when elements have particular knowledge about child elements or parent elements that make it practical to either add elements to or remove elements from the default calculated event route.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 6d1f6d21c33..1544568c750 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -674,7 +674,7 @@
   
  To revert the behavior of setting this property to the eventual default, set it to `null` again.  
   
- The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented with no programmatic values from any source, the default cursor over a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application will be an arrow.  
+ The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented with no programmatic values from any source, the default cursor over a Windows Presentation Foundation (WPF) application will be an arrow.  
   
  Each movement of the mouse over a WPF application raises a <xref:System.Windows.ContentElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor via the arguments of this event. If that happens, the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkContentElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkContentElement.ForceCursor%2A> is set.  
   
@@ -1884,7 +1884,7 @@
 ## Remarks  
  The default implementation of this virtual method raises the event as described earlier in this topic. Overrides should call base() to preserve this behavior.  
   
- Note that the <xref:System.Windows.FrameworkContentElement.IsInitialized%2A> property is read-only. Therefore, you cannot set it to force initialization behavior that way. Initialization setting is intended to be done only by the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework.  
+ Note that the <xref:System.Windows.FrameworkContentElement.IsInitialized%2A> property is read-only. Therefore, you cannot set it to force initialization behavior that way. Initialization setting is intended to be done only by the Windows Presentation Foundation (WPF) framework.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 376cf9e672e..266cbe73225 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -1061,7 +1061,7 @@
   
  To revert the behavior of setting this property to the eventual default, set it to `null` again.  
   
- The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented without programmatic values from any source, the default cursor that is visually over a [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] application will be an arrow. However, the transient cursor changes are not set to the <xref:System.Windows.FrameworkElement.Cursor%2A> values of the elements when they are passed over. The <xref:System.Windows.FrameworkElement.Cursor%2A> property will only report non null values in cases where it was actually set, for instance through code or a style. Each movement of the mouse over a WPF application raises a <xref:System.Windows.UIElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor through the arguments of this event. This is the mechanism that produces the visually apparent cursor in most cases. If a <xref:System.Windows.UIElement.QueryCursor> handler returns a cursor result, then the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkElement.ForceCursor%2A> is set.  
+ The `null` default really means that determination of the practical cursor value is deferred here and should be obtained from elsewhere. If presented without programmatic values from any source, the default cursor that is visually over a Windows Presentation Foundation (WPF) application will be an arrow. However, the transient cursor changes are not set to the <xref:System.Windows.FrameworkElement.Cursor%2A> values of the elements when they are passed over. The <xref:System.Windows.FrameworkElement.Cursor%2A> property will only report non null values in cases where it was actually set, for instance through code or a style. Each movement of the mouse over a WPF application raises a <xref:System.Windows.UIElement.QueryCursor> event. The event bubbles, and any element along the route has the opportunity to handle the event and to set the value of the cursor through the arguments of this event. This is the mechanism that produces the visually apparent cursor in most cases. If a <xref:System.Windows.UIElement.QueryCursor> handler returns a cursor result, then the fact that the event is handled and has a changed value in the arguments takes precedence over the value of the <xref:System.Windows.FrameworkElement.Cursor%2A> property at any level, unless <xref:System.Windows.FrameworkElement.ForceCursor%2A> is set.  
   
  If not are not creating a custom cursor, you typically set this property to a static property value of the <xref:System.Windows.Input.Cursors> class. Setting <xref:System.Windows.FrameworkElement.Cursor%2A> in code requires one of the following:  
   
@@ -3005,7 +3005,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Override <xref:System.Windows.FrameworkElement.MeasureOverride%2A> to implement custom layout sizing behavior for your element as it participates in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] layout system. Your implementation should do the following:  
+ Override <xref:System.Windows.FrameworkElement.MeasureOverride%2A> to implement custom layout sizing behavior for your element as it participates in the Windows Presentation Foundation (WPF) layout system. Your implementation should do the following:  
   
 1.  Iterate your element's particular collection of children that are part of layout, call <xref:System.Windows.UIElement.Measure%2A> on each child element.  
   
@@ -3572,7 +3572,7 @@
 ## Remarks  
  This particular On* method is not a class handler hook. Nor does it exactly follow the established common language runtime (CLR) On* method convention that the matching event could be suppressed by overriding this method and not calling the base implementation.  
   
- Note that the <xref:System.Windows.FrameworkElement.IsInitialized%2A> property is read-only, so you cannot set <xref:System.Windows.FrameworkElement.IsInitialized%2A> to force initialization behavior. Setting the initialization state is intended to be done only by the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework.  
+ Note that the <xref:System.Windows.FrameworkElement.IsInitialized%2A> property is read-only, so you cannot set <xref:System.Windows.FrameworkElement.IsInitialized%2A> to force initialization behavior. Setting the initialization state is intended to be done only by the Windows Presentation Foundation (WPF) framework.  
   
  ]]></format>
         </remarks>
@@ -3814,7 +3814,7 @@
         <block subset="none" type="overrides">
           <para>The default implementation of this virtual method queries for the new parent, raises various initialization events, and sets internal flags about initialization state of the <see cref="T:System.Windows.FrameworkElement" /> as appropriate. Finally, it calls the successive base implementations as declared by <see cref="T:System.Windows.UIElement" />, which in turn calls its base in <see cref="T:System.Windows.Media.Visual" />. Always call the base implementation to preserve this behavior, otherwise the element tree behavior for this element when declared as a child of another element may not be as expected.  
   
- A few existing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] classes override this method, for example: <see cref="M:System.Windows.Window.OnVisualParentChanged(System.Windows.DependencyObject)" />, <see cref="M:System.Windows.Controls.ListBoxItem.OnVisualParentChanged(System.Windows.DependencyObject)" />. The most common scenario is to enforce that the new parent must be a particular type. This might involve throwing an exception if the new parent failed some manner of type test. A specialized version of this scenario exists in implementations for list items and menu items, which do not make any sense outside a parent visual that owns an appropriate collection to store them in. Note that these cases do not necessarily raise exceptions, because there might be designer scenarios that rely on reparenting elements that are momentarily without their "regular" parents.  
+ A few existing Windows Presentation Foundation (WPF) classes override this method, for example: <see cref="M:System.Windows.Window.OnVisualParentChanged(System.Windows.DependencyObject)" />, <see cref="M:System.Windows.Controls.ListBoxItem.OnVisualParentChanged(System.Windows.DependencyObject)" />. The most common scenario is to enforce that the new parent must be a particular type. This might involve throwing an exception if the new parent failed some manner of type test. A specialized version of this scenario exists in implementations for list items and menu items, which do not make any sense outside a parent visual that owns an appropriate collection to store them in. Note that these cases do not necessarily raise exceptions, because there might be designer scenarios that rely on reparenting elements that are momentarily without their "regular" parents.  
   
  This method is also overridden in certain elements that are typically the root element, such as  <see cref="T:System.Windows.Window" />. Another case is elements that are the apparent root element in markup but which autogenerate a greater infrastructure in a compiled logical tree (such as <see cref="T:System.Windows.Controls.Page" />). The <see cref="T:System.Windows.Window" /> and <see cref="T:System.Windows.Controls.Page" /> implementations deliberately seal the method.</para>
         </block>
diff --git a/xml/System.Windows/Freezable.xml b/xml/System.Windows/Freezable.xml
index 482962d9e02..25f22c9bc12 100644
--- a/xml/System.Windows/Freezable.xml
+++ b/xml/System.Windows/Freezable.xml
@@ -939,7 +939,7 @@
         <param name="oldValue">The previous value of the data member.</param>
         <param name="newValue">The current value of the data member.</param>
         <param name="property">The property that changed.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/FreezableCollection`1+Enumerator.xml b/xml/System.Windows/FreezableCollection`1+Enumerator.xml
index db259a4bf2a..32fe0c2e175 100644
--- a/xml/System.Windows/FreezableCollection`1+Enumerator.xml
+++ b/xml/System.Windows/FreezableCollection`1+Enumerator.xml
@@ -148,7 +148,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>To be added.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -175,7 +175,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/IInputElement.xml b/xml/System.Windows/IInputElement.xml
index e84b2e96cad..72cfa9967d4 100644
--- a/xml/System.Windows/IInputElement.xml
+++ b/xml/System.Windows/IInputElement.xml
@@ -202,7 +202,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.Focusable%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.Focusable%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.Focusable%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.Focusable%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsEnabled%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsEnabled%2A?displayProperty=nameWithType>) make this property read/write and establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsEnabled%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsEnabled%2A?displayProperty=nameWithType>) make this property read/write and establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -378,7 +378,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsKeyboardFocused%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsKeyboardFocused%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsKeyboardFocused%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsKeyboardFocused%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -413,7 +413,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsKeyboardFocusWithin%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsKeyboardFocusWithin%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsKeyboardFocusWithin%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsKeyboardFocusWithin%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -448,7 +448,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsMouseCaptured%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseCaptured%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsMouseCaptured%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseCaptured%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -483,7 +483,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsMouseDirectlyOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseDirectlyOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsMouseDirectlyOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseDirectlyOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -518,7 +518,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsMouseOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsMouseOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsMouseOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -553,7 +553,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsStylusCaptured%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusCaptured%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsStylusCaptured%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusCaptured%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -588,7 +588,7 @@
 ## Remarks  
  This interface is not intended for public implementation. For more information, see remarks for the <xref:System.Windows.IInputElement> interface.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsStylusDirectlyOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusDirectlyOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsStylusDirectlyOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusDirectlyOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
@@ -625,7 +625,7 @@
   
  Some core classes that implement <xref:System.Windows.IInputElement>, such as <xref:System.Windows.UIElement>, also implement an event that tracks changes to this property. However, this interface does not include such an event as part of its contract.  
   
- Existing implementations in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] core (see <xref:System.Windows.ContentElement.IsStylusOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
+ Existing implementations in the Windows Presentation Foundation (WPF) core (see <xref:System.Windows.ContentElement.IsStylusOver%2A?displayProperty=nameWithType> and <xref:System.Windows.UIElement.IsStylusOver%2A?displayProperty=nameWithType>) establish this property as a dependency property.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/Point.xml b/xml/System.Windows/Point.xml
index 0b38662bcf6..50f3fc2f586 100644
--- a/xml/System.Windows/Point.xml
+++ b/xml/System.Windows/Point.xml
@@ -920,7 +920,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows/Size.xml b/xml/System.Windows/Size.xml
index a75e4216335..c23ef44bda7 100644
--- a/xml/System.Windows/Size.xml
+++ b/xml/System.Windows/Size.xml
@@ -522,7 +522,7 @@
       <Docs>
         <param name="format">The format to use.</param>
         <param name="provider">The provider to use to format the value.</param>
-        <summary>This type or member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This type or member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Size.ToString(System.IFormatProvider)" />
diff --git a/xml/System.Windows/Style.xml b/xml/System.Windows/Style.xml
index 532b28fd877..c769b4f5431 100644
--- a/xml/System.Windows/Style.xml
+++ b/xml/System.Windows/Style.xml
@@ -59,7 +59,7 @@
 > [!NOTE]
 >  If there is more than one setter in the setter collection with the same <xref:System.Windows.Setter.Property%2A> property value, the setter that is declared last is used. Similarly, if you set a value for the same property in a style and on an element directly, the value set on the element directly takes precedence.  
   
- The [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] styling and templating model allows maintenance and sharing of a look as well as the separation of presentation and logic. The styling and templating model includes a suite of features that enable you to customize your UI. This suite of features includes the <xref:System.Windows.Style> class as well as the following:  
+ The Windows Presentation Foundation (WPF) styling and templating model allows maintenance and sharing of a look as well as the separation of presentation and logic. The styling and templating model includes a suite of features that enable you to customize your UI. This suite of features includes the <xref:System.Windows.Style> class as well as the following:  
   
 -   <xref:System.Windows.Trigger>  
   
diff --git a/xml/System.Windows/TemplateKey.xml b/xml/System.Windows/TemplateKey.xml
index 0dae575fb98..e13703e5a9c 100644
--- a/xml/System.Windows/TemplateKey.xml
+++ b/xml/System.Windows/TemplateKey.xml
@@ -214,7 +214,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -240,7 +240,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/TriggerActionCollection.xml b/xml/System.Windows/TriggerActionCollection.xml
index 91c8fe8e5c3..fa624a681a8 100644
--- a/xml/System.Windows/TriggerActionCollection.xml
+++ b/xml/System.Windows/TriggerActionCollection.xml
@@ -501,7 +501,7 @@
       <Docs>
         <param name="array">The one-dimensional array that is the destination of the items that are copied from the collection. The array must use zero-based indexing.</param>
         <param name="index">The zero-based index in the <paramref name="array" /> where copying starts.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -526,7 +526,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if access to the <see cref="T:System.Collections.ICollection" /> is synchronized (thread safe); otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -553,7 +553,7 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that can be used to synchronize access to the <see cref="T:System.Collections.ICollection" />.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -580,7 +580,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>An <see cref="T:System.Collections.IEnumerator" /> object that can be used to iterate through the collection.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -610,7 +610,7 @@
       </Parameters>
       <Docs>
         <param name="value">The <see cref="T:System.Object" /> to add to the <see cref="T:System.Collections.IList" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The position into which the new element was inserted.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -640,7 +640,7 @@
       </Parameters>
       <Docs>
         <param name="value">The <see cref="T:System.Object" /> to locate in the <see cref="T:System.Collections.IList" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>
           <see langword="true" /> if the <see cref="T:System.Object" /> is found in the <see cref="T:System.Collections.IList" />; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
@@ -671,7 +671,7 @@
       </Parameters>
       <Docs>
         <param name="value">The <see cref="T:System.Object" /> to locate in the <see cref="T:System.Collections.IList" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <returns>The index of <paramref name="value" /> if found in the list; otherwise, -1.</returns>
         <remarks>To be added.</remarks>
       </Docs>
@@ -703,7 +703,7 @@
       <Docs>
         <param name="index">The zero-based index at which <paramref name="value" /> should be inserted.</param>
         <param name="value">The <see cref="T:System.Object" /> to insert into the <see cref="T:System.Collections.IList" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -728,7 +728,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>
           <see langword="true" /> if the <see cref="T:System.Collections.IList" /> has a fixed size; otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
@@ -759,7 +759,7 @@
       </Parameters>
       <Docs>
         <param name="index">The zero-based index of the item to get or set.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <value>The object that is at the specified index.</value>
         <remarks>To be added.</remarks>
       </Docs>
@@ -789,7 +789,7 @@
       </Parameters>
       <Docs>
         <param name="value">The <see cref="T:System.Object" /> to remove from the <see cref="T:System.Collections.IList" />.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 700c655331b..7c206f41cdd 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -648,7 +648,7 @@
   
  For WPF core-level element deriving scenarios, the behavior for <xref:System.Windows.UIElement.Arrange%2A> should not (and cannot, unless you shadow) be changed. Instead, you should override <xref:System.Windows.UIElement.ArrangeCore%2A> in your class. Your <xref:System.Windows.UIElement.ArrangeCore%2A> implementation is called internally by <xref:System.Windows.UIElement.Arrange%2A> as part of default WPF framework-level layout operations. However, this assumes you are using WPF framework-level layout and its layout system, which is often not the case if you are specifically deriving elements at the WPF core-level from the <xref:System.Windows.UIElement> base element class. Your <xref:System.Windows.UIElement.ArrangeCore%2A> implementation should also call <xref:System.Windows.UIElement.Arrange%2A> on each child element, if it has child elements. Note that the WPF core-level scenario implies that you are not using a <xref:System.Windows.FrameworkElement> derived class, because <xref:System.Windows.FrameworkElement> seals <xref:System.Windows.FrameworkElement.ArrangeCore%2A>.  
   
- Computation of WPF framework-level layout positioning in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] consists of a <xref:System.Windows.UIElement.Measure%2A> call and an <xref:System.Windows.UIElement.Arrange%2A> call. During the <xref:System.Windows.UIElement.Measure%2A> call, the layout system determines an element's size requirements using a provided <xref:System.Windows.Size> (`availableSize`) argument. During the <xref:System.Windows.UIElement.Arrange%2A> call, the layout system finalizes the size and position of an element's bounding box.  For more information, see [Layout](/dotnet/framework/wpf/advanced/layout).  
+ Computation of WPF framework-level layout positioning in Windows Presentation Foundation (WPF) consists of a <xref:System.Windows.UIElement.Measure%2A> call and an <xref:System.Windows.UIElement.Arrange%2A> call. During the <xref:System.Windows.UIElement.Measure%2A> call, the layout system determines an element's size requirements using a provided <xref:System.Windows.Size> (`availableSize`) argument. During the <xref:System.Windows.UIElement.Arrange%2A> call, the layout system finalizes the size and position of an element's bounding box.  For more information, see [Layout](/dotnet/framework/wpf/advanced/layout).  
   
  `availableSize` can be any number from zero to infinity. Elements to be laid out return the minimum <xref:System.Windows.Size> they require through the `availableSize` parameter.  
   
@@ -5423,7 +5423,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Computation of layout positioning in [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] is comprised of a <xref:System.Windows.UIElement.Measure%2A> call and an <xref:System.Windows.UIElement.Arrange%2A> call. During the <xref:System.Windows.UIElement.Measure%2A> call, an element determines its size requirements by using an `availableSize` input. During the <xref:System.Windows.UIElement.Arrange%2A> call, the element size is finalized.  
+ Computation of layout positioning in Windows Presentation Foundation (WPF) is comprised of a <xref:System.Windows.UIElement.Measure%2A> call and an <xref:System.Windows.UIElement.Arrange%2A> call. During the <xref:System.Windows.UIElement.Measure%2A> call, an element determines its size requirements by using an `availableSize` input. During the <xref:System.Windows.UIElement.Arrange%2A> call, the element size is finalized.  
   
  `availableSize` can be any number from zero to infinite. Elements participating in layout should return the minimum <xref:System.Windows.Size> they require for a given `availableSize`.  
   
@@ -6436,13 +6436,13 @@ Image with an Elliptical Clip Region
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns class-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations for the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Returns class-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations for the Windows Presentation Foundation (WPF) infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>To be added.</remarks>
         <block subset="none" type="overrides">
           <para>The implementation of this method is typically to call the constructor of a specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation, and return it as the return value.  
   
- All <see cref="T:System.Windows.UIElement" /> derived classes should implement this method in order to provide their own specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure. For details on implementing this pattern, see <see cref="T:System.Windows.Automation.Peers.AutomationPeer" />.</para>
+ All <see cref="T:System.Windows.UIElement" /> derived classes should implement this method in order to provide their own specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the Windows Presentation Foundation (WPF) infrastructure. For details on implementing this pattern, see <see cref="T:System.Windows.Automation.Peers.AutomationPeer" />.</para>
         </block>
       </Docs>
     </Member>
@@ -6671,7 +6671,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method, although virtual, does have a default implementation that raises the event.  
   
- This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement.IsFocused%2A> property value changes. The <xref:System.Windows.UIElement.OnGotFocus%2A> implementation differs from some other [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] On* implementations, which only provide a convenient way to add class handling for that event.  
+ This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement.IsFocused%2A> property value changes. The <xref:System.Windows.UIElement.OnGotFocus%2A> implementation differs from some other Windows Presentation Foundation (WPF) On* implementations, which only provide a convenient way to add class handling for that event.  
   
  ]]></format>
         </remarks>
@@ -7219,7 +7219,7 @@ Image with an Elliptical Clip Region
 ## Remarks  
  This method, although virtual, does have a default implementation that raises the event.  
   
- This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement.IsFocused%2A> property value changes. This implementation differs from some other [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] On* implementations, which only provide a convenient way to add class handling for that event.  
+ This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement.IsFocused%2A> property value changes. This implementation differs from some other Windows Presentation Foundation (WPF) On* implementations, which only provide a convenient way to add class handling for that event.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/UIElement3D.xml b/xml/System.Windows/UIElement3D.xml
index 37bb3f512d3..bee6b531c5f 100644
--- a/xml/System.Windows/UIElement3D.xml
+++ b/xml/System.Windows/UIElement3D.xml
@@ -4816,7 +4816,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns class-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations for the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure.</summary>
+        <summary>Returns class-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations for the Windows Presentation Foundation (WPF) infrastructure.</summary>
         <returns>The type-specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -4829,7 +4829,7 @@
         <block subset="none" type="overrides">
           <para>The implementation of this method is typically to call the constructor of a specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementation, and return it as the return value.  
   
- All <see cref="T:System.Windows.UIElement3D" /> derived classes should implement this method in order to provide their own specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure. For details on implementing this pattern, see <see cref="T:System.Windows.Automation.Peers.AutomationPeer" />.</para>
+ All <see cref="T:System.Windows.UIElement3D" /> derived classes should implement this method in order to provide their own specific <see cref="T:System.Windows.Automation.Peers.AutomationPeer" /> implementations to the Windows Presentation Foundation (WPF) infrastructure. For details on implementing this pattern, see <see cref="T:System.Windows.Automation.Peers.AutomationPeer" />.</para>
         </block>
       </Docs>
     </Member>
@@ -5068,7 +5068,7 @@
 ## Remarks  
  This method, although virtual, does have a default implementation that raises the event.  
   
- This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement3D.IsFocused%2A> property value changes. The <xref:System.Windows.UIElement3D.OnGotFocus%2A> implementation differs from some other [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] On* implementations, which only provide a convenient way to add class handling for that event.  
+ This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement3D.IsFocused%2A> property value changes. The <xref:System.Windows.UIElement3D.OnGotFocus%2A> implementation differs from some other Windows Presentation Foundation (WPF) On* implementations, which only provide a convenient way to add class handling for that event.  
   
  <xref:System.Windows.UIElement3D.OnGotFocus%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
@@ -5649,7 +5649,7 @@
 ## Remarks  
  This method, although virtual, does have a default implementation that raises the event.  
   
- This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement3D.IsFocused%2A> property value changes. This implementation differs from some other [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] On* implementations, which only provide a convenient way to add class handling for that event.  
+ This On* method implementation is intended to raise the event, and this same method implementation is invoked internally to raise the event when the <xref:System.Windows.UIElement3D.IsFocused%2A> property value changes. This implementation differs from some other Windows Presentation Foundation (WPF) On* implementations, which only provide a convenient way to add class handling for that event.  
   
  <xref:System.Windows.UIElement3D.OnLostFocus%2A> is introduced in the .NET Framework version 3.5.  For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
diff --git a/xml/System.Windows/UIPropertyMetadata.xml b/xml/System.Windows/UIPropertyMetadata.xml
index 7e57ae8aeac..efd995b9e30 100644
--- a/xml/System.Windows/UIPropertyMetadata.xml
+++ b/xml/System.Windows/UIPropertyMetadata.xml
@@ -238,7 +238,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In general, the default dependency properties available in the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] framework implementation APIs can be animated. You might set this property to `true` in the metadata of your own custom dependency property to disable animations on it.  
+ In general, the default dependency properties available in the Windows Presentation Foundation (WPF) framework implementation APIs can be animated. You might set this property to `true` in the metadata of your own custom dependency property to disable animations on it.  
   
  If a property with this value `true` attempts to be used as an animation target, a runtime exception will be raised.  
   
diff --git a/xml/System.Windows/Vector.xml b/xml/System.Windows/Vector.xml
index ff1632fcda9..e6b6733d08d 100644
--- a/xml/System.Windows/Vector.xml
+++ b/xml/System.Windows/Vector.xml
@@ -1523,7 +1523,7 @@
  -or-  
   
  <see langword="null" /> to obtain the numeric format information from the current locale setting of the operating system.</param>
-        <summary>This member supports the [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
+        <summary>This member supports the Windows Presentation Foundation (WPF) infrastructure and is not intended to be used directly from your code. For a description of this member, see <see cref="M:System.IFormattable.ToString(System.String,System.IFormatProvider)" />.</summary>
         <returns>A string containing the value of the current instance in the specified format.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Windows/VisualStateManager.xml b/xml/System.Windows/VisualStateManager.xml
index 852831818d6..1b69c4d2af0 100644
--- a/xml/System.Windows/VisualStateManager.xml
+++ b/xml/System.Windows/VisualStateManager.xml
@@ -24,7 +24,7 @@
   
  The <xref:System.Windows.VisualStateManager> also enables you to specify when a control enters a specific state. The method that you should call to change states depends on your scenario. If you create a control that uses the <xref:System.Windows.VisualStateManager> in its <xref:System.Windows.Controls.ControlTemplate>, call the <xref:System.Windows.VisualStateManager.GoToState%2A> method. For more information about how to create controls that use the <xref:System.Windows.VisualStateManager>, see [Creating a Control That Has a Customizable Appearance](/dotnet/framework/wpf/controls/creating-a-control-that-has-a-customizable-appearance). If you use the <xref:System.Windows.VisualStateManager> outside of a <xref:System.Windows.Controls.ControlTemplate> (for example, if you use a <xref:System.Windows.VisualStateManager> in a <xref:System.Windows.Controls.UserControl> or in a single element), call the <xref:System.Windows.VisualStateManager.GoToElementState%2A> method. In either case, the <xref:System.Windows.VisualStateManager> performs the logic that is required to appropriately start and stop the storyboards that are associated with the involved state. For example, suppose that a control defines the states, `State1` and `State2`, each of which has a storyboard associated with it. If the control is in `State1` and you pass `State2` to <xref:System.Windows.VisualStateManager.GoToState%2A> or <xref:System.Windows.VisualStateManager.GoToElementState%2A>, the <xref:System.Windows.VisualStateManager> starts the storyboard in `State2` and stops the storyboard in `State1`.  
   
- Controls that are included with [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] use the <xref:System.Windows.VisualStateManager> to change visual states. When you create a <xref:System.Windows.Controls.ControlTemplate> for a control that is included with WPF, you can add <xref:System.Windows.VisualState> objects to the control's <xref:System.Windows.Controls.ControlTemplate> to specify the control's appearance in a certain state. To find the names of the visual states for the controls that are included with WPF, see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). The control's logic handles transitioning between states, so you do not need to do anything other than define the <xref:System.Windows.VisualState> objects in the new <xref:System.Windows.Controls.ControlTemplate>. For more information about how to create control templates for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
+ Controls that are included with Windows Presentation Foundation (WPF) use the <xref:System.Windows.VisualStateManager> to change visual states. When you create a <xref:System.Windows.Controls.ControlTemplate> for a control that is included with WPF, you can add <xref:System.Windows.VisualState> objects to the control's <xref:System.Windows.Controls.ControlTemplate> to specify the control's appearance in a certain state. To find the names of the visual states for the controls that are included with WPF, see [Control Styles and Templates](/dotnet/framework/wpf/controls/control-styles-and-templates). The control's logic handles transitioning between states, so you do not need to do anything other than define the <xref:System.Windows.VisualState> objects in the new <xref:System.Windows.Controls.ControlTemplate>. For more information about how to create control templates for existing controls, see [Customizing the Appearance of an Existing Control by Creating a ControlTemplate](/dotnet/framework/wpf/controls/customizing-the-appearance-of-an-existing-control).  
   
  If you want to implement your own logic for transitioning between states, you must inherit from <xref:System.Windows.VisualStateManager>, override the <xref:System.Windows.VisualStateManager.GoToStateCore%2A> method, and set the <xref:System.Windows.VisualStateManager.CustomVisualStateManager%2A?displayProperty=nameWithType> attached property on the control that uses the custom logic.  
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index c4e98e4dd42..a164fe35f73 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The point of interaction between a user and a standalone application is a window. A [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] window consists of two distinct areas:  
+ The point of interaction between a user and a standalone application is a window. A Windows Presentation Foundation (WPF) window consists of two distinct areas:  
   
 -   A non-client area, which hosts the windows adornments, including an icon, title, System menu, minimize button, maximize button, restore button, close button, and a border.  
   
diff --git a/xml/System.Xaml/XamlServices.xml b/xml/System.Xaml/XamlServices.xml
index c74da051173..bf02c9b5370 100644
--- a/xml/System.Xaml/XamlServices.xml
+++ b/xml/System.Xaml/XamlServices.xml
@@ -76,7 +76,7 @@
 -   The XAML types that are specified in the source XAML must resolve to backing types in the relevant XAML namespaces. For example, XAML types for WPF namespaces can resolve to a WPF XAML namespace as specified in the XAML; the assemblies for WPF must be included in the project or available in the run time; and so on.  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing Windows Presentation Foundation (WPF) types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>
@@ -272,7 +272,7 @@
 -   The XAML types that are specified in the `xaml` input must resolve to backing types in the relevant XAML namespaces. For example, XAML types for a WPF namespace can resolve to a WPF XAML namespace as specified in the XAML; the assemblies for WPF must be included in the project or be available in the run time; and so on.  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML, and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing Windows Presentation Foundation (WPF) types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML, and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>
@@ -354,7 +354,7 @@
 ## Remarks  
   
 > [!IMPORTANT]
->  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing [!INCLUDE[TLA#tla_winclient](~/includes/tlasharptla-winclient-md.md)] types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
+>  <xref:System.Xaml.XamlServices> is not the recommended XAML reading or XAML writing API set if you are processing Windows Presentation Foundation (WPF) types, or types based on WPF. For WPF usage, use <xref:System.Windows.Markup.XamlReader?displayProperty=nameWithType> for reading or loading XAML; and <xref:System.Windows.Markup.XamlWriter?displayProperty=nameWithType> for writing back XAML. These classes use <xref:System.Xaml> APIs internally in their implementation; however, they also provide support for WPF-specific concepts that influence the nature of XAML reading and writing, such as optimizations for dependency properties.  
   
  ]]></format>
         </remarks>

From 6dd17ad631c4de467f96829333dafde5939c73c2 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:11:14 -0800
Subject: [PATCH 169/236] tlasharptla-winexpl

---
 xml/System.Windows.Automation/ExpandCollapsePattern.xml | 4 ++--
 xml/System.Windows/Window.xml                           | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Windows.Automation/ExpandCollapsePattern.xml b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
index 9684130b837..b73f9690cee 100644
--- a/xml/System.Windows.Automation/ExpandCollapsePattern.xml
+++ b/xml/System.Windows.Automation/ExpandCollapsePattern.xml
@@ -94,7 +94,7 @@
 ## Remarks  
  This is a blocking method that returns after the UI Automation element has been collapsed.  
   
- There are cases when a UI Automation element that is marked as a leaf node might not know whether it has children until either the <xref:System.Windows.Automation.ExpandCollapsePattern.Collapse%2A> or the <xref:System.Windows.Automation.ExpandCollapsePattern.Expand%2A> method is called. This behavior is possible with a tree view control that does delayed loading of its child items. For example, [!INCLUDE[TLA#tla_winexpl](~/includes/tlasharptla-winexpl-md.md)] might display the expand icon for a node even though there are currently no child items; when the icon is clicked, the control polls for child items, finds none, and removes the expand icon. In these cases clients should listen for a property-changed event on the <xref:System.Windows.Automation.ExpandCollapsePattern.ExpandCollapsePatternInformation.ExpandCollapseState%2A> property by registering an event handler with the <xref:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler%2A> method.  
+ There are cases when a UI Automation element that is marked as a leaf node might not know whether it has children until either the <xref:System.Windows.Automation.ExpandCollapsePattern.Collapse%2A> or the <xref:System.Windows.Automation.ExpandCollapsePattern.Expand%2A> method is called. This behavior is possible with a tree view control that does delayed loading of its child items. For example, Microsoft Windows Explorer might display the expand icon for a node even though there are currently no child items; when the icon is clicked, the control polls for child items, finds none, and removes the expand icon. In these cases clients should listen for a property-changed event on the <xref:System.Windows.Automation.ExpandCollapsePattern.ExpandCollapsePatternInformation.ExpandCollapseState%2A> property by registering an event handler with the <xref:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler%2A> method.  
   
    
   
@@ -172,7 +172,7 @@
 ## Remarks  
  This is a blocking method that returns after the <xref:System.Windows.Automation.AutomationElement> has been expanded.  
   
- There are cases when a <xref:System.Windows.Automation.AutomationElement> that is marked as a leaf node might not know whether it has children until either the <xref:System.Windows.Automation.ExpandCollapsePattern.Collapse%2A> or the <xref:System.Windows.Automation.ExpandCollapsePattern.Expand%2A> method is called. This behavior is possible with a tree view control that does delayed loading of its child items. For example, [!INCLUDE[TLA#tla_winexpl](~/includes/tlasharptla-winexpl-md.md)] might display the expand icon for a node even though there are currently no child items; when the icon is clicked, the control polls for child items, finds none, and removes the expand icon. In these cases clients should listen for a property-changed event on the <xref:System.Windows.Automation.ExpandCollapsePattern.ExpandCollapsePatternInformation.ExpandCollapseState%2A> property by registering an event handler with the <xref:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler%2A> method.  
+ There are cases when a <xref:System.Windows.Automation.AutomationElement> that is marked as a leaf node might not know whether it has children until either the <xref:System.Windows.Automation.ExpandCollapsePattern.Collapse%2A> or the <xref:System.Windows.Automation.ExpandCollapsePattern.Expand%2A> method is called. This behavior is possible with a tree view control that does delayed loading of its child items. For example, Microsoft Windows Explorer might display the expand icon for a node even though there are currently no child items; when the icon is clicked, the control polls for child items, finds none, and removes the expand icon. In these cases clients should listen for a property-changed event on the <xref:System.Windows.Automation.ExpandCollapsePattern.ExpandCollapsePatternInformation.ExpandCollapseState%2A> property by registering an event handler with the <xref:System.Windows.Automation.Automation.AddAutomationPropertyChangedEventHandler%2A> method.  
   
    
   
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index a164fe35f73..884ba2e2aa0 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -874,7 +874,7 @@
   
  If you use <xref:System.Windows.Window.Icon%2A> to specify a custom window icon, you can restore the default application icon by setting <xref:System.Windows.Window.Icon%2A> to `null`.  
   
- A single icon can be used in a variety of ways in Windows, including being shown in the title bar of a window, the task bar for a window, the ALT+TAB file selection list. Each of these shows the icon using a different size; a 16x16 pixel icon is displayed in the title bar of a window and in the task bar, while a 32x32 pixel icon is displayed in the ALT+TAB file selection list. Some applications, like [!INCLUDE[TLA#tla_winexpl](~/includes/tlasharptla-winexpl-md.md)], provide a **View** menu that allows you to choose the size of the icon you'd like to view.  
+ A single icon can be used in a variety of ways in Windows, including being shown in the title bar of a window, the task bar for a window, the ALT+TAB file selection list. Each of these shows the icon using a different size; a 16x16 pixel icon is displayed in the title bar of a window and in the task bar, while a 32x32 pixel icon is displayed in the ALT+TAB file selection list. Some applications, like Microsoft Windows Explorer, provide a **View** menu that allows you to choose the size of the icon you'd like to view.  
   
  To cater to the various display sizes, an icon file is composed of one or more actual icons where each one represents a version of the icon that targets a specific size and color depth. For example, one icon may only have a single 16x16 pixel icon with 16 colors, while another may contain 16x16 pixel and 32x32 pixel icons with both 16 colors and 256 colors.  
   

From f77fe22a6a9df54ac239dbacab263edaa746aa57 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:11:37 -0800
Subject: [PATCH 170/236] tlasharptla-winforms

---
 .../ElementHost.xml                           | 22 +++++++++----------
 .../PropertyMap.xml                           |  2 +-
 .../PropertyTranslator.xml                    |  2 +-
 .../IKeyboardInputSink.xml                    |  2 +-
 .../IKeyboardInputSite.xml                    |  2 +-
 xml/System.Windows.Threading/Dispatcher.xml   |  2 +-
 .../DispatcherFrame.xml                       |  4 ++--
 xml/ns-System.Windows.Forms.Integration.xml   |  6 ++---
 8 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/xml/System.Windows.Forms.Integration/ElementHost.xml b/xml/System.Windows.Forms.Integration/ElementHost.xml
index 7ec0d343c61..7b8fc4786f3 100644
--- a/xml/System.Windows.Forms.Integration/ElementHost.xml
+++ b/xml/System.Windows.Forms.Integration/ElementHost.xml
@@ -43,9 +43,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Windows.Forms.Integration.ElementHost> control to place a WPF <xref:System.Windows.UIElement> on your [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control or form.  
+ Use the <xref:System.Windows.Forms.Integration.ElementHost> control to place a WPF <xref:System.Windows.UIElement> on your Windows Forms control or form.  
   
- To host a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control in a WPF element, use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> element.  
+ To host a Windows Forms control in a WPF element, use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> element.  
   
 > [!NOTE]
 >  WindowsFormsIntegration.dll is installed with the WPF assemblies. The default location for the assembly is %programfiles%\Reference Assemblies\Microsoft\Framework\v3.0\WindowsFormsIntegration.dll.  
@@ -805,12 +805,12 @@
       </Parameters>
       <Docs>
         <param name="window">The Windows Presentation Foundation (WPF) window to be opened modelessly.</param>
-        <summary>Enables a <see cref="T:System.Windows.Window" /> to receive keyboard messages correctly when it is opened modelessly from [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)].</summary>
+        <summary>Enables a <see cref="T:System.Windows.Window" /> to receive keyboard messages correctly when it is opened modelessly from Windows Forms.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Call the <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method to forward all keyboard messages when a WPF window is opened modelessly. The <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method installs a message filter in the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application. The filter forwards all keyboard messages when the modeless window is active.  
+ Call the <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method to forward all keyboard messages when a WPF window is opened modelessly. The <xref:System.Windows.Forms.Integration.ElementHost.EnableModelessKeyboardInterop%2A> method installs a message filter in the Windows Forms-based application. The filter forwards all keyboard messages when the modeless window is active.  
   
  ]]></format>
         </remarks>
@@ -2321,14 +2321,14 @@
       <Docs>
         <param name="msg">A <see cref="T:System.Windows.Forms.Message" />, passed by reference, that represents the window message to process.</param>
         <param name="keyData">One of the <see cref="T:System.Windows.Forms.Keys" /> values representing the key to process.</param>
-        <summary>Processes a command key, ensuring that the hosted element has an opportunity to handle the command before normal [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] processing.</summary>
+        <summary>Processes a command key, ensuring that the hosted element has an opportunity to handle the command before normal Windows Forms processing.</summary>
         <returns>
           <see langword="true" /> if the character is a Windows Presentation Foundation (WPF) shortcut key; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a key message is not handled by the hosted WPF element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
+ If a key message is not handled by the hosted WPF element, it is forwarded up the Windows Forms class hierarchy for processing.  
   
  ]]></format>
         </remarks>
@@ -2357,14 +2357,14 @@
       </Parameters>
       <Docs>
         <param name="charCode">The character to process.</param>
-        <summary>Processes a mnemonic character, ensuring that the hosted element has an opportunity to handle the mnemonic before normal [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] processing.</summary>
+        <summary>Processes a mnemonic character, ensuring that the hosted element has an opportunity to handle the mnemonic before normal Windows Forms processing.</summary>
         <returns>
           <see langword="true" /> if the character is a Windows Presentation Foundation (WPF) shortcut key; otherwise, <see langword="false" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If a key message is not handled by the hosted WPF element, it is forwarded up the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] class hierarchy for processing.  
+ If a key message is not handled by the hosted WPF element, it is forwarded up the Windows Forms class hierarchy for processing.  
   
  ]]></format>
         </remarks>
@@ -2405,7 +2405,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF technologies have two similar but different property models. *Property mapping* supports interoperation between the two architectures. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
+ The Windows Forms and WPF technologies have two similar but different property models. *Property mapping* supports interoperation between the two architectures. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
   
    
   
@@ -2564,7 +2564,7 @@
       <Docs>
         <param name="dx">The scaling factor for the x-axis.</param>
         <param name="dy">The scaling factor for the y-axis.</param>
-        <summary>Scales the parent container and the hosted [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control.</summary>
+        <summary>Scales the parent container and the hosted Windows Forms control.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Forms.Integration.WindowsFormsHost" />
       </Docs>
@@ -2604,7 +2604,7 @@
   
  Repeated calls to the <xref:System.Windows.Forms.Integration.ElementHost.Select%2A> method do not traverse the hosted elements. To select subsequent elements, call the <xref:System.Windows.FrameworkElement.MoveFocus%2A> method on the <xref:System.Windows.Forms.Integration.ElementHost.HostContainer%2A> property.  
   
- This implementation forwards tab keys from [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] to Windows Presentation Foundation (WPF).  
+ This implementation forwards tab keys from Windows Forms to Windows Presentation Foundation (WPF).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms.Integration/PropertyMap.xml b/xml/System.Windows.Forms.Integration/PropertyMap.xml
index 6e10e4251f8..2c86470dc36 100644
--- a/xml/System.Windows.Forms.Integration/PropertyMap.xml
+++ b/xml/System.Windows.Forms.Integration/PropertyMap.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Windows.Forms.Integration.PropertyMap> class to define translations between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] properties and Windows Presentation Foundation (WPF) properties in a hybrid application. The <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A?displayProperty=nameWithType> and <xref:System.Windows.Forms.Integration.WindowsFormsHost.PropertyMap%2A?displayProperty=nameWithType> properties on the <xref:System.Windows.Forms.Integration.ElementHost> and <xref:System.Windows.Forms.Integration.WindowsFormsHost> classes define mappings from one technology to the other.  
+ Use the <xref:System.Windows.Forms.Integration.PropertyMap> class to define translations between Windows Forms properties and Windows Presentation Foundation (WPF) properties in a hybrid application. The <xref:System.Windows.Forms.Integration.ElementHost.PropertyMap%2A?displayProperty=nameWithType> and <xref:System.Windows.Forms.Integration.WindowsFormsHost.PropertyMap%2A?displayProperty=nameWithType> properties on the <xref:System.Windows.Forms.Integration.ElementHost> and <xref:System.Windows.Forms.Integration.WindowsFormsHost> classes define mappings from one technology to the other.  
   
  For more information, see [Walkthrough: Mapping Properties Using the ElementHost Control](/dotnet/desktop/wpf/advanced/walkthrough-mapping-properties-using-the-elementhost-control?view=netframeworkdesktop-4.8) and [Walkthrough: Mapping Properties Using the WindowsFormsHost Element](/dotnet/desktop/wpf/advanced/walkthrough-mapping-properties-using-the-windowsformshost-element?view=netframeworkdesktop-4.8).  
   
diff --git a/xml/System.Windows.Forms.Integration/PropertyTranslator.xml b/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
index 2839d749d45..67ef96d1a73 100644
--- a/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
+++ b/xml/System.Windows.Forms.Integration/PropertyTranslator.xml
@@ -31,7 +31,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Forms.Integration.PropertyTranslator> delegate is used by the <xref:System.Windows.Forms.Integration.PropertyMap> class to implement property mapping between [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
+ The <xref:System.Windows.Forms.Integration.PropertyTranslator> delegate is used by the <xref:System.Windows.Forms.Integration.PropertyMap> class to implement property mapping between Windows Forms and WPF. For more information, see [Windows Forms and WPF Property Mapping](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-property-mapping).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Interop/IKeyboardInputSink.xml b/xml/System.Windows.Interop/IKeyboardInputSink.xml
index ebf7512ee47..bbc27226430 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSink.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSink.xml
@@ -22,7 +22,7 @@
   
  If your component contains other components, and maintains a tab order, your component must also implement <xref:System.Windows.Interop.IKeyboardInputSite> and keep track of which component has focus.  
   
- For a discussion of the input architecture specifically implemented for [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] interop, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
+ For a discussion of the input architecture specifically implemented for Windows Forms interop, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
   
  <xref:System.Windows.Interop.HwndSource> and <xref:System.Windows.Interop.HwndHost> each implement the <xref:System.Windows.Interop.IKeyboardInputSink> interface, through explicit interface definitions. The explicit definitions supply default behaviors, and can also be accessed if necessary through an <xref:System.Windows.Interop.IKeyboardInputSink> interface cast of <xref:System.Windows.Interop.HwndSource> or <xref:System.Windows.Interop.HwndHost>.  
   
diff --git a/xml/System.Windows.Interop/IKeyboardInputSite.xml b/xml/System.Windows.Interop/IKeyboardInputSite.xml
index fe9e54f17b7..91823c1d836 100644
--- a/xml/System.Windows.Interop/IKeyboardInputSite.xml
+++ b/xml/System.Windows.Interop/IKeyboardInputSite.xml
@@ -22,7 +22,7 @@
   
  The <xref:System.Windows.Interop.IKeyboardInputSite> interface and the <xref:System.Windows.Interop.IKeyboardInputSink> are used together to provide support for keyboard actions across interoperation boundaries. A site (<xref:System.Windows.Interop.IKeyboardInputSite> implementation) represents a parent of a sink (<xref:System.Windows.Interop.IKeyboardInputSink>). The sink (<xref:System.Windows.Interop.IKeyboardInputSink>) implements the majority of keyboard behavior. Each site must also provide a sink, because the site-specific sink is returned by a property of the <xref:System.Windows.Interop.IKeyboardInputSite> interface.  
   
- For a discussion of the input architecture specifically implemented for [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] interoperation, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
+ For a discussion of the input architecture specifically implemented for Windows Forms interoperation, see [Windows Forms and WPF Interoperability Input Architecture](/dotnet/framework/wpf/advanced/windows-forms-and-wpf-interoperability-input-architecture).  
   
  For more information about WPF-Win32 interoperation scenarios, see [WPF and Win32 Interoperation](/dotnet/framework/wpf/advanced/wpf-and-win32-interoperation).  
   
diff --git a/xml/System.Windows.Threading/Dispatcher.xml b/xml/System.Windows.Threading/Dispatcher.xml
index 9d17fba7961..e87532d934f 100644
--- a/xml/System.Windows.Threading/Dispatcher.xml
+++ b/xml/System.Windows.Threading/Dispatcher.xml
@@ -2025,7 +2025,7 @@
  <xref:System.Windows.Threading.DispatcherFrame> allows for the <xref:System.Windows.Threading.DispatcherFrame.Continue%2A> property to be set explicitly and it respects the <xref:System.Windows.Threading.Dispatcher.HasShutdownStarted%2A> property on the <xref:System.Windows.Threading.Dispatcher>.  This means when the <xref:System.Windows.Threading.Dispatcher> starts to shut down, frames that use the default <xref:System.Windows.Threading.DispatcherFrame> implementation will exit, which enables all nested frames to exit.
   
 ## Examples  
- The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
+ The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the Windows Forms <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
   
  [!code-csharp[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/csharp/VS_Snippets_Wpf/DispatcherSnippets/CSharp/Window1.xaml.cs#dispatcherdispatcherframedoevents)]
  [!code-vb[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DispatcherSnippets/visualbasic/window1.xaml.vb#dispatcherdispatcherframedoevents)]  
diff --git a/xml/System.Windows.Threading/DispatcherFrame.xml b/xml/System.Windows.Threading/DispatcherFrame.xml
index 8a091b2d078..f42e59dbd78 100644
--- a/xml/System.Windows.Threading/DispatcherFrame.xml
+++ b/xml/System.Windows.Threading/DispatcherFrame.xml
@@ -35,7 +35,7 @@
    
   
 ## Examples  
- The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
+ The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the Windows Forms <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
   
  [!code-csharp[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/csharp/VS_Snippets_Wpf/DispatcherSnippets/CSharp/Window1.xaml.cs#dispatcherdispatcherframedoevents)]
  [!code-vb[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DispatcherSnippets/visualbasic/window1.xaml.vb#dispatcherdispatcherframedoevents)]  
@@ -160,7 +160,7 @@ At application shutdown, all frames are requested to exit.
    
   
 ## Examples  
- The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
+ The following example shows how to use a <xref:System.Windows.Threading.DispatcherFrame> to achieve similar results as the Windows Forms <xref:System.Windows.Forms.Application.DoEvents%2A> method.  
   
  [!code-csharp[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/csharp/VS_Snippets_Wpf/DispatcherSnippets/CSharp/Window1.xaml.cs#dispatcherdispatcherframedoevents)]
  [!code-vb[dispatchersnippets#DispatcherDispatcherFrameDoEvents](~/samples/snippets/visualbasic/VS_Snippets_Wpf/DispatcherSnippets/visualbasic/window1.xaml.vb#dispatcherdispatcherframedoevents)]  
diff --git a/xml/ns-System.Windows.Forms.Integration.xml b/xml/ns-System.Windows.Forms.Integration.xml
index 63b7c31d405..0ea65c764c5 100644
--- a/xml/ns-System.Windows.Forms.Integration.xml
+++ b/xml/ns-System.Windows.Forms.Integration.xml
@@ -5,13 +5,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Forms.Integration> namespace contains classes that enable interoperation between the [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] and WPF technologies. When you use <xref:System.Windows.Forms.Integration> classes, you can host [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] controls on WPF pages, and WPF elements in [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based applications.  
+ The <xref:System.Windows.Forms.Integration> namespace contains classes that enable interoperation between the Windows Forms and WPF technologies. When you use <xref:System.Windows.Forms.Integration> classes, you can host Windows Forms controls on WPF pages, and WPF elements in Windows Forms-based applications.  
   
  The two key classes that implement interoperation capabilities are <xref:System.Windows.Forms.Integration.WindowsFormsHost> and <xref:System.Windows.Forms.Integration.ElementHost>. Which class you use depends on your control implementation:  
   
--   Use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> class when you must use a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)] control on a WPF page.  
+-   Use the <xref:System.Windows.Forms.Integration.WindowsFormsHost> class when you must use a Windows Forms control on a WPF page.  
   
--   Use the <xref:System.Windows.Forms.Integration.ElementHost> class when you must use a WPF element in a [!INCLUDE[TLA#tla_winforms](~/includes/tlasharptla-winforms-md.md)]-based application.  
+-   Use the <xref:System.Windows.Forms.Integration.ElementHost> class when you must use a WPF element in a Windows Forms-based application.  
   
  ]]></format>
     </remarks>

From 5d1ffbc0bed32d1d61adb9f0ce5d20d5dbab82f6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:12:07 -0800
Subject: [PATCH 171/236] tlasharptla-winfxwebapp

---
 xml/System.Windows.Controls.Primitives/Popup.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Controls.Primitives/Popup.xml b/xml/System.Windows.Controls.Primitives/Popup.xml
index 1a97c01eb2f..958ebeac0ae 100644
--- a/xml/System.Windows.Controls.Primitives/Popup.xml
+++ b/xml/System.Windows.Controls.Primitives/Popup.xml
@@ -58,7 +58,7 @@
   
  A <xref:System.Windows.Controls.Primitives.Popup> is sized to its content by default. When this occurs, applying a <xref:System.Windows.UIElement.RenderTransform%2A> or bitmap effects may cause the <xref:System.Windows.Controls.Primitives.Popup> to be obscured. This occurs because the default size of the content does not provide enough area for the effects to display. If more space is required, you can define a margin around the <xref:System.Windows.Controls.Primitives.Popup> content to increase the area that is available to the control.  
   
- The <xref:System.Windows.FrameworkElement.Parent%2A> property must be set on the <xref:System.Windows.Controls.Primitives.Popup> when used in a [!INCLUDE[TLA#tla_winfxwebapp](~/includes/tlasharptla-winfxwebapp-md.md)].  
+ The <xref:System.Windows.FrameworkElement.Parent%2A> property must be set on the <xref:System.Windows.Controls.Primitives.Popup> when used in a XAML browser application (XBAP).  
   
  To create a tooltip, use the <xref:System.Windows.Controls.ToolTip> and <xref:System.Windows.Controls.ToolTipService> classes. For more information, see [ToolTip Overview](/dotnet/framework/wpf/controls/tooltip-overview).  
   
@@ -129,7 +129,7 @@
 ## Remarks  
  A <xref:System.Windows.Controls.Primitives.Popup> control can only contain transparent content when the application runs with full trust. An application that runs with full trust has complete access to system resources and is typically installed on the local system. For more information, see [Security (WPF)](/dotnet/framework/wpf/security-wpf).  
   
- This property cannot be set to `true` when the <xref:System.Windows.Controls.Primitives.Popup> is hosted in a [!INCLUDE[TLA#tla_winfxwebapp](~/includes/tlasharptla-winfxwebapp-md.md)].  
+ This property cannot be set to `true` when the <xref:System.Windows.Controls.Primitives.Popup> is hosted in a XAML browser application (XBAP).  
   
  If the <xref:System.Windows.Controls.Primitives.Popup.AllowsTransparency%2A> property is set to `true` in an application that does not run in full trust, the <xref:System.Windows.Controls.Primitives.Popup.AllowsTransparency%2A> property value is changed to `false`. An application that is hosted in a browser is an example of an application that does not run in full trust.  
   

From 15e0e5d75253852a633ff372974b1ed28d4d6347 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:12:29 -0800
Subject: [PATCH 172/236] tlasharptla-winvista

---
 xml/Microsoft.Win32/FileDialogCustomPlace.xml | 2 +-
 xml/Microsoft.Win32/OpenFileDialog.xml        | 2 +-
 xml/Microsoft.Win32/SaveFileDialog.xml        | 2 +-
 xml/System.Windows.Input/Stylus.xml           | 8 ++++----
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/Microsoft.Win32/FileDialogCustomPlace.xml b/xml/Microsoft.Win32/FileDialogCustomPlace.xml
index 79d62ab356f..6ef0441f7ae 100644
--- a/xml/Microsoft.Win32/FileDialogCustomPlace.xml
+++ b/xml/Microsoft.Win32/FileDialogCustomPlace.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Starting in [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)], open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. This class allows you to modify the list that appears when your application uses a file dialog box. For the list of known folders for custom places, see <xref:Microsoft.Win32.FileDialogCustomPlaces>.  
+ Starting in Windows Vista, open and save file dialog boxes have a **Favorite Links** panel on the left side of the dialog box that allows the user to quickly navigate to a different location. These links are called custom places. This class allows you to modify the list that appears when your application uses a file dialog box. For the list of known folders for custom places, see <xref:Microsoft.Win32.FileDialogCustomPlaces>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/Microsoft.Win32/OpenFileDialog.xml b/xml/Microsoft.Win32/OpenFileDialog.xml
index ac70989c902..87fbf6f4e90 100644
--- a/xml/Microsoft.Win32/OpenFileDialog.xml
+++ b/xml/Microsoft.Win32/OpenFileDialog.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The following figure shows an <xref:Microsoft.Win32.OpenFileDialog> for [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)].  
+ The following figure shows an <xref:Microsoft.Win32.OpenFileDialog> for Windows Vista.  
   
  ![Open dialog box](~/add/media/dialogboxesoverviewfigure2.png "Open dialog box")  
   
diff --git a/xml/Microsoft.Win32/SaveFileDialog.xml b/xml/Microsoft.Win32/SaveFileDialog.xml
index 709a7b7e241..a389c74737d 100644
--- a/xml/Microsoft.Win32/SaveFileDialog.xml
+++ b/xml/Microsoft.Win32/SaveFileDialog.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The following figure shows a <xref:Microsoft.Win32.SaveFileDialog> for [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)].  
+ The following figure shows a <xref:Microsoft.Win32.SaveFileDialog> for Windows Vista.  
   
  ![Save As dialog box](~/add/media/dialogboxesoverviewfigure3.png "Save As dialog box")  
   
diff --git a/xml/System.Windows.Input/Stylus.xml b/xml/System.Windows.Input/Stylus.xml
index 661116c1ed3..00512064d1d 100644
--- a/xml/System.Windows.Input/Stylus.xml
+++ b/xml/System.Windows.Input/Stylus.xml
@@ -1122,7 +1122,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)], a flick, one of the possible system gestures, is a short, quick, straight stroke that can be mapped to a navigation or shortcut command. By default, flicks are disabled on the <xref:System.Windows.Controls.InkCanvas>, <xref:System.Windows.Controls.InkPresenter>, and <xref:System.Windows.Controls.Primitives.ScrollBar>. Flicks are enabled on all other controls.  
+ In Windows Vista, a flick, one of the possible system gestures, is a short, quick, straight stroke that can be mapped to a navigation or shortcut command. By default, flicks are disabled on the <xref:System.Windows.Controls.InkCanvas>, <xref:System.Windows.Controls.InkPresenter>, and <xref:System.Windows.Controls.Primitives.ScrollBar>. Flicks are enabled on all other controls.  
   
 <a name="dependencyPropertyInfo_IsFlicksEnabled"></a>   
 ## Dependency Property Information  
@@ -1185,7 +1185,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Press and hold maps to a right-click on a mouse. In [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)] you can disable this behavior on elements if you foresee a situation where the user might hold the tablet pen down without intending to simulate a right-click.  
+ Press and hold maps to a right-click on a mouse. In Windows Vista you can disable this behavior on elements if you foresee a situation where the user might hold the tablet pen down without intending to simulate a right-click.  
   
 <a name="dependencyPropertyInfo_IsPressAndHoldEnabled"></a>   
 ## Dependency Property Information  
@@ -1248,7 +1248,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)], a short animation occurs when the user taps the control. By default, tap feedback is disabled on the <xref:System.Windows.Controls.InkCanvas>. It is enabled on all other controls.  
+ In Windows Vista, a short animation occurs when the user taps the control. By default, tap feedback is disabled on the <xref:System.Windows.Controls.InkCanvas>. It is enabled on all other controls.  
   
 <a name="dependencyPropertyInfo_IsTapFeedbackEnabled"></a>   
 ## Dependency Property Information  
@@ -1312,7 +1312,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_winvista](~/includes/tlasharptla-winvista-md.md)], a short animation occurs when the user touches the control with a finger. By default, touch feedback is disabled on the <xref:System.Windows.Controls.InkCanvas>. It is enabled on all other controls.  
+ In Windows Vista, a short animation occurs when the user touches the control with a finger. By default, touch feedback is disabled on the <xref:System.Windows.Controls.InkCanvas>. It is enabled on all other controls.  
   
 <a name="dependencyPropertyInfo_IsTouchFeedbackEnabled"></a>   
 ## Dependency Property Information  

From bc169f7925521ba3cff21a48a045cacb478329a6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:13:03 -0800
Subject: [PATCH 173/236] tlasharptla-wmp

---
 xml/System.Windows.Automation/MultipleViewPattern.xml | 2 +-
 xml/System.Windows.Media/ExceptionEventArgs.xml       | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Automation/MultipleViewPattern.xml b/xml/System.Windows.Automation/MultipleViewPattern.xml
index cc1aee14022..10d5a5bada2 100644
--- a/xml/System.Windows.Automation/MultipleViewPattern.xml
+++ b/xml/System.Windows.Automation/MultipleViewPattern.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)] documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and [!INCLUDE[TLA#tla_wmp](~/includes/tlasharptla-wmp-md.md)] skins. The supported views are determined by the control developer and are specific to each control.  
+ Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)] documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and Microsoft Windows Media Player skins. The supported views are determined by the control developer and are specific to each control.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media/ExceptionEventArgs.xml b/xml/System.Windows.Media/ExceptionEventArgs.xml
index b117767c5ef..ba9aaf651e3 100644
--- a/xml/System.Windows.Media/ExceptionEventArgs.xml
+++ b/xml/System.Windows.Media/ExceptionEventArgs.xml
@@ -54,7 +54,7 @@
  -or-  
   
  The file format is not recognized.</exception>
-        <exception cref="T:System.Windows.Media.InvalidWmpVersionException">The detected version of [!INCLUDE[TLA#tla_wmp](~/includes/tlasharptla-wmp-md.md)] is not supported.</exception>
+        <exception cref="T:System.Windows.Media.InvalidWmpVersionException">The detected version of Microsoft Windows Media Player is not supported.</exception>
         <exception cref="T:System.NotSupportedException">The operation is not supported.</exception>
         <exception cref="T:System.Runtime.InteropServices.COMException">A COM error code appears.</exception>
       </Docs>

From 79b27d4439ee2e465914a9c646f8e63f94cd0efb Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:13:21 -0800
Subject: [PATCH 174/236] tlasharptla-word

---
 xml/System.Windows.Automation/MultipleViewPattern.xml | 2 +-
 xml/System.Windows/Application.xml                    | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Automation/MultipleViewPattern.xml b/xml/System.Windows.Automation/MultipleViewPattern.xml
index 10d5a5bada2..95ff7d84e7e 100644
--- a/xml/System.Windows.Automation/MultipleViewPattern.xml
+++ b/xml/System.Windows.Automation/MultipleViewPattern.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)] documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and Microsoft Windows Media Player skins. The supported views are determined by the control developer and are specific to each control.  
+ Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), Microsoft Word documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and Microsoft Windows Media Player skins. The supported views are determined by the control developer and are specific to each control.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 394185e7e4a..9e86b8ec4db 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -2348,7 +2348,7 @@ This example illustrates how to use XAML together with application-scope resourc
    
   
 ## Examples  
- The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to multiple-document interface (MDI) applications like [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)], or multiple-instance Single Document Interface (SDI) applications like [!INCLUDE[TLA#tla_word](~/includes/tlasharptla-word-md.md)].  
+ The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to multiple-document interface (MDI) applications like [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)], or multiple-instance Single Document Interface (SDI) applications like Microsoft Word.  
   
  [!code-csharp[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationWindowsSnippets/CSharp/WindowMenuItem.cs#windowmenuitemcode)]
  [!code-vb[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationWindowsSnippets/visualbasic/windowmenuitem.vb#windowmenuitemcode)]  

From c1d722697a484c21037bfbdee791012aa5c1cbe7 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:13:40 -0800
Subject: [PATCH 175/236] tlasharptla-wys

---
 xml/System.Windows.Documents/FixedDocument.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Documents/FixedDocument.xml b/xml/System.Windows.Documents/FixedDocument.xml
index 1e6237f6951..1f3dc5cc7f0 100644
--- a/xml/System.Windows.Documents/FixedDocument.xml
+++ b/xml/System.Windows.Documents/FixedDocument.xml
@@ -46,7 +46,7 @@
   
  <xref:System.Windows.Documents.PageContent> is the only allowable child element of the <xref:System.Windows.Documents.FixedDocument> element.  Each <xref:System.Windows.Documents.PageContent> element refers to the source of the content for a single page. <xref:System.Windows.Documents.PageContent> elements must be in sequential markup order, matching the page order of the document.  
   
- <xref:System.Windows.Documents.FixedDocument> is designed for [!INCLUDE[TLA#tla_wys](~/includes/tlasharptla-wys-md.md)] applications where the document layout is defined and controlled by the application for rendering to the highest accuracy of the display or print device.  
+ <xref:System.Windows.Documents.FixedDocument> is designed for "what you see is what you get" (WYSIWYG) applications where the document layout is defined and controlled by the application for rendering to the highest accuracy of the display or print device.  
   
  <xref:System.Windows.Documents.FlowDocument>, on the other hand, is designed to maximize user readability, and dynamically adjusts the document layout based on user preferences (for example, a user-chosen type size or font) and other variables, such as display size and resolution.  
   

From 685181b3bb804c6bf2942438f489d81f773eac7d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:14:03 -0800
Subject: [PATCH 176/236] tlasharptla-xaml

---
 .../MarkupCompilePass1.xml                       |  4 ++--
 .../MarkupCompilePass2.xml                       |  4 ++--
 .../ButtonBase.xml                               |  2 +-
 .../TextBoxBase.xml                              |  6 +++---
 xml/System.Windows.Controls/Border.xml           |  6 +++---
 xml/System.Windows.Controls/ContentControl.xml   |  4 ++--
 xml/System.Windows.Controls/Decorator.xml        |  2 +-
 xml/System.Windows.Controls/DockPanel.xml        |  2 +-
 xml/System.Windows.Controls/Frame.xml            |  2 +-
 xml/System.Windows.Controls/Grid.xml             |  6 +++---
 xml/System.Windows.Controls/GridView.xml         |  8 ++++----
 .../GridViewRowPresenter.xml                     |  2 +-
 xml/System.Windows.Controls/InkCanvas.xml        | 16 ++++++++--------
 .../InkCanvasClipboardFormat.xml                 |  2 +-
 xml/System.Windows.Controls/ItemsControl.xml     |  2 +-
 xml/System.Windows.Controls/Page.xml             |  2 +-
 .../PageRangeSelection.xml                       |  2 +-
 xml/System.Windows.Controls/Panel.xml            |  2 +-
 xml/System.Windows.Controls/PrintDialog.xml      | 10 +++++-----
 .../ScrollContentPresenter.xml                   |  2 +-
 xml/System.Windows.Controls/Viewport3D.xml       |  2 +-
 .../VirtualizingPanel.xml                        |  2 +-
 .../VirtualizingStackPanel.xml                   |  2 +-
 xml/System.Windows.Controls/WrapPanel.xml        | 10 +++++-----
 xml/System.Windows.Data/Binding.xml              |  2 +-
 xml/System.Windows.Data/BindingBase.xml          |  4 ++--
 xml/System.Windows.Data/CollectionView.xml       |  2 +-
 xml/System.Windows.Data/CollectionViewSource.xml |  2 +-
 xml/System.Windows.Data/MultiBinding.xml         |  4 ++--
 xml/System.Windows.Data/ObjectDataProvider.xml   |  2 +-
 xml/System.Windows.Data/PriorityBinding.xml      |  2 +-
 xml/System.Windows.Data/XmlNamespaceMapping.xml  |  4 ++--
 .../XmlNamespaceMappingCollection.xml            |  2 +-
 xml/System.Windows.Input/CursorType.xml          |  2 +-
 xml/System.Windows.Input/KeyBinding.xml          |  6 +++---
 xml/System.Windows.Input/MouseBinding.xml        |  2 +-
 .../BamlLocalizableResource.xml                  |  2 +-
 .../BamlLocalizableResourceKey.xml               |  2 +-
 .../BooleanAnimationBase.xml                     |  2 +-
 .../ColorAnimationBase.xml                       |  2 +-
 .../DoubleAnimationBase.xml                      |  2 +-
 .../DoubleAnimationUsingPath.xml                 |  2 +-
 .../Int16AnimationBase.xml                       |  2 +-
 .../Int32AnimationBase.xml                       |  2 +-
 .../Int64AnimationBase.xml                       |  2 +-
 .../MatrixAnimationBase.xml                      |  2 +-
 .../ObjectAnimationBase.xml                      |  2 +-
 .../PointAnimationBase.xml                       |  2 +-
 .../RectAnimationBase.xml                        |  2 +-
 .../SizeAnimationBase.xml                        |  2 +-
 .../StringAnimationBase.xml                      |  2 +-
 .../ThicknessAnimationBase.xml                   |  2 +-
 .../BaseIListConverter.xml                       |  2 +-
 .../BoolIListConverter.xml                       |  2 +-
 .../CharIListConverter.xml                       |  2 +-
 .../DoubleIListConverter.xml                     |  2 +-
 .../PointIListConverter.xml                      |  2 +-
 .../UShortIListConverter.xml                     |  2 +-
 .../BitmapEncoder.xml                            |  2 +-
 xml/System.Windows.Media.Imaging/BitmapImage.xml |  8 ++++----
 xml/System.Windows.Media/FontFamily.xml          |  8 ++++----
 xml/System.Windows.Media/MediaPlayer.xml         |  2 +-
 .../NavigationService.xml                        |  2 +-
 .../NavigationWindow.xml                         |  2 +-
 xml/System.Windows.Resources/ContentTypes.xml    |  4 ++--
 xml/System.Windows.Shapes/Polygon.xml            |  2 +-
 xml/System.Windows.Shapes/Polyline.xml           |  2 +-
 .../ThumbButtonInfoCollection.xml                |  2 +-
 .../AttachedPropertyBrowsableAttribute.xml       |  2 +-
 ...chedPropertyBrowsableForChildrenAttribute.xml |  2 +-
 ...AttachedPropertyBrowsableForTypeAttribute.xml |  2 +-
 ...rtyBrowsableWhenAttributePresentAttribute.xml |  2 +-
 xml/System.Windows/Clipboard.xml                 |  8 ++++----
 xml/System.Windows/CornerRadius.xml              |  2 +-
 xml/System.Windows/DataFormats.xml               |  8 ++++----
 xml/System.Windows/DataTemplate.xml              |  2 +-
 xml/System.Windows/DependencyProperty.xml        |  6 +++---
 xml/System.Windows/EventSetter.xml               |  2 +-
 xml/System.Windows/EventTrigger.xml              |  2 +-
 xml/System.Windows/FrameworkContentElement.xml   |  6 +++---
 xml/System.Windows/FrameworkElement.xml          | 12 ++++++------
 xml/System.Windows/GridUnitType.xml              |  2 +-
 xml/System.Windows/LengthConverter.xml           |  2 +-
 xml/System.Windows/Localization.xml              |  2 +-
 xml/System.Windows/PresentationSource.xml        |  2 +-
 xml/System.Windows/ResourceDictionary.xml        |  2 +-
 xml/System.Windows/RoutedEventArgs.xml           |  2 +-
 xml/System.Windows/Thickness.xml                 | 10 +++++-----
 xml/System.Windows/TriggerBase.xml               |  4 ++--
 xml/System.Windows/UIElement.xml                 |  4 ++--
 xml/System.Windows/VerticalAlignment.xml         |  2 +-
 91 files changed, 151 insertions(+), 151 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
index 8f0198ed92b..6cd5cb512a7 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
@@ -682,8 +682,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies how to generate localization information for each [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file.</summary>
-        <value>A value that specifies how to generate localization information for each [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file. The valid values are **None**, **CommentsOnly**, and **All**.</value>
+        <summary>Gets or sets a value that specifies how to generate localization information for each Extensible Application Markup Language (XAML) file.</summary>
+        <value>A value that specifies how to generate localization information for each Extensible Application Markup Language (XAML) file. The valid values are **None**, **CommentsOnly**, and **All**.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
index b808c82abf4..bcf539b7cae 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass2.xml
@@ -288,8 +288,8 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that specifies how to generate localization information for each [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file.</summary>
-        <value>A value that specifies how to generate localization information for each [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file. The valid values are **None**, **CommentsOnly**, and **All**.</value>
+        <summary>Gets or sets a value that specifies how to generate localization information for each Extensible Application Markup Language (XAML) file.</summary>
+        <value>A value that specifies how to generate localization information for each Extensible Application Markup Language (XAML) file. The valid values are **None**, **CommentsOnly**, and **All**.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Windows.Controls.Primitives/ButtonBase.xml b/xml/System.Windows.Controls.Primitives/ButtonBase.xml
index cd773c8419b..29b36c2dc92 100644
--- a/xml/System.Windows.Controls.Primitives/ButtonBase.xml
+++ b/xml/System.Windows.Controls.Primitives/ButtonBase.xml
@@ -273,7 +273,7 @@
 ## Remarks  
  This property is used to associate a command with a particular button instance.  
   
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], this property is most often set to be a static command value from one of the existing command libraries, such as <xref:System.Windows.Input.ApplicationCommands> or <xref:System.Windows.Input.NavigationCommands>. For details, see [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview) or <xref:System.Windows.Input.ICommand>.  
+ In Extensible Application Markup Language (XAML), this property is most often set to be a static command value from one of the existing command libraries, such as <xref:System.Windows.Input.ApplicationCommands> or <xref:System.Windows.Input.NavigationCommands>. For details, see [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview) or <xref:System.Windows.Input.ICommand>.  
   
 <a name="xamlAttributeUsage_Command"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
index b828a4e264e..8a251bd657d 100644
--- a/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
+++ b/xml/System.Windows.Controls.Primitives/TextBoxBase.xml
@@ -32,7 +32,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example demonstrates how to use the derived <xref:System.Windows.Controls.TextBox> object in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to use the derived <xref:System.Windows.Controls.TextBox> object in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[TextBoxBase_Samp#TextBoxBase1](~/samples/snippets/csharp/VS_Snippets_Wpf/TextBoxBase_Samp/CSharp/Window1.xaml#textboxbase1)]  
   
@@ -798,7 +798,7 @@ TextBox with CaretBrush set to blue
    
   
 ## Examples  
- The following example demonstrates how to set the value of the <xref:System.Windows.Controls.Primitives.TextBoxBase.HorizontalScrollBarVisibility%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to set the value of the <xref:System.Windows.Controls.Primitives.TextBoxBase.HorizontalScrollBarVisibility%2A> property by using Extensible Application Markup Language (XAML).  
   
  [!code-xaml[TextBoxBase_Samp#TextBoxBase1](~/samples/snippets/csharp/VS_Snippets_Wpf/TextBoxBase_Samp/CSharp/Window1.xaml#textboxbase1)]  
   
@@ -1098,7 +1098,7 @@ TextBox with CaretBrush set to blue
    
   
 ## Examples  
- The following example demonstrates how to use the <xref:System.Windows.Controls.Primitives.TextBoxBase.IsUndoEnabled%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to use the <xref:System.Windows.Controls.Primitives.TextBoxBase.IsUndoEnabled%2A> property in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[TextBoxBase_Samp#TextBoxBase1](~/samples/snippets/csharp/VS_Snippets_Wpf/TextBoxBase_Samp/CSharp/Window1.xaml#textboxbase1)]  
   
diff --git a/xml/System.Windows.Controls/Border.xml b/xml/System.Windows.Controls/Border.xml
index 26709df6686..2f2c78b226d 100644
--- a/xml/System.Windows.Controls/Border.xml
+++ b/xml/System.Windows.Controls/Border.xml
@@ -29,7 +29,7 @@
    
   
 ## Examples  
- The following example demonstrates how to create a <xref:System.Windows.Controls.Border> and set properties in code and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to create a <xref:System.Windows.Controls.Border> and set properties in code and Extensible Application Markup Language (XAML).  
   
  [!code-cpp[marginpaddingalignmentsample#3](~/samples/snippets/cpp/VS_Snippets_Wpf/MarginPaddingAlignmentSample/CPP/Margin_Padding_Alignment_Sample.cpp#3)]
  [!code-csharp[marginpaddingalignmentsample#3](~/samples/snippets/csharp/VS_Snippets_Wpf/MarginPaddingAlignmentSample/CSharp/Margin_Padding_Alignment_Sample.cs#3)]
@@ -139,7 +139,7 @@
    
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Controls.Border.Background%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Controls.Border.Background%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#1)]
  [!code-vb[ThicknessStruct#1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#1)]
@@ -208,7 +208,7 @@
    
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Controls.Border.BorderBrush%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Controls.Border.BorderBrush%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#1)]
  [!code-vb[ThicknessStruct#1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#1)]
diff --git a/xml/System.Windows.Controls/ContentControl.xml b/xml/System.Windows.Controls/ContentControl.xml
index 327e01e2a5e..6cb4c1f91bd 100644
--- a/xml/System.Windows.Controls/ContentControl.xml
+++ b/xml/System.Windows.Controls/ContentControl.xml
@@ -65,7 +65,7 @@ Four buttons with different types of content
  The following example demonstrates how to create the four buttons shown in the Remarks section.  
   
 > [!NOTE]
->  Although the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] version of the example could use the `<Button.Content>` tags around the content of each button, it is not necessary. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+>  Although the Extensible Application Markup Language (XAML) version of the example could use the `<Button.Content>` tags around the content of each button, it is not necessary. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  [!code-xaml[ControlContentOverviewSnippets#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ControlContentOverviewSnippets/CSharp/Window1.xaml#1)]  
   
@@ -237,7 +237,7 @@ Four buttons with different types of content
 -   A <xref:System.Windows.Controls.Panel> control that contains other <xref:System.Windows.UIElement> objects.  
   
 > [!NOTE]
->  Although the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] version of the example could use the `<Button.Content>` tags around the content of each button, it is not necessary. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+>  Although the Extensible Application Markup Language (XAML) version of the example could use the `<Button.Content>` tags around the content of each button, it is not necessary. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  [!code-xaml[ControlContentOverviewSnippets#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ControlContentOverviewSnippets/CSharp/Window1.xaml#1)]  
   
diff --git a/xml/System.Windows.Controls/Decorator.xml b/xml/System.Windows.Controls/Decorator.xml
index d07d9647572..1b67916ac9c 100644
--- a/xml/System.Windows.Controls/Decorator.xml
+++ b/xml/System.Windows.Controls/Decorator.xml
@@ -42,7 +42,7 @@
 ## Examples  
  The following example adds a <xref:System.Windows.Controls.TextBox> the <xref:System.Windows.Controls.Decorator.Child%2A> property of a <xref:System.Windows.Controls.Border>.  
   
- **Note** The [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] version of the example could use the `<Border.Child>` tags around the content of the <xref:System.Windows.Controls.Border>, but it is not necessary because the <xref:System.Windows.Controls.Decorator> applies the <xref:System.Windows.Markup.ContentPropertyAttribute> to the <xref:System.Windows.Controls.Decorator.Child%2A> property. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
+ **Note** The Extensible Application Markup Language (XAML) version of the example could use the `<Border.Child>` tags around the content of the <xref:System.Windows.Controls.Border>, but it is not necessary because the <xref:System.Windows.Controls.Decorator> applies the <xref:System.Windows.Markup.ContentPropertyAttribute> to the <xref:System.Windows.Controls.Decorator.Child%2A> property. For more information, see [XAML Overview (WPF)](/dotnet/framework/wpf/advanced/xaml-overview-wpf).  
   
  [!code-xaml[Border_snip#SimpleBorderWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/Border_snip/CS/simpleborder.xaml#simpleborderwholepage)]  
   
diff --git a/xml/System.Windows.Controls/DockPanel.xml b/xml/System.Windows.Controls/DockPanel.xml
index a2e9b1e0324..08209142b26 100644
--- a/xml/System.Windows.Controls/DockPanel.xml
+++ b/xml/System.Windows.Controls/DockPanel.xml
@@ -127,7 +127,7 @@
    
   
 ## Examples  
- The following example shows how to set the <xref:System.Windows.Controls.DockPanel.Dock%2A> attached property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example shows how to set the <xref:System.Windows.Controls.DockPanel.Dock%2A> attached property by using Extensible Application Markup Language (XAML).  
   
  [!code-cpp[DockPanelOvwSample#1](~/samples/snippets/cpp/VS_Snippets_Wpf/DockPanelOvwSample/CPP/DockPanel_Ovw_Sample.cpp#1)]
  [!code-csharp[DockPanelOvwSample#1](~/samples/snippets/csharp/VS_Snippets_Wpf/DockPanelOvwSample/CSharp/DockPanel_Ovw_Sample.cs#1)]
diff --git a/xml/System.Windows.Controls/Frame.xml b/xml/System.Windows.Controls/Frame.xml
index e70056a1baf..2c834167d3e 100644
--- a/xml/System.Windows.Controls/Frame.xml
+++ b/xml/System.Windows.Controls/Frame.xml
@@ -1532,7 +1532,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets whether a <see cref="T:System.Windows.Controls.Frame" /> isolates external [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] content within a partial trust security sandbox (with the default <see langword="Internet" /> permission set).</summary>
+        <summary>Gets or sets whether a <see cref="T:System.Windows.Controls.Frame" /> isolates external Extensible Application Markup Language (XAML) content within a partial trust security sandbox (with the default <see langword="Internet" /> permission set).</summary>
         <value>
           <see langword="true" /> if content is isolated within a partial trust security sandbox; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Controls/Grid.xml b/xml/System.Windows.Controls/Grid.xml
index 8a23e0a138e..f06e6e3e38c 100644
--- a/xml/System.Windows.Controls/Grid.xml
+++ b/xml/System.Windows.Controls/Grid.xml
@@ -28,7 +28,7 @@
 ## Remarks  
  A <xref:System.Windows.Controls.Grid> contains a collection of <xref:System.Windows.UIElement> objects, which are in the <xref:System.Windows.Controls.Panel.Children%2A> property.  
   
- Columns and rows that are defined within a <xref:System.Windows.Controls.Grid> can take advantage of <xref:System.Windows.GridUnitType.Star> sizing to distribute remaining space proportionally. When <xref:System.Windows.GridUnitType.Star> is selected as the height or width of a row or column, that column or row receives a weighted proportion of the remaining available space. This is in contrast to <xref:System.Windows.GridUnitType.Auto>, which distributes space evenly based on the size of the content that is within a column or row. This value is expressed as `*` or `2*` when you use [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. In the first case, the row or column would receive one times the available space, while in the second case, the row or column would receive two times the available space, and so on. By combining this technique to proportionally distribute space with a <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> and <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> value of `Stretch`, it is possible to partition layout space by percentage of screen space. <xref:System.Windows.Controls.Grid> is the only layout panel that can distribute space in this manner.  
+ Columns and rows that are defined within a <xref:System.Windows.Controls.Grid> can take advantage of <xref:System.Windows.GridUnitType.Star> sizing to distribute remaining space proportionally. When <xref:System.Windows.GridUnitType.Star> is selected as the height or width of a row or column, that column or row receives a weighted proportion of the remaining available space. This is in contrast to <xref:System.Windows.GridUnitType.Auto>, which distributes space evenly based on the size of the content that is within a column or row. This value is expressed as `*` or `2*` when you use Extensible Application Markup Language (XAML). In the first case, the row or column would receive one times the available space, while in the second case, the row or column would receive two times the available space, and so on. By combining this technique to proportionally distribute space with a <xref:System.Windows.FrameworkElement.HorizontalAlignment%2A> and <xref:System.Windows.FrameworkElement.VerticalAlignment%2A> value of `Stretch`, it is possible to partition layout space by percentage of screen space. <xref:System.Windows.Controls.Grid> is the only layout panel that can distribute space in this manner.  
   
  By default, rows and columns take up the least amount of space necessary to accommodate the largest content within any cell contained in a given row or column. For example, if a column has one cell with a long word like "hippopotamus" contained within it but all the other cells in the column have smaller words like "dog", the width of the column will be the width of the largest word (hippopotamus).  
   
@@ -502,7 +502,7 @@
    
   
 ## Examples  
- The following code examples demonstrate how to use the <xref:System.Windows.Controls.Grid.IsSharedSizeScope%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following code examples demonstrate how to use the <xref:System.Windows.Controls.Grid.IsSharedSizeScope%2A> property in Extensible Application Markup Language (XAML) and code.  
   
  [!code-xml[gridIssharedsizescopeProp#1](~/samples/snippets/csharp/VS_Snippets_Wpf/gridIssharedsizescopeProp/CSharp/Window1.xaml#1)]  
   
@@ -512,7 +512,7 @@
   
  ...  
   
- Events defined in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] are handled using code.  
+ Events defined in Extensible Application Markup Language (XAML) are handled using code.  
   
  [!code-csharp[gridIssharedsizescopeProp#3](~/samples/snippets/csharp/VS_Snippets_Wpf/gridIssharedsizescopeProp/CSharp/Window1.xaml.cs#3)]
  [!code-vb[gridIssharedsizescopeProp#3](~/samples/snippets/visualbasic/VS_Snippets_Wpf/gridIssharedsizescopeProp/VisualBasic/Window1.xaml.vb#3)]  
diff --git a/xml/System.Windows.Controls/GridView.xml b/xml/System.Windows.Controls/GridView.xml
index 189f36df908..f2a11b9fb8c 100644
--- a/xml/System.Windows.Controls/GridView.xml
+++ b/xml/System.Windows.Controls/GridView.xml
@@ -45,7 +45,7 @@
   
  ![ListView with GridView output](~/add/media/listviewgridview.JPG "ListView with GridView output")  
   
- The columns in a <xref:System.Windows.Controls.GridView> are defined as <xref:System.Windows.Controls.GridViewColumn> objects. In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], you can define <xref:System.Windows.Controls.GridViewColumn> objects as child elements of the <xref:System.Windows.Controls.GridView>. In code, you can add a <xref:System.Windows.Controls.GridViewColumn> to the <xref:System.Windows.Controls.GridView> by using the <xref:System.Windows.Controls.GridView.Columns%2A> property and the <xref:System.Collections.ObjectModel.Collection%601.Add%2A> method that is defined for the <xref:System.Collections.ObjectModel.Collection%601> class. Similarly, you can use other <xref:System.Collections.ObjectModel.Collection%601> methods such as <xref:System.Collections.ObjectModel.Collection%601.Remove%2A> and <xref:System.Collections.ObjectModel.Collection%601.Insert%2A> to modify the columns in a <xref:System.Windows.Controls.GridView>.  
+ The columns in a <xref:System.Windows.Controls.GridView> are defined as <xref:System.Windows.Controls.GridViewColumn> objects. In Extensible Application Markup Language (XAML), you can define <xref:System.Windows.Controls.GridViewColumn> objects as child elements of the <xref:System.Windows.Controls.GridView>. In code, you can add a <xref:System.Windows.Controls.GridViewColumn> to the <xref:System.Windows.Controls.GridView> by using the <xref:System.Windows.Controls.GridView.Columns%2A> property and the <xref:System.Collections.ObjectModel.Collection%601.Add%2A> method that is defined for the <xref:System.Collections.ObjectModel.Collection%601> class. Similarly, you can use other <xref:System.Collections.ObjectModel.Collection%601> methods such as <xref:System.Collections.ObjectModel.Collection%601.Remove%2A> and <xref:System.Collections.ObjectModel.Collection%601.Insert%2A> to modify the columns in a <xref:System.Windows.Controls.GridView>.  
   
  The following example shows how to define the columns of a <xref:System.Windows.Controls.GridView>.  
   
@@ -1086,7 +1086,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can use this read-only static property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by assigning its static value to another property value. Specifically, this property's static value defines the resource key that is used to look up the default <xref:System.Windows.Controls.ScrollViewer> style of a <xref:System.Windows.Controls.GridView>. To redefine this style, reference the <xref:System.Windows.Controls.GridView.GridViewScrollViewerStyleKey%2A> by using the [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) and assign that value as the [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of the new <xref:System.Windows.Style>.  
+ You can use this read-only static property in Extensible Application Markup Language (XAML) by assigning its static value to another property value. Specifically, this property's static value defines the resource key that is used to look up the default <xref:System.Windows.Controls.ScrollViewer> style of a <xref:System.Windows.Controls.GridView>. To redefine this style, reference the <xref:System.Windows.Controls.GridView.GridViewScrollViewerStyleKey%2A> by using the [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) and assign that value as the [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of the new <xref:System.Windows.Style>.  
   
  ]]></format>
         </remarks>
@@ -1116,9 +1116,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can use this read-only static property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by assigning its static value to another property value. Specifically, this property's static value defines the resource key that is used to look up the default <xref:System.Windows.Controls.ListView> style. To redefine this style, reference the <xref:System.Windows.Controls.GridView.GridViewStyleKey%2A> by using the [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) and assign that value as the [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of the new <xref:System.Windows.Style>.  
+ You can use this read-only static property in Extensible Application Markup Language (XAML) by assigning its static value to another property value. Specifically, this property's static value defines the resource key that is used to look up the default <xref:System.Windows.Controls.ListView> style. To redefine this style, reference the <xref:System.Windows.Controls.GridView.GridViewStyleKey%2A> by using the [x:Static Markup Extension](/dotnet/framework/xaml-services/x-static-markup-extension) and assign that value as the [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of the new <xref:System.Windows.Style>.  
   
- You can use this read-only property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] as an [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of a <xref:System.Windows.Style> that redefines the <xref:System.Windows.Style> for the <xref:System.Windows.Controls.ListView>.    
+ You can use this read-only property in Extensible Application Markup Language (XAML) as an [x:Key Directive](/dotnet/framework/xaml-services/x-key-directive) of a <xref:System.Windows.Style> that redefines the <xref:System.Windows.Style> for the <xref:System.Windows.Controls.ListView>.    
  
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Controls/GridViewRowPresenter.xml b/xml/System.Windows.Controls/GridViewRowPresenter.xml
index 17303c05576..5be40020bea 100644
--- a/xml/System.Windows.Controls/GridViewRowPresenter.xml
+++ b/xml/System.Windows.Controls/GridViewRowPresenter.xml
@@ -114,7 +114,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The typical usage of the <xref:System.Windows.Controls.GridViewRowPresenter> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] is to place it in a <xref:System.Windows.Controls.ControlTemplate> of a control. The template binds the <xref:System.Windows.Controls.GridViewRowPresenter.Content%2A> property to a property of the control by using [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension). The following example shows how to bind the <xref:System.Windows.Controls.GridViewRowPresenter.Content%2A> property of a <xref:System.Windows.Controls.GridViewRowPresenter> to the <xref:System.Windows.Controls.ContentControl.Content%2A> property of a <xref:System.Windows.Controls.ListViewItem> control.  
+ The typical usage of the <xref:System.Windows.Controls.GridViewRowPresenter> in Extensible Application Markup Language (XAML) is to place it in a <xref:System.Windows.Controls.ControlTemplate> of a control. The template binds the <xref:System.Windows.Controls.GridViewRowPresenter.Content%2A> property to a property of the control by using [TemplateBinding Markup Extension](/dotnet/framework/wpf/advanced/templatebinding-markup-extension). The following example shows how to bind the <xref:System.Windows.Controls.GridViewRowPresenter.Content%2A> property of a <xref:System.Windows.Controls.GridViewRowPresenter> to the <xref:System.Windows.Controls.ContentControl.Content%2A> property of a <xref:System.Windows.Controls.ListViewItem> control.  
   
  [!code-xaml[ListViewItemStyleSnippet#ControlTemplate](~/samples/snippets/csharp/VS_Snippets_Wpf/ListViewItemStyleSnippet/CS/Window1.xaml#controltemplate)]   
   
diff --git a/xml/System.Windows.Controls/InkCanvas.xml b/xml/System.Windows.Controls/InkCanvas.xml
index 9f6b4fab71b..55961e42191 100644
--- a/xml/System.Windows.Controls/InkCanvas.xml
+++ b/xml/System.Windows.Controls/InkCanvas.xml
@@ -431,7 +431,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -528,7 +528,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF).  
   
    
   
@@ -568,7 +568,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format. Strokes to the Clipboard are both Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF).  
   
    
   
@@ -2417,7 +2417,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format.  
   
  ]]></format>
         </remarks>
@@ -2447,7 +2447,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -2490,7 +2490,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF), and text format.  
+ The <xref:System.Windows.Controls.InkCanvas> can support Clipboard data in Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF), and text format.  
   
    
   
@@ -2556,12 +2556,12 @@
    
   
 ## Examples  
- The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
+ The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF).  
   
  [!code-csharp[InkCanvasSamples#26](~/samples/snippets/csharp/VS_Snippets_Wpf/InkCanvasSamples/CSharp/Window1.xaml.cs#26)]
  [!code-vb[InkCanvasSamples#26](~/samples/snippets/visualbasic/VS_Snippets_Wpf/InkCanvasSamples/VisualBasic/Window1.xaml.vb#26)]  
   
- The following example accomplishes the same thing in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example accomplishes the same thing in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[InkCanvasSamples#38](~/samples/snippets/csharp/VS_Snippets_Wpf/InkCanvasSamples/CSharp/Window2.xaml#38)]  
   
diff --git a/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml b/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
index 48099b873db..906be03446d 100644
--- a/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
+++ b/xml/System.Windows.Controls/InkCanvasClipboardFormat.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] format, Ink Serialized Format (ISF).  
+ The following example sets the <xref:System.Windows.Controls.InkCanvas.PreferredPasteFormats%2A> to make the <xref:System.Windows.Controls.InkCanvas> accept Extensible Application Markup Language (XAML) format, Ink Serialized Format (ISF).  
   
  [!code-csharp[InkCanvasSamples#26](~/samples/snippets/csharp/VS_Snippets_Wpf/InkCanvasSamples/CSharp/Window1.xaml.cs#26)]
  [!code-vb[InkCanvasSamples#26](~/samples/snippets/visualbasic/VS_Snippets_Wpf/InkCanvasSamples/VisualBasic/Window1.xaml.vb#26)]  
diff --git a/xml/System.Windows.Controls/ItemsControl.xml b/xml/System.Windows.Controls/ItemsControl.xml
index 024e989191b..c06750cb5f8 100644
--- a/xml/System.Windows.Controls/ItemsControl.xml
+++ b/xml/System.Windows.Controls/ItemsControl.xml
@@ -1503,7 +1503,7 @@ ListBox that contains multiple types of objects
  This property may be used to add items to an <xref:System.Windows.Controls.ItemsControl>. Adding a child to an <xref:System.Windows.Controls.ItemsControl> object implicitly adds it to the <xref:System.Windows.Controls.ItemCollection> for the <xref:System.Windows.Controls.ItemsControl> object.  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] via the collection syntax shown, or by accessing the collection object and using its various methods such as `Add`. The property to access the collection object itself is read-only, and the collection itself is read-write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) via the collection syntax shown, or by accessing the collection object and using its various methods such as `Add`. The property to access the collection object itself is read-only, and the collection itself is read-write.  
   
  Note that you use either the <xref:System.Windows.Controls.ItemsControl.Items%2A> or the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property to specify the collection that should be used to generate the content of your <xref:System.Windows.Controls.ItemsControl>. When the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property is set, the <xref:System.Windows.Controls.ItemsControl.Items%2A> collection is made read-only and fixed-size.  
   
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 4269b17d26b..7d269b70d85 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -1348,7 +1348,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and Windows Internet Explorer, is the name of the file that is currently being hosted (with an .xaml extension if the page is loose [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], or an .xbap extension if the page is part of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).  
+ By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and Windows Internet Explorer, is the name of the file that is currently being hosted (with an .xaml extension if the page is loose Extensible Application Markup Language (XAML), or an .xbap extension if the page is part of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).  
   
  A page can change the default by setting its <xref:System.Windows.Controls.Page.WindowTitle%2A> property.  
   
diff --git a/xml/System.Windows.Controls/PageRangeSelection.xml b/xml/System.Windows.Controls/PageRangeSelection.xml
index 62492f3c932..6ff5c32b161 100644
--- a/xml/System.Windows.Controls/PageRangeSelection.xml
+++ b/xml/System.Windows.Controls/PageRangeSelection.xml
@@ -25,7 +25,7 @@
    
   
 ## Examples  
- The following example shows how to use the enumeration to set the <xref:System.Windows.Controls.PrintDialog.PageRangeSelection%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to use the enumeration to set the <xref:System.Windows.Controls.PrintDialog.PageRangeSelection%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-xaml[PrintDialog#2](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#2)]  
   
diff --git a/xml/System.Windows.Controls/Panel.xml b/xml/System.Windows.Controls/Panel.xml
index 7ad42ac1c67..951a4aa7047 100644
--- a/xml/System.Windows.Controls/Panel.xml
+++ b/xml/System.Windows.Controls/Panel.xml
@@ -840,7 +840,7 @@
    
   
 ## Examples  
- The following example demonstrates how to set the value of the <xref:System.Windows.Controls.Panel.ZIndex%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example demonstrates how to set the value of the <xref:System.Windows.Controls.Panel.ZIndex%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-cpp[canvasz-order#1](~/samples/snippets/cpp/VS_Snippets_Wpf/CanvasZ-Order/CPP/CanvasZ-Order.cpp#1)]
  [!code-csharp[canvasz-order#1](~/samples/snippets/csharp/VS_Snippets_Wpf/CanvasZ-Order/Csharp/CanvasZ-Order.cs#1)]
diff --git a/xml/System.Windows.Controls/PrintDialog.xml b/xml/System.Windows.Controls/PrintDialog.xml
index bfc59c57865..e4763fef9fc 100644
--- a/xml/System.Windows.Controls/PrintDialog.xml
+++ b/xml/System.Windows.Controls/PrintDialog.xml
@@ -30,7 +30,7 @@
    
   
 ## Examples  
- The following example shows how to create an instance of and display a simple <xref:System.Windows.Controls.PrintDialog> by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup and code.  
+ The following example shows how to create an instance of and display a simple <xref:System.Windows.Controls.PrintDialog> by using Extensible Application Markup Language (XAML) markup and code.  
   
  [!code-xaml[PrintDialog#2](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#2)]  
   
@@ -229,7 +229,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the <xref:System.Windows.Controls.PrintDialog.PageRangeSelection%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup and code.  
+ The following example shows how to set the <xref:System.Windows.Controls.PrintDialog.PageRangeSelection%2A> property by using Extensible Application Markup Language (XAML) markup and code.  
   
  [!code-xaml[PrintDialog#2](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#2)]  
   
@@ -266,7 +266,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to get the value of the <xref:System.Windows.Controls.PrintDialog.PrintableAreaHeight%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup and code.  
+ The following example shows how to get the value of the <xref:System.Windows.Controls.PrintDialog.PrintableAreaHeight%2A> property by using Extensible Application Markup Language (XAML) markup and code.  
   
  [!code-xaml[PrintDialog#4](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#4)]  
   
@@ -303,7 +303,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to get the value of the <xref:System.Windows.Controls.PrintDialog.PrintableAreaWidth%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup and code.  
+ The following example shows how to get the value of the <xref:System.Windows.Controls.PrintDialog.PrintableAreaWidth%2A> property by using Extensible Application Markup Language (XAML) markup and code.  
   
  [!code-xaml[PrintDialog#3](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#3)]  
   
@@ -562,7 +562,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the <xref:System.Windows.Controls.PrintDialog.UserPageRangeEnabled%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup and code.  
+ The following example shows how to set the <xref:System.Windows.Controls.PrintDialog.UserPageRangeEnabled%2A> property by using Extensible Application Markup Language (XAML) markup and code.  
   
  [!code-xaml[PrintDialog#2](~/samples/snippets/csharp/VS_Snippets_Wpf/PrintDialog/CSharp/Window1.xaml#2)]  
   
diff --git a/xml/System.Windows.Controls/ScrollContentPresenter.xml b/xml/System.Windows.Controls/ScrollContentPresenter.xml
index a1c591a9a1b..fced68c2412 100644
--- a/xml/System.Windows.Controls/ScrollContentPresenter.xml
+++ b/xml/System.Windows.Controls/ScrollContentPresenter.xml
@@ -159,7 +159,7 @@
    
   
 ## Examples  
- The following example demonstrates how to use the <xref:System.Windows.Controls.ScrollContentPresenter.CanContentScroll%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to use the <xref:System.Windows.Controls.ScrollContentPresenter.CanContentScroll%2A> property in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[styled_scrollviewer#1](~/samples/snippets/csharp/VS_Snippets_Wpf/Styled_ScrollViewer/CS/default.xaml#1)]  
   
diff --git a/xml/System.Windows.Controls/Viewport3D.xml b/xml/System.Windows.Controls/Viewport3D.xml
index 8ed1a4d1c5c..9eb841d6c29 100644
--- a/xml/System.Windows.Controls/Viewport3D.xml
+++ b/xml/System.Windows.Controls/Viewport3D.xml
@@ -148,7 +148,7 @@
  [!code-csharp[3DGallery_procedural_snip#Basic3DShapeCodeExampleInline1](~/samples/snippets/csharp/VS_Snippets_Wpf/3DGallery_procedural_snip/CSharp/Basic3DShapeExample.cs#basic3dshapecodeexampleinline1)]
  [!code-vb[3DGallery_procedural_snip#Basic3DShapeCodeExampleInline1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/3DGallery_procedural_snip/visualbasic/basic3dshapeexample.vb#basic3dshapecodeexampleinline1)]  
   
- The following example shows setting the <xref:System.Windows.Controls.Viewport3D.Camera%2A> property of a <xref:System.Windows.Controls.Viewport3D> using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. To see the entirety of the code from which this excerpt was taken, see [How to: Create a 3-D Scene](/dotnet/framework/wpf/graphics-multimedia/how-to-create-a-3-d-scene).  
+ The following example shows setting the <xref:System.Windows.Controls.Viewport3D.Camera%2A> property of a <xref:System.Windows.Controls.Viewport3D> using Extensible Application Markup Language (XAML). To see the entirety of the code from which this excerpt was taken, see [How to: Create a 3-D Scene](/dotnet/framework/wpf/graphics-multimedia/how-to-create-a-3-d-scene).  
   
  [!code-xaml[basic3d#Basic3DXAML3DN1](~/samples/snippets/xaml/VS_Snippets_Wpf/Basic3D/XAML/Window1.xaml#basic3dxaml3dn1)]  
   
diff --git a/xml/System.Windows.Controls/VirtualizingPanel.xml b/xml/System.Windows.Controls/VirtualizingPanel.xml
index 0b0ee351edd..2044689285c 100644
--- a/xml/System.Windows.Controls/VirtualizingPanel.xml
+++ b/xml/System.Windows.Controls/VirtualizingPanel.xml
@@ -34,7 +34,7 @@
    
   
 ## Examples  
- The following example demonstrates how to use the derived <xref:System.Windows.Controls.VirtualizingStackPanel> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to use the derived <xref:System.Windows.Controls.VirtualizingStackPanel> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[virtualizingstackpanel_intro#1](~/samples/snippets/csharp/VS_Snippets_Wpf/VirtualizingStackPanel_Intro/CS/default.xaml#1)]  
   
diff --git a/xml/System.Windows.Controls/VirtualizingStackPanel.xml b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
index 191621a4ada..9b5320f5bf8 100644
--- a/xml/System.Windows.Controls/VirtualizingStackPanel.xml
+++ b/xml/System.Windows.Controls/VirtualizingStackPanel.xml
@@ -37,7 +37,7 @@
    
   
 ## Examples  
- The following example shows how to bind to an XML data source and virtualize the items displayed in a <xref:System.Windows.Controls.ListBox> element using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. Notice that the `VirtualizingStackPanel.IsVirtualizing` attached property is explicitly set to `true`.  
+ The following example shows how to bind to an XML data source and virtualize the items displayed in a <xref:System.Windows.Controls.ListBox> element using Extensible Application Markup Language (XAML). Notice that the `VirtualizingStackPanel.IsVirtualizing` attached property is explicitly set to `true`.  
   
  [!code-xaml[VirtualizingStackPanel_Intro#2](~/samples/snippets/csharp/VS_Snippets_Wpf/VirtualizingStackPanel_Intro/CS/default.xaml#2)]  
   
diff --git a/xml/System.Windows.Controls/WrapPanel.xml b/xml/System.Windows.Controls/WrapPanel.xml
index a07f6dda40e..7c652f5dd98 100644
--- a/xml/System.Windows.Controls/WrapPanel.xml
+++ b/xml/System.Windows.Controls/WrapPanel.xml
@@ -27,7 +27,7 @@
    
   
 ## Examples  
- The following example demonstrates how to create a <xref:System.Windows.Controls.WrapPanel> in code and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to create a <xref:System.Windows.Controls.WrapPanel> in code and Extensible Application Markup Language (XAML).  
   
  [!code-cpp[WrapPanel_Intro#1](~/samples/snippets/cpp/VS_Snippets_Wpf/WrapPanel_Intro/CPP/WrapPanel_Code.cpp#1)]
  [!code-csharp[WrapPanel_Intro#1](~/samples/snippets/csharp/VS_Snippets_Wpf/WrapPanel_Intro/CSharp/WrapPanel_Code.cs#1)]
@@ -164,7 +164,7 @@
    
   
 ## Examples  
- The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.ItemHeight%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.ItemHeight%2A> property in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[WrapPanel_Intro2#1](~/samples/snippets/csharp/VS_Snippets_Wpf/WrapPanel_Intro2/CS/default.xaml#1)]  
   
@@ -233,7 +233,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this property is not set (or if it is set to `Auto` in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] or to `Double.NaN` in code), the size of the layout partition is equal to the <xref:System.Windows.UIElement.DesiredSize%2A> of the child element.  
+ If this property is not set (or if it is set to `Auto` in Extensible Application Markup Language (XAML) or to `Double.NaN` in code), the size of the layout partition is equal to the <xref:System.Windows.UIElement.DesiredSize%2A> of the child element.  
   
  A child element of a <xref:System.Windows.Controls.WrapPanel> may have its width property set explicitly. <xref:System.Windows.Controls.WrapPanel.ItemWidth%2A> specifies the size of the layout partition that is reserved by the <xref:System.Windows.Controls.WrapPanel> for the child element. As a result, <xref:System.Windows.Controls.WrapPanel.ItemWidth%2A> takes precedence over an element's own width.  
   
@@ -280,7 +280,7 @@
    
   
 ## Examples  
- The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.ItemWidth%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.ItemWidth%2A> property in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[WrapPanel_Intro2#1](~/samples/snippets/csharp/VS_Snippets_Wpf/WrapPanel_Intro2/CS/default.xaml#1)]  
   
@@ -390,7 +390,7 @@
    
   
 ## Examples  
- The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.Orientation%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to set the <xref:System.Windows.Controls.WrapPanel.Orientation%2A> property in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[WrapPanel_Intro2#1](~/samples/snippets/csharp/VS_Snippets_Wpf/WrapPanel_Intro2/CS/default.xaml#1)]  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 5a668ba3bb0..5b52af220bb 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -1518,7 +1518,7 @@
  The binding engine checks each <xref:System.Windows.Controls.ValidationRule> associated with a binding each time an input value (the binding target property value) is transferred to the binding source property. For a detailed discussion of the validation process, see the Data Validation section in the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
 > [!NOTE]
->  This property can be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] only by using the collection syntax shown, or by accessing the collection object and using its various methods, such as `Add`. The property to access the collection object is read-only, whereas the collection itself is read-write.  
+>  This property can be set in Extensible Application Markup Language (XAML) only by using the collection syntax shown, or by accessing the collection object and using its various methods, such as `Add`. The property to access the collection object is read-only, whereas the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_ValidationRules"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Data/BindingBase.xml b/xml/System.Windows.Data/BindingBase.xml
index 9c0bd732487..6068423d44e 100644
--- a/xml/System.Windows.Data/BindingBase.xml
+++ b/xml/System.Windows.Data/BindingBase.xml
@@ -32,7 +32,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Because the <xref:System.Windows.Data.BindingBase.ProvideValue%2A?displayProperty=nameWithType> method is sealed, a custom binding class that derives from <xref:System.Windows.Data.BindingBase> will not function correctly as a [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] markup extension.  
+ Because the <xref:System.Windows.Data.BindingBase.ProvideValue%2A?displayProperty=nameWithType> method is sealed, a custom binding class that derives from <xref:System.Windows.Data.BindingBase> will not function correctly as a Extensible Application Markup Language (XAML) markup extension.  
   
  ]]></format>
     </remarks>
@@ -235,7 +235,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This implementation provides the base syntax support for binding through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] for all provided practical derived classes (<xref:System.Windows.Data.Binding>, <xref:System.Windows.Data.PriorityBinding>, and <xref:System.Windows.Data.MultiBinding>).  
+ This implementation provides the base syntax support for binding through Extensible Application Markup Language (XAML) for all provided practical derived classes (<xref:System.Windows.Data.Binding>, <xref:System.Windows.Data.PriorityBinding>, and <xref:System.Windows.Data.MultiBinding>).  
   
  The <xref:System.Windows.Data.BindingBase> class implementation of this method is expected to return an expression object that is the result of a binding. Binding a property works by targeting a given <xref:System.Windows.DependencyProperty> on a given <xref:System.Windows.DependencyObject>. These two pieces of information are transmitted by querying for an <xref:System.Windows.Markup.IProvideValueTarget> implementation on the `serviceProvider`, which the WPF XAML reader makes available during parsing of a binding. This base class implementation is responsible for checking for a valid <xref:System.Windows.DependencyProperty> and <xref:System.Windows.DependencyObject>. If these are found, the actual implementation of returning a binding expression falls to various derived classes, as implemented by having the base class call an internal abstract method. Otherwise, the extension returns the binding object itself. Returning the binding itself results in a type mismatch error, but this should not occur under normal circumstances.  
   
diff --git a/xml/System.Windows.Data/CollectionView.xml b/xml/System.Windows.Data/CollectionView.xml
index f55cde0c2d9..3d725bdbd79 100644
--- a/xml/System.Windows.Data/CollectionView.xml
+++ b/xml/System.Windows.Data/CollectionView.xml
@@ -46,7 +46,7 @@
   
  In WPF applications, all collections have an associated default collection view. Rather than working with the collection directly, the binding engine always accesses the collection through the associated view. To get the default view, use the <xref:System.Windows.Data.CollectionViewSource.GetDefaultView%2A?displayProperty=nameWithType> method. An internal class based on <xref:System.Windows.Data.CollectionView> is the default view for collections that implement only <xref:System.Collections.IEnumerable>. <xref:System.Windows.Data.ListCollectionView> is the default view for collections that implement <xref:System.Collections.IList>. <xref:System.Windows.Data.BindingListCollectionView> is the default view for collections that implement <xref:System.ComponentModel.IBindingListView> or <xref:System.ComponentModel.IBindingList>.  
   
- Alternatively, you can create a view of your collection in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by using the <xref:System.Windows.Data.CollectionViewSource> class and then bind your control to that view. The <xref:System.Windows.Data.CollectionViewSource> class is the XAML representation of the <xref:System.Windows.Data.CollectionView> class. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
+ Alternatively, you can create a view of your collection in Extensible Application Markup Language (XAML) by using the <xref:System.Windows.Data.CollectionViewSource> class and then bind your control to that view. The <xref:System.Windows.Data.CollectionViewSource> class is the XAML representation of the <xref:System.Windows.Data.CollectionView> class. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
   
  For more information, see "Binding to Collections" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
diff --git a/xml/System.Windows.Data/CollectionViewSource.xml b/xml/System.Windows.Data/CollectionViewSource.xml
index cb20c8fad26..2a2517ed11c 100644
--- a/xml/System.Windows.Data/CollectionViewSource.xml
+++ b/xml/System.Windows.Data/CollectionViewSource.xml
@@ -484,7 +484,7 @@
 ## Remarks  
  This default view is never affiliated with any <xref:System.Windows.Data.CollectionViewSource> objects.  
   
- All collections have a default <xref:System.Windows.Data.CollectionView>. WPF always binds to a view rather than a collection. If you bind directly to a collection, WPF actually binds to the default view for that collection. This default view is shared by all bindings to the collection, which causes all direct bindings to the collection to share the sort, filter, group, and current item characteristics of the one default view. Alternatively, you can create a view of your collection in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] or code using the <xref:System.Windows.Data.CollectionViewSource> class, and binding your control to that view. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
+ All collections have a default <xref:System.Windows.Data.CollectionView>. WPF always binds to a view rather than a collection. If you bind directly to a collection, WPF actually binds to the default view for that collection. This default view is shared by all bindings to the collection, which causes all direct bindings to the collection to share the sort, filter, group, and current item characteristics of the one default view. Alternatively, you can create a view of your collection in Extensible Application Markup Language (XAML) or code using the <xref:System.Windows.Data.CollectionViewSource> class, and binding your control to that view. For an example, see [How to: Sort and Group Data Using a View in XAML](/dotnet/framework/wpf/data/how-to-sort-and-group-data-using-a-view-in-xaml).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Data/MultiBinding.xml b/xml/System.Windows.Data/MultiBinding.xml
index 618d34d2be4..fbaa1b2afdb 100644
--- a/xml/System.Windows.Data/MultiBinding.xml
+++ b/xml/System.Windows.Data/MultiBinding.xml
@@ -97,7 +97,7 @@
 ## Remarks  
   
 > [!NOTE]
->  This property can be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] only by using the syntax that is shown, or by accessing the collection object and using its various methods, such as `Add`. The property used to access the collection object is read-only, whereas the collection itself is read/write.  
+>  This property can be set in Extensible Application Markup Language (XAML) only by using the syntax that is shown, or by accessing the collection object and using its various methods, such as `Add`. The property used to access the collection object is read-only, whereas the collection itself is read/write.  
   
 <a name="xamlPropertyElementUsage_Bindings"></a>   
 ## XAML Property Element Usage  
@@ -789,7 +789,7 @@
  For more information about the validation process and how to provide visual feedback upon invalidation, see "Data Validation" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
 > [!NOTE]
->  This property can be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] only by using the syntax shown, or by accessing the collection object and using its various methods, such as `Add`. The property used to access the collection object is read-only, whereas the collection itself is read-write.  
+>  This property can be set in Extensible Application Markup Language (XAML) only by using the syntax shown, or by accessing the collection object and using its various methods, such as `Add`. The property used to access the collection object is read-only, whereas the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_ValidationRules"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Data/ObjectDataProvider.xml b/xml/System.Windows.Data/ObjectDataProvider.xml
index 5802f3bde2a..8956a0df943 100644
--- a/xml/System.Windows.Data/ObjectDataProvider.xml
+++ b/xml/System.Windows.Data/ObjectDataProvider.xml
@@ -31,7 +31,7 @@
 > [!IMPORTANT]
 >  <xref:System.Windows.Data.ObjectDataProvider> fails when it does not have permissions to perform reflection on the given type or member. For more information, see Permissions Requirements in [Binding Sources Overview](/dotnet/framework/wpf/data/binding-sources-overview).  
   
- There are many ways to create an object to use as a binding source. For example, you can create your object in the resources section of your [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] page, or you can create your object in code and set it as the `DataContext` of your window.  
+ There are many ways to create an object to use as a binding source. For example, you can create your object in the resources section of your Extensible Application Markup Language (XAML) page, or you can create your object in code and set it as the `DataContext` of your window.  
   
  <xref:System.Windows.Data.ObjectDataProvider> enables you to create your object in XAML and make it available as a binding source. It provides the following properties that enable you to execute a query on your object and bind to the results.  
   
diff --git a/xml/System.Windows.Data/PriorityBinding.xml b/xml/System.Windows.Data/PriorityBinding.xml
index bf85c701fa9..74cd7e6e4b9 100644
--- a/xml/System.Windows.Data/PriorityBinding.xml
+++ b/xml/System.Windows.Data/PriorityBinding.xml
@@ -110,7 +110,7 @@
 ## Remarks  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] by using the collection syntax that is shown in the following example, or by accessing the collection object and using its various methods, such as Add. The property that you use to access the collection object is read-only, whereas the collection itself is read/write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) by using the collection syntax that is shown in the following example, or by accessing the collection object and using its various methods, such as Add. The property that you use to access the collection object is read-only, whereas the collection itself is read/write.  
   
 <a name="xamlPropertyElementUsage_Bindings"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows.Data/XmlNamespaceMapping.xml b/xml/System.Windows.Data/XmlNamespaceMapping.xml
index cdd590075f8..82312422fc6 100644
--- a/xml/System.Windows.Data/XmlNamespaceMapping.xml
+++ b/xml/System.Windows.Data/XmlNamespaceMapping.xml
@@ -93,7 +93,7 @@
         <Parameter Name="uri" Type="System.Uri" />
       </Parameters>
       <Docs>
-        <param name="prefix">The prefix to use in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].</param>
+        <param name="prefix">The prefix to use in Extensible Application Markup Language (XAML).</param>
         <param name="uri">The <see cref="T:System.Uri" /> of the namespace to create the mapping for.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Data.XmlNamespaceMapping" /> class with the specified prefix and uniform resource identifier (URI).</summary>
         <remarks>To be added.</remarks>
@@ -239,7 +239,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the prefix to use in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].</summary>
+        <summary>Gets or sets the prefix to use in Extensible Application Markup Language (XAML).</summary>
         <value>The prefix to associate with the URI. The default is an empty string("").</value>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Data.XmlDataProvider" />
diff --git a/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml b/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
index db21980c4f5..c8fd8ec598f 100644
--- a/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
+++ b/xml/System.Windows.Data/XmlNamespaceMappingCollection.xml
@@ -43,7 +43,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Data.XmlNamespaceMapping> class provides a mapping between the namespace specified in your XML binding source and a prefix you specify that you can use in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The <xref:System.Windows.Data.XmlNamespaceMapping> class provides a mapping between the namespace specified in your XML binding source and a prefix you specify that you can use in Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/CursorType.xml b/xml/System.Windows.Input/CursorType.xml
index 0a108463b02..8d32ca910fa 100644
--- a/xml/System.Windows.Input/CursorType.xml
+++ b/xml/System.Windows.Input/CursorType.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Input.CursorType> is mostly used in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] to specify the cursor.  In code, you should use the <xref:System.Windows.Input.Cursors> class.  
+ <xref:System.Windows.Input.CursorType> is mostly used in Extensible Application Markup Language (XAML) to specify the cursor.  In code, you should use the <xref:System.Windows.Input.Cursors> class.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Input/KeyBinding.xml b/xml/System.Windows.Input/KeyBinding.xml
index d4dce7fa7fb..357ebd210d7 100644
--- a/xml/System.Windows.Input/KeyBinding.xml
+++ b/xml/System.Windows.Input/KeyBinding.xml
@@ -25,7 +25,7 @@
   
  With the exception of the function keys and the numeric keypad keys, a valid <xref:System.Windows.Input.KeyGesture> must contain exactly one <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  Function keys and numeric keypad keys do not require a modifier key in order to be a valid <xref:System.Windows.Input.KeyGesture>. It is possible to specify an invalid <xref:System.Windows.Input.KeyGesture> and a <xref:System.Windows.Input.KeyBinding> with an invalid associated gesture, either through XAML or code. For instance, there is no validation that prevents creating and binding a <xref:System.Windows.Input.KeyGesture> that contains only a nonfunction key, or only modifiers but no key. Such a <xref:System.Windows.Input.KeyBinding> will never attempt to invoke its associated command.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in Extensible Application Markup Language (XAML) there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
  A <xref:System.Windows.Input.KeyBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.KeyBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in XAML by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
   
@@ -271,7 +271,7 @@
 ## Remarks  
  With the exception of the function keys and the numeric keypad keys, a <xref:System.Windows.Input.KeyGesture> must contain a <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in Extensible Application Markup Language (XAML) there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
  ]]></format>
         </remarks>
@@ -332,7 +332,7 @@
 ## Remarks  
  With the exception of the function keys and the numeric keypad keys, a <xref:System.Windows.Input.KeyGesture> must contain a <xref:System.Windows.Input.Key> and one or more <xref:System.Windows.Input.ModifierKeys>.  
   
- When defining a <xref:System.Windows.Input.KeyBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.KeyBinding> in Extensible Application Markup Language (XAML) there are two ways to specify the <xref:System.Windows.Input.KeyGesture>. The first way to establish a <xref:System.Windows.Input.KeyBinding> in XAML is to define the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.KeyBinding> element, which enables a syntax to specify keys and modifiers as a single string, for example "CTRL+P". The second way is to define the <xref:System.Windows.Input.KeyBinding.Key%2A> attribute and the <xref:System.Windows.Input.KeyBinding.Modifiers%2A> attributes of the <xref:System.Windows.Input.KeyBinding> element. Both ways of setting the <xref:System.Windows.Input.KeyGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.KeyBinding.Key%2A>, <xref:System.Windows.Input.KeyBinding.Modifiers%2A>, and the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attributes are all set, the attribute which is defined last will be used for the <xref:System.Windows.Input.KeyGesture>. You can potentially have situations where for example a <xref:System.Windows.Input.KeyBinding.Key%2A> set last will overwrite just the Key component of a preceding Gesture but leave the Gesture's modifiers the same. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML; this will avoid ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
 <a name="xamlAttributeUsage_Modifiers"></a>   
 ## XAML Attribute Usage  
diff --git a/xml/System.Windows.Input/MouseBinding.xml b/xml/System.Windows.Input/MouseBinding.xml
index 1732604f8a2..e150cb9a912 100644
--- a/xml/System.Windows.Input/MouseBinding.xml
+++ b/xml/System.Windows.Input/MouseBinding.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  A <xref:System.Windows.Input.MouseBinding> associates a <xref:System.Windows.Input.MouseGesture> with an <xref:System.Windows.Input.ICommand> implementation. <xref:System.Windows.Input.RoutedCommand> is the primary implementation of the <xref:System.Windows.Input.ICommand> interface for the WPF commanding system. In general, when the <xref:System.Windows.Input.MouseGesture> is executed, the command is invoked, although the command behavior is further influenced by command-specific factors such as the <xref:System.Windows.Input.CanExecuteRoutedEventArgs.CanExecute%2A> value.  For more information on commanding, see the [Commanding Overview](/dotnet/framework/wpf/advanced/commanding-overview).  
   
- When defining a <xref:System.Windows.Input.MouseBinding> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], there are two ways to specify the <xref:System.Windows.Input.MouseGesture>. The first way to establish a <xref:System.Windows.Input.MouseBinding> in XAML is to define the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element, which enables a syntax to specify mouse actions and modifiers as a single string; for example, "CTRL+LeftClick". The second way is to define the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element. Both ways of setting the <xref:System.Windows.Input.MouseGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> and the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attributes are both set, the gesture is invalid. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML, even if you do not specify modifiers; this avoids ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
+ When defining a <xref:System.Windows.Input.MouseBinding> in Extensible Application Markup Language (XAML), there are two ways to specify the <xref:System.Windows.Input.MouseGesture>. The first way to establish a <xref:System.Windows.Input.MouseBinding> in XAML is to define the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element, which enables a syntax to specify mouse actions and modifiers as a single string; for example, "CTRL+LeftClick". The second way is to define the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> attribute of the <xref:System.Windows.Input.MouseBinding> element. Both ways of setting the <xref:System.Windows.Input.MouseGesture> are equivalent and modify the same underlying object, but there will be a conflict if both are used.  In the case when the <xref:System.Windows.Input.MouseBinding.MouseAction%2A> and the <xref:System.Windows.Input.MouseBinding.Gesture%2A> attributes are both set, the gesture is invalid. In general, it is recommended that you use only the <xref:System.Windows.Input.KeyBinding.Gesture%2A> attribute from XAML, even if you do not specify modifiers; this avoids ambiguity, provides the most streamlined syntax, and provides the most straightforward representation for serialization.  
   
  A <xref:System.Windows.Input.MouseBinding> can be defined on a specific object or at the class level by registering a <xref:System.Windows.Input.CommandManager.RegisterClassInputBinding%2A> on the <xref:System.Windows.Input.CommandManager> class. The most typical way to define a <xref:System.Windows.Input.MouseBinding> is within the control template, setting the <xref:System.Windows.UIElement.InputBindings%2A> property in XAML by declaring one or more <xref:System.Windows.Input.MouseBinding> or <xref:System.Windows.Input.KeyBinding> elements.  
   
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
index f96b99a60c6..651cc5d5eed 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResource.xml
@@ -169,7 +169,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Localization comments are authored by the developer to provide rules or hints for localizers. The comments are free-form strings that are extracted from BAML or from localization comments files. To attach comments to an element in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], use the <xref:System.Windows.Localization.Comments%2A?displayProperty=nameWithType> attached property For more information on this attached property, see [Localization Attributes and Comments](/dotnet/framework/wpf/advanced/localization-attributes-and-comments).  
+ Localization comments are authored by the developer to provide rules or hints for localizers. The comments are free-form strings that are extracted from BAML or from localization comments files. To attach comments to an element in Extensible Application Markup Language (XAML), use the <xref:System.Windows.Localization.Comments%2A?displayProperty=nameWithType> attached property For more information on this attached property, see [Localization Attributes and Comments](/dotnet/framework/wpf/advanced/localization-attributes-and-comments).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
index 8e6e6eb4709..811b5339d5a 100644
--- a/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
+++ b/xml/System.Windows.Markup.Localizer/BamlLocalizableResourceKey.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class represents a key that can uniquely identify a localizable value inside binary XAML (BAML). It represents a combination of a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A>, class name, and property name.  
   
- The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file either by using the `updateuid` Microsoft build engine (MSBuild) target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
+ The <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> value must be added to the source Extensible Application Markup Language (XAML) file either by using the `updateuid` Microsoft build engine (MSBuild) target (for example, `msbuild /t:updateuid myproj.proj`), or manually in the markup. BAML without a <xref:System.Windows.Markup.Localizer.BamlLocalizableResourceKey.Uid%2A> cannot be localized. The class name is the type name of the element that contains the localizable property. The property name refers to the property that has the localizable value. A special property called "`$Content`" is used to represent values that are the initialization text or content property of an element. For example the `$Content` property name would apply to the initialization text `Click` in the following XAML:  
   
  `<TextBlock x:Uid="myBlock">Click </TextBlock>`  
     
diff --git a/xml/System.Windows.Media.Animation/BooleanAnimationBase.xml b/xml/System.Windows.Media.Animation/BooleanAnimationBase.xml
index 452c52b6551..b4690b6888a 100644
--- a/xml/System.Windows.Media.Animation/BooleanAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/BooleanAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.BooleanAnimationUsingKeyFrames> class using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.BooleanAnimationUsingKeyFrames> class using Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#BooleanAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/BooleanAnimationUsingKeyFramesExample.xaml#booleananimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/ColorAnimationBase.xml b/xml/System.Windows.Media.Animation/ColorAnimationBase.xml
index 438b2f4b9ea..8d63f7474b5 100644
--- a/xml/System.Windows.Media.Animation/ColorAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/ColorAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ColorAnimationUsingKeyFrames> class using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ColorAnimationUsingKeyFrames> class using Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#ColorAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/ColorAnimationUsingKeyFramesExample.xaml#coloranimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/DoubleAnimationBase.xml b/xml/System.Windows.Media.Animation/DoubleAnimationBase.xml
index edef3e5148f..47a65b908cf 100644
--- a/xml/System.Windows.Media.Animation/DoubleAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/DoubleAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class using Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#AltDoubleAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/AltDoubleAnimationUsingKeyFramesExample.xaml#altdoubleanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/DoubleAnimationUsingPath.xml b/xml/System.Windows.Media.Animation/DoubleAnimationUsingPath.xml
index 76ebfe8f124..2d09d898ca2 100644
--- a/xml/System.Windows.Media.Animation/DoubleAnimationUsingPath.xml
+++ b/xml/System.Windows.Media.Animation/DoubleAnimationUsingPath.xml
@@ -299,7 +299,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], you can use a special abbreviated syntax to describe the path.  
+ In Extensible Application Markup Language (XAML), you can use a special abbreviated syntax to describe the path.  
   
  [!code-xaml[PathAnimationGallery_snippet#DoubleAnimationUsingPathAttributeSyntaxExample](~/samples/snippets/csharp/VS_Snippets_Wpf/PathAnimationGallery_snippet/CS/doubleanimationusingpathattributesyntaxexample.xaml#doubleanimationusingpathattributesyntaxexample)] 
   
diff --git a/xml/System.Windows.Media.Animation/Int16AnimationBase.xml b/xml/System.Windows.Media.Animation/Int16AnimationBase.xml
index 7e3503da1fa..5d910b571c1 100644
--- a/xml/System.Windows.Media.Animation/Int16AnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/Int16AnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int16AnimationUsingKeyFrames>.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML), but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int16AnimationUsingKeyFrames>.  
   
  [!code-xaml[keyframes_ovw_snippet#AltDoubleAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/AltDoubleAnimationUsingKeyFramesExample.xaml#altdoubleanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/Int32AnimationBase.xml b/xml/System.Windows.Media.Animation/Int32AnimationBase.xml
index c6cbd152de7..5f4af8eb6bc 100644
--- a/xml/System.Windows.Media.Animation/Int32AnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/Int32AnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int32AnimationUsingKeyFrames>.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML), but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int32AnimationUsingKeyFrames>.  
   
  [!code-xaml[keyframes_ovw_snippet#AltDoubleAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/AltDoubleAnimationUsingKeyFramesExample.xaml#altdoubleanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/Int64AnimationBase.xml b/xml/System.Windows.Media.Animation/Int64AnimationBase.xml
index 4e62d0b55e5..11196196f68 100644
--- a/xml/System.Windows.Media.Animation/Int64AnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/Int64AnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int64AnimationUsingKeyFrames>.  
+ The following code example demonstrates how to use the <xref:System.Windows.Media.Animation.DoubleAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML), but generically shows how to use other derived classes such as <xref:System.Windows.Media.Animation.Int64AnimationUsingKeyFrames>.  
   
  [!code-xaml[keyframes_ovw_snippet#AltDoubleAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/AltDoubleAnimationUsingKeyFramesExample.xaml#altdoubleanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/MatrixAnimationBase.xml b/xml/System.Windows.Media.Animation/MatrixAnimationBase.xml
index 0c6d2affd09..01a65d104ca 100644
--- a/xml/System.Windows.Media.Animation/MatrixAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/MatrixAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.MatrixAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.MatrixAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#MatrixAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/MatrixAnimationUsingKeyFramesExample.xaml#matrixanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/ObjectAnimationBase.xml b/xml/System.Windows.Media.Animation/ObjectAnimationBase.xml
index 51a6b849ff1..fe6945b3a45 100644
--- a/xml/System.Windows.Media.Animation/ObjectAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/ObjectAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ObjectAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ObjectAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#ObjectAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/ObjectAnimationUsingKeyFramesExample.xaml#objectanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/PointAnimationBase.xml b/xml/System.Windows.Media.Animation/PointAnimationBase.xml
index 9c8088e90c6..50903e0a78f 100644
--- a/xml/System.Windows.Media.Animation/PointAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/PointAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.PointAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.PointAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#PointAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/PointAnimationUsingKeyFramesExample.xaml#pointanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/RectAnimationBase.xml b/xml/System.Windows.Media.Animation/RectAnimationBase.xml
index f4055b9567c..90053c79118 100644
--- a/xml/System.Windows.Media.Animation/RectAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/RectAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.RectAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.RectAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#RectAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/RectAnimationUsingKeyFramesExample.xaml#rectanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/SizeAnimationBase.xml b/xml/System.Windows.Media.Animation/SizeAnimationBase.xml
index 04b646445d2..63a206adbbf 100644
--- a/xml/System.Windows.Media.Animation/SizeAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/SizeAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.SizeAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.SizeAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#SizeAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/SizeAnimationUsingKeyFramesExample.xaml#sizeanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/StringAnimationBase.xml b/xml/System.Windows.Media.Animation/StringAnimationBase.xml
index 02d1f673d37..893f5f3f5cb 100644
--- a/xml/System.Windows.Media.Animation/StringAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/StringAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.StringAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.StringAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#StringAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/StringAnimationUsingKeyFramesExample.xaml#stringanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Animation/ThicknessAnimationBase.xml b/xml/System.Windows.Media.Animation/ThicknessAnimationBase.xml
index fcf79941fdf..f958e1554e7 100644
--- a/xml/System.Windows.Media.Animation/ThicknessAnimationBase.xml
+++ b/xml/System.Windows.Media.Animation/ThicknessAnimationBase.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ThicknessAnimationUsingKeyFrames> class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following code example demonstrates how to use the derived <xref:System.Windows.Media.Animation.ThicknessAnimationUsingKeyFrames> class in Extensible Application Markup Language (XAML).  
   
  [!code-xaml[keyframes_ovw_snippet#ThicknessAnimationUsingKeyFramesWholePage](~/samples/snippets/csharp/VS_Snippets_Wpf/keyframes_ovw_snippet/CS/ThicknessAnimationUsingKeyFramesExample.xaml#thicknessanimationusingkeyframeswholepage)]   
   
diff --git a/xml/System.Windows.Media.Converters/BaseIListConverter.xml b/xml/System.Windows.Media.Converters/BaseIListConverter.xml
index b1787e940db..0bf2971f71b 100644
--- a/xml/System.Windows.Media.Converters/BaseIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/BaseIListConverter.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class and its derivatives are intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class and its derivatives are intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Converters/BoolIListConverter.xml b/xml/System.Windows.Media.Converters/BoolIListConverter.xml
index 6d03fee4e02..7804de09805 100644
--- a/xml/System.Windows.Media.Converters/BoolIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/BoolIListConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The converted <xref:System.String> is a sequence of delimited zeros and ones; zero indicates false and one indicates true.  
   
- This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Converters/CharIListConverter.xml b/xml/System.Windows.Media.Converters/CharIListConverter.xml
index 9ce05b6821d..d2a5d65d4f6 100644
--- a/xml/System.Windows.Media.Converters/CharIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/CharIListConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The converted <xref:System.String> is a concatenated list of all the characters in the <xref:System.Collections.IList>. They are not delimited.  
   
- This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Converters/DoubleIListConverter.xml b/xml/System.Windows.Media.Converters/DoubleIListConverter.xml
index 8a9e9aa47df..24179b47cc0 100644
--- a/xml/System.Windows.Media.Converters/DoubleIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/DoubleIListConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The converted <xref:System.String> is a sequence of delimited numbers.  
   
- This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Converters/PointIListConverter.xml b/xml/System.Windows.Media.Converters/PointIListConverter.xml
index a15b843563a..4d5f6aa7174 100644
--- a/xml/System.Windows.Media.Converters/PointIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/PointIListConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The converted <xref:System.String> is a sequence of delimited <xref:System.Windows.Point> values.  
   
- This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Converters/UShortIListConverter.xml b/xml/System.Windows.Media.Converters/UShortIListConverter.xml
index 9bd7f4aa7c5..0888918d0e9 100644
--- a/xml/System.Windows.Media.Converters/UShortIListConverter.xml
+++ b/xml/System.Windows.Media.Converters/UShortIListConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  The converted <xref:System.String> is a sequence of delimited UShort values.  
   
- This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ This class is only intended to be used by the <xref:System.Windows.Markup.Primitives.MarkupWriter> for serialization of Extensible Application Markup Language (XAML).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
index f8a10a65c7f..1983978c5da 100644
--- a/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapEncoder.xml
@@ -200,7 +200,7 @@
   
 <a name="xamlTextUsage_Frames"></a>   
 ## XAML Text Usage  
- You cannot use this property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ You cannot use this property in Extensible Application Markup Language (XAML).  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapImage.xml b/xml/System.Windows.Media.Imaging/BitmapImage.xml
index 9420ed1b7a9..08623766830 100644
--- a/xml/System.Windows.Media.Imaging/BitmapImage.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapImage.xml
@@ -29,7 +29,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Media.Imaging.BitmapImage> primarily exists to support [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] syntax and introduces additional properties for bitmap loading that are not defined by <xref:System.Windows.Media.Imaging.BitmapSource>.  
+ <xref:System.Windows.Media.Imaging.BitmapImage> primarily exists to support Extensible Application Markup Language (XAML) syntax and introduces additional properties for bitmap loading that are not defined by <xref:System.Windows.Media.Imaging.BitmapSource>.  
   
  <xref:System.Windows.Media.Imaging.BitmapImage> implements the <xref:System.ComponentModel.ISupportInitialize> interface to optimize initialization on multiple properties. Property changes can only occur during object initialization. Call <xref:System.Windows.Media.Imaging.BitmapImage.BeginInit%2A> to signal that initialization has begun and <xref:System.Windows.Media.Imaging.BitmapImage.EndInit%2A> to signal that initialization has completed. After initialization, property changes are ignored.  
   
@@ -38,7 +38,7 @@
    
   
 ## Examples  
- The following code examples demonstrate how to use a <xref:System.Windows.Media.Imaging.BitmapImage> in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following code examples demonstrate how to use a <xref:System.Windows.Media.Imaging.BitmapImage> in Extensible Application Markup Language (XAML) and code.  
   
  [!code-xaml[ImageElementExample#SimpleXAML2](~/samples/snippets/csharp/VS_Snippets_Wpf/ImageElementExample/CSharp/SimpleImageExample.xaml#simplexaml2)]
  [!code-xaml[ImageElementExample#SimpleXAML2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ImageElementExample/VB/SimpleImageExample.xaml#simplexaml2)]  
@@ -862,7 +862,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to rotate an image by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following code example demonstrates how to rotate an image by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-xaml[ImageElementExample#TransformedXAML2](~/samples/snippets/csharp/VS_Snippets_Wpf/ImageElementExample/CSharp/TransformedImageExample.xaml#transformedxaml2)]  
   
@@ -1128,7 +1128,7 @@
    
   
 ## Examples  
- The following example demonstrates the use the <xref:System.Windows.Media.Imaging.BitmapImage.UriSource%2A> property in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example demonstrates the use the <xref:System.Windows.Media.Imaging.BitmapImage.UriSource%2A> property in Extensible Application Markup Language (XAML) and code.  
   
  [!code-xaml[imageelementexample#SimpleXAML2](~/samples/snippets/csharp/VS_Snippets_Wpf/ImageElementExample/CSharp/SimpleImageExample.xaml#simplexaml2)]
  [!code-xaml[imageelementexample#SimpleXAML2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ImageElementExample/VB/SimpleImageExample.xaml#simplexaml2)]  
diff --git a/xml/System.Windows.Media/FontFamily.xml b/xml/System.Windows.Media/FontFamily.xml
index 092b80c4914..b03de0ce780 100644
--- a/xml/System.Windows.Media/FontFamily.xml
+++ b/xml/System.Windows.Media/FontFamily.xml
@@ -40,7 +40,7 @@
  ![Fonts](~/add/media/fonts.PNG "Fonts")  
 Example of typefaces that are members of the "Times New Roman" font family  
   
- Most user interface (UI) elements, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBlock>, provide a <xref:System.Windows.Controls.Control.FontFamily%2A> property that can be used to specify a font for the text content of a control. You define the font by setting that property with a <xref:System.Windows.Media.FontFamily> value. The following examples show how to reference a font, in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and in code.  
+ Most user interface (UI) elements, such as <xref:System.Windows.Controls.Button> and <xref:System.Windows.Controls.TextBlock>, provide a <xref:System.Windows.Controls.Control.FontFamily%2A> property that can be used to specify a font for the text content of a control. You define the font by setting that property with a <xref:System.Windows.Media.FontFamily> value. The following examples show how to reference a font, in Extensible Application Markup Language (XAML) and in code.  
   
  [!code-csharp[FontSnippets#FontFallbackSnippet3](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontFamilySnippets.xaml.cs#fontfallbacksnippet3)]
  [!code-vb[FontSnippets#FontFallbackSnippet3](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontfamilysnippets.xaml.vb#fontfallbacksnippet3)]
@@ -49,7 +49,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  In the preceding example, the font that is referenced, "Comic Sans MS", is referred to by its *friendly name*. Also, in this example the font is assumed to be in the system font collection.  
   
 ## Specifying Fonts in Alternate Directories  
- A Windows Presentation Foundation (WPF) application can specify a directory, other than the directory that contains the systems font collection, for resolving font references. The friendly name of the font can specify an absolute uniform resource identifier (URI) value to resolve the font reference, as shown in the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code examples.  
+ A Windows Presentation Foundation (WPF) application can specify a directory, other than the directory that contains the systems font collection, for resolving font references. The friendly name of the font can specify an absolute uniform resource identifier (URI) value to resolve the font reference, as shown in the following Extensible Application Markup Language (XAML) and code examples.  
   
  [!code-csharp[FontSnippets#FontPackageSnippet6](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml.cs#fontpackagesnippet6)]
  [!code-vb[FontSnippets#FontPackageSnippet6](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontpackagesnippets.xaml.vb#fontpackagesnippet6)]
@@ -65,7 +65,7 @@ Example of typefaces that are members of the "Times New Roman" font family
  [!code-csharp[FontSnippets#FontPackageSnippet2](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml.cs#fontpackagesnippet2)]
  [!code-vb[FontSnippets#FontPackageSnippet2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontpackagesnippets.xaml.vb#fontpackagesnippet2)]  
   
- When a <xref:System.Windows.Media.FontFamily> is specified as an attribute in markup, the base URI value is always implied - its value is the URI of the XAML page. The implied base URI value is used with the relative URI value in the friendly name string to obtain the location of the font. In the following [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] example, notice that the relative URI value uses the "./" notation, which means "in the current folder" of the base URI value.  
+ When a <xref:System.Windows.Media.FontFamily> is specified as an attribute in markup, the base URI value is always implied - its value is the URI of the XAML page. The implied base URI value is used with the relative URI value in the friendly name string to obtain the location of the font. In the following Extensible Application Markup Language (XAML) example, notice that the relative URI value uses the "./" notation, which means "in the current folder" of the base URI value.  
   
  [!code-xaml[FontSnippets#FontPackageSnippet1](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontPackageSnippets.xaml#fontpackagesnippet1)]  
   
@@ -85,7 +85,7 @@ Example of typefaces that are members of the "Times New Roman" font family
 ## Defining a Font Fallback Sequence in Code  
  You can define a font fallback sequence in your code, which lets you define an alternate font. When you create a <xref:System.Windows.Media.FontFamily> object, provide multiple font family names, separated by commas, for the <xref:System.String> parameter, such as "Comic Sans MS, Verdana". In this case, if the glyphs from the "Comic Sans MS" typeface are not available, glyphs from the "Verdana" typeface are used. If neither "Comic Sans MS" nor "Verdana" have the required glyphs, the fallback font family of the typeface is used, which is "Global User Interface" by default.  
   
- The following examples show how to define a font fallback sequence, in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and in code.  
+ The following examples show how to define a font fallback sequence, in Extensible Application Markup Language (XAML) and in code.  
   
  [!code-csharp[FontSnippets#FontFallbackSnippet1](~/samples/snippets/csharp/VS_Snippets_Wpf/FontSnippets/CSharp/FontFamilySnippets.xaml.cs#fontfallbacksnippet1)]
  [!code-vb[FontSnippets#FontFallbackSnippet1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/FontSnippets/visualbasic/fontfamilysnippets.xaml.vb#fontfallbacksnippet1)]
diff --git a/xml/System.Windows.Media/MediaPlayer.xml b/xml/System.Windows.Media/MediaPlayer.xml
index 0e55fecf701..dbedfd63763 100644
--- a/xml/System.Windows.Media/MediaPlayer.xml
+++ b/xml/System.Windows.Media/MediaPlayer.xml
@@ -22,7 +22,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Although you can declare an instance of this class in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], you cannot load and play its media without using code. To play media in XAML only, use a <xref:System.Windows.Controls.MediaElement>. Also, if you declare an instance in XAML, the only practical use is to fill property element syntax for the <xref:System.Windows.Media.VideoDrawing.Player%2A> property.  
+ Although you can declare an instance of this class in Extensible Application Markup Language (XAML), you cannot load and play its media without using code. To play media in XAML only, use a <xref:System.Windows.Controls.MediaElement>. Also, if you declare an instance in XAML, the only practical use is to fill property element syntax for the <xref:System.Windows.Media.VideoDrawing.Player%2A> property.  
   
  When distributing media with your application, you cannot use a media file as a project resource. In your project file, you must instead set the media type to `Content` and set `CopyToOutputDirectory` to `PreserveNewest` or `Always`.  
   
diff --git a/xml/System.Windows.Navigation/NavigationService.xml b/xml/System.Windows.Navigation/NavigationService.xml
index 7e3a9dbdbfb..a072d3bde39 100644
--- a/xml/System.Windows.Navigation/NavigationService.xml
+++ b/xml/System.Windows.Navigation/NavigationService.xml
@@ -826,7 +826,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is only for standalone applications and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] content.  
+ This method is only for standalone applications and Extensible Application Markup Language (XAML) content.  
   
  This method exhibits the same behavior as <xref:System.Windows.Navigation.NavigationService.Navigate%2A?displayProperty=nameWithType>, and extends it by ensuring that the content that is being downloaded is placed into a partial trust security sandbox (with the default Internet zone set of permissions - see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security)).  
   
diff --git a/xml/System.Windows.Navigation/NavigationWindow.xml b/xml/System.Windows.Navigation/NavigationWindow.xml
index 663aee26997..d77edec0d80 100644
--- a/xml/System.Windows.Navigation/NavigationWindow.xml
+++ b/xml/System.Windows.Navigation/NavigationWindow.xml
@@ -1241,7 +1241,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether a <see cref="T:System.Windows.Navigation.NavigationWindow" /> isolates external [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] content within a partial trust security sandbox (with default Internet zone permission set).</summary>
+        <summary>Gets or sets a value that indicates whether a <see cref="T:System.Windows.Navigation.NavigationWindow" /> isolates external Extensible Application Markup Language (XAML) content within a partial trust security sandbox (with default Internet zone permission set).</summary>
         <value>
           <see langword="true" /> if content is isolated within a partial trust security sandbox; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Resources/ContentTypes.xml b/xml/System.Windows.Resources/ContentTypes.xml
index 6d116f4e361..f37b51a7bd1 100644
--- a/xml/System.Windows.Resources/ContentTypes.xml
+++ b/xml/System.Windows.Resources/ContentTypes.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The only purpose of this class is to provide the Multipurpose Internet Mail Extensions (MIME) type string for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] as a public field.  
+ The only purpose of this class is to provide the Multipurpose Internet Mail Extensions (MIME) type string for Extensible Application Markup Language (XAML) as a public field.  
   
  ]]></format>
     </remarks>
@@ -70,7 +70,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Declares the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] content type.</summary>
+        <summary>Declares the Extensible Application Markup Language (XAML) content type.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Windows.Resources.StreamResourceInfo" />
       </Docs>
diff --git a/xml/System.Windows.Shapes/Polygon.xml b/xml/System.Windows.Shapes/Polygon.xml
index a8091fd8406..7744d461b53 100644
--- a/xml/System.Windows.Shapes/Polygon.xml
+++ b/xml/System.Windows.Shapes/Polygon.xml
@@ -180,7 +180,7 @@ FillRule Example
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], use a space-delimited list of comma-separated x-coordinate and y-coordinate pairs to set this attribute. Use simple notation, that is, `x1,y1 x2,y2 ... xn,yn`.  
+ In Extensible Application Markup Language (XAML), use a space-delimited list of comma-separated x-coordinate and y-coordinate pairs to set this attribute. Use simple notation, that is, `x1,y1 x2,y2 ... xn,yn`.  
   
 <a name="dependencyPropertyInfo_Points"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Shapes/Polyline.xml b/xml/System.Windows.Shapes/Polyline.xml
index 353b3183876..14e2ae0d010 100644
--- a/xml/System.Windows.Shapes/Polyline.xml
+++ b/xml/System.Windows.Shapes/Polyline.xml
@@ -181,7 +181,7 @@ FillRule Example
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], use a space-delimited list of comma-separated x- coordinate and y-coordinate pairs to set this attribute. Use simple notation, that is, `x1,y1 x2,y2 ... xn,yn`.  
+ In Extensible Application Markup Language (XAML), use a space-delimited list of comma-separated x- coordinate and y-coordinate pairs to set this attribute. Use simple notation, that is, `x1,y1 x2,y2 ... xn,yn`.  
   
 <a name="dependencyPropertyInfo_Points"></a>   
 ## Dependency Property Information  
diff --git a/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml b/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
index d5d009b77e5..6e8604921d9 100644
--- a/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
+++ b/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
@@ -23,7 +23,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Shell.ThumbButtonInfoCollection> is a strongly-typed <xref:System.Windows.FreezableCollection%601> that is used to support declarations in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ <xref:System.Windows.Shell.ThumbButtonInfoCollection> is a strongly-typed <xref:System.Windows.FreezableCollection%601> that is used to support declarations in Extensible Application Markup Language (XAML).  
   
  The [!INCLUDE[win7](~/includes/win7-md.md)] shell allows a maximum of seven buttons in the taskbar preview. If more than seven <xref:System.Windows.Shell.ThumbButtonInfo> objects are added to the <xref:System.Windows.Shell.ThumbButtonInfoCollection>, the additional objects are treated as overflow. When a button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements and no space is reserved for it. In this case, additional buttons from the <xref:System.Windows.Shell.ThumbButtonInfoCollection> overflow are displayed.  
   
diff --git a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
index b42ea709ebe..ced40381734 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableAttribute.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute (and derived classes) is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for Extensible Application Markup Language (XAML), because an attached property is primarily a XAML concept.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
index 0a066e43839..0fa33270b4b 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForChildrenAttribute.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for Extensible Application Markup Language (XAML), because an attached property is primarily a XAML concept.  
   
  When this  .NET Framework attribute is applied to the get accessor for an attached property, this  .NET Framework attribute specifies that an attached property is browsable when the attached property owner is a parent element of other elements.  
   
diff --git a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
index f9f8795f2bd..538c88f09b9 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableForTypeAttribute.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for Extensible Application Markup Language (XAML), because an attached property is primarily a XAML concept.  
   
  If more than one type is specified for a <xref:System.Windows.AttachedPropertyBrowsableForTypeAttribute> .NET Framework attribute, the property is browsable if any specified type matches (logical or).  The type can also be an interface.  
   
diff --git a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
index 9d89c80905a..ac4f5a7d693 100644
--- a/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
+++ b/xml/System.Windows/AttachedPropertyBrowsableWhenAttributePresentAttribute.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], because an attached property is primarily a XAML concept.  
+ The meaning of the term `browsable` as used in descriptions for this .NET Framework attribute is analogous to the descriptions given for <xref:System.ComponentModel.BrowsableAttribute>, but the browsable state for an attached property is particularly relevant to property information for Extensible Application Markup Language (XAML), because an attached property is primarily a XAML concept.  
   
  This .NET Framework attribute should only be applied on the get accessor of attached property definitions. Do not apply this .NET Framework attribute to the set accessor. Although intuitively it is the set operation that is being made browsable for XAML on relevant elements, it is the presence and characteristics of the get accessor on the property defining element that controls the true behavior.  
   
diff --git a/xml/System.Windows/Clipboard.xml b/xml/System.Windows/Clipboard.xml
index 9f333247bad..3fcd1604de5 100644
--- a/xml/System.Windows/Clipboard.xml
+++ b/xml/System.Windows/Clipboard.xml
@@ -31,13 +31,13 @@
   
 -   Copy can only be on user selected content.  
   
--   On copy or cut, partial trust code puts plaintext and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] on to the clipboard. Plaintext includes text, Unicode text, OEM (Object Exchange Model) text, and CSV (Comma-separated values).  
+-   On copy or cut, partial trust code puts plaintext and Extensible Application Markup Language (XAML) on to the clipboard. Plaintext includes text, Unicode text, OEM (Object Exchange Model) text, and CSV (Comma-separated values).  
   
--   On paste, Windows Presentation Foundation (WPF) will paste in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] if the source of that content is from a equally trusted or more trusted site. Specifically:  
+-   On paste, Windows Presentation Foundation (WPF) will paste in Extensible Application Markup Language (XAML) if the source of that content is from a equally trusted or more trusted site. Specifically:  
   
-    -   A partial trust application can paste [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] from a full trust application.  
+    -   A partial trust application can paste Extensible Application Markup Language (XAML) from a full trust application.  
   
-    -   A partial trust application can paste [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] from a partial trust application.  
+    -   A partial trust application can paste Extensible Application Markup Language (XAML) from a partial trust application.  
   
     -   A full trust application can paste XAML only from another fully trusted application.  
   
diff --git a/xml/System.Windows/CornerRadius.xml b/xml/System.Windows/CornerRadius.xml
index 564527bbe0f..013b683490c 100644
--- a/xml/System.Windows/CornerRadius.xml
+++ b/xml/System.Windows/CornerRadius.xml
@@ -71,7 +71,7 @@
    
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Controls.Border.CornerRadius%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Controls.Border.CornerRadius%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#1](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#1)]
  [!code-vb[ThicknessStruct#1](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#1)]
diff --git a/xml/System.Windows/DataFormats.xml b/xml/System.Windows/DataFormats.xml
index 9d260789789..68a43ae29b2 100644
--- a/xml/System.Windows/DataFormats.xml
+++ b/xml/System.Windows/DataFormats.xml
@@ -48,8 +48,8 @@
 |<xref:System.Windows.DataFormats.Tiff>|"TaggedImageFileFormat"|Specifies the Tagged Image File Format (TIFF) data format.|  
 |<xref:System.Windows.DataFormats.UnicodeText>|"UnicodeText"|Specifies the Unicode text data format.|  
 |<xref:System.Windows.DataFormats.WaveAudio>|"WaveAudio"|Specifies the wave audio data format.|  
-|<xref:System.Windows.DataFormats.Xaml>|"Xaml"|Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] data format.|  
-|<xref:System.Windows.DataFormats.XamlPackage>|"XamlPackage"|Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] package data format.|  
+|<xref:System.Windows.DataFormats.Xaml>|"Xaml"|Specifies the Extensible Application Markup Language (XAML) data format.|  
+|<xref:System.Windows.DataFormats.XamlPackage>|"XamlPackage"|Specifies the Extensible Application Markup Language (XAML) package data format.|  
   
  ]]></format>
     </remarks>
@@ -862,7 +862,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] data format.</summary>
+        <summary>Specifies the Extensible Application Markup Language (XAML) data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -895,7 +895,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Specifies the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] package data format.</summary>
+        <summary>Specifies the Extensible Application Markup Language (XAML) package data format.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows/DataTemplate.xml b/xml/System.Windows/DataTemplate.xml
index 5489ae57cbf..6c585999766 100644
--- a/xml/System.Windows/DataTemplate.xml
+++ b/xml/System.Windows/DataTemplate.xml
@@ -266,7 +266,7 @@
  If you are creating triggers within a data template, the setters of the triggers should be setting properties that are within the scope of the data template. Otherwise, it may be more suitable to create triggers using a style that targets the type that contains the data. For example, if you are binding a <xref:System.Windows.Controls.ListBox> control, the containers are <xref:System.Windows.Controls.ListBoxItem> objects. If you are using triggers to set properties that are not within the scope of the <xref:System.Windows.DataTemplate>, then it may be more suitable to create a <xref:System.Windows.Controls.ListBoxItem> style and create triggers within that style. For more information, see What Belongs in a DataTemplate? in the [Data Templating Overview](/dotnet/framework/wpf/data/data-templating-overview).  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_Triggers"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index bd49f8808ad..d7ac1b68337 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -1027,7 +1027,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by Extensible Application Markup Language (XAML). WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1085,7 +1085,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by Extensible Application Markup Language (XAML). WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
@@ -1134,7 +1134,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An attached property is a property concept defined by [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
+ An attached property is a property concept defined by Extensible Application Markup Language (XAML). WPF implements attached properties as dependency properties. Because the WPF attached properties are dependency properties, they can have metadata applied that can be used by the general property system for operations such as reporting layout characteristics. For more information, see [Attached Properties Overview](/dotnet/framework/wpf/advanced/attached-properties-overview).  
   
  For more information on dependency property registration, see <xref:System.Windows.DependencyProperty>.  
   
diff --git a/xml/System.Windows/EventSetter.xml b/xml/System.Windows/EventSetter.xml
index cb7562950cf..505accaf056 100644
--- a/xml/System.Windows/EventSetter.xml
+++ b/xml/System.Windows/EventSetter.xml
@@ -25,7 +25,7 @@
   
  You can only declare event setters for events that are routed events. You can declare event setters for routed events with a direct routing strategy, bubbling events, or tunneling events.  
   
- Instances of the <xref:System.Windows.EventSetter> class are usually created through [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], as an object element within a style defined through XAML. An <xref:System.Windows.EventSetter> might also be instantiated from code.  
+ Instances of the <xref:System.Windows.EventSetter> class are usually created through Extensible Application Markup Language (XAML), as an object element within a style defined through XAML. An <xref:System.Windows.EventSetter> might also be instantiated from code.  
   
  Event setters cannot be used in a style that is contained in a theme resource dictionary. This is because a theme resource dictionary at run time is often loose binary XAML (BAML) files, and does not have any scope defined where accompanying code-behind that defines the handlers can exist.  
   
diff --git a/xml/System.Windows/EventTrigger.xml b/xml/System.Windows/EventTrigger.xml
index a706fd4d3d5..42cb160347a 100644
--- a/xml/System.Windows/EventTrigger.xml
+++ b/xml/System.Windows/EventTrigger.xml
@@ -144,7 +144,7 @@
  Adding a <xref:System.Windows.TriggerAction> child to an <xref:System.Windows.EventTrigger> object implicitly adds it to the <xref:System.Windows.TriggerActionCollection> for the <xref:System.Windows.EventTrigger> object.  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_Actions"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows/FrameworkContentElement.xml b/xml/System.Windows/FrameworkContentElement.xml
index 1544568c750..d6a83baf45c 100644
--- a/xml/System.Windows/FrameworkContentElement.xml
+++ b/xml/System.Windows/FrameworkContentElement.xml
@@ -1327,7 +1327,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This event will be raised whenever the <xref:System.Windows.FrameworkContentElement.EndInit%2A> or <xref:System.Windows.FrameworkContentElement.OnInitialized%2A> methods are called. Calls to these methods could have been made by deliberate code, or by the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] loading process.  
+ This event will be raised whenever the <xref:System.Windows.FrameworkContentElement.EndInit%2A> or <xref:System.Windows.FrameworkContentElement.OnInitialized%2A> methods are called. Calls to these methods could have been made by deliberate code, or by the Extensible Application Markup Language (XAML) loading process.  
   
  ]]></format>
         </remarks>
@@ -1423,7 +1423,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value indicating whether this element has been initialized, either by being loaded as [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], or by explicitly having its <see cref="M:System.Windows.FrameworkContentElement.EndInit" /> method called.</summary>
+        <summary>Gets a value indicating whether this element has been initialized, either by being loaded as Extensible Application Markup Language (XAML), or by explicitly having its <see cref="M:System.Windows.FrameworkContentElement.EndInit" /> method called.</summary>
         <value>
           <see langword="true" /> if the element is initialized per the aforementioned loading or method calls; otherwise, <see langword="false" />.</value>
         <remarks>
@@ -2302,7 +2302,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Resource dictionaries that can be defined completely or partially in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] are typically created as a property element, and are typically on the root element for any individual page or for the application. Placing the resource dictionary at this level makes it easier to find from individual child elements in the page (or from any page, in the application case). In most application scenarios, we recommend that styles be defined as object elements within a resource dictionary, or be defined as external resources so that the entire style resource can be self-contained (this approach helps separate designer responsibilities from developer responsibilities by separating the physical files that need to be edited).  
+ Resource dictionaries that can be defined completely or partially in Extensible Application Markup Language (XAML) are typically created as a property element, and are typically on the root element for any individual page or for the application. Placing the resource dictionary at this level makes it easier to find from individual child elements in the page (or from any page, in the application case). In most application scenarios, we recommend that styles be defined as object elements within a resource dictionary, or be defined as external resources so that the entire style resource can be self-contained (this approach helps separate designer responsibilities from developer responsibilities by separating the physical files that need to be edited).  
   
  Note that this property returns only the resource dictionary declared directly within that element. This is different than the actual resource lookup process, where a child element can access any of the resources defined in each parent element, searching recursively upwards.  
   
diff --git a/xml/System.Windows/FrameworkElement.xml b/xml/System.Windows/FrameworkElement.xml
index 266cbe73225..70443386a61 100644
--- a/xml/System.Windows/FrameworkElement.xml
+++ b/xml/System.Windows/FrameworkElement.xml
@@ -77,7 +77,7 @@
   
  As can be seen from the class hierarchy, many WPF classes derive from <xref:System.Windows.FrameworkElement>, either directly or through intermediate base classes such as <xref:System.Windows.Controls.Panel> or <xref:System.Windows.Controls.Control>.  
   
- If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create user interface (UI) in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]. For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create XAML child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
+ If you intend to use <xref:System.Windows.FrameworkElement> as a base class, you might want to first examine the existing derived classes. <xref:System.Windows.FrameworkElement> provides support for a number of basic scenarios, but also lacks a number of features that are desirable for an "element" in the sense of a building block that you use to create user interface (UI) in Extensible Application Markup Language (XAML). For instance, a <xref:System.Windows.FrameworkElement> does not define any true content model; <xref:System.Windows.FrameworkElement> as a base class does not define a property that can create XAML child elements. In particular, you might want to look at <xref:System.Windows.Controls.Control> and <xref:System.Windows.Controls.ContentControl>.  
   
  ]]></format>
     </remarks>
@@ -2211,7 +2211,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This event will be raised whenever the <xref:System.Windows.FrameworkElement.EndInit%2A> or <xref:System.Windows.FrameworkElement.OnVisualParentChanged%2A> methods are called. Calls to either method could have come from application code, or through the [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] processor behavior when a XAML page is processed.  
+ This event will be raised whenever the <xref:System.Windows.FrameworkElement.EndInit%2A> or <xref:System.Windows.FrameworkElement.OnVisualParentChanged%2A> methods are called. Calls to either method could have come from application code, or through the Extensible Application Markup Language (XAML) processor behavior when a XAML page is processed.  
   
  Whether you choose to handle <xref:System.Windows.FrameworkElement.Loaded> or <xref:System.Windows.FrameworkElement.Initialized> depends on your requirements. If you do not need to read element properties, intend to reset properties, and do not need any layout information, <xref:System.Windows.FrameworkElement.Initialized> might be the better event to act upon. If you need all properties of the element to be available, and you will be setting properties that are likely to reset the layout, <xref:System.Windows.FrameworkElement.Loaded> might be the better event to act upon. Be careful of reentrancy if your handler resets any properties that are interpreted by the layout system to mean that a new layout pass is required. (You might need to check the <xref:System.Windows.FrameworkPropertyMetadata> values on the property if you are unsure of which properties can require a new layout pass if they are changed.)  
   
@@ -2693,10 +2693,10 @@
   
  The default unit for a <xref:System.Windows.Thickness> measure is device-independent unit (1/96th inch). You can also specify other units by appending the unit type strings `cm`, `in`, or `pt` to any measure.  
   
- Number values provided as XAML attributes need not specify decimal points (0 is acceptable, does not have to be provided as 0.0). For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
+ Number values provided as XAML attributes need not specify decimal points (0 is acceptable, does not have to be provided as 0.0). For more information on Extensible Application Markup Language (XAML) usage, see <xref:System.Windows.Thickness>.  
   
  *thicknessReference*  
- An object reference to an existing <xref:System.Windows.Thickness>. This might be a `}`, a , or `}` reference. For more information on [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] usage, see <xref:System.Windows.Thickness>.  
+ An object reference to an existing <xref:System.Windows.Thickness>. This might be a `}`, a , or `}` reference. For more information on Extensible Application Markup Language (XAML) usage, see <xref:System.Windows.Thickness>.  
   
 <a name="dependencyPropertyInfo_Margin"></a>   
 ## Dependency Property Information  
@@ -4206,7 +4206,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Resource dictionaries that can be defined completely or partially in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] are typically created as a property element, and are typically on the root element for any individual page or for the application. Placing the resource dictionary at this level makes it easier to find from individual child elements in the page (or from any page, in the application case). In most application scenarios, we recommend that styles be defined as object elements within a resource dictionary, or be defined as external resources so that the entire style resource can be self-contained (this approach helps separate designer responsibilities from developer responsibilities by separating the physical files that need to be edited).  
+ Resource dictionaries that can be defined completely or partially in Extensible Application Markup Language (XAML) are typically created as a property element, and are typically on the root element for any individual page or for the application. Placing the resource dictionary at this level makes it easier to find from individual child elements in the page (or from any page, in the application case). In most application scenarios, we recommend that styles be defined as object elements within a resource dictionary, or be defined as external resources so that the entire style resource can be self-contained (this approach helps separate designer responsibilities from developer responsibilities by separating the physical files that need to be edited).  
   
  Note that this property returns only the resource dictionary declared directly within that element. This is different than the actual resource lookup process, where a child element can access any of the resources defined in each parent element, searching recursively upwards.  
   
@@ -5214,7 +5214,7 @@
 ## Remarks  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] through the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write. The property only exists on root elements; attempting to find it or set it elsewhere will cause an exception to be thrown.  
+>  This property can only be set in Extensible Application Markup Language (XAML) through the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write. The property only exists on root elements; attempting to find it or set it elsewhere will cause an exception to be thrown.  
   
  This property does not enable you to examine triggers that exist as part of styles in use on this element. It only reports the collection of triggers that are literally added to the collection, either in markup or code. Elements do not typically have such elements existing by default (through a template for instance); it is more common for triggers that come from control compositing to be established in styles instead.  
   
diff --git a/xml/System.Windows/GridUnitType.xml b/xml/System.Windows/GridUnitType.xml
index 3ae5ca08060..4134a5bd617 100644
--- a/xml/System.Windows/GridUnitType.xml
+++ b/xml/System.Windows/GridUnitType.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  Star sizing is used to distribute available space by weighted proportions.  
   
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], star values are expressed as * or 2*. In the first case, the row or column would receive one times the available space; in the second case, the row or column would receive two times the available space, and so on.  
+ In Extensible Application Markup Language (XAML), star values are expressed as * or 2*. In the first case, the row or column would receive one times the available space; in the second case, the row or column would receive two times the available space, and so on.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/LengthConverter.xml b/xml/System.Windows/LengthConverter.xml
index e9ea715be73..d13f659d32f 100644
--- a/xml/System.Windows/LengthConverter.xml
+++ b/xml/System.Windows/LengthConverter.xml
@@ -24,7 +24,7 @@
  <xref:System.Windows.LengthConverter> supports conversion to and from the following types: <xref:System.String>, <xref:System.Decimal>, <xref:System.Single>, <xref:System.Double>, <xref:System.Int16>, <xref:System.Int32>, <xref:System.Int64>, <xref:System.UInt16>, <xref:System.UInt32>, and <xref:System.UInt64>.  
   
 ## Examples  
- The following example shows how to create and use an instance of the <xref:System.Windows.LengthConverter> object. A custom method called `ChangeLeft` is defined, which converts the content of a <xref:System.Windows.Controls.ListBoxItem> (defined in a separate [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] file) to an instance of <xref:System.Double>, and later into a <xref:System.String>. This method passes the <xref:System.Windows.Controls.ListBoxItem> to a <xref:System.Windows.LengthConverter> object, which converts the <xref:System.Windows.Controls.ListBoxItem> <xref:System.Windows.Controls.ContentControl.Content%2A> to an instance of <xref:System.Double>. Notice that this value has already been converted to a <xref:System.String> by using the <xref:System.Windows.Controls.Control.ToString%2A> method. This value is then passed back to the <xref:System.Windows.Controls.Canvas.SetLeft%2A> method and the <xref:System.Windows.Controls.Canvas.GetLeft%2A> method of the <xref:System.Windows.Controls.Canvas> in order to change the position of the `text1` object.  
+ The following example shows how to create and use an instance of the <xref:System.Windows.LengthConverter> object. A custom method called `ChangeLeft` is defined, which converts the content of a <xref:System.Windows.Controls.ListBoxItem> (defined in a separate Extensible Application Markup Language (XAML) file) to an instance of <xref:System.Double>, and later into a <xref:System.String>. This method passes the <xref:System.Windows.Controls.ListBoxItem> to a <xref:System.Windows.LengthConverter> object, which converts the <xref:System.Windows.Controls.ListBoxItem> <xref:System.Windows.Controls.ContentControl.Content%2A> to an instance of <xref:System.Double>. Notice that this value has already been converted to a <xref:System.String> by using the <xref:System.Windows.Controls.Control.ToString%2A> method. This value is then passed back to the <xref:System.Windows.Controls.Canvas.SetLeft%2A> method and the <xref:System.Windows.Controls.Canvas.GetLeft%2A> method of the <xref:System.Windows.Controls.Canvas> in order to change the position of the `text1` object.  
   
  [!code-csharp[CanvasPositioningProperties#2](~/samples/snippets/csharp/VS_Snippets_Wpf/CanvasPositioningProperties/CSharp/Window1.xaml.cs#2)]
  [!code-vb[CanvasPositioningProperties#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/CanvasPositioningProperties/VisualBasic/Window1.xaml.vb#2)]  
diff --git a/xml/System.Windows/Localization.xml b/xml/System.Windows/Localization.xml
index 73e7127aca9..5968a7e7e09 100644
--- a/xml/System.Windows/Localization.xml
+++ b/xml/System.Windows/Localization.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Markup authors may have specific requirements for elements in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] UI, such as constraints for text length, font family, or font size. Localizers need to know about them in order to provide consistent localization. Localization properties can be specified inside [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], allowing authors to communicate their localization needs to localizers. These properties provide rules and hints for localization, which can be used to modify the application. There are two types of localization properties:  
+ Markup authors may have specific requirements for elements in Extensible Application Markup Language (XAML) UI, such as constraints for text length, font family, or font size. Localizers need to know about them in order to provide consistent localization. Localization properties can be specified inside Extensible Application Markup Language (XAML), allowing authors to communicate their localization needs to localizers. These properties provide rules and hints for localization, which can be used to modify the application. There are two types of localization properties:  
   
 -   Localization attributes. The attributes specify which resources, such as <xref:System.Windows.Media.FontFamily>, are to be localized.  
   
diff --git a/xml/System.Windows/PresentationSource.xml b/xml/System.Windows/PresentationSource.xml
index b83cfd07a84..f9dc966e3dd 100644
--- a/xml/System.Windows/PresentationSource.xml
+++ b/xml/System.Windows/PresentationSource.xml
@@ -112,7 +112,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Despite what the syntax block for this event states, there is no legitimate [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] attached property usage. You should not attempt to add handlers in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], and handlers in code should only be placed on objects that serve as hosts for presentation (<xref:System.Windows.PresentationSource> ) content. Such handlers should only be attached during object initialization, and should be explicitly removed in a Dispose method or equivalent object cleanup.  
+ Despite what the syntax block for this event states, there is no legitimate Extensible Application Markup Language (XAML) attached property usage. You should not attempt to add handlers in Extensible Application Markup Language (XAML), and handlers in code should only be placed on objects that serve as hosts for presentation (<xref:System.Windows.PresentationSource> ) content. Such handlers should only be attached during object initialization, and should be explicitly removed in a Dispose method or equivalent object cleanup.  
   
  Even though this is a routed event, there are special restrictions placed on this event that differ from normal routed event behavior, due to the relatively small number of elements in a typical application scenario that would concern themselves with handling this event.  
   
diff --git a/xml/System.Windows/ResourceDictionary.xml b/xml/System.Windows/ResourceDictionary.xml
index acfa7314350..60245254b7e 100644
--- a/xml/System.Windows/ResourceDictionary.xml
+++ b/xml/System.Windows/ResourceDictionary.xml
@@ -61,7 +61,7 @@
   
  The <xref:System.Windows.ResourceDictionary> class is not derived from <xref:System.Collections.DictionaryBase>. Instead, the <xref:System.Windows.ResourceDictionary> class implements <xref:System.Collections.IDictionary> but relies on a <xref:System.Collections.Hashtable> internally.  
   
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], the <xref:System.Windows.ResourceDictionary> class is typically an implicit collection element that is the object element value of several `Resources` properties, when given in property element syntax. For details on implicit collections in XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). An exception is when you want to specify a merged dictionary; for details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
+ In Extensible Application Markup Language (XAML), the <xref:System.Windows.ResourceDictionary> class is typically an implicit collection element that is the object element value of several `Resources` properties, when given in property element syntax. For details on implicit collections in XAML, see [XAML Syntax In Detail](/dotnet/framework/wpf/advanced/xaml-syntax-in-detail). An exception is when you want to specify a merged dictionary; for details, see [Merged Resource Dictionaries](/dotnet/framework/wpf/advanced/merged-resource-dictionaries).  
   
  Another possible XAML usage is to declare a resource dictionary as a discrete XAML file, and either load it at run time with <xref:System.Windows.Markup.XamlReader.Load%2A> or include it in a (full-trust) project as a resource or loose file. In this case, <xref:System.Windows.ResourceDictionary> can be declared as an object element, serving as the root element of the XAML. You must map the appropriate XML namespace values (default for the WPF namespace and typically `x:` for the XAML namespace) onto the <xref:System.Windows.ResourceDictionary> element if you plan to use it as the root element. Then you can add child elements that define the resources, each with an [x:Key](/dotnet/framework/xaml-services/x-key-directive) value.  
   
diff --git a/xml/System.Windows/RoutedEventArgs.xml b/xml/System.Windows/RoutedEventArgs.xml
index 957b627c275..587f558440f 100644
--- a/xml/System.Windows/RoutedEventArgs.xml
+++ b/xml/System.Windows/RoutedEventArgs.xml
@@ -212,7 +212,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Marking the event handled will limit the visibility of the routed event to listeners along the event route. The event does still travel the remainder of the route, but only handlers specifically added with `HandledEventsToo` `true` in the <xref:System.Windows.UIElement.AddHandler%28System.Windows.RoutedEvent%2CSystem.Delegate%2CSystem.Boolean%29> method call will be invoked in response. Default handlers on instance listeners (such as those expressed in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)]) will not be invoked. Handling events that are marked handled is not a common scenario.  
+ Marking the event handled will limit the visibility of the routed event to listeners along the event route. The event does still travel the remainder of the route, but only handlers specifically added with `HandledEventsToo` `true` in the <xref:System.Windows.UIElement.AddHandler%28System.Windows.RoutedEvent%2CSystem.Delegate%2CSystem.Boolean%29> method call will be invoked in response. Default handlers on instance listeners (such as those expressed in Extensible Application Markup Language (XAML)) will not be invoked. Handling events that are marked handled is not a common scenario.  
   
  If you are a control author defining your own events, the decisions you make regarding event handling at the class level will impact users of your control as well as any users of derived controls, and potentially other elements that are either contained by your control or that contain your control. For more information, see [Marking Routed Events as Handled, and Class Handling](/dotnet/framework/wpf/advanced/marking-routed-events-as-handled-and-class-handling).  
   
diff --git a/xml/System.Windows/Thickness.xml b/xml/System.Windows/Thickness.xml
index 80f710f80d0..09b0abfe642 100644
--- a/xml/System.Windows/Thickness.xml
+++ b/xml/System.Windows/Thickness.xml
@@ -87,7 +87,7 @@
    
   
 ## Examples  
- The following example shows how to create an instance of a <xref:System.Windows.Thickness> structure and set its properties by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to create an instance of a <xref:System.Windows.Thickness> structure and set its properties by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#2)]
  [!code-vb[ThicknessStruct#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#2)]
@@ -212,7 +212,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Thickness.Bottom%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Thickness.Bottom%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#2)]
  [!code-vb[ThicknessStruct#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#2)]
@@ -362,7 +362,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Thickness.Left%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Thickness.Left%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#2)]
  [!code-vb[ThicknessStruct#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#2)]
@@ -480,7 +480,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Thickness.Right%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Thickness.Right%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#2)]
  [!code-vb[ThicknessStruct#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#2)]
@@ -524,7 +524,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- The following example shows how to set the value of the <xref:System.Windows.Thickness.Top%2A> property by using [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] and code.  
+ The following example shows how to set the value of the <xref:System.Windows.Thickness.Top%2A> property by using Extensible Application Markup Language (XAML) and code.  
   
  [!code-csharp[ThicknessStruct#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ThicknessStruct/CSharp/ThicknessSamp.cs#2)]
  [!code-vb[ThicknessStruct#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ThicknessStruct/VisualBasic/ThicknessSampVB.vb#2)]
diff --git a/xml/System.Windows/TriggerBase.xml b/xml/System.Windows/TriggerBase.xml
index 5cfdd7a0e45..71b4bc7b41f 100644
--- a/xml/System.Windows/TriggerBase.xml
+++ b/xml/System.Windows/TriggerBase.xml
@@ -85,7 +85,7 @@
  This property does not apply to the <xref:System.Windows.EventTrigger> class because an event represents a point in time while <xref:System.Windows.TriggerBase.EnterActions%2A> and <xref:System.Windows.TriggerBase.ExitActions%2A> correspond to object states. For <xref:System.Windows.EventTrigger> objects, use the <xref:System.Windows.EventTrigger.Actions%2A> property instead.  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_EnterActions"></a>   
 ## XAML Property Element Usage  
@@ -141,7 +141,7 @@
  This property does not apply to the <xref:System.Windows.EventTrigger> class because an event represents a point in time while <xref:System.Windows.TriggerBase.EnterActions%2A> and <xref:System.Windows.TriggerBase.ExitActions%2A> correspond to object states. For <xref:System.Windows.EventTrigger> objects, use the <xref:System.Windows.EventTrigger.Actions%2A> property instead.  
   
 > [!NOTE]
->  This property can only be set in [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
+>  This property can only be set in Extensible Application Markup Language (XAML) via the collection syntax shown, or by accessing the collection object and using its various methods such as Add. The property to access the collection object itself is read-only, the collection itself is read-write.  
   
 <a name="xamlPropertyElementUsage_ExitActions"></a>   
 ## XAML Property Element Usage  
diff --git a/xml/System.Windows/UIElement.xml b/xml/System.Windows/UIElement.xml
index 7c206f41cdd..31f7827a35e 100644
--- a/xml/System.Windows/UIElement.xml
+++ b/xml/System.Windows/UIElement.xml
@@ -9993,7 +9993,7 @@ Image with an Elliptical Clip Region
   
  The most typical <xref:System.Windows.Media.Brush> for this purpose is an <xref:System.Windows.Media.ImageBrush>, which can be used for a variety of photo masking techniques such as a vignette. But any defined <xref:System.Windows.Media.Brush> (such as <xref:System.Windows.Media.LinearGradientBrush>) can be used.  
   
- In [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)], this property value can use an inline syntax that is specific to each implementation of the <xref:System.Windows.Media.Brush> abstract class. For more information, see [Painting with Solid Colors and Gradients Overview](/dotnet/framework/wpf/graphics-multimedia/painting-with-solid-colors-and-gradients-overview).  
+ In Extensible Application Markup Language (XAML), this property value can use an inline syntax that is specific to each implementation of the <xref:System.Windows.Media.Brush> abstract class. For more information, see [Painting with Solid Colors and Gradients Overview](/dotnet/framework/wpf/graphics-multimedia/painting-with-solid-colors-and-gradients-overview).  
   
 <a name="dependencyPropertyInfo_OpacityMask"></a>   
 ## Dependency Property Information  
@@ -10097,7 +10097,7 @@ Image with an Elliptical Clip Region
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.UIElement.PersistId%2A> uniquely identifies each element. An element keeps the same <xref:System.Windows.UIElement.PersistId%2A> every time the same [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)] is loaded (including binary representations). This identifier is used for internal loading, parsing and serialization requirements. It is not intended to be used by your application code.  
+ <xref:System.Windows.UIElement.PersistId%2A> uniquely identifies each element. An element keeps the same <xref:System.Windows.UIElement.PersistId%2A> every time the same Extensible Application Markup Language (XAML) is loaded (including binary representations). This identifier is used for internal loading, parsing and serialization requirements. It is not intended to be used by your application code.  
   
  This property has no relationship to the <xref:System.Object.GetHashCode%2A> result for any given instance.  
   
diff --git a/xml/System.Windows/VerticalAlignment.xml b/xml/System.Windows/VerticalAlignment.xml
index a23bc96a044..9e6597934fd 100644
--- a/xml/System.Windows/VerticalAlignment.xml
+++ b/xml/System.Windows/VerticalAlignment.xml
@@ -31,7 +31,7 @@
    
   
 ## Examples  
- The following example demonstrates how to use the <xref:System.Windows.VerticalAlignment> enumeration in code and [!INCLUDE[TLA#tla_xaml](~/includes/tlasharptla-xaml-md.md)].  
+ The following example demonstrates how to use the <xref:System.Windows.VerticalAlignment> enumeration in code and Extensible Application Markup Language (XAML).  
   
  [!code-csharp[mpalayoutverticalalignment#2](~/samples/snippets/csharp/VS_Snippets_Wpf/MPALayoutVerticalAlignment/CSharp/MPA_Layout_VerticalAlignment.cs#2)]
  [!code-vb[mpalayoutverticalalignment#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/MPALayoutVerticalAlignment/VisualBasic/MPA_Layout_VerticalAlignment.vb#2)]

From 1cee47518933caa7b40e5b048117eadab9b9ba54 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:15:19 -0800
Subject: [PATCH 177/236] tlasharptla-xbap

---
 .../MarkupCompilePass1.xml                           |  4 ++--
 xml/System.Windows.Controls/Page.xml                 |  8 ++++----
 xml/System.Windows.Interop/BrowserInteropHelper.xml  | 12 ++++++------
 xml/System.Windows.Markup/XamlReader.xml             |  2 +-
 xml/System.Windows/Application.xml                   |  8 ++++----
 5 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
index 6cd5cb512a7..f090151e4d2 100644
--- a/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
+++ b/xml/Microsoft.Build.Tasks.Windows/MarkupCompilePass1.xml
@@ -532,9 +532,9 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the generated assembly is a [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)].</summary>
+        <summary>Gets or sets a value that indicates whether the generated assembly is a XAML browser application (XBAP).</summary>
         <value>
-          <see langword="true" /> if the generated assembly is a [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]; otherwise, <see langword="false" />.</value>
+          <see langword="true" /> if the generated assembly is a XAML browser application (XBAP); otherwise, <see langword="false" />.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/System.Windows.Controls/Page.xml b/xml/System.Windows.Controls/Page.xml
index 7d269b70d85..c146b4fc0fc 100644
--- a/xml/System.Windows.Controls/Page.xml
+++ b/xml/System.Windows.Controls/Page.xml
@@ -573,7 +573,7 @@
 -   When a page has a lot of content, it may take a long time to instantiate. If the page is not kept alive, and the page is frequently navigated to, the cost of constantly instantiating the page may have a negative impact on the user experience. However, from a performance perspective, you should rely on the default settings and profile your application's performance; if testing identifies pages with load times that fall below the range required for your application, configuring the pages to be kept alive may be one way to solve the problem.  
   
 > [!NOTE]
->  Entries for pages that are kept alive are not retained in navigation history of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] if a user navigates away from and back to the [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]. Only journal entries for pages that are not kept alive are retained in navigation history.  
+>  Entries for pages that are kept alive are not retained in navigation history of an XAML browser application (XBAP) if a user navigates away from and back to the XAML browser application (XBAP). Only journal entries for pages that are not kept alive are retained in navigation history.  
   
 <a name="dependencyPropertyInfo_PageKeepAlive"></a>   
 ## Dependency Property Information  
@@ -1303,7 +1303,7 @@
   
  If a <xref:System.Windows.Controls.Page> is hosted by a <xref:System.Windows.Controls.Frame>, setting <xref:System.Windows.Controls.Page.WindowHeight%2A> has no effect, but you can still get the value of <xref:System.Windows.Controls.Page.WindowHeight%2A>.  
   
- A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowHeight%2A> to change the height of Windows Internet Explorer; the height cannot be changed by setting <xref:System.Windows.FrameworkElement.Height%2A>, <xref:System.Windows.FrameworkElement.MinHeight%2A>, or <xref:System.Windows.FrameworkElement.MaxHeight%2A>.  
+ A <xref:System.Windows.Controls.Page> in an XAML browser application (XBAP) can only use <xref:System.Windows.Controls.Page.WindowHeight%2A> to change the height of Windows Internet Explorer; the height cannot be changed by setting <xref:System.Windows.FrameworkElement.Height%2A>, <xref:System.Windows.FrameworkElement.MinHeight%2A>, or <xref:System.Windows.FrameworkElement.MaxHeight%2A>.  
   
  The minimum height of the Windows Internet Explorer window is 150 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowHeight%2A> may not be applied if it would cause the total height of the Windows Internet Explorer window to be less than 150 pixels.  
   
@@ -1348,7 +1348,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and Windows Internet Explorer, is the name of the file that is currently being hosted (with an .xaml extension if the page is loose Extensible Application Markup Language (XAML), or an .xbap extension if the page is part of an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).  
+ By default, the title of a window that hosts a page, including <xref:System.Windows.Navigation.NavigationWindow> and Windows Internet Explorer, is the name of the file that is currently being hosted (with an .xaml extension if the page is loose Extensible Application Markup Language (XAML), or an .xbap extension if the page is part of an XAML browser application (XBAP)).  
   
  A page can change the default by setting its <xref:System.Windows.Controls.Page.WindowTitle%2A> property.  
   
@@ -1414,7 +1414,7 @@
   
  If a <xref:System.Windows.Controls.Page> is hosted by a <xref:System.Windows.Controls.Frame>, setting <xref:System.Windows.Controls.Page.WindowWidth%2A> has no effect, but you can still get the value of <xref:System.Windows.Controls.Page.WindowWidth%2A>.  
   
- A <xref:System.Windows.Controls.Page> in an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] can only use <xref:System.Windows.Controls.Page.WindowWidth%2A> to change the width of Windows Internet Explorer; the width cannot be changed by setting <xref:System.Windows.FrameworkElement.Width%2A>, <xref:System.Windows.FrameworkElement.MinWidth%2A>, or <xref:System.Windows.FrameworkElement.MaxWidth%2A>.  
+ A <xref:System.Windows.Controls.Page> in an XAML browser application (XBAP) can only use <xref:System.Windows.Controls.Page.WindowWidth%2A> to change the width of Windows Internet Explorer; the width cannot be changed by setting <xref:System.Windows.FrameworkElement.Width%2A>, <xref:System.Windows.FrameworkElement.MinWidth%2A>, or <xref:System.Windows.FrameworkElement.MaxWidth%2A>.  
   
  The minimum width of the Windows Internet Explorer window is 250 pixels. For browser-hosted pages, this means that the value of <xref:System.Windows.Controls.Page.WindowWidth%2A> may not be applied if it would cause the total width of the Windows Internet Explorer window to be less than 250 pixels.  
   
diff --git a/xml/System.Windows.Interop/BrowserInteropHelper.xml b/xml/System.Windows.Interop/BrowserInteropHelper.xml
index 987a988e724..d0957651c30 100644
--- a/xml/System.Windows.Interop/BrowserInteropHelper.xml
+++ b/xml/System.Windows.Interop/BrowserInteropHelper.xml
@@ -77,8 +77,8 @@
         <ReturnType>System.Object</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a script object that provides access to the HTML window object, custom script functions, and global variables for the HTML page, if the [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] is hosted in a frame.</summary>
-        <value>A script object that provides access to the HTML window object, custom script functions, and global variables for the HTML page, if the [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] is hosted in a frame; otherwise, <see langword="null" />.</value>
+        <summary>Gets a script object that provides access to the HTML window object, custom script functions, and global variables for the HTML page, if the XAML browser application (XBAP) is hosted in a frame.</summary>
+        <value>A script object that provides access to the HTML window object, custom script functions, and global variables for the HTML page, if the XAML browser application (XBAP) is hosted in a frame; otherwise, <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -129,7 +129,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Controls.Page> can be host agnostic and, consequently, can be loaded into several different types of hosts, including a <xref:System.Windows.Controls.Frame>, a <xref:System.Windows.Navigation.NavigationWindow>, or a browser. This can happen when you have a library assembly that contains one or more pages, and which is referenced by multiple standalone and browsable ([!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]) host applications.  
+ A <xref:System.Windows.Controls.Page> can be host agnostic and, consequently, can be loaded into several different types of hosts, including a <xref:System.Windows.Controls.Frame>, a <xref:System.Windows.Navigation.NavigationWindow>, or a browser. This can happen when you have a library assembly that contains one or more pages, and which is referenced by multiple standalone and browsable (XAML browser application (XBAP)) host applications.  
   
    
   
@@ -161,13 +161,13 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the uniform resource identifier (URI) for the location from which a [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] application was launched.</summary>
-        <value>The <see cref="T:System.Uri" /> for the location from which a [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] application was launched; otherwise, <see langword="null" />.</value>
+        <summary>Gets the uniform resource identifier (URI) for the location from which a XAML browser application (XBAP) application was launched.</summary>
+        <value>The <see cref="T:System.Uri" /> for the location from which a XAML browser application (XBAP) application was launched; otherwise, <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Interop.BrowserInteropHelper.Source%2A> property contains only a <xref:System.Uri> for [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] applications. For an example of the <xref:System.Windows.Interop.BrowserInteropHelper.Source%2A> property, see <xref:System.Windows.Interop.BrowserInteropHelper.IsBrowserHosted%2A>.  
+ The <xref:System.Windows.Interop.BrowserInteropHelper.Source%2A> property contains only a <xref:System.Uri> for XAML browser application (XBAP) applications. For an example of the <xref:System.Windows.Interop.BrowserInteropHelper.Source%2A> property, see <xref:System.Windows.Interop.BrowserInteropHelper.IsBrowserHosted%2A>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Markup/XamlReader.xml b/xml/System.Windows.Markup/XamlReader.xml
index 93e5e0b090c..257513cd284 100644
--- a/xml/System.Windows.Markup/XamlReader.xml
+++ b/xml/System.Windows.Markup/XamlReader.xml
@@ -41,7 +41,7 @@
 ## Code Access Security, Loose XAML, and XamlReader  
  XAML is a markup language that directly represents object instantiation and execution. Therefore, elements created in XAML have the same ability to interact with system resources (network access, file system IO, for example) as the equivalent generated code does.  
   
- WPF supports the .NET security framework Code Access Security (CAS). This means that WPF content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)] are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
+ WPF supports the .NET security framework Code Access Security (CAS). This means that WPF content running in the internet zone has reduced execution permissions. "Loose XAML" (pages of noncompiled XAML interpreted at load time by a XAML viewer) and XAML browser application (XBAP) are usually run in this internet zone and use the same permission set.  However, XAML loaded in to a fully trusted application has the same access to the system resources as the hosting application does. For more information, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
   
  The implications of these statements for <xref:System.Windows.Markup.XamlReader> is that your application design must make trust decisions about the XAML you decide to load. If you are loading XAML that is not trusted, consider implementing your own sandboxing technique for how you load the resulting object graph.  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 9e86b8ec4db..cc2854cfce6 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -352,7 +352,7 @@
   
  If your application handles the <xref:System.Windows.Application.SessionEnding> event and subsequently cancels it, <xref:System.Windows.Application.Exit> is not raised and the application continues running in accordance with the shutdown mode.  
   
- The exit code can be set from an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)], although the value is ignored.  
+ The exit code can be set from an XAML browser application (XBAP), although the value is ignored.  
   
  For XBAPs, <xref:System.Windows.Application.Exit> is raised in the following circumstances:  
   
@@ -1781,7 +1781,7 @@ This example illustrates how to use XAML together with application-scope resourc
  ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">
-          <see cref="M:System.Windows.Application.Run" /> is called from a browser-hosted application (for example, an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).</exception>
+          <see cref="M:System.Windows.Application.Run" /> is called from a browser-hosted application (for example, an XAML browser application (XBAP)).</exception>
         <altmember cref="M:System.Windows.Application.Run(System.Windows.Window)" />
         <altmember cref="M:System.Windows.Application.Shutdown(System.Int32)" />
         <altmember cref="E:System.Windows.Application.Exit" />
@@ -1842,7 +1842,7 @@ This example illustrates how to use XAML together with application-scope resourc
  ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">
-          <see cref="M:System.Windows.Application.Run" /> is called from a browser-hosted application (for example, an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)]).</exception>
+          <see cref="M:System.Windows.Application.Run" /> is called from a browser-hosted application (for example, an XAML browser application (XBAP)).</exception>
         <altmember cref="M:System.Windows.Application.Shutdown" />
         <altmember cref="M:System.Windows.Application.Shutdown(System.Int32)" />
       </Docs>
@@ -2159,7 +2159,7 @@ This example illustrates how to use XAML together with application-scope resourc
 > [!NOTE]
 >  If your application uses <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> to specify a credential policy, you need to set <xref:System.Net.AuthenticationManager.CredentialPolicy%2A> after <xref:System.Windows.Application.Startup> is raised; otherwise, WPF sets it to a default internal policy directly after the <xref:System.Windows.Application.Startup> event has been raised.  
   
- The command-line arguments that are passed to the <xref:System.Windows.Application.Startup> event handler are not the same as the URL query string parameters that are passed to an [!INCLUDE[TLA#tla_xbap](~/includes/tlasharptla-xbap-md.md)].  
+ The command-line arguments that are passed to the <xref:System.Windows.Application.Startup> event handler are not the same as the URL query string parameters that are passed to an XAML browser application (XBAP).  
   
    
   

From fe1f2ab91497ecbb301ac451f6589b48bd89d751 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:15:51 -0800
Subject: [PATCH 178/236] tlasharptla-xbapsharpplural

---
 xml/System.Windows/Application.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index cc2854cfce6..9be60960aa3 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -46,7 +46,7 @@
  You can implement an <xref:System.Windows.Application> using markup, markup and code-behind, or code. If <xref:System.Windows.Application> is implemented with markup, whether markup or markup and code-behind, the markup file must be configured as an Microsoft build engine (MSBuild) `ApplicationDefinition` item.  
   
 > [!NOTE]
->  A standalone application does not require an <xref:System.Windows.Application> object; it is possible to implement a custom `static` entry point method (`Main`) that opens a window without creating an instance of <xref:System.Windows.Application>. However, [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)] require an <xref:System.Windows.Application> object.  
+>  A standalone application does not require an <xref:System.Windows.Application> object; it is possible to implement a custom `static` entry point method (`Main`) that opens a window without creating an instance of <xref:System.Windows.Application>. However, XAML browser applications (XBAPs) require an <xref:System.Windows.Application> object.  
   
    
   
@@ -146,7 +146,7 @@
   
  Once an application becomes active, <xref:System.Windows.Application.Activated> will not be raised again until the application is deactivated, irrespective of how many windows within an application are activated while the application is active.  
   
- <xref:System.Windows.Application.Activated> is not raised for [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)].  
+ <xref:System.Windows.Application.Activated> is not raised for XAML browser applications (XBAPs).  
   
    
   
@@ -236,7 +236,7 @@
   
  After an application is first activated, it may be deactivated and reactivated many times during its lifetime. If an application's behavior or state depends on its activation state, it can handle both <xref:System.Windows.Application.Deactivated> and <xref:System.Windows.Application.Activated> events to determine which state it's in.  
   
- <xref:System.Windows.Application.Deactivated> is not raised for [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)].  
+ <xref:System.Windows.Application.Deactivated> is not raised for XAML browser applications (XBAPs).  
   
    
   
@@ -877,7 +877,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.InvalidOperationException">
-          <see cref="P:System.Windows.Application.MainWindow" /> is set from an application that's hosted in a browser, such as an [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)].</exception>
+          <see cref="P:System.Windows.Application.MainWindow" /> is set from an application that's hosted in a browser, such as an XAML browser applications (XBAPs).</exception>
         <altmember cref="E:System.Windows.Application.Exit" />
       </Docs>
     </Member>
@@ -2171,7 +2171,7 @@ This example illustrates how to use XAML together with application-scope resourc
  [!code-csharp[ApplicationStartupSnippets#HandleStartupCODEBEHIND](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationStartupSnippets/CSharp/App.xaml.cs#handlestartupcodebehind)]
  [!code-vb[ApplicationStartupSnippets#HandleStartupCODEBEHIND](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationStartupSnippets/visualbasic/application.xaml.vb#handlestartupcodebehind)]  
   
- [!INCLUDE[TLA#tla_xbap#plural](~/includes/tlasharptla-xbapsharpplural-md.md)] cannot retrieve and process command-line arguments because they are launched with ClickOnce deployment (see [Deploying a WPF Application (WPF)](/dotnet/framework/wpf/app-development/deploying-a-wpf-application-wpf)). However, they can retrieve and process query string parameters from the URLs that are used to launch them.  
+ XAML browser applications (XBAPs) cannot retrieve and process command-line arguments because they are launched with ClickOnce deployment (see [Deploying a WPF Application (WPF)](/dotnet/framework/wpf/app-development/deploying-a-wpf-application-wpf)). However, they can retrieve and process query string parameters from the URLs that are used to launch them.  
   
  ]]></format>
         </remarks>

From a6b16b243deb8bcf5509b51dca4c32a15941b238 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:16:12 -0800
Subject: [PATCH 179/236] tlasharptla-xl

---
 xml/System.Windows.Automation/MultipleViewPattern.xml | 2 +-
 xml/System.Windows.Automation/TextPattern.xml         | 4 ++--
 xml/System.Windows/Application.xml                    | 2 +-
 3 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.Windows.Automation/MultipleViewPattern.xml b/xml/System.Windows.Automation/MultipleViewPattern.xml
index 95ff7d84e7e..4f7885bd72e 100644
--- a/xml/System.Windows.Automation/MultipleViewPattern.xml
+++ b/xml/System.Windows.Automation/MultipleViewPattern.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] charts (pie, line, bar, cell value with a formula), Microsoft Word documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and Microsoft Windows Media Player skins. The supported views are determined by the control developer and are specific to each control.  
+ Examples of controls that can present multiple views include the list view (which can show its contents as thumbnails, tiles, icons, or details), Microsoft Excel charts (pie, line, bar, cell value with a formula), Microsoft Word documents (normal, Web layout, print layout, reading layout, outline), Microsoft Outlook calendar (year, month, week, day) and Microsoft Windows Media Player skins. The supported views are determined by the control developer and are specific to each control.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Automation/TextPattern.xml b/xml/System.Windows.Automation/TextPattern.xml
index c1c660962f6..44809412ae9 100644
--- a/xml/System.Windows.Automation/TextPattern.xml
+++ b/xml/System.Windows.Automation/TextPattern.xml
@@ -1457,7 +1457,7 @@
       </Parameters>
       <Docs>
         <param name="childElement">The enclosed object.</param>
-        <summary>Retrieves a text range enclosing a child element such as an image, hyperlink, [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] spreadsheet, or other embedded object.</summary>
+        <summary>Retrieves a text range enclosing a child element such as an image, hyperlink, Microsoft Excel spreadsheet, or other embedded object.</summary>
         <returns>A range that spans the child element.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1510,7 +1510,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A text range that wraps a child object is returned if the screen coordinates are within the coordinates of an image, hyperlink, [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)] spreadsheet, or other embedded object.  
+ A text range that wraps a child object is returned if the screen coordinates are within the coordinates of an image, hyperlink, Microsoft Excel spreadsheet, or other embedded object.  
   
  Because hidden text is not ignored by <xref:System.Windows.Automation.TextPattern.RangeFromPoint%2A>, a degenerate range from the visible text closest to the given point is returned.  
   
diff --git a/xml/System.Windows/Application.xml b/xml/System.Windows/Application.xml
index 9be60960aa3..88a75beb87e 100644
--- a/xml/System.Windows/Application.xml
+++ b/xml/System.Windows/Application.xml
@@ -2348,7 +2348,7 @@ This example illustrates how to use XAML together with application-scope resourc
    
   
 ## Examples  
- The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to multiple-document interface (MDI) applications like [!INCLUDE[TLA#tla_xl](~/includes/tlasharptla-xl-md.md)], or multiple-instance Single Document Interface (SDI) applications like Microsoft Word.  
+ The following example demonstrates how to enumerate the <xref:System.Windows.Application.Windows%2A> property to build a top-level Windows menu, which is common to multiple-document interface (MDI) applications like Microsoft Excel, or multiple-instance Single Document Interface (SDI) applications like Microsoft Word.  
   
  [!code-csharp[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/csharp/VS_Snippets_Wpf/ApplicationWindowsSnippets/CSharp/WindowMenuItem.cs#windowmenuitemcode)]
  [!code-vb[ApplicationWindowsSnippets#WindowMenuItemCODE](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ApplicationWindowsSnippets/visualbasic/windowmenuitem.vb#windowmenuitemcode)]  

From 09e2c1f9ce556b9ca826491c7bb794f709a72159 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:16:41 -0800
Subject: [PATCH 180/236] tlasharptla-xml

---
 xml/System.ComponentModel/SortDescription.xml          |  2 +-
 .../PackageDigitalSignatureManager.xml                 |  8 ++++----
 xml/System.Windows.Controls/ItemCollection.xml         |  2 +-
 xml/System.Windows.Data/Binding.xml                    | 10 +++++-----
 xml/System.Windows.Data/CompositeCollection.xml        |  2 +-
 xml/System.Windows.Data/XmlDataProvider.xml            |  8 ++++----
 .../BasePackagingPolicy.xml                            |  4 ++--
 .../XpsPackagingPolicy.xml                             | 10 +++++-----
 xml/System.Windows/DataTemplate.xml                    |  4 ++--
 xml/System.Windows/LocalizabilityAttribute.xml         |  2 +-
 xml/System.Windows/LocalizationCategory.xml            |  2 +-
 11 files changed, 27 insertions(+), 27 deletions(-)

diff --git a/xml/System.ComponentModel/SortDescription.xml b/xml/System.ComponentModel/SortDescription.xml
index e3d1ec88d85..ca17249b619 100644
--- a/xml/System.ComponentModel/SortDescription.xml
+++ b/xml/System.ComponentModel/SortDescription.xml
@@ -253,7 +253,7 @@
 ## Remarks  
  This property should be a public property of the items in the underlying collection.  
   
- The string is interpreted by the particular <xref:System.ComponentModel.ICollectionView> object involved in the sorting. <xref:System.Windows.Data.BindingListCollectionView> only supports simple column names. <xref:System.Windows.Data.ListCollectionView> supports general property paths and `XPath` for [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data. Therefore, when the view is a <xref:System.Windows.Data.ListCollectionView> object, you can sort XML nodes in an <xref:System.Windows.Data.XmlDataProvider> based on an attribute of those nodes. For example, if the attribute name is `Cost`, you would specify "@Cost" for the <xref:System.ComponentModel.SortDescription.PropertyName%2A> in the <xref:System.ComponentModel.SortDescription>.  
+ The string is interpreted by the particular <xref:System.ComponentModel.ICollectionView> object involved in the sorting. <xref:System.Windows.Data.BindingListCollectionView> only supports simple column names. <xref:System.Windows.Data.ListCollectionView> supports general property paths and `XPath` for XML data. Therefore, when the view is a <xref:System.Windows.Data.ListCollectionView> object, you can sort XML nodes in an <xref:System.Windows.Data.XmlDataProvider> based on an attribute of those nodes. For example, if the attribute name is `Cost`, you would specify "@Cost" for the <xref:System.ComponentModel.SortDescription.PropertyName%2A> in the <xref:System.ComponentModel.SortDescription>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
index 54480950a9e..8b5068a970b 100644
--- a/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
+++ b/xml/System.IO.Packaging/PackageDigitalSignatureManager.xml
@@ -793,14 +793,14 @@
   
  This <xref:System.IO.Packaging.PackageDigitalSignatureManager.Sign%2A> method ignores the <xref:System.Security.Cryptography.Xml.Reference.DigestMethod%2A> property associated with each <xref:System.Security.Cryptography.Xml.Reference> defined in `objectReferences`.  
   
- This <xref:System.IO.Packaging.PackageDigitalSignatureManager.Sign%2A> overload provides support for generation of [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] signatures that require custom `Object` tags.  For any provided `Object` tag to be signed, a corresponding `Reference` tag must be provided with a uniform resource identifier (URI) that specifies the `Object` tag in local fragment syntax.  For example if the `Object` tag has an ID of "myObject", the URI in the `Reference` tag would be "#myObject".  For unsigned objects, no `Reference` is required.  
+ This <xref:System.IO.Packaging.PackageDigitalSignatureManager.Sign%2A> overload provides support for generation of XML signatures that require custom `Object` tags.  For any provided `Object` tag to be signed, a corresponding `Reference` tag must be provided with a uniform resource identifier (URI) that specifies the `Object` tag in local fragment syntax.  For example if the `Object` tag has an ID of "myObject", the URI in the `Reference` tag would be "#myObject".  For unsigned objects, no `Reference` is required.  
   
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">Neither <paramref name="parts" />, <paramref name="relationshipSelectors" />, <paramref name="signatureObjects" />, nor <paramref name="objectReferences" /> specify any elements to sign.</exception>
         <exception cref="T:System.InvalidOperationException">A <see cref="P:System.IO.Packaging.PackagePart.ContentType" /> of a part being signed references an empty, <see langword="null" />, or undefined <see cref="P:System.IO.Packaging.PackageDigitalSignatureManager.TransformMapping" />.</exception>
         <exception cref="T:System.Xml.XmlException">
-          <paramref name="signatureId" /> is not <see langword="null" /> and is not a valid [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] schema ID (for example, begins with a leading numeric digit).</exception>
+          <paramref name="signatureId" /> is not <see langword="null" /> and is not a valid XML schema ID (for example, begins with a leading numeric digit).</exception>
         <related type="ExternalDocumentation" href="https://go.microsoft.com/fwlink/?LinkId=74494">Digital Signing Framework of the Open Packaging Conventions</related>
       </Docs>
     </Member>
@@ -974,8 +974,8 @@
         <ReturnType>System.Collections.Generic.Dictionary&lt;System.String,System.String&gt;</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a dictionary that contains each defined <see cref="P:System.IO.Packaging.PackagePart.ContentType" /> and its associated [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] <see cref="T:System.Security.Cryptography.Xml.Transform" />.<see cref="P:System.Security.Cryptography.Xml.Transform.Algorithm" /> identifier.</summary>
-        <value>A dictionary that contains each defined <see cref="P:System.IO.Packaging.PackagePart.ContentType" /> and its associated [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] <see cref="T:System.Security.Cryptography.Xml.Transform" />.<see cref="P:System.Security.Cryptography.Xml.Transform.Algorithm" /> identifier.</value>
+        <summary>Gets a dictionary that contains each defined <see cref="P:System.IO.Packaging.PackagePart.ContentType" /> and its associated XML <see cref="T:System.Security.Cryptography.Xml.Transform" />.<see cref="P:System.Security.Cryptography.Xml.Transform.Algorithm" /> identifier.</summary>
+        <value>A dictionary that contains each defined <see cref="P:System.IO.Packaging.PackagePart.ContentType" /> and its associated XML <see cref="T:System.Security.Cryptography.Xml.Transform" />.<see cref="P:System.Security.Cryptography.Xml.Transform.Algorithm" /> identifier.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Controls/ItemCollection.xml b/xml/System.Windows.Controls/ItemCollection.xml
index 1540e327bca..02c546b8721 100644
--- a/xml/System.Windows.Controls/ItemCollection.xml
+++ b/xml/System.Windows.Controls/ItemCollection.xml
@@ -63,7 +63,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Controls.ItemCollection> maintains a collection of items such as strings, objects, [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] nodes, elements, and other collections. An <xref:System.Windows.Controls.ItemsControl> uses the data in the <xref:System.Windows.Controls.ItemCollection> to generate its content. If you want to aggregate more than one collection, assign a <xref:System.Windows.Data.CompositeCollection> to the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property of your <xref:System.Windows.Controls.ItemsControl>.  
+ <xref:System.Windows.Controls.ItemCollection> maintains a collection of items such as strings, objects, XML nodes, elements, and other collections. An <xref:System.Windows.Controls.ItemsControl> uses the data in the <xref:System.Windows.Controls.ItemCollection> to generate its content. If you want to aggregate more than one collection, assign a <xref:System.Windows.Data.CompositeCollection> to the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property of your <xref:System.Windows.Controls.ItemsControl>.  
   
  Use either the <xref:System.Windows.Controls.ItemsControl.Items%2A> property or the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property to specify the collection that should be used to generate the content of your <xref:System.Windows.Controls.ItemsControl>. When the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property is set, the <xref:System.Windows.Controls.ItemsControl.Items%2A> collection will be made read-only and fixed-size. This means that if you are using the <xref:System.Windows.Controls.ItemsControl.ItemsSource%2A> property, you cannot add, delete, or change items in the <xref:System.Windows.Controls.ItemCollection> directly.  
   
diff --git a/xml/System.Windows.Data/Binding.xml b/xml/System.Windows.Data/Binding.xml
index 5b52af220bb..0cef1147b2d 100644
--- a/xml/System.Windows.Data/Binding.xml
+++ b/xml/System.Windows.Data/Binding.xml
@@ -494,7 +494,7 @@
       </Parameters>
       <Docs>
         <param name="target">The object from which to get namespace information.</param>
-        <summary>Returns an [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] namespace manager object used by the binding attached to the specified object.</summary>
+        <summary>Returns an XML namespace manager object used by the binding attached to the specified object.</summary>
         <returns>A returned object used for viewing XML namespaces that relate to the binding on the passed object element. This object should be cast as <see cref="T:System.Xml.XmlNamespaceManager" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -780,7 +780,7 @@
   
  For information about path syntax, see [Binding Declarations Overview](/dotnet/framework/wpf/data/binding-declarations-overview) or [PropertyPath XAML Syntax](/dotnet/framework/wpf/advanced/propertypath-xaml-syntax).  
   
- For [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] bindings, see the <xref:System.Windows.Data.Binding.XPath%2A> property.  
+ For XML bindings, see the <xref:System.Windows.Data.Binding.XPath%2A> property.  
   
  To bind to an entire object, you do not need to specify the <xref:System.Windows.Data.Binding.Path%2A> property. For more information, see "Specifying the Path to the Value" in [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
@@ -1561,7 +1561,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This attached property uses property value inheritance, which reproduces the behavior of namespace inheritance that is present in [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)]. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
+ This attached property uses property value inheritance, which reproduces the behavior of namespace inheritance that is present in XML. For details, see [Property Value Inheritance](/dotnet/framework/wpf/advanced/property-value-inheritance).  
   
 <a name="dependencyPropertyInfo_XmlNamespaceManager"></a>   
 ## Dependency Property Information  
@@ -1625,13 +1625,13 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets an <see langword="XPath" /> query that returns the value on the [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] binding source to use.</summary>
+        <summary>Gets or sets an <see langword="XPath" /> query that returns the value on the XML binding source to use.</summary>
         <value>The <see langword="XPath" /> query. The default is <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When the binding source is [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data instead of a common language runtime (CLR) object, the <xref:System.Windows.Data.Binding.XPath%2A> property is used instead of the <xref:System.Windows.Data.Binding.Path%2A> property to indicate the path to the value on the binding source to use.  
+ When the binding source is XML data instead of a common language runtime (CLR) object, the <xref:System.Windows.Data.Binding.XPath%2A> property is used instead of the <xref:System.Windows.Data.Binding.Path%2A> property to indicate the path to the value on the binding source to use.  
   
  By setting the <xref:System.Windows.Data.Binding.XPath%2A> property, you are creating an `XPath` query to select a node or a collection of nodes (<xref:System.Xml.XmlElement?displayProperty=nameWithType> and <xref:System.Xml.XmlAttribute?displayProperty=nameWithType> both derive from <xref:System.Xml.XmlNode?displayProperty=nameWithType>). <xref:System.Xml.XmlNode?displayProperty=nameWithType> is a common language runtime (CLR) object, which means you can bind to its properties using the <xref:System.Windows.Data.Binding.Path%2A> property.  
   
diff --git a/xml/System.Windows.Data/CompositeCollection.xml b/xml/System.Windows.Data/CompositeCollection.xml
index 6af2eec9ccd..72f5e3f901a 100644
--- a/xml/System.Windows.Data/CompositeCollection.xml
+++ b/xml/System.Windows.Data/CompositeCollection.xml
@@ -47,7 +47,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Data.CompositeCollection> can contain items such as strings, objects, [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] nodes, elements, as well as other collections. An <xref:System.Windows.Controls.ItemsControl> uses the data in the <xref:System.Windows.Data.CompositeCollection> to generate its content according to its <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A>. For more information about using <xref:System.Windows.Controls.ItemsControl> objects to bind to collections, see the Binding to Collections section of the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
+ <xref:System.Windows.Data.CompositeCollection> can contain items such as strings, objects, XML nodes, elements, as well as other collections. An <xref:System.Windows.Controls.ItemsControl> uses the data in the <xref:System.Windows.Data.CompositeCollection> to generate its content according to its <xref:System.Windows.Controls.ItemsControl.ItemTemplate%2A>. For more information about using <xref:System.Windows.Controls.ItemsControl> objects to bind to collections, see the Binding to Collections section of the [Data Binding Overview](/dotnet/framework/wpf/data/data-binding-overview).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Data/XmlDataProvider.xml b/xml/System.Windows.Data/XmlDataProvider.xml
index a2feafe8577..fa88e0d2894 100644
--- a/xml/System.Windows.Data/XmlDataProvider.xml
+++ b/xml/System.Windows.Data/XmlDataProvider.xml
@@ -39,7 +39,7 @@
 > [!IMPORTANT]
 >  In a partial-trust sandbox, <xref:System.Windows.Data.XmlDataProvider> fails when it does not have permissions to access the given data. For more information about partial trust security, see [WPF Partial Trust Security](/dotnet/framework/wpf/wpf-partial-trust-security).  
   
- <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
+ <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access XML data.  
   
 -   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
@@ -175,7 +175,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
+ <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access XML data.  
   
 -   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
@@ -394,13 +394,13 @@
         <ReturnType>System.Uri</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the <see cref="T:System.Uri" /> of the [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data file to use as the binding source.</summary>
+        <summary>Gets or sets the <see cref="T:System.Uri" /> of the XML data file to use as the binding source.</summary>
         <value>The <see cref="T:System.Uri" /> of the XML data file to use as the binding source. The default value is <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.  
+ <xref:System.Windows.Data.XmlDataProvider> exposes the following ways to access XML data.  
   
 -   You can embed inline XML data using the <xref:System.Windows.Data.XmlDataProvider> class.  
   
diff --git a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
index 6e35c3924ca..c87a8f7d738 100644
--- a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
+++ b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
@@ -486,7 +486,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] relationship parts in packages, see chapter 1 of the [Open Packaging Conventions](https://www.microsoft.com/whdc/xps/xpspkg.mspx) schema.  
+ For more information about XML relationship parts in packages, see chapter 1 of the [Open Packaging Conventions](https://www.microsoft.com/whdc/xps/xpspkg.mspx) schema.  
   
  ]]></format>
         </remarks>
@@ -519,7 +519,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] relationship parts in packages, see chapter 1 of the [Open Packaging Conventions](https://www.microsoft.com/whdc/xps/xpspkg.mspx) schema.  
+ For more information about XML relationship parts in packages, see chapter 1 of the [Open Packaging Conventions](https://www.microsoft.com/whdc/xps/xpspkg.mspx) schema.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml b/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
index 05033194599..891bc6578c7 100644
--- a/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
@@ -292,7 +292,7 @@
       <Parameters />
       <Docs>
         <summary>Acquires the <see cref="T:System.Xml.XmlWriter" /> for the current <see cref="T:System.Windows.Documents.FixedDocument" />.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] writer for the current <see cref="T:System.Windows.Documents.FixedDocument" />.</returns>
+        <returns>The XML writer for the current <see cref="T:System.Windows.Documents.FixedDocument" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocumentSequence" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedPage" />
@@ -321,7 +321,7 @@
       <Parameters />
       <Docs>
         <summary>Acquires the <see cref="T:System.Xml.XmlWriter" /> for the current <see cref="T:System.Windows.Documents.FixedDocumentSequence" />.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] writer for the current <see cref="T:System.Windows.Documents.FixedDocumentSequence" />.</returns>
+        <returns>The XML writer for the current <see cref="T:System.Windows.Documents.FixedDocumentSequence" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocument" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedPage" />
@@ -350,7 +350,7 @@
       <Parameters />
       <Docs>
         <summary>Acquires the <see cref="T:System.Xml.XmlWriter" /> for the current <see cref="T:System.Windows.Documents.FixedPage" />.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] writer for the current <see cref="T:System.Windows.Documents.FixedPage" />.</returns>
+        <returns>The XML writer for the current <see cref="T:System.Windows.Documents.FixedPage" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocument" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocumentSequence" />
@@ -379,7 +379,7 @@
       <Parameters />
       <Docs>
         <summary>Acquires the <see cref="T:System.Xml.XmlWriter" /> for the current page.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] writer for the current <see cref="T:System.Windows.Documents.FixedPage" />.</returns>
+        <returns>The XML writer for the current <see cref="T:System.Windows.Documents.FixedPage" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocument" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocumentSequence" />
@@ -408,7 +408,7 @@
       <Parameters />
       <Docs>
         <summary>Acquires the <see cref="T:System.Xml.XmlWriter" /> for the current <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" />.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] writer for the current <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" />.</returns>
+        <returns>The XML writer for the current <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocument" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireXmlWriterForFixedDocumentSequence" />
diff --git a/xml/System.Windows/DataTemplate.xml b/xml/System.Windows/DataTemplate.xml
index 6c585999766..a3b9a9e4062 100644
--- a/xml/System.Windows/DataTemplate.xml
+++ b/xml/System.Windows/DataTemplate.xml
@@ -116,7 +116,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- To refer to the Type name of the class, use the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension). If the template is intended for [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data, this is the string that represents the tag name of the data.  
+ To refer to the Type name of the class, use the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension). If the template is intended for XML data, this is the string that represents the tag name of the data.  
   
  ]]></format>
         </remarks>
@@ -218,7 +218,7 @@
 <a name="xamlValues_DataType"></a>   
 ## XAML Values  
  *typeName*  
- If the template is intended for object data, this property contains the type name of the data object (as a string). To refer to the type name of the class, use the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension). If the template is intended for [!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data, this property contains the XML element name. See the documentation remarks for details about specifying a non-default namespace for the XML element.  
+ If the template is intended for object data, this property contains the type name of the data object (as a string). To refer to the type name of the class, use the [x:Type Markup Extension](/dotnet/framework/xaml-services/x-type-markup-extension). If the template is intended for XML data, this property contains the XML element name. See the documentation remarks for details about specifying a non-default namespace for the XML element.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/LocalizabilityAttribute.xml b/xml/System.Windows/LocalizabilityAttribute.xml
index 64e05b5febc..f0d1c5ea3f6 100644
--- a/xml/System.Windows/LocalizabilityAttribute.xml
+++ b/xml/System.Windows/LocalizabilityAttribute.xml
@@ -106,7 +106,7 @@
 |<xref:System.Windows.LocalizationCategory.ToolTip>|A <xref:System.Windows.Controls.ToolTip> or related control.|  
 |<xref:System.Windows.LocalizationCategory.Hyperlink>|A <xref:System.Windows.Documents.Hyperlink> or related control.|  
 |<xref:System.Windows.LocalizationCategory.TextFlow>|A <xref:System.Windows.Documents.FlowDocument> or other panel that can contain text.|  
-|<xref:System.Windows.LocalizationCategory.XmlData>|[!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.|  
+|<xref:System.Windows.LocalizationCategory.XmlData>|XML data.|  
 |<xref:System.Windows.LocalizationCategory.Font>|Font-related data such as font family, font style, or font size.|  
 |<xref:System.Windows.LocalizationCategory.Inherit>|Inherits category from parent node.|  
 |<xref:System.Windows.LocalizationCategory.Ignore>|Do not localize this resource. This does not apply to any child nodes of the resource.|  
diff --git a/xml/System.Windows/LocalizationCategory.xml b/xml/System.Windows/LocalizationCategory.xml
index b218bbf099b..ebf88c70681 100644
--- a/xml/System.Windows/LocalizationCategory.xml
+++ b/xml/System.Windows/LocalizationCategory.xml
@@ -429,7 +429,7 @@
       </ReturnValue>
       <MemberValue>13</MemberValue>
       <Docs>
-        <summary>[!INCLUDE[TLA#tla_xml](~/includes/tlasharptla-xml-md.md)] data.</summary>
+        <summary>XML data.</summary>
       </Docs>
     </Member>
   </Members>

From d6255f69b4b4cd74d1fc64a58626ab390f8ffa62 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:17:05 -0800
Subject: [PATCH 181/236] tlasharptla-xmldom

---
 xml/System.Xaml/XamlReader.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Xaml/XamlReader.xml b/xml/System.Xaml/XamlReader.xml
index 7b6c110f52e..09ca75b5487 100644
--- a/xml/System.Xaml/XamlReader.xml
+++ b/xml/System.Xaml/XamlReader.xml
@@ -36,7 +36,7 @@
   
  Other XAML readers from other frameworks include <xref:System.Windows.Baml2006.Baml2006Reader> and <xref:System.Activities.Debugger.XamlDebuggerXmlReader>.  
   
- <xref:System.Xaml.XamlReader> differs from [!INCLUDE[TLA#tla_xmldom](~/includes/tlasharptla-xmldom-md.md)] and <xref:System.Xml.XmlReader> design principles because <xref:System.Xaml.XamlReader> does not have a `Create` method to return underlying default XAML reader implementations. You must instead instantiate specific derived XAML reader classes by calling their constructors or other class-specific helper APIs.  
+ <xref:System.Xaml.XamlReader> differs from XML Document Object Model (DOM) and <xref:System.Xml.XmlReader> design principles because <xref:System.Xaml.XamlReader> does not have a `Create` method to return underlying default XAML reader implementations. You must instead instantiate specific derived XAML reader classes by calling their constructors or other class-specific helper APIs.  
   
 ## Subtree Readers  
  For the most part, you call <xref:System.Xaml.XamlReader> API in the context of specific XAML reader classes that derive from <xref:System.Xaml.XamlReader>. However, in one particular case, you access <xref:System.Xaml.XamlReader> API on a practical XAML reader instance that is not public and not derived from <xref:System.Xaml.XamlObjectReader> or <xref:System.Xaml.XamlXmlReader>. This case is when you call <xref:System.Xaml.XamlReader.ReadSubtree%2A>, which returns a <xref:System.Xaml.XamlReader> instance. In the default implementation, the <xref:System.Xaml.XamlReader> that is returned by this API is an internal class.  

From f7f07112c2b09627a05edaeb6c8790b04dd1208d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:17:22 -0800
Subject: [PATCH 182/236] tlasharptla-xmp

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml    | 10 +++++-----
 .../BitmapMetadataBlob.xml                             |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index 66409ccceee..af9a753fda6 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index 87609b91ee7..7b399c15945 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and [!INCLUDE[TLA#tla_xmp](~/includes/tlasharptla-xmp-md.md)].  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
   
  ]]></format>
     </remarks>

From f5a7135e4f3bf725dbb1f3bba357fd2116bc61fc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:17:41 -0800
Subject: [PATCH 183/236] tlasharptla-xps

---
 xml/System.IO.Packaging/PackagePart.xml       |  6 +++---
 xml/System.Printing/PrintQueue.xml            | 12 +++++------
 xml/System.Printing/PrintQueueStream.xml      |  2 +-
 .../NamedElement.xml                          |  2 +-
 .../ParagraphStructure.xml                    |  2 +-
 .../StoryFragment.xml                         | 14 ++++++-------
 .../TableCellStructure.xml                    |  2 +-
 .../TableRowGroupStructure.xml                |  2 +-
 .../TableRowStructure.xml                     |  2 +-
 .../TableStructure.xml                        |  2 +-
 xml/System.Windows.Documents/LinkTarget.xml   |  4 ++--
 .../IDocumentStructureProvider.xml            |  6 +++---
 .../IStoryFragmentProvider.xml                |  4 ++--
 .../IXpsFixedDocumentReader.xml               |  4 ++--
 .../IXpsFixedDocumentSequenceReader.xml       |  2 +-
 .../IXpsFixedPageReader.xml                   |  4 ++--
 .../IXpsFixedPageWriter.xml                   |  2 +-
 .../XpsDocument.xml                           |  6 +++---
 .../XpsResourceDictionary.xml                 |  2 +-
 .../XpsSignatureDefinition.xml                | 20 +++++++++----------
 .../BasePackagingPolicy.xml                   |  2 +-
 .../PackageSerializationManager.xml           |  2 +-
 .../XpsPackagingPolicy.xml                    | 14 ++++++-------
 .../XpsSerializationManager.xml               |  2 +-
 .../XpsSerializationManagerAsync.xml          |  4 ++--
 xml/ns-System.Windows.Xps.Packaging.xml       |  2 +-
 26 files changed, 63 insertions(+), 63 deletions(-)

diff --git a/xml/System.IO.Packaging/PackagePart.xml b/xml/System.IO.Packaging/PackagePart.xml
index a4d394ed158..ab83057cbd1 100644
--- a/xml/System.IO.Packaging/PackagePart.xml
+++ b/xml/System.IO.Packaging/PackagePart.xml
@@ -168,7 +168,7 @@
   
  By default, the <xref:System.IO.Packaging.PackagePart.CompressionOption%2A> property of the part is initialized to <xref:System.IO.Packaging.CompressionOption.NotCompressed>.  
   
- `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in XML Paper Specification (XPS) documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
@@ -233,7 +233,7 @@
 ## Remarks  
  `partUri` must be valid <xref:System.IO.Packaging.PackagePart> URI formed in accordance with the [RFC 3986](https://tools.ietf.org/html/rfc3986) *Uniform Resource Identifier (URI) Generic Syntax* specification and the [Open Packaging Conventions](https://go.microsoft.com/fwlink/?LinkID=71255) specification.  
   
- `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ `contentType` must be a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in XML Paper Specification (XPS) documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
@@ -340,7 +340,7 @@
   
  The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is automatically set by the <xref:System.IO.Packaging.PackagePart.%23ctor%2A> constructor.  After it is set by the constructor, the <xref:System.IO.Packaging.PackagePart.ContentType%2A> cannot be changed.  
   
- The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] documents.  
+ The <xref:System.IO.Packaging.PackagePart.ContentType%2A> property is a MIME type formed in accordance with the [RFC 2616](https://www.w3.org/Protocols/rfc2616/rfc2616.html) *Hypertext Transfer Protocol - HTTP*, Section 3.7.  The following table shows an example of the content MIME types used in XML Paper Specification (XPS) documents.  
   
 |Description|Content Type|  
 |-----------------|------------------|  
diff --git a/xml/System.Printing/PrintQueue.xml b/xml/System.Printing/PrintQueue.xml
index 925b39eb469..46600caa533 100644
--- a/xml/System.Printing/PrintQueue.xml
+++ b/xml/System.Printing/PrintQueue.xml
@@ -424,7 +424,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or XML Paper Specification (XPS). If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
@@ -481,7 +481,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
+ Use this method to write device specific information, to a spool file, that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or XML Paper Specification (XPS). If you prefer to work with the <xref:System.IO.Stream> API, you can use the <xref:System.Printing.PrintQueueStream> class instead of this method.  
   
  After the <xref:System.Printing.PrintQueue.AddJob%2A> method has been called, you must write a <xref:System.Byte> array to the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property of the <xref:System.Printing.PrintSystemJobInfo> that is returned by <xref:System.Printing.PrintQueue.AddJob%2A> or no print job is created. This array is what prints if the printer is working and is not paused.  
   
@@ -531,7 +531,7 @@
       <Docs>
         <param name="jobName">The path and name of the document that is being printed.</param>
         <param name="printTicket">The settings of the print job.</param>
-        <summary>Inserts a new print job for an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] Document into the queue, and gives it the specified name and settings.</summary>
+        <summary>Inserts a new print job for an XML Paper Specification (XPS) Document into the queue, and gives it the specified name and settings.</summary>
         <returns>A <see cref="T:System.Printing.PrintSystemJobInfo" /> that represents the print job and its status.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -576,7 +576,7 @@
         <param name="documentPath">The path and name of the document that is being printed.</param>
         <param name="fastCopy">
           <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid XPS; otherwise, <see langword="false" />.</param>
-        <summary>Inserts a new print job for an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] Document into the queue, gives it the specified name, and specifies whether or not it should be validated.</summary>
+        <summary>Inserts a new print job for an XML Paper Specification (XPS) Document into the queue, gives it the specified name, and specifies whether or not it should be validated.</summary>
         <returns>A <see cref="T:System.Printing.PrintSystemJobInfo" /> that represents the print job and its status.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -598,7 +598,7 @@
    
   
 ## Examples  
- The following example shows how to use <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> to batch print all the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] files in a directory.  
+ The following example shows how to use <xref:System.Printing.PrintQueue.AddJob%28System.String%2CSystem.String%2CSystem.Boolean%29> to batch print all the XML Paper Specification (XPS) files in a directory.  
   
  [!code-csharp[BatchPrintXPSFiles#BatchPrintXPSFiles](~/samples/snippets/csharp/VS_Snippets_Wpf/BatchPrintXPSFiles/CSharp/Program.cs#batchprintxpsfiles)]
  [!code-vb[BatchPrintXPSFiles#BatchPrintXPSFiles](~/samples/snippets/visualbasic/VS_Snippets_Wpf/BatchPrintXPSFiles/visualbasic/program.vb#batchprintxpsfiles)]  
@@ -645,7 +645,7 @@
         <param name="fastCopy">
           <see langword="true" /> to spool quickly without page-by-page progress feedback and without validating that the file is valid XPS; otherwise, <see langword="false" />.</param>
         <param name="printTicket">The settings of the print job.</param>
-        <summary>Inserts a new print job for an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] Document into the queue, gives it the specified name and settings, and specifies whether or not it should be validated.</summary>
+        <summary>Inserts a new print job for an XML Paper Specification (XPS) Document into the queue, gives it the specified name and settings, and specifies whether or not it should be validated.</summary>
         <returns>A <see cref="T:System.Printing.PrintSystemJobInfo" /> that represents the print job and its status.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Printing/PrintQueueStream.xml b/xml/System.Printing/PrintQueueStream.xml
index 5e9460503c7..6fce3457265 100644
--- a/xml/System.Printing/PrintQueueStream.xml
+++ b/xml/System.Printing/PrintQueueStream.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this class to write device specific information to a spool file that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)]. If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
+ Use this class to write device specific information to a spool file that is not automatically included by the Microsoft Windows spooler. Of course, you need to know whether the spool file is Enhanced Metafile (EMF) or XML Paper Specification (XPS). If you prefer working with a <xref:System.Byte> array, you can also use two of the overloads of the <xref:System.Printing.PrintQueue.AddJob%2A> method and the <xref:System.Printing.PrintSystemJobInfo.JobStream%2A> property to write to the spool file.  
   
 > [!CAUTION]
 >  Classes within the <xref:System.Printing> namespace are not supported for use within a Windows service or ASP.NET application or service. Attempting to use these classes from within one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.  
diff --git a/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml b/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
index dee4ee2f8e2..beca7682981 100644
--- a/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/NamedElement.xml
@@ -28,7 +28,7 @@
    
   
 ## Examples  
- The following example shows the use of <xref:System.Windows.Documents.DocumentStructures.ParagraphStructure> and <xref:System.Windows.Documents.DocumentStructures.FigureStructure> elements in an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, each with a <xref:System.Windows.Documents.DocumentStructures.NamedElement> child.  
+ The following example shows the use of <xref:System.Windows.Documents.DocumentStructures.ParagraphStructure> and <xref:System.Windows.Documents.DocumentStructures.FigureStructure> elements in an XML Paper Specification (XPS) document, each with a <xref:System.Windows.Documents.DocumentStructures.NamedElement> child.  
   
  [!code-xaml[DocumentStructure#DocStructParaStruct2](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage2_structure.xaml#docstructparastruct2)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/ParagraphStructure.xml b/xml/System.Windows.Documents.DocumentStructures/ParagraphStructure.xml
index fa2725d60cb..60c0cdfdf07 100644
--- a/xml/System.Windows.Documents.DocumentStructures/ParagraphStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/ParagraphStructure.xml
@@ -50,7 +50,7 @@
    
   
 ## Examples  
- The following example shows the `<ParagraphStructure>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<ParagraphStructure>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructParaStruct2](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage2_structure.xaml#docstructparastruct2)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml b/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
index ac54813e56f..64bca9223df 100644
--- a/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/StoryFragment.xml
@@ -157,12 +157,12 @@
   
  In the example above, if the empty cell had not been added by the producing application, then a merger of the fragments would produce a table whose first row had only one cell containing both the "SomeContent" and "MoreContent" references instead of the original first row with two cells, each containing a single reference  
   
- When the entire story is being merged, the algorithm should be repeated for each subsequent fragment that is part of the same story. The fragments that belong to a story are indexed in the `<Story>` element. See section 9.1.15 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx). The last fragment for a given story will have a <xref:System.Windows.Documents.DocumentStructures.StoryBreak> element as its last child.  
+ When the entire story is being merged, the algorithm should be repeated for each subsequent fragment that is part of the same story. The fragments that belong to a story are indexed in the `<Story>` element. See section 9.1.15 of the XML Paper Specification (XPS) specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx). The last fragment for a given story will have a <xref:System.Windows.Documents.DocumentStructures.StoryBreak> element as its last child.  
   
    
   
 ## Examples  
- The following example shows the `<StoryFragment>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<StoryFragment>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructStoryFragContent1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructstoryfragcontent1)]  
   
@@ -251,7 +251,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `FragmentName` attribute of the `</StoryFragment>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, see chapter 9 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `FragmentName` attribute of the `</StoryFragment>` part of an XML Paper Specification (XPS) document, see chapter 9 of the XML Paper Specification (XPS) specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
@@ -295,12 +295,12 @@
 ## Remarks  
  Possible values include "Header," "Footer," and "Content."  
   
- For more information about the `FragmentType` attribute of the `</StoryFragment>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, see chapter 9 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `FragmentType` attribute of the `</StoryFragment>` part of an XML Paper Specification (XPS) document, see chapter 9 of the XML Paper Specification (XPS) specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
 ## Examples  
- The following example shows the `FragmentType` attribute of the `<StoryFragment>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `FragmentType` attribute of the `<StoryFragment>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructStoryFragContent1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructstoryfragcontent1)]  
   
@@ -343,14 +343,14 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- All fragments of a given story must have the same value for this property. It must match the `StoryName` attribute of the `<Story>` element. See section 9.1.15 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ All fragments of a given story must have the same value for this property. It must match the `StoryName` attribute of the `<Story>` element. See section 9.1.15 of the XML Paper Specification (XPS) specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  This property can be unspecified if <xref:System.Windows.Documents.DocumentStructures.StoryFragment.FragmentType%2A> is Header or Footer.  
   
    
   
 ## Examples  
- The following example shows the `StoryName` attribute of the `<StoryFragment>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `StoryName` attribute of the `<StoryFragment>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructStoryFragContent1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructstoryfragcontent1)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/TableCellStructure.xml b/xml/System.Windows.Documents.DocumentStructures/TableCellStructure.xml
index 1aee3505a9d..9ae28a7a466 100644
--- a/xml/System.Windows.Documents.DocumentStructures/TableCellStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/TableCellStructure.xml
@@ -42,7 +42,7 @@
    
   
 ## Examples  
- The following example shows the `<TableCellStructure>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<TableCellStructure>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructTableStruct1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructtablestruct1)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/TableRowGroupStructure.xml b/xml/System.Windows.Documents.DocumentStructures/TableRowGroupStructure.xml
index de4e87994ed..d89ab777813 100644
--- a/xml/System.Windows.Documents.DocumentStructures/TableRowGroupStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/TableRowGroupStructure.xml
@@ -42,7 +42,7 @@
    
   
 ## Examples  
- The following example shows the `<TableRowGroupStructure>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<TableRowGroupStructure>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructTableStruct1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructtablestruct1)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/TableRowStructure.xml b/xml/System.Windows.Documents.DocumentStructures/TableRowStructure.xml
index 61087bbfd02..946c2a83014 100644
--- a/xml/System.Windows.Documents.DocumentStructures/TableRowStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/TableRowStructure.xml
@@ -42,7 +42,7 @@
    
   
 ## Examples  
- The following example shows the `<TableRowStructure>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<TableRowStructure>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructTableStruct1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructtablestruct1)]  
   
diff --git a/xml/System.Windows.Documents.DocumentStructures/TableStructure.xml b/xml/System.Windows.Documents.DocumentStructures/TableStructure.xml
index dcdc2c5d0f9..cc18593898e 100644
--- a/xml/System.Windows.Documents.DocumentStructures/TableStructure.xml
+++ b/xml/System.Windows.Documents.DocumentStructures/TableStructure.xml
@@ -50,7 +50,7 @@
    
   
 ## Examples  
- The following example shows the `<TableStructure>` part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.  
+ The following example shows the `<TableStructure>` part of an XML Paper Specification (XPS) document.  
   
  [!code-xaml[DocumentStructure#DocStructTableStruct1](~/samples/snippets/csharp/VS_Snippets_Wpf/DocumentStructure/CSharp/Content/FixedPage1_structure.xaml#docstructtablestruct1)]  
   
diff --git a/xml/System.Windows.Documents/LinkTarget.xml b/xml/System.Windows.Documents/LinkTarget.xml
index 95a176ca600..26e3fa94c54 100644
--- a/xml/System.Windows.Documents/LinkTarget.xml
+++ b/xml/System.Windows.Documents/LinkTarget.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an XML Paper Specification (XPS) document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
@@ -86,7 +86,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ The names of all of the link targets for all of the pages in a <xref:System.Windows.Documents.FixedDocument> are gathered into the Page Content part of an XML Paper Specification (XPS) document. This enables consuming applications to determine if a particular target is in a particular document without having to load the entire document. For more information about the `<PageContent>` and `<LinkTarget>` elements, see chapter 3 of the XPS specification which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml b/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
index 700e443ee31..1631a7f98c7 100644
--- a/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
+++ b/xml/System.Windows.Xps.Packaging/IDocumentStructureProvider.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `DocumentStructure` element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `DocumentStructure` element of an XPS package, see chapter 9 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
@@ -43,13 +43,13 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Adds the <see langword="DocumentStructure" /> part of [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] to an XPS package.</summary>
+        <summary>Adds the <see langword="DocumentStructure" /> part of XML Paper Specification (XPS) to an XPS package.</summary>
         <returns>An <see cref="T:System.Windows.Xps.Packaging.XpsStructure" /> that represents the <see langword="DocumentStructure" /> part of an XPS package.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `DocumentStructure` element of an XPS package, see chapter 9 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `DocumentStructure` element of an XPS package, see chapter 9 of the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml b/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
index 73ab8e25942..78a42c034c6 100644
--- a/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
+++ b/xml/System.Windows.Xps.Packaging/IStoryFragmentProvider.xml
@@ -18,7 +18,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
   
  ]]></format>
     </remarks>
@@ -49,7 +49,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://go.microsoft.com/fwlink/?LinkId=67000).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
index 7aa4147eae0..6af81cfae25 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentReader.xml
@@ -134,7 +134,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document does not need to have a Document Structure part.  
+ An XML Paper Specification (XPS) document does not need to have a Document Structure part.  
   
  ]]></format>
         </remarks>
@@ -224,7 +224,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an XML Paper Specification (XPS) document, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
index 54c451f9fb5..a5a7e6e05ea 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedDocumentSequenceReader.xml
@@ -116,7 +116,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] sequence, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an XML Paper Specification (XPS) sequence, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
index f505667b82a..4b97a3bc186 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedPageReader.xml
@@ -289,7 +289,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Printing.PrintTicket> part of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] page, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Printing.PrintTicket> part of an XML Paper Specification (XPS) page, see chapter 2 in the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
@@ -343,7 +343,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the <xref:System.Windows.Documents.DocumentStructures.StoryFragments> element of an XPS package, see chapter 9 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
index bbc4c1be68a..15433f08253 100644
--- a/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
+++ b/xml/System.Windows.Xps.Packaging/IXpsFixedPageWriter.xml
@@ -396,7 +396,7 @@
         <param name="resourceType">The type of resource to add.</param>
         <param name="resourceUri">The absolute path of the resource to add, or <see langword="null" />.</param>
         <summary>Adds a new <see cref="T:System.Windows.Xps.Packaging.XpsResource" /> to the current page.</summary>
-        <returns>The new [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] resource that was added.</returns>
+        <returns>The new XML Paper Specification (XPS) resource that was added.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Windows.Xps.Packaging/XpsDocument.xml b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
index 8a98503d818..589d01010f1 100644
--- a/xml/System.Windows.Xps.Packaging/XpsDocument.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsDocument.xml
@@ -312,7 +312,7 @@
       <Parameters />
       <Docs>
         <summary>Adds a root <see cref="T:System.Windows.Documents.FixedDocumentSequence" /> to the package and returns a writer.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] fixed-document sequence writer for this <see cref="T:System.Windows.Xps.Packaging.XpsDocument" />.</returns>
+        <returns>The XML Paper Specification (XPS) fixed-document sequence writer for this <see cref="T:System.Windows.Xps.Packaging.XpsDocument" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -457,7 +457,7 @@
       <Docs>
         <param name="xpsDocument">The XPS document to write.</param>
         <summary>Creates an <see cref="T:System.Windows.Xps.XpsDocumentWriter" /> for writing an <see cref="T:System.Windows.Xps.Packaging.XpsDocument" />.</summary>
-        <returns>The <see cref="T:System.Windows.Xps.XpsDocumentWriter" /> to use for writing the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</returns>
+        <returns>The <see cref="T:System.Windows.Xps.XpsDocumentWriter" /> to use for writing the XML Paper Specification (XPS) document.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -932,7 +932,7 @@
         <ReturnType>System.Windows.Xps.Packaging.XpsThumbnail</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] thumbnail image that is associated with the document.</summary>
+        <summary>Gets or sets the XML Paper Specification (XPS) thumbnail image that is associated with the document.</summary>
         <value>An <see cref="T:System.Windows.Xps.Packaging.XpsThumbnail" /> that represents the thumbnail image that is associated with the document.</value>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Packaging.XpsDocument.AddThumbnail(System.Windows.Xps.Packaging.XpsImageType)" />
diff --git a/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml b/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
index c56ec92a433..f4278ca51ff 100644
--- a/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsResourceDictionary.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  This class has no public constructor. Get a reference to an <xref:System.Windows.Xps.Packaging.XpsResourceDictionary> by using the <xref:System.Windows.Xps.Packaging.IXpsFixedPageWriter.AddResourceDictionary%2A?displayProperty=nameWithType> method.  
   
- For more information about the `ResourceDictionary` element of an XPS package, see chapter 7 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `ResourceDictionary` element of an XPS package, see chapter 7 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml b/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
index 0936a86d11b..6202f504bec 100644
--- a/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
+++ b/xml/System.Windows.Xps.Packaging/XpsSignatureDefinition.xml
@@ -172,7 +172,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `Intent` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages, see chapter 10 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `Intent` element of signature definitions in XML Paper Specification (XPS) packages, see chapter 10 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
@@ -216,9 +216,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property corresponds to the `SignerName` attribute of the `SignatureDefinition` element in an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] package. Notice the difference in the names.  
+ This property corresponds to the `SignerName` attribute of the `SignatureDefinition` element in an XML Paper Specification (XPS) package. Notice the difference in the names.  
   
- For more information about the `SignerName` attribute, see chapter 10 of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SignerName` attribute, see chapter 10 of the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
@@ -262,7 +262,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `SignBy` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages, see the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SignBy` element of signature definitions in XML Paper Specification (XPS) packages, see the XPS specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
@@ -306,11 +306,11 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property corresponds to the `SigningLocation` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages. Notice the difference in the names.  
+ This property corresponds to the `SigningLocation` element of signature definitions in XML Paper Specification (XPS) packages. Notice the difference in the names.  
   
- The original producer of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] package can set this property. Optionally, the signer can set the property at the time of signing the package if no one else has already signed.  
+ The original producer of the XML Paper Specification (XPS) package can set this property. Optionally, the signer can set the property at the time of signing the package if no one else has already signed.  
   
- For more information about the `SigningLocation` element, see chapter 10 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SigningLocation` element, see chapter 10 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
@@ -356,7 +356,7 @@
 ## Remarks  
  To link a `Signature` element to this <xref:System.Windows.Xps.Packaging.XpsSignatureDefinition>, you must set the `Id` attribute of the `Signature` to the value of the <xref:System.Windows.Xps.Packaging.XpsSignatureDefinition.SpotId%2A> property. For more information about `Signature` elements, see the [Open Packaging Conventions](https://www.microsoft.com/whdc/xps/xpspkg.mspx) schema.  
   
- For more information about the `SpotID` attribute of the `SignatureDefinition` element in an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] package, see chapter 10 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SpotID` attribute of the `SignatureDefinition` element in an XML Paper Specification (XPS) package, see chapter 10 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
    
   
@@ -394,13 +394,13 @@
         <ReturnType>System.Windows.Xps.Packaging.SpotLocation</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the location that specifies where to display the visible digital signature in an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</summary>
+        <summary>Gets or sets the location that specifies where to display the visible digital signature in an XML Paper Specification (XPS) document.</summary>
         <value>A <see cref="T:System.Windows.Xps.Packaging.SpotLocation" /> that represents the location in the package where a visible request for a signature appears. The default value is <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about the `SpotLocation` element of signature definitions in [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] packages, see chapter 10 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `SpotLocation` element of signature definitions in XML Paper Specification (XPS) packages, see chapter 10 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
index c87a8f7d738..d17b5039b91 100644
--- a/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
+++ b/xml/System.Windows.Xps.Serialization/BasePackagingPolicy.xml
@@ -228,7 +228,7 @@
   
  `<LinkTarget Name=\"` *target name* `\" />`, where *target name* is the string.  
   
- For more information about the `<PageContent.LinkTargets>` and <xref:System.Windows.Documents.LinkTarget> elements, see chapter 3 in the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
+ For more information about the `<PageContent.LinkTargets>` and <xref:System.Windows.Documents.LinkTarget> elements, see chapter 3 in the XML Paper Specification (XPS) specification, which you can obtain at [XPS: Specification and License Downloads](https://www.microsoft.com/whdc/xps/downloads.mspx).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Xps.Serialization/PackageSerializationManager.xml b/xml/System.Windows.Xps.Serialization/PackageSerializationManager.xml
index 92847129cbc..7d40b6fcf45 100644
--- a/xml/System.Windows.Xps.Serialization/PackageSerializationManager.xml
+++ b/xml/System.Windows.Xps.Serialization/PackageSerializationManager.xml
@@ -79,7 +79,7 @@
       </Parameters>
       <Docs>
         <param name="serializedObject">The object to save.</param>
-        <summary>When overridden in a derived class, saves the specified serialized object to an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] package.</summary>
+        <summary>When overridden in a derived class, saves the specified serialized object to an XML Paper Specification (XPS) package.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml b/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
index 891bc6578c7..eb473a7331a 100644
--- a/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsPackagingPolicy.xml
@@ -77,7 +77,7 @@
         <Parameter Name="interleavingType" Type="System.Windows.Xps.Packaging.PackageInterleavingOrder" />
       </Parameters>
       <Docs>
-        <param name="xpsPackage">The [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document that the packaging policy applies to.</param>
+        <param name="xpsPackage">The XML Paper Specification (XPS) document that the packaging policy applies to.</param>
         <param name="interleavingType">The order in which to interleave document elements.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Xps.Serialization.XpsPackagingPolicy" /> class with a specified <see cref="T:System.Windows.Xps.Packaging.XpsDocument" /> and specified interleave order.</summary>
         <remarks>To be added.</remarks>
@@ -176,9 +176,9 @@
         <Parameter Name="resourceId" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="resourceId">The identifier of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] font.</param>
+        <param name="resourceId">The identifier of the XML Paper Specification (XPS) font.</param>
         <summary>Acquires the <see cref="T:System.Windows.Xps.Serialization.XpsResourceStream" /> for a specified <see cref="T:System.Windows.Xps.Packaging.XpsFont" />.</summary>
-        <returns>The resource stream for the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] font that has the specified <paramref name="resourceId" />.</returns>
+        <returns>The resource stream for the XML Paper Specification (XPS) font that has the specified <paramref name="resourceId" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireResourceStreamForXpsColorContext(System.String)" />
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireResourceStreamForXpsImage(System.String)" />
@@ -207,7 +207,7 @@
         <Parameter Name="resourceId" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="resourceId">The resource identifier of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] image.</param>
+        <param name="resourceId">The resource identifier of the XML Paper Specification (XPS) image.</param>
         <summary>Acquires the resource stream for a specified <see cref="T:System.Windows.Xps.Packaging.XpsImage" />.</summary>
         <returns>The resource stream for the <see cref="T:System.Windows.Xps.Packaging.XpsImage" /> that has the specified <paramref name="resourceId" />.</returns>
         <remarks>To be added.</remarks>
@@ -240,7 +240,7 @@
       <Docs>
         <param name="resourceId">The identifier of the resource dictionary.</param>
         <summary>Acquires the resource stream for a specified <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" />.</summary>
-        <returns>The [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] resource stream for the <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" /> that has the specified <paramref name="resourceId" />.</returns>
+        <returns>The XML Paper Specification (XPS) resource stream for the <see cref="T:System.Windows.Xps.Packaging.XpsResourceDictionary" /> that has the specified <paramref name="resourceId" />.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="M:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireResourceStreamForXpsColorContext(System.String)" />
         <altmember cref="Overload:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireResourceStreamForXpsFont" />
@@ -507,7 +507,7 @@
         <Parameter Name="printTicket" Type="System.Printing.PrintTicket" />
       </Parameters>
       <Docs>
-        <param name="printTicket">The print ticket to store as part of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</param>
+        <param name="printTicket">The print ticket to store as part of the XML Paper Specification (XPS) document.</param>
         <summary>Stores a specified <see cref="T:System.Printing.PrintTicket" /> as part of the <see cref="T:System.Windows.Xps.Packaging.XpsDocument" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -687,7 +687,7 @@
         <Parameter Name="resourceId" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="resourceId">The identifier of the [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] font that you want to release.</param>
+        <param name="resourceId">The identifier of the XML Paper Specification (XPS) font that you want to release.</param>
         <summary>Releases the <see cref="T:System.Windows.Xps.Serialization.XpsResourceStream" /> for a specified <see cref="T:System.Windows.Xps.Packaging.XpsFont" />.</summary>
         <remarks>To be added.</remarks>
         <altmember cref="Overload:System.Windows.Xps.Serialization.XpsPackagingPolicy.AcquireResourceStreamForXpsFont" />
diff --git a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
index 921bb239b76..ef3195bf1ce 100644
--- a/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsSerializationManager.xml
@@ -49,7 +49,7 @@
         <Parameter Name="batchMode" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="packagingPolicy">An object that provides methods for acquiring serialization readers and writers for different parts of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</param>
+        <param name="packagingPolicy">An object that provides methods for acquiring serialization readers and writers for different parts of an XML Paper Specification (XPS) document.</param>
         <param name="batchMode">
           <see langword="true" /> to specify batch mode; otherwise, <see langword="false" />.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Xps.Serialization.XpsSerializationManager" /> class.</summary>
diff --git a/xml/System.Windows.Xps.Serialization/XpsSerializationManagerAsync.xml b/xml/System.Windows.Xps.Serialization/XpsSerializationManagerAsync.xml
index 7628039db7e..e230dec4ae7 100644
--- a/xml/System.Windows.Xps.Serialization/XpsSerializationManagerAsync.xml
+++ b/xml/System.Windows.Xps.Serialization/XpsSerializationManagerAsync.xml
@@ -48,7 +48,7 @@
         <Parameter Name="batchMode" Type="System.Boolean" />
       </Parameters>
       <Docs>
-        <param name="packagingPolicy">An object that provides methods for acquiring serialization readers and writers for different parts of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document.</param>
+        <param name="packagingPolicy">An object that provides methods for acquiring serialization readers and writers for different parts of an XML Paper Specification (XPS) document.</param>
         <param name="batchMode">
           <see langword="true" /> to specify batch mode; otherwise, <see langword="false" />.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Windows.Xps.Serialization.XpsSerializationManagerAsync" /> class.</summary>
@@ -123,7 +123,7 @@
       </Parameters>
       <Docs>
         <param name="serializedObject">The object that is saved.</param>
-        <summary>Saves a specified serialized object to an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] package.</summary>
+        <summary>Saves a specified serialized object to an XML Paper Specification (XPS) package.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/ns-System.Windows.Xps.Packaging.xml b/xml/ns-System.Windows.Xps.Packaging.xml
index 8627dbc93f4..877f57db1a8 100644
--- a/xml/ns-System.Windows.Xps.Packaging.xml
+++ b/xml/ns-System.Windows.Xps.Packaging.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In addition to the interfaces and the types that represent the major parts of an [!INCLUDE[TLA#tla_xps](~/includes/tlasharptla-xps-md.md)] document, the <xref:System.Windows.Xps.Packaging> namespace provides control over the packaging process, including digital signatures and Digital Rights Management (DRM) of XPS documents.  
+ In addition to the interfaces and the types that represent the major parts of an XML Paper Specification (XPS) document, the <xref:System.Windows.Xps.Packaging> namespace provides control over the packaging process, including digital signatures and Digital Rights Management (DRM) of XPS documents.  
   
  For more information, see the XML Paper Specification (XPS) available for download at [https://go.microsoft.com/fwlink/?LinkID=65761](https://go.microsoft.com/fwlink/?LinkID=65761).  
   

From 9e2f42f84a06d51e391b917336fbdf66ddb76098 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:17:59 -0800
Subject: [PATCH 184/236] tlasharptla-xrml

---
 .../PublishLicense.xml                                 |  2 +-
 .../UnsignedPublishLicense.xml                         |  4 ++--
 xml/System.Security.RightsManagement/UseLicense.xml    | 10 +++++-----
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Security.RightsManagement/PublishLicense.xml b/xml/System.Security.RightsManagement/PublishLicense.xml
index 664791a0ce4..7fc16614767 100644
--- a/xml/System.Security.RightsManagement/PublishLicense.xml
+++ b/xml/System.Security.RightsManagement/PublishLicense.xml
@@ -291,7 +291,7 @@
       <Parameters />
       <Docs>
         <summary>Returns the serialized XrML string that was used to create this license.</summary>
-        <returns>The serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string that was used to create this license.</returns>
+        <returns>The serialized Extensible Rights Markup Language (XrML) string that was used to create this license.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
index b36fc74d002..87ef0db9ec9 100644
--- a/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
+++ b/xml/System.Security.RightsManagement/UnsignedPublishLicense.xml
@@ -96,7 +96,7 @@
         <Parameter Name="publishLicenseTemplate" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="publishLicenseTemplate">The [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] publish-license template to use to create this license.</param>
+        <param name="publishLicenseTemplate">The Extensible Rights Markup Language (XrML) publish-license template to use to create this license.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Security.RightsManagement.UnsignedPublishLicense" /> class from a specified XrML publish-license template.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -221,7 +221,7 @@
 ## Remarks  
  <xref:System.Security.RightsManagement.UnsignedPublishLicense.Owner%2A> specifies the user who owns the <xref:System.Security.RightsManagement.PublishLicense>.  
   
- <xref:System.Security.RightsManagement.UnsignedPublishLicense.Owner%2A> is also associated with the Owner node in the issuance license [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)].  
+ <xref:System.Security.RightsManagement.UnsignedPublishLicense.Owner%2A> is also associated with the Owner node in the issuance license Extensible Rights Markup Language (XrML).  
   
    
   
diff --git a/xml/System.Security.RightsManagement/UseLicense.xml b/xml/System.Security.RightsManagement/UseLicense.xml
index 579111ac625..67f428ba2fe 100644
--- a/xml/System.Security.RightsManagement/UseLicense.xml
+++ b/xml/System.Security.RightsManagement/UseLicense.xml
@@ -59,7 +59,7 @@
         <Parameter Name="useLicense" Type="System.String" />
       </Parameters>
       <Docs>
-        <param name="useLicense">A use license in serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] form.</param>
+        <param name="useLicense">A use license in serialized Extensible Rights Markup Language (XrML) form.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Security.RightsManagement.UseLicense" /> class.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
@@ -205,7 +205,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Security.RightsManagement.UseLicense.Equals%2A> tests for equivalence comparing the serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] strings specified to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructors.  
+ <xref:System.Security.RightsManagement.UseLicense.Equals%2A> tests for equivalence comparing the serialized Extensible Rights Markup Language (XrML) strings specified to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructors.  
   
  ]]></format>
         </remarks>
@@ -237,7 +237,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The returned hash code is based on the serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string passed to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructor.  
+ The returned hash code is based on the serialized Extensible Rights Markup Language (XrML) string passed to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructor.  
   
  ]]></format>
         </remarks>
@@ -267,7 +267,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The license owner is obtained from the serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string passed to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructor.  
+ The license owner is obtained from the serialized Extensible Rights Markup Language (XrML) string passed to the <xref:System.Security.RightsManagement.UseLicense.%23ctor%2A> constructor.  
   
  ]]></format>
         </remarks>
@@ -293,7 +293,7 @@
       <Parameters />
       <Docs>
         <summary>Returns the serialized XrML string used to create this license.</summary>
-        <returns>The serialized [!INCLUDE[TLA#tla_xrml](~/includes/tlasharptla-xrml-md.md)] string originally passed to the <see cref="M:System.Security.RightsManagement.UseLicense.#ctor(System.String)" /> constructor.</returns>
+        <returns>The serialized Extensible Rights Markup Language (XrML) string originally passed to the <see cref="M:System.Security.RightsManagement.UseLicense.#ctor(System.String)" /> constructor.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

From 6136f290b6378f9166a98f5e0365784cfbc6c498 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:18:26 -0800
Subject: [PATCH 185/236] tlasharptla-xsd

---
 xml/System.IO.Packaging/PackageRelationshipSelector.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.IO.Packaging/PackageRelationshipSelector.xml b/xml/System.IO.Packaging/PackageRelationshipSelector.xml
index eb268ef3115..c0b99ea9b80 100644
--- a/xml/System.IO.Packaging/PackageRelationshipSelector.xml
+++ b/xml/System.IO.Packaging/PackageRelationshipSelector.xml
@@ -84,7 +84,7 @@
         <exception cref="T:System.ArgumentNullException">
           <paramref name="sourceUri" /> or <paramref name="selectionCriteria" /> is <see langword="null" />.</exception>
         <exception cref="T:System.ArgumentOutOfRangeException">The <paramref name="selectorType" /> parameter is not valid.</exception>
-        <exception cref="T:System.Xml.XmlException">The <paramref name="selectorType" /> parameter is <see cref="F:System.IO.Packaging.PackageRelationshipSelectorType.Id" /> but <paramref name="selectionCriteria" /> is not a valid [!INCLUDE[TLA#tla_xsd](~/includes/tlasharptla-xsd-md.md)] identifier (ID).</exception>
+        <exception cref="T:System.Xml.XmlException">The <paramref name="selectorType" /> parameter is <see cref="F:System.IO.Packaging.PackageRelationshipSelectorType.Id" /> but <paramref name="selectionCriteria" /> is not a valid XML Schema Definition (XSD) identifier (ID).</exception>
         <exception cref="T:System.ArgumentException">The <paramref name="selectionCriteria" /> is not valid for the specified <paramref name="selectorType" />.
 
 -or-

From 6a9bfba9925b0645f3921aca247fcbf4fee17dff Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:19:05 -0800
Subject: [PATCH 186/236] tsql

---
 xml/System.Data.SqlClient/SqlBulkCopy.xml   |  2 +-
 xml/System.Data.SqlClient/SqlCommand.xml    | 10 +++++-----
 xml/System.Data.SqlClient/SqlConnection.xml | 12 ++++++------
 xml/System.Data.SqlClient/SqlDataReader.xml |  2 +-
 4 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/xml/System.Data.SqlClient/SqlBulkCopy.xml b/xml/System.Data.SqlClient/SqlBulkCopy.xml
index a4c0f9be11b..4258c67c642 100644
--- a/xml/System.Data.SqlClient/SqlBulkCopy.xml
+++ b/xml/System.Data.SqlClient/SqlBulkCopy.xml
@@ -417,7 +417,7 @@
  In this example, the source data is first read from a SQL Server table to a <xref:System.Data.SqlClient.SqlDataReader> instance. The source data does not have to be located on SQL Server; you can use any data source that can be read to an <xref:System.Data.IDataReader> or loaded to a <xref:System.Data.DataTable>.  
   
 > [!IMPORTANT]
->  This sample will not run unless you have created the work tables as described in [Bulk Copy Example Setup](/dotnet/framework/data/adonet/sql/bulk-copy-example-setup). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a [!INCLUDE[tsql](~/includes/tsql-md.md)]`INSERT ... SELECT` statement to copy the data.  
+>  This sample will not run unless you have created the work tables as described in [Bulk Copy Example Setup](/dotnet/framework/data/adonet/sql/bulk-copy-example-setup). This code is provided to demonstrate the syntax for using **SqlBulkCopy** only. If the source and destination tables are in the same SQL Server instance, it is easier and faster to use a Transact-SQL`INSERT ... SELECT` statement to copy the data.  
   
  [!code-csharp[DataWorks SqlBulkCopy.Timeout#1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/DataWorks SqlBulkCopy.Timeout/CS/source.cs#1)]
  [!code-vb[DataWorks SqlBulkCopy.Timeout#1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/DataWorks SqlBulkCopy.Timeout/VB/source.vb#1)]  
diff --git a/xml/System.Data.SqlClient/SqlCommand.xml b/xml/System.Data.SqlClient/SqlCommand.xml
index 930483ae4a6..64d5dacf291 100644
--- a/xml/System.Data.SqlClient/SqlCommand.xml
+++ b/xml/System.Data.SqlClient/SqlCommand.xml
@@ -795,7 +795,7 @@ class Program {
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method starts the process of asynchronously executing a [!INCLUDE[tsql](~/includes/tsql-md.md)] statement or stored procedure that does not return rows, so that other tasks can run concurrently while the statement is executing. When the statement has completed, developers must call the <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> method to finish the operation. The <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method returns immediately, but until the code executes the corresponding <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> method call, it must not execute any other calls that start a synchronous or asynchronous execution against the same <xref:System.Data.SqlClient.SqlCommand> object. Calling the <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> before the command's execution is completed causes the <xref:System.Data.SqlClient.SqlCommand> object to block until the execution is finished.  
+ The <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method starts the process of asynchronously executing a Transact-SQL statement or stored procedure that does not return rows, so that other tasks can run concurrently while the statement is executing. When the statement has completed, developers must call the <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> method to finish the operation. The <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method returns immediately, but until the code executes the corresponding <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> method call, it must not execute any other calls that start a synchronous or asynchronous execution against the same <xref:System.Data.SqlClient.SqlCommand> object. Calling the <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> before the command's execution is completed causes the <xref:System.Data.SqlClient.SqlCommand> object to block until the execution is finished.  
   
  Note that the command text and parameters are sent to the server synchronously. If a large command or many parameters are sent, this method may block during writes. After the command is sent, the method returns immediately without waiting for an answer from the server--that is, reads are asynchronous.  
   
@@ -2339,7 +2339,7 @@ public class A {
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you call <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> to execute a [!INCLUDE[tsql](~/includes/tsql-md.md)] statement, you must call <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> in order to complete the operation. If the process of executing the command has not yet finished, this method blocks until the operation is complete. Users can verify that the command has completed its operation by using the <xref:System.IAsyncResult> instance returned by the <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method. If a callback procedure was specified in the call to <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A>, this method must be called.  
+ When you call <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> to execute a Transact-SQL statement, you must call <xref:System.Data.SqlClient.SqlCommand.EndExecuteNonQuery%2A> in order to complete the operation. If the process of executing the command has not yet finished, this method blocks until the operation is complete. Users can verify that the command has completed its operation by using the <xref:System.IAsyncResult> instance returned by the <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A> method. If a callback procedure was specified in the call to <xref:System.Data.SqlClient.SqlCommand.BeginExecuteNonQuery%2A>, this method must be called.  
   
    
   
@@ -2676,7 +2676,7 @@ If no statements are detected that contribute to the count, the return value is
       </Parameters>
       <Docs>
         <param name="cancellationToken">The cancellation instruction.</param>
-        <summary>An asynchronous version of <see cref="M:System.Data.SqlClient.SqlCommand.ExecuteNonQuery" />, which executes a [!INCLUDE[tsql](~/includes/tsql-md.md)] statement against the connection and returns the number of rows affected. The cancellation token can be used to request that the operation be abandoned before the command timeout elapses.  Exceptions will be reported via the returned Task object.</summary>
+        <summary>An asynchronous version of <see cref="M:System.Data.SqlClient.SqlCommand.ExecuteNonQuery" />, which executes a Transact-SQL statement against the connection and returns the number of rows affected. The cancellation token can be used to request that the operation be abandoned before the command timeout elapses.  Exceptions will be reported via the returned Task object.</summary>
         <returns>A task representing the asynchronous operation.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -2898,7 +2898,7 @@ The <see cref="T:System.Data.SqlClient.SqlConnection" /> closed or dropped durin
         <AssemblyVersion>4.1.0.0</AssemblyVersion>
       </AssemblyInfo>
       <Docs>
-        <summary>Initiates the asynchronous execution of the [!INCLUDE[tsql](~/includes/tsql-md.md)] statement or stored procedure that is described by this <see cref="T:System.Data.SqlClient.SqlCommand" />.</summary>
+        <summary>Initiates the asynchronous execution of the Transact-SQL statement or stored procedure that is described by this <see cref="T:System.Data.SqlClient.SqlCommand" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -3412,7 +3412,7 @@ A timeout occurred during a streaming operation. For more information about stre
 ## Remarks  
  The **XmlReader** returned by this method does not support asynchronous operations.
 
- The <xref:System.Data.SqlClient.SqlCommand.CommandText%2A> property ordinarily specifies a [!INCLUDE[tsql](~/includes/tsql-md.md)] statement with a valid FOR XML clause. However, <xref:System.Data.SqlClient.SqlCommand.CommandText%2A> can also specify a statement that returns `ntext` or `nvarchar` data that contains valid XML, or the contents of a column defined with the `xml` data type.  
+ The <xref:System.Data.SqlClient.SqlCommand.CommandText%2A> property ordinarily specifies a Transact-SQL statement with a valid FOR XML clause. However, <xref:System.Data.SqlClient.SqlCommand.CommandText%2A> can also specify a statement that returns `ntext` or `nvarchar` data that contains valid XML, or the contents of a column defined with the `xml` data type.  
   
  A typical <xref:System.Data.SqlClient.SqlCommand.ExecuteXmlReader%2A> query can be formatted as in the following Microsoft Visual C# example:  
   
diff --git a/xml/System.Data.SqlClient/SqlConnection.xml b/xml/System.Data.SqlClient/SqlConnection.xml
index d36b898fa2c..78fa2418cd5 100644
--- a/xml/System.Data.SqlClient/SqlConnection.xml
+++ b/xml/System.Data.SqlClient/SqlConnection.xml
@@ -113,7 +113,7 @@ using (SqlConnection connection = new SqlConnection(connectionString))
 
 
 ## Examples
- The following example creates a <xref:System.Data.SqlClient.SqlCommand> and a <xref:System.Data.SqlClient.SqlConnection>. The <xref:System.Data.SqlClient.SqlConnection> is opened and set as the <xref:System.Data.SqlClient.SqlCommand.Connection%2A> for the <xref:System.Data.SqlClient.SqlCommand>. The example then calls <xref:System.Data.SqlClient.SqlCommand.ExecuteNonQuery%2A>. To accomplish this, the <xref:System.Data.SqlClient.SqlCommand.ExecuteNonQuery%2A> is passed a connection string and a query string that is a [!INCLUDE[tsql](~/includes/tsql-md.md)] INSERT statement. The connection is closed automatically when the code exits the using block.
+ The following example creates a <xref:System.Data.SqlClient.SqlCommand> and a <xref:System.Data.SqlClient.SqlConnection>. The <xref:System.Data.SqlClient.SqlConnection> is opened and set as the <xref:System.Data.SqlClient.SqlCommand.Connection%2A> for the <xref:System.Data.SqlClient.SqlCommand>. The example then calls <xref:System.Data.SqlClient.SqlCommand.ExecuteNonQuery%2A>. To accomplish this, the <xref:System.Data.SqlClient.SqlCommand.ExecuteNonQuery%2A> is passed a connection string and a query string that is a Transact-SQL INSERT statement. The connection is closed automatically when the code exits the using block.
 
  [!code-csharp[Classic WebData SqlCommand.ExecuteNonQuery Example#1](~/samples/snippets/csharp/VS_Snippets_ADO.NET/Classic WebData SqlCommand.ExecuteNonQuery Example/CS/source.cs#1)]
  [!code-vb[Classic WebData SqlCommand.ExecuteNonQuery Example#1](~/samples/snippets/visualbasic/VS_Snippets_ADO.NET/Classic WebData SqlCommand.ExecuteNonQuery Example/VB/source.vb#1)]
@@ -515,7 +515,7 @@ using (SqlConnection connection = new SqlConnection(connectionString))
  You must explicitly commit or roll back the transaction using the <xref:System.Data.SqlClient.SqlTransaction.Commit%2A> or <xref:System.Data.SqlClient.SqlTransaction.Rollback%2A> method. To make sure that the .NET Framework Data Provider for SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server.
 
 > [!NOTE]
-> After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A?displayProperty=nameWithType> followed immediately by <xref:System.Data.SqlClient.SqlTransaction.Commit%2A?displayProperty=nameWithType>. For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels).
+> After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A?displayProperty=nameWithType> followed immediately by <xref:System.Data.SqlClient.SqlTransaction.Commit%2A?displayProperty=nameWithType>. For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels).
 
  For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql).
 
@@ -668,7 +668,7 @@ using (SqlConnection connection = new SqlConnection(connectionString))
  You must explicitly commit or roll back the transaction using the <xref:System.Data.SqlClient.SqlTransaction.Commit%2A> or <xref:System.Data.SqlClient.SqlTransaction.Rollback%2A> method. To make sure that the SQL Server transaction management model performs correctly, avoid using other transaction management models, such as the one provided by SQL Server.
 
 > [!NOTE]
->  After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the [!INCLUDE[tsql](~/includes/tsql-md.md)] SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A?displayProperty=nameWithType> followed immediately by <xref:System.Data.SqlClient.SqlTransaction.Commit%2A?displayProperty=nameWithType>. For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels).
+>  After a transaction is committed or rolled back, the isolation level of the transaction persists for all subsequent commands that are in autocommit mode (the SQL Server default). This can produce unexpected results, such as an isolation level of REPEATABLE READ persisting and locking other users out of a row. To reset the isolation level to the default (READ COMMITTED), execute the Transact-SQL SET TRANSACTION ISOLATION LEVEL READ COMMITTED statement, or call <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A?displayProperty=nameWithType> followed immediately by <xref:System.Data.SqlClient.SqlTransaction.Commit%2A?displayProperty=nameWithType>. For more information on SQL Server isolation levels, see [Transaction Isolation Levels](/sql/t-sql/language-elements/transaction-isolation-levels).
 
  For more information on SQL Server transactions, see [Transactions (Transact-SQL)](/sql/t-sql/language-elements/transactions-transact-sql).
 
@@ -1124,7 +1124,7 @@ The connection string contains <see langword="Context Connection=true" />.
  The <xref:System.Data.SqlClient.SqlConnection.Close%2A> method rolls back any pending transactions. It then releases the connection to the connection pool, or closes the connection if connection pooling is disabled.
 
 > [!NOTE]
->  Pending transactions started using [!INCLUDE[tsql](~/includes/tsql-md.md)] or <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A> are automatically rolled back when the connection is reset if connection pooling is enabled. If connection pooling is off, the transaction is rolled back after `SqlConnection.Close` is called. Transactions started through <xref:System.Transactions> are controlled through the `System.Transactions` infrastructure, and are not affected by `SqlConnection.Close`.
+>  Pending transactions started using Transact-SQL or <xref:System.Data.SqlClient.SqlConnection.BeginTransaction%2A> are automatically rolled back when the connection is reset if connection pooling is enabled. If connection pooling is off, the transaction is rolled back after `SqlConnection.Close` is called. Transactions started through <xref:System.Transactions> are controlled through the `System.Transactions` infrastructure, and are not affected by `SqlConnection.Close`.
 
  An application can call <xref:System.Data.SqlClient.SqlConnection.Close%2A> more than one time. No exception is generated.
 
@@ -1750,7 +1750,7 @@ The connection string contains <see langword="Context Connection=true" />.
           <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The <xref:System.Data.SqlClient.SqlConnection.Database%2A> property updates dynamically. If you change the current database using a [!INCLUDE[tsql](~/includes/tsql-md.md)] statement or the <xref:System.Data.SqlClient.SqlConnection.ChangeDatabase%2A> method, an informational message is sent and the property is updated automatically.
+ The <xref:System.Data.SqlClient.SqlConnection.Database%2A> property updates dynamically. If you change the current database using a Transact-SQL statement or the <xref:System.Data.SqlClient.SqlConnection.ChangeDatabase%2A> method, an informational message is sent and the property is updated automatically.
 
 
 
@@ -2140,7 +2140,7 @@ The connection string contains <see langword="Context Connection=true" />.
 
 -   Gets schema information of the database, tables, and some columns.
 
- Before you run the sample, you need to create the sample database, using the following [!INCLUDE[tsql](~/includes/tsql-md.md)]:
+ Before you run the sample, you need to create the sample database, using the following Transact-SQL:
 
 ```
 USE [master]
diff --git a/xml/System.Data.SqlClient/SqlDataReader.xml b/xml/System.Data.SqlClient/SqlDataReader.xml
index 638e5b45cf4..5fc4f137bf4 100644
--- a/xml/System.Data.SqlClient/SqlDataReader.xml
+++ b/xml/System.Data.SqlClient/SqlDataReader.xml
@@ -3952,7 +3952,7 @@ This member is an explicit interface member implementation. It can be used only
       </Parameters>
       <Docs>
         <param name="cancellationToken">The cancellation instruction.</param>
-        <summary>An asynchronous version of <see cref="M:System.Data.SqlClient.SqlDataReader.NextResult" />, which advances the data reader to the next result, when reading the results of batch [!INCLUDE[tsql](~/includes/tsql-md.md)] statements.  
+        <summary>An asynchronous version of <see cref="M:System.Data.SqlClient.SqlDataReader.NextResult" />, which advances the data reader to the next result, when reading the results of batch Transact-SQL statements.  
   
  The cancellation token can be used to request that the operation be abandoned before the command timeout elapses.  Exceptions will be reported via the returned Task object.</summary>
         <returns>A task representing the asynchronous operation.</returns>

From 960802292734bcfede2c54bd004ceea5e84f275a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:19:30 -0800
Subject: [PATCH 187/236] vbprvbext

---
 .../TypeForwardedToAttribute.xml                                | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml b/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
index 57a6dc30f53..5cb2cfb18e3 100644
--- a/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
+++ b/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
@@ -49,7 +49,7 @@
 ## Remarks  
  Use the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to move a type from one assembly to another without disrupting callers that compiled against the old assembly.  
   
- **Note** [!INCLUDE[vbprvbext](~/includes/vbprvbext-md.md)] does not support the use of the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to forward types written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)]. Applications written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] can use forwarded types written in other languages.  
+ **Note** Microsoft Visual Basic 2005 does not support the use of the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to forward types written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)]. Applications written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] can use forwarded types written in other languages.  
   
  ]]></format>
     </remarks>

From a2f48c85c52f7b67e675fbf0737e1469fab432fa Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:19:55 -0800
Subject: [PATCH 188/236] vbprvblong

---
 .../WindowsFormsApplicationBase.xml                |  4 ++--
 .../TypeForwardedToAttribute.xml                   |  2 +-
 xml/System.Runtime.InteropServices/Marshal.xml     |  2 +-
 xml/System.Windows.Forms/Application.xml           |  2 +-
 xml/System/Type.xml                                | 14 +++++++-------
 5 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/Microsoft.VisualBasic.ApplicationServices/WindowsFormsApplicationBase.xml b/xml/Microsoft.VisualBasic.ApplicationServices/WindowsFormsApplicationBase.xml
index fac8e3b7687..38b8d8096e9 100644
--- a/xml/Microsoft.VisualBasic.ApplicationServices/WindowsFormsApplicationBase.xml
+++ b/xml/Microsoft.VisualBasic.ApplicationServices/WindowsFormsApplicationBase.xml
@@ -1673,12 +1673,12 @@
       <Docs>
         <summary>When overridden in a derived class, this property allows a designer to specify the default text rendering engine for the application's forms.</summary>
         <value>
-          <see langword="Boolean" />. A value of <see langword="False" /> indicates that the application should use the default text rendering engine for [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)]. A value of <see langword="True" /> indicates that the application should use the text rendering engine for Visual Basic .NET 2002 and Visual Basic .NET 2003.</value>
+          <see langword="Boolean" />. A value of <see langword="False" /> indicates that the application should use the default text rendering engine for Visual Basic 2005. A value of <see langword="True" /> indicates that the application should use the text rendering engine for Visual Basic .NET 2002 and Visual Basic .NET 2003.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, this property returns `False` to indicate that the GDI text rendering engine for [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] be used for the application's forms. However, you can override this property to return `True` and specify that the application's forms use the GDI+ text rendering engine, which is used in Visual Basic .NET 2002 and Visual Basic .NET 2003.  
+ By default, this property returns `False` to indicate that the GDI text rendering engine for Visual Basic 2005 be used for the application's forms. However, you can override this property to return `True` and specify that the application's forms use the GDI+ text rendering engine, which is used in Visual Basic .NET 2002 and Visual Basic .NET 2003.  
   
  This property is called by the <xref:Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase> constructor.  
   
diff --git a/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml b/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
index 5cb2cfb18e3..ca045baa7f4 100644
--- a/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
+++ b/xml/System.Runtime.CompilerServices/TypeForwardedToAttribute.xml
@@ -49,7 +49,7 @@
 ## Remarks  
  Use the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to move a type from one assembly to another without disrupting callers that compiled against the old assembly.  
   
- **Note** Microsoft Visual Basic 2005 does not support the use of the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to forward types written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)]. Applications written in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] can use forwarded types written in other languages.  
+ **Note** Microsoft Visual Basic 2005 does not support the use of the <xref:System.Runtime.CompilerServices.TypeForwardedToAttribute> attribute to forward types written in Visual Basic 2005. Applications written in Visual Basic 2005 can use forwarded types written in other languages.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Runtime.InteropServices/Marshal.xml b/xml/System.Runtime.InteropServices/Marshal.xml
index ad130c478bb..5305ed761b8 100644
--- a/xml/System.Runtime.InteropServices/Marshal.xml
+++ b/xml/System.Runtime.InteropServices/Marshal.xml
@@ -470,7 +470,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Runtime.InteropServices.Marshal.BindToMoniker%2A> exposes the COM `BindToMoniker` method, which produces an object that you can cast to any COM interface you require. This method provides the same functionality as the `GetObject` method in Visual Basic 6.0 and [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)].  
+ <xref:System.Runtime.InteropServices.Marshal.BindToMoniker%2A> exposes the COM `BindToMoniker` method, which produces an object that you can cast to any COM interface you require. This method provides the same functionality as the `GetObject` method in Visual Basic 6.0 and Visual Basic 2005.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Forms/Application.xml b/xml/System.Windows.Forms/Application.xml
index 9ba7e6c47c0..9b1c105fe62 100644
--- a/xml/System.Windows.Forms/Application.xml
+++ b/xml/System.Windows.Forms/Application.xml
@@ -1522,7 +1522,7 @@
 ## Examples  
   
 > [!IMPORTANT]
->  To set the default value for `UseCompatibleTextRendering` in [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)] or later, see <xref:Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.UseCompatibleTextRendering%2A?displayProperty=nameWithType>.  
+>  To set the default value for `UseCompatibleTextRendering` in Visual Basic 2005 or later, see <xref:Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.UseCompatibleTextRendering%2A?displayProperty=nameWithType>.  
   
  In Visual C# 2005 or later, a call to <xref:System.Windows.Forms.Application.SetCompatibleTextRenderingDefault%2A> is automatically generated in the Program.cs file. To change the text rendering default, modify the generated code.  
   
diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 91434971bd6..431e3211d9f 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -7059,7 +7059,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, by using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, use the <xref:System.Type.GetProperty%28System.String%2CSystem.Reflection.BindingFlags%29> method overload and add the <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> flag to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7181,7 +7181,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, include <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7274,7 +7274,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7370,7 +7370,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7475,7 +7475,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7575,7 +7575,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7736,7 +7736,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- [!INCLUDE[vbprvblong](~/includes/vbprvblong-md.md)], Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   

From 0ef17bfa5fdfafe6f6f30171020ec293862e9b4b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:21:31 -0800
Subject: [PATCH 189/236] vbtecdlinq

---
 .../ColumnAttribute.xml                       | 18 +++++++-------
 xml/System.Data.Linq.Mapping/MetaModel.xml    |  2 +-
 .../ProviderAttribute.xml                     |  6 ++---
 .../TableAttribute.xml                        |  6 ++---
 xml/System.Data.Linq/ChangeAction.xml         |  2 +-
 xml/System.Data.Linq/DataContext.xml          | 24 +++++++++----------
 xml/System.Data.Linq/Link`1.xml               |  2 +-
 xml/System.Data.Linq/Table`1.xml              |  8 +++----
 xml/System.Linq.Expressions/Expression`1.xml  |  2 +-
 xml/ns-System.Data.Linq.xml                   |  2 +-
 10 files changed, 36 insertions(+), 36 deletions(-)

diff --git a/xml/System.Data.Linq.Mapping/ColumnAttribute.xml b/xml/System.Data.Linq.Mapping/ColumnAttribute.xml
index 43a969314f8..e98acf3293b 100644
--- a/xml/System.Data.Linq.Mapping/ColumnAttribute.xml
+++ b/xml/System.Data.Linq.Mapping/ColumnAttribute.xml
@@ -28,7 +28,7 @@
 ## Remarks  
  Use this attribute to designate a member of an entity class to represent a column in a database table. You can apply this attribute to any field or property that is `public`, `private`, or `internal`.  
   
- Only those entity class members identified as columns are persisted when [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] saves changes to the database.  
+ Only those entity class members identified as columns are persisted when LINQ to SQL saves changes to the database.  
   
  Use commas to separate multiple properties on the attribute.  
   
@@ -277,7 +277,7 @@ public class Employees
  For example, if you want to create a column defined in SQL as `InventoryVal AS UnitPrice * UnitsInStock`, use the following *expression* string: `"UnitPrice * UnitsInStock"`.  
   
 > [!NOTE]
->  [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not support computed columns as primary keys.  
+>  LINQ to SQL does not support computed columns as primary keys.  
   
    
   
@@ -364,7 +364,7 @@ public class Employees
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets whether a column contains a discriminator value for a [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] inheritance hierarchy.</summary>
+        <summary>Gets or sets whether a column contains a discriminator value for a LINQ to SQL inheritance hierarchy.</summary>
         <value>Default = <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -417,12 +417,12 @@ public class Employees
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Assuming an entity class, you must provide at least one member with this attribute, and it must be mapped to the primary key or a unique key in the corresponding table or view. Failure to do this prompts [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] to consider instances of the class as read-only for submitting changes to the database.  
+ Assuming an entity class, you must provide at least one member with this attribute, and it must be mapped to the primary key or a unique key in the corresponding table or view. Failure to do this prompts LINQ to SQL to consider instances of the class as read-only for submitting changes to the database.  
   
  If you designate more than one member of the class by using this property, the key is said to be a composite of the associated columns.  
   
 > [!NOTE]
->  [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not support computed columns as primary keys.  
+>  LINQ to SQL does not support computed columns as primary keys.  
   
    
   
@@ -467,11 +467,11 @@ public class Employees
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Version numbers are incremented and timestamp columns are updated every time that the associated row is updated. (This property tells [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] that a column should be updated to show that it is a new version; it is not meant to record information such as who made the update.)  
+ Version numbers are incremented and timestamp columns are updated every time that the associated row is updated. (This property tells LINQ to SQL that a column should be updated to show that it is a new version; it is not meant to record information such as who made the update.)  
   
  Note the following when `IsVersion` is true:  
   
--   Use <xref:System.Data.Linq.Mapping.ColumnAttribute.DbType%2A> to specify the correct modifiers to designate a version number or timestamp column. If you do not specify <xref:System.Data.Linq.Mapping.ColumnAttribute.DbType%2A>, [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] infers the correct modifiers.  
+-   Use <xref:System.Data.Linq.Mapping.ColumnAttribute.DbType%2A> to specify the correct modifiers to designate a version number or timestamp column. If you do not specify <xref:System.Data.Linq.Mapping.ColumnAttribute.DbType%2A>, LINQ to SQL infers the correct modifiers.  
   
  Version numbers are incremented and timestamp columns are updated every time that the associated row is updated. Members with `IsVersion=true` are synchronized immediately after the data row is updated. The new values are visible after <xref:System.Data.Linq.DataContext.SubmitChanges%2A> finishes.  
   
@@ -512,7 +512,7 @@ public class Employees
         <ReturnType>System.Data.Linq.Mapping.UpdateCheck</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets how [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] approaches the detection of optimistic concurrency conflicts.</summary>
+        <summary>Gets or sets how LINQ to SQL approaches the detection of optimistic concurrency conflicts.</summary>
         <value>Default = <see cref="F:System.Data.Linq.Mapping.UpdateCheck.Always" />, unless <see cref="P:System.Data.Linq.Mapping.ColumnAttribute.IsVersion" /> is <see langword="true" /> for a member.  
   
  Other values are <see cref="F:System.Data.Linq.Mapping.UpdateCheck.Never" /> and <see cref="F:System.Data.Linq.Mapping.UpdateCheck.WhenChanged" />.</value>
@@ -520,7 +520,7 @@ public class Employees
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When this property is used with one of three enums, it determines how [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] detects concurrency conflicts.  
+ When this property is used with one of three enums, it determines how LINQ to SQL detects concurrency conflicts.  
   
  If no member is designed as `IsVersion=true`, original member values are compared with the current database state.  
   
diff --git a/xml/System.Data.Linq.Mapping/MetaModel.xml b/xml/System.Data.Linq.Mapping/MetaModel.xml
index 5b13b7abc9c..05af40642a7 100644
--- a/xml/System.Data.Linq.Mapping/MetaModel.xml
+++ b/xml/System.Data.Linq.Mapping/MetaModel.xml
@@ -257,7 +257,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this property is specified, an existing provider type can be used. This will eliminate a round trip to the server to obtain this information. [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] has to know the provider type to establish appropriate query translation rules. [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] supports <xref:System.Data.Linq.SqlClient.Sql2000Provider> and <xref:System.Data.Linq.SqlClient.Sql2005Provider> providers.  
+ If this property is specified, an existing provider type can be used. This will eliminate a round trip to the server to obtain this information. LINQ to SQL has to know the provider type to establish appropriate query translation rules. LINQ to SQL supports <xref:System.Data.Linq.SqlClient.Sql2000Provider> and <xref:System.Data.Linq.SqlClient.Sql2005Provider> providers.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Linq.Mapping/ProviderAttribute.xml b/xml/System.Data.Linq.Mapping/ProviderAttribute.xml
index 3e73ab6165b..34f913fe586 100644
--- a/xml/System.Data.Linq.Mapping/ProviderAttribute.xml
+++ b/xml/System.Data.Linq.Mapping/ProviderAttribute.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
+ LINQ to SQL supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
   
  ]]></format>
     </remarks>
@@ -94,7 +94,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
+ LINQ to SQL supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
   
  ]]></format>
         </remarks>
@@ -129,7 +129,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
+ LINQ to SQL supports <xref:System.Data.Linq.SqlClient.Sql2000Provider>, <xref:System.Data.Linq.SqlClient.Sql2005Provider>, and <xref:System.Data.Linq.SqlClient.Sql2008Provider> providers. These are subclasses of <xref:System.Data.Linq.SqlClient.SqlProvider>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Linq.Mapping/TableAttribute.xml b/xml/System.Data.Linq.Mapping/TableAttribute.xml
index 008ae9e5156..8e35292e414 100644
--- a/xml/System.Data.Linq.Mapping/TableAttribute.xml
+++ b/xml/System.Data.Linq.Mapping/TableAttribute.xml
@@ -26,14 +26,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this attribute to designate a class as an entity class that is associated with a database table or view. [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] treats classes that have the <xref:System.Data.Linq.Mapping.TableAttribute> attribute as persistent classes.  
+ Use this attribute to designate a class as an entity class that is associated with a database table or view. LINQ to SQL treats classes that have the <xref:System.Data.Linq.Mapping.TableAttribute> attribute as persistent classes.  
   
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] supports only single-table mapping. That is, an entity class must be mapped to exactly one database table, and you cannot map a database table to multiple classes at the same time.  
+ LINQ to SQL supports only single-table mapping. That is, an entity class must be mapped to exactly one database table, and you cannot map a database table to multiple classes at the same time.  
   
  You can use the <xref:System.Data.Linq.Mapping.TableAttribute.Name%2A> property of the <xref:System.Data.Linq.Mapping.TableAttribute> attribute to specify a name for the table, and you can optionally use the schema name to qualify a table name. If you do not specify a name by using the <xref:System.Data.Linq.Mapping.TableAttribute.Name%2A> property, the table name is assumed to be the same as the class name.  
   
 ## Schema-qualified Names  
- You can optionally use the schema name to qualify a table name. By default, the token to the left of the first period in the <xref:System.Data.Linq.Mapping.TableAttribute.Name%2A> string is considered to be the schema name. The remainder of the name is considered to be the table name. The provider quotes the table name as appropriate. For example, the [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] provider for SQL Server makes sure that brackets are used at least where they are needed.  
+ You can optionally use the schema name to qualify a table name. By default, the token to the left of the first period in the <xref:System.Data.Linq.Mapping.TableAttribute.Name%2A> string is considered to be the schema name. The remainder of the name is considered to be the table name. The provider quotes the table name as appropriate. For example, the LINQ to SQL provider for SQL Server makes sure that brackets are used at least where they are needed.  
   
 > [!NOTE]
 >  In some cases, you must explicitly quote attributes because the SQL Server provider cannot auto-quote. The following table shows some examples.  
diff --git a/xml/System.Data.Linq/ChangeAction.xml b/xml/System.Data.Linq/ChangeAction.xml
index d30c5b34357..dcddb987c79 100644
--- a/xml/System.Data.Linq/ChangeAction.xml
+++ b/xml/System.Data.Linq/ChangeAction.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use with `OnValidate()` in [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] applications to specify or omit validation based on the type of change being submitted.  
+ Use with `OnValidate()` in LINQ to SQL applications to specify or omit validation based on the type of change being submitted.  
   
    
   
diff --git a/xml/System.Data.Linq/DataContext.xml b/xml/System.Data.Linq/DataContext.xml
index f1e04728daa..f67b7536b35 100644
--- a/xml/System.Data.Linq/DataContext.xml
+++ b/xml/System.Data.Linq/DataContext.xml
@@ -26,7 +26,7 @@
 ## Remarks  
  The <xref:System.Data.Linq.DataContext> is the source of all entities mapped over a database connection. It tracks changes that you made to all retrieved entities and maintains an "identity cache" that guarantees that entities retrieved more than one time are represented by using the same object instance.  
   
- In general, a <xref:System.Data.Linq.DataContext> instance is designed to last for one "unit of work" however your application defines that term. A <xref:System.Data.Linq.DataContext> is lightweight and is not expensive to create. A typical [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] application creates <xref:System.Data.Linq.DataContext> instances at method scope or as a member of short-lived classes that represent a logical set of related database operations.  
+ In general, a <xref:System.Data.Linq.DataContext> instance is designed to last for one "unit of work" however your application defines that term. A <xref:System.Data.Linq.DataContext> is lightweight and is not expensive to create. A typical LINQ to SQL application creates <xref:System.Data.Linq.DataContext> instances at method scope or as a member of short-lived classes that represent a logical set of related database operations.  
   
  ]]></format>
     </remarks>
@@ -118,7 +118,7 @@
   
  The name of a server where a database is present. In this case the provider uses the default database for a user.  
   
- A complete connection string. [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] just passes the string to the provider without modification.</param>
+ A complete connection string. LINQ to SQL just passes the string to the provider without modification.</param>
         <param name="mapping">A source for mapping.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Data.Linq.DataContext" /> class by referencing a file source and a mapping source.</summary>
         <remarks>To be added.</remarks>
@@ -577,7 +577,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is a pass-through mechanism for cases where [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not adequately provide for a particular scenario.  
+ This method is a pass-through mechanism for cases where LINQ to SQL does not adequately provide for a particular scenario.  
   
  The syntax for the command is almost the same as the syntax used to create an ADO.NET `DataCommand`. The only difference is in how the parameters are specified. Specifically, you specify parameters by enclosing them in braces ({…}) and enumerate them starting from 0. The parameter is associated with the equally numbered object in the parameters array.  
   
@@ -633,7 +633,7 @@ The following example opens a connection and passes a SQL `UPDATE` command to th
       </Parameters>
       <Docs>
         <param name="entity">The entity to be deleted.</param>
-        <summary>Executes, inside delete override methods, to redelegate to [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] the task of generating and executing dynamic SQL for delete operations.</summary>
+        <summary>Executes, inside delete override methods, to redelegate to LINQ to SQL the task of generating and executing dynamic SQL for delete operations.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -665,7 +665,7 @@ The following example opens a connection and passes a SQL `UPDATE` command to th
       </Parameters>
       <Docs>
         <param name="entity">The entity to be inserted.</param>
-        <summary>Executes, inside insert override methods, to redelegate to [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] the task of generating and executing dynamic SQL for insert operations.</summary>
+        <summary>Executes, inside insert override methods, to redelegate to LINQ to SQL the task of generating and executing dynamic SQL for insert operations.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -678,7 +678,7 @@ The following example opens a connection and passes a SQL `UPDATE` command to th
   
 -   It is the responsibility of the developer to pass in the correct entity. The implementation verifies that the passed-in entity is tracked. However, it is the responsibility of the developer to maintain the order or pass in the same entity two times.  
   
--   It is the responsibility of the developer to invoke the correct dynamic API. For example, in the `Update` override method, only the <xref:System.Data.Linq.DataContext.ExecuteDynamicUpdate%2A> method can be called. [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not detect or verify whether the invoked dynamic method matches the applicable operation. The results are undefined if an inapplicable method is called (for example, calling <xref:System.Data.Linq.DataContext.ExecuteDynamicDelete%2A> for an object to be updated).  
+-   It is the responsibility of the developer to invoke the correct dynamic API. For example, in the `Update` override method, only the <xref:System.Data.Linq.DataContext.ExecuteDynamicUpdate%2A> method can be called. LINQ to SQL does not detect or verify whether the invoked dynamic method matches the applicable operation. The results are undefined if an inapplicable method is called (for example, calling <xref:System.Data.Linq.DataContext.ExecuteDynamicDelete%2A> for an object to be updated).  
   
  ]]></format>
         </remarks>
@@ -705,7 +705,7 @@ The following example opens a connection and passes a SQL `UPDATE` command to th
       </Parameters>
       <Docs>
         <param name="entity">The entity to be updated.</param>
-        <summary>Executes, inside update override methods, to redelegate to [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] the task of generating and executing dynamic SQL for update operations.</summary>
+        <summary>Executes, inside update override methods, to redelegate to LINQ to SQL the task of generating and executing dynamic SQL for update operations.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -876,7 +876,7 @@ The following example opens a connection and passes a SQL `UPDATE` command to th
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method is a pass-through mechanism for cases where [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not provide for a particular scenario.  
+ This method is a pass-through mechanism for cases where LINQ to SQL does not provide for a particular scenario.  
   
  The algorithm for matching columns in the result of the query to fields and properties in the object works as follows:  
   
@@ -1001,7 +1001,7 @@ Next
       </Parameters>
       <Docs>
         <param name="query">The query whose SQL command information is to be retrieved.</param>
-        <summary>Gets the information about SQL commands generated by [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)].</summary>
+        <summary>Gets the information about SQL commands generated by LINQ to SQL.</summary>
         <returns>The requested command information object.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1013,7 +1013,7 @@ Next
   
 -   The argument must be non-null. Otherwise, a null argument exception is thrown.  
   
--   Normal query translation exceptions thrown during [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] query execution apply for a query that cannot be translated.  
+-   Normal query translation exceptions thrown during LINQ to SQL query execution apply for a query that cannot be translated.  
   
 -   Only the first query command is returned. Specifically, additional commands that are used for eager loading (<xref:System.Data.Linq.DataLoadOptions.LoadWith%2A>) are not included.  
   
@@ -1399,7 +1399,7 @@ Next
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If override methods are present for insert, update, or delete, <xref:System.Data.Linq.DataContext.SubmitChanges%2A> executes these methods instead of the default [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] commands.  
+ If override methods are present for insert, update, or delete, <xref:System.Data.Linq.DataContext.SubmitChanges%2A> executes these methods instead of the default LINQ to SQL commands.  
   
  <xref:System.Data.Linq.DataContext.SubmitChanges%2A> starts a transaction and will roll back if an exception occurs while <xref:System.Data.Linq.DataContext.SubmitChanges%2A> is executing. However, this does not roll back the changes in memory or tracked by the <xref:System.Data.Linq.DataContext>; those changes will need to be rolled back manually. You can start with a new instance of the <xref:System.Data.Linq.DataContext> if the changes in memory are to be discarded.  
   
@@ -1430,7 +1430,7 @@ Next
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If override methods are present for insert, update, or delete, <xref:System.Data.Linq.DataContext.SubmitChanges%2A> executes these methods instead of the default [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] commands.  
+ If override methods are present for insert, update, or delete, <xref:System.Data.Linq.DataContext.SubmitChanges%2A> executes these methods instead of the default LINQ to SQL commands.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Linq/Link`1.xml b/xml/System.Data.Linq/Link`1.xml
index 27524737146..461a9740d50 100644
--- a/xml/System.Data.Linq/Link`1.xml
+++ b/xml/System.Data.Linq/Link`1.xml
@@ -147,7 +147,7 @@
 ## Remarks  
  "Loaded" means that the data was loaded during materialization or at deferred loading. "Assigned" means that you have manually given the data a value.  
   
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] uses this property to make sure that the <xref:System.Data.Linq.Link%601> has a value, so that accessing it will not trigger deferred loading.  
+ LINQ to SQL uses this property to make sure that the <xref:System.Data.Linq.Link%601> has a value, so that accessing it will not trigger deferred loading.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Data.Linq/Table`1.xml b/xml/System.Data.Linq/Table`1.xml
index 6118eab6ae9..abd9559206f 100644
--- a/xml/System.Data.Linq/Table`1.xml
+++ b/xml/System.Data.Linq/Table`1.xml
@@ -382,12 +382,12 @@ End Using
    
   
 ## Examples  
- The following example shows how you can update an `Order` object on a different <xref:System.Data.Linq.DataContext> instance. The example assumes that you have a connection to a database and have made a [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] file for it (in this case, the Northwind sample database).  
+ The following example shows how you can update an `Order` object on a different <xref:System.Data.Linq.DataContext> instance. The example assumes that you have a connection to a database and have made a LINQ to SQL file for it (in this case, the Northwind sample database).  
   
  [!code-csharp[DLinqNTier#1](~/samples/snippets/csharp/VS_Snippets_Data/DLinqNTier/cs/Program.cs#1)]
  [!code-vb[DLinqNTier#1](~/samples/snippets/visualbasic/VS_Snippets_Data/DLinqNTier/vb/Module1.vb#1)]  
   
- In the following example, an entity object to be attached has a foreign key relation with another object and is stored in the cache but not attached. When you call <xref:System.Data.Linq.DataContext.SubmitChanges%2A>, the `ChangeProcessor` adds an `Insert` operation for all the foreign key objects. This is a side-effect when an entity instance is re-used in a different <xref:System.Data.Linq.DataContext> instance. For this reason, [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not support re-use of objects.  
+ In the following example, an entity object to be attached has a foreign key relation with another object and is stored in the cache but not attached. When you call <xref:System.Data.Linq.DataContext.SubmitChanges%2A>, the `ChangeProcessor` adds an `Insert` operation for all the foreign key objects. This is a side-effect when an entity instance is re-used in a different <xref:System.Data.Linq.DataContext> instance. For this reason, LINQ to SQL does not support re-use of objects.  
   
  [!code-csharp[DlinqNTier#7](~/samples/snippets/csharp/VS_Snippets_Data/DLinqNTier/cs/Program.cs#7)]
  [!code-vb[DlinqNTier#7](~/samples/snippets/visualbasic/VS_Snippets_Data/DLinqNTier/vb/Module1.vb#7)]  
@@ -529,7 +529,7 @@ db.SubmitChanges()
  The removed entity does not disappear from the query results until after <xref:System.Data.Linq.DataContext.SubmitChanges%2A> is called. Disconnected entities must first be attached before they can be deleted. For more information, see [Data Retrieval and CUD Operations in N-Tier Applications (LINQ to SQL)](/dotnet/framework/data/adonet/sql/linq/data-retrieval-and-cud-operations-in-n-tier-applications).  
   
 > [!NOTE]
->  [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not support or recognize cascade-delete operations. If you want to delete a row in a table that has constraints against it, you must either set the `ON DELETE CASCADE` rule in the foreign-key constraint in the database, or use your own code to first delete the child objects that prevent the parent object from being deleted. Otherwise, an exception is thrown.  
+>  LINQ to SQL does not support or recognize cascade-delete operations. If you want to delete a row in a table that has constraints against it, you must either set the `ON DELETE CASCADE` rule in the foreign-key constraint in the database, or use your own code to first delete the child objects that prevent the parent object from being deleted. Otherwise, an exception is thrown.  
   
    
   
@@ -1171,7 +1171,7 @@ db.SubmitChanges()
  This member is an explicit interface member implementation. It can be used only when the <xref:System.Data.Linq.Table%601> instance is cast to an <xref:System.Data.Linq.ITable> interface.  
   
 > [!NOTE]
->  [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] does not support or recognize cascade-delete operations. If you want to delete a row in a table that has constraints against it, you must either set the `ON DELETE CASCADE` rule in the foreign-key constraint in the database, or use your own code to first delete the child objects that prevent the parent object from being deleted. Otherwise, an exception is thrown.  
+>  LINQ to SQL does not support or recognize cascade-delete operations. If you want to delete a row in a table that has constraints against it, you must either set the `ON DELETE CASCADE` rule in the foreign-key constraint in the database, or use your own code to first delete the child objects that prevent the parent object from being deleted. Otherwise, an exception is thrown.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Linq.Expressions/Expression`1.xml b/xml/System.Linq.Expressions/Expression`1.xml
index 064bdf6ae33..62d2864df52 100644
--- a/xml/System.Linq.Expressions/Expression`1.xml
+++ b/xml/System.Linq.Expressions/Expression`1.xml
@@ -51,7 +51,7 @@
   
  The expression tree is an in-memory data representation of the lambda expression. The expression tree makes the structure of the lambda expression transparent and explicit. You can interact with the data in the expression tree just as you can with any other data structure.  
   
- The ability to treat expressions as data structures enables APIs to receive user code in a format that can be inspected, transformed, and processed in a custom manner. For example, the [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] data access implementation uses this facility to translate expression trees to Transact-SQL statements that can be evaluated by the database.  
+ The ability to treat expressions as data structures enables APIs to receive user code in a format that can be inspected, transformed, and processed in a custom manner. For example, the LINQ to SQL data access implementation uses this facility to translate expression trees to Transact-SQL statements that can be evaluated by the database.  
   
  Many standard query operators defined in the <xref:System.Linq.Queryable> class have one or more parameters of type <xref:System.Linq.Expressions.Expression%601>.  
   
diff --git a/xml/ns-System.Data.Linq.xml b/xml/ns-System.Data.Linq.xml
index 8c2b45e94d9..42884c3c47a 100644
--- a/xml/ns-System.Data.Linq.xml
+++ b/xml/ns-System.Data.Linq.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- [!INCLUDE[vbtecdlinq](~/includes/vbtecdlinq-md.md)] is a technology that provides a run-time infrastructure for managing relational data as objects. For more information, see [LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/).
+ LINQ to SQL is a technology that provides a run-time infrastructure for managing relational data as objects. For more information, see [LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/).
 
  ]]></format>
     </remarks>

From 0045b52dea2c05bdd4f969d47b515c2bac3e979d Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:22:03 -0800
Subject: [PATCH 190/236] vbteclinq

---
 .../InheritanceMappingAttribute.xml                |  2 +-
 xml/System.Data/DataTableExtensions.xml            |  4 ++--
 xml/System.Data/DataView.xml                       |  2 +-
 xml/System.Data/TypedTableBaseExtensions.xml       |  2 +-
 xml/System.Linq/Enumerable.xml                     |  2 +-
 xml/System.Linq/IQueryProvider.xml                 | 14 +++++++-------
 xml/System.Linq/IQueryable.xml                     |  4 ++--
 xml/System.Linq/Queryable.xml                      |  4 ++--
 .../ExecutionScope.xml                             |  2 +-
 xml/System.Xml.Linq/Extensions.xml                 |  2 +-
 xml/System.Xml.Linq/XContainer.xml                 | 10 +++++-----
 xml/index.xml                                      |  4 ++--
 xml/ns-System.Linq.xml                             |  4 ++--
 13 files changed, 28 insertions(+), 28 deletions(-)

diff --git a/xml/System.Data.Linq.Mapping/InheritanceMappingAttribute.xml b/xml/System.Data.Linq.Mapping/InheritanceMappingAttribute.xml
index a0d762d06b9..313c4a422e6 100644
--- a/xml/System.Data.Linq.Mapping/InheritanceMappingAttribute.xml
+++ b/xml/System.Data.Linq.Mapping/InheritanceMappingAttribute.xml
@@ -34,7 +34,7 @@
   
 -   The table for an inheritance hierarchy must be declared on the mapped type that is at the top of the hierarchy. You cannot specify the table or mapping attributes in a class that is derived from the top class.  
   
--   You can use an interface in a hierarchy, but [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] does not map it.  
+-   You can use an interface in a hierarchy, but LINQ does not map it.  
   
 -   You can skip a class in the hierarchy when you map classes, but you can query against mapped classes only.  
   
diff --git a/xml/System.Data/DataTableExtensions.xml b/xml/System.Data/DataTableExtensions.xml
index f98807ebc6a..3c3b7f7e440 100644
--- a/xml/System.Data/DataTableExtensions.xml
+++ b/xml/System.Data/DataTableExtensions.xml
@@ -198,13 +198,13 @@
       </Parameters>
       <Docs>
         <param name="source">The source <see cref="T:System.Data.DataTable" /> to make enumerable.</param>
-        <summary>Returns an <see cref="T:System.Collections.Generic.IEnumerable`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression or method query.</summary>
+        <summary>Returns an <see cref="T:System.Collections.Generic.IEnumerable`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a LINQ expression or method query.</summary>
         <returns>An <see cref="T:System.Collections.Generic.IEnumerable`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] queries work on data sources that implement the <xref:System.Collections.Generic.IEnumerable%601> interface or the <xref:System.Linq.IQueryable> interface.  The <xref:System.Data.DataTable> class does not implement either interface, so you must call the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method to use the <xref:System.Data.DataTable> as a source in the `From` clause of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query. You can also obtain custom, domain-specific operators, such as <xref:System.Data.DataTableExtensions.CopyToDataTable%2A>, by returning an <xref:System.Collections.Generic.IEnumerable%601> object.  
+ [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] queries work on data sources that implement the <xref:System.Collections.Generic.IEnumerable%601> interface or the <xref:System.Linq.IQueryable> interface.  The <xref:System.Data.DataTable> class does not implement either interface, so you must call the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method to use the <xref:System.Data.DataTable> as a source in the `From` clause of a LINQ query. You can also obtain custom, domain-specific operators, such as <xref:System.Data.DataTableExtensions.CopyToDataTable%2A>, by returning an <xref:System.Collections.Generic.IEnumerable%601> object.  
   
  The enumerable object returned by the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method is permanently bound to the <xref:System.Data.DataTable> that produced it. Multiple calls to the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method will return multiple, independent queryable objects that are all bound to the source <xref:System.Data.DataTable>.  
   
diff --git a/xml/System.Data/DataView.xml b/xml/System.Data/DataView.xml
index e8b4e9fafe2..5f88ccfec75 100644
--- a/xml/System.Data/DataView.xml
+++ b/xml/System.Data/DataView.xml
@@ -136,7 +136,7 @@
 > [!NOTE]
 >  If you do not explicitly specify sort criteria for `DataView`, the `DataRowView` objects in `DataView` are sorted based on the index of DataView's corresponding `DataRow` in the `DataTable.Rows` `DataRowCollection`.  
   
- LINQ to DataSet allows developers to create complex, powerful queries over a <xref:System.Data.DataSet> by using [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)]. A LINQ to DataSet query returns an enumeration of <xref:System.Data.DataRow> objects, however, which is not easily used in a binding scenario. <xref:System.Data.DataView> can be created from a LINQ to DataSet query and takes on the filtering and sorting characteristics of that query. LINQ to DataSet extends the functionality of the <xref:System.Data.DataView> by providing [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression-based filtering and sorting, which allows for much more complex and powerful filtering and sorting operations than string-based filtering and sorting. See [Data Binding and LINQ to DataSet](/dotnet/framework/data/adonet/data-binding-and-linq-to-dataset) for more information.  
+ LINQ to DataSet allows developers to create complex, powerful queries over a <xref:System.Data.DataSet> by using LINQ. A LINQ to DataSet query returns an enumeration of <xref:System.Data.DataRow> objects, however, which is not easily used in a binding scenario. <xref:System.Data.DataView> can be created from a LINQ to DataSet query and takes on the filtering and sorting characteristics of that query. LINQ to DataSet extends the functionality of the <xref:System.Data.DataView> by providing LINQ expression-based filtering and sorting, which allows for much more complex and powerful filtering and sorting operations than string-based filtering and sorting. See [Data Binding and LINQ to DataSet](/dotnet/framework/data/adonet/data-binding-and-linq-to-dataset) for more information.  
   
    
   
diff --git a/xml/System.Data/TypedTableBaseExtensions.xml b/xml/System.Data/TypedTableBaseExtensions.xml
index 39be8cac16f..771e8c8ebc1 100644
--- a/xml/System.Data/TypedTableBaseExtensions.xml
+++ b/xml/System.Data/TypedTableBaseExtensions.xml
@@ -86,7 +86,7 @@
       <Docs>
         <typeparam name="TRow">The type to convert the elements of the source to.</typeparam>
         <param name="source">The source <see cref="T:System.Data.TypedTableBase`1" /> to make enumerable.</param>
-        <summary>Enumerates the data row elements of the <see cref="T:System.Data.TypedTableBase`1" /> and returns an <see cref="T:System.Data.EnumerableRowCollection`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression or method query.</summary>
+        <summary>Enumerates the data row elements of the <see cref="T:System.Data.TypedTableBase`1" /> and returns an <see cref="T:System.Data.EnumerableRowCollection`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a LINQ expression or method query.</summary>
         <returns>An <see cref="T:System.Data.EnumerableRowCollection`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Linq/Enumerable.xml b/xml/System.Linq/Enumerable.xml
index 42c2bad6e82..f3e9e0f3e6f 100644
--- a/xml/System.Linq/Enumerable.xml
+++ b/xml/System.Linq/Enumerable.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The methods in this class provide an implementation of the standard query operators for querying data sources that implement <xref:System.Collections.Generic.IEnumerable%601>. The standard query operators are general purpose methods that follow the [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] pattern and enable you to express traversal, filter, and projection operations over data in any .NET-based programming language.  
+ The methods in this class provide an implementation of the standard query operators for querying data sources that implement <xref:System.Collections.Generic.IEnumerable%601>. The standard query operators are general purpose methods that follow the LINQ pattern and enable you to express traversal, filter, and projection operations over data in any .NET-based programming language.  
   
  The majority of the methods in this class are defined as extension methods that extend <xref:System.Collections.Generic.IEnumerable%601>. This means they can be called like an instance method on any object that implements <xref:System.Collections.Generic.IEnumerable%601>.  
   
diff --git a/xml/System.Linq/IQueryProvider.xml b/xml/System.Linq/IQueryProvider.xml
index 3391650fa8d..478821d86fb 100644
--- a/xml/System.Linq/IQueryProvider.xml
+++ b/xml/System.Linq/IQueryProvider.xml
@@ -83,7 +83,7 @@
         <Parameter Name="expression" Type="System.Linq.Expressions.Expression" />
       </Parameters>
       <Docs>
-        <param name="expression">An expression tree that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.</param>
+        <param name="expression">An expression tree that represents a LINQ query.</param>
         <summary>Constructs an <see cref="T:System.Linq.IQueryable" /> object that can evaluate the query represented by a specified expression tree.</summary>
         <returns>An <see cref="T:System.Linq.IQueryable" /> that can evaluate the query represented by the specified expression tree.</returns>
         <remarks>
@@ -96,7 +96,7 @@
   
  The <xref:System.Linq.IQueryProvider.CreateQuery%2A> method is used to create new <xref:System.Linq.IQueryable> objects, given an expression tree. The query that is represented by the returned object is associated with a specific LINQ provider.  
   
- Several of the standard query operator methods defined in <xref:System.Linq.Queryable>, such as <xref:System.Linq.Queryable.OfType%2A> and <xref:System.Linq.Queryable.Cast%2A>, call this method. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.  
+ Several of the standard query operator methods defined in <xref:System.Linq.Queryable>, such as <xref:System.Linq.Queryable.OfType%2A> and <xref:System.Linq.Queryable.Cast%2A>, call this method. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a LINQ query.  
   
  ]]></format>
         </remarks>
@@ -142,7 +142,7 @@
       </Parameters>
       <Docs>
         <typeparam name="TElement">The type of the elements of the <see cref="T:System.Linq.IQueryable`1" /> that is returned.</typeparam>
-        <param name="expression">An expression tree that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.</param>
+        <param name="expression">An expression tree that represents a LINQ query.</param>
         <summary>Constructs an <see cref="T:System.Linq.IQueryable`1" /> object that can evaluate the query represented by a specified expression tree.</summary>
         <returns>An <see cref="T:System.Linq.IQueryable`1" /> that can evaluate the query represented by the specified expression tree.</returns>
         <remarks>
@@ -155,7 +155,7 @@
   
  The <xref:System.Linq.IQueryProvider.CreateQuery%2A> method is used to create new <xref:System.Linq.IQueryable%601> objects, given an expression tree. The query that is represented by the returned object is associated with a specific LINQ provider.  
   
- Most of the <xref:System.Linq.Queryable> standard query operator methods that return enumerable results call this method. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.  
+ Most of the <xref:System.Linq.Queryable> standard query operator methods that return enumerable results call this method. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a LINQ query.  
   
  ]]></format>
         </remarks>
@@ -198,7 +198,7 @@
         <Parameter Name="expression" Type="System.Linq.Expressions.Expression" />
       </Parameters>
       <Docs>
-        <param name="expression">An expression tree that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.</param>
+        <param name="expression">An expression tree that represents a LINQ query.</param>
         <summary>Executes the query represented by a specified expression tree.</summary>
         <returns>The value that results from executing the specified query.</returns>
         <remarks>
@@ -251,7 +251,7 @@
       </Parameters>
       <Docs>
         <typeparam name="TResult">The type of the value that results from executing the query.</typeparam>
-        <param name="expression">An expression tree that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.</param>
+        <param name="expression">An expression tree that represents a LINQ query.</param>
         <summary>Executes the strongly-typed query represented by a specified expression tree.</summary>
         <returns>The value that results from executing the specified query.</returns>
         <remarks>
@@ -260,7 +260,7 @@
 ## Remarks  
  The <xref:System.Linq.IQueryProvider.Execute%2A> method executes queries that return a single value (instead of an enumerable sequence of values). Expression trees that represent queries that return enumerable results are executed when the <xref:System.Linq.IQueryable%601> object that contains the expression tree is enumerated.  
   
- The <xref:System.Linq.Queryable> standard query operator methods that return singleton results call <xref:System.Linq.IQueryProvider.Execute%2A>. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query.  
+ The <xref:System.Linq.Queryable> standard query operator methods that return singleton results call <xref:System.Linq.IQueryProvider.Execute%2A>. They pass it a <xref:System.Linq.Expressions.MethodCallExpression> that represents a LINQ query.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Linq/IQueryable.xml b/xml/System.Linq/IQueryable.xml
index 78eced14e9a..0f24f168bff 100644
--- a/xml/System.Linq/IQueryable.xml
+++ b/xml/System.Linq/IQueryable.xml
@@ -137,7 +137,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If an instance of <xref:System.Linq.IQueryable> represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query against a data source, the associated expression tree represents that query.  
+ If an instance of <xref:System.Linq.IQueryable> represents a LINQ query against a data source, the associated expression tree represents that query.  
   
  ]]></format>
         </remarks>
@@ -182,7 +182,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If an instance of <xref:System.Linq.IQueryable> represents a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query against a data source, the associated query provider is the provider that created the <xref:System.Linq.IQueryable> instance.  
+ If an instance of <xref:System.Linq.IQueryable> represents a LINQ query against a data source, the associated query provider is the provider that created the <xref:System.Linq.IQueryable> instance.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Linq/Queryable.xml b/xml/System.Linq/Queryable.xml
index 4ca77cd790d..2e8a711fb9c 100644
--- a/xml/System.Linq/Queryable.xml
+++ b/xml/System.Linq/Queryable.xml
@@ -37,7 +37,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The set of methods declared in the <xref:System.Linq.Queryable> class provides an implementation of the standard query operators for querying data sources that implement <xref:System.Linq.IQueryable%601>. The standard query operators are general purpose methods that follow the [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] pattern and enable you to express traversal, filter, and projection operations over data in any .NET-based programming language.  
+ The set of methods declared in the <xref:System.Linq.Queryable> class provides an implementation of the standard query operators for querying data sources that implement <xref:System.Linq.IQueryable%601>. The standard query operators are general purpose methods that follow the LINQ pattern and enable you to express traversal, filter, and projection operations over data in any .NET-based programming language.  
   
  The majority of the methods in this class are defined as extension methods that extend the <xref:System.Linq.IQueryable%601> type. This means they can be called like an instance method on any object that implements <xref:System.Linq.IQueryable%601>. These methods that extend <xref:System.Linq.IQueryable%601> do not perform any querying directly. Instead, their functionality is to build an <xref:System.Linq.Expressions.Expression> object, which is an expression tree that represents the cumulative query. The methods then pass the new expression tree to either the <xref:System.Linq.IQueryProvider.Execute%60%601%28System.Linq.Expressions.Expression%29> method or the <xref:System.Linq.IQueryProvider.CreateQuery%60%601%28System.Linq.Expressions.Expression%29> method of the input <xref:System.Linq.IQueryable%601>. The method that is called depends on whether the <xref:System.Linq.Queryable> method returns a singleton value, in which case <xref:System.Linq.IQueryProvider.Execute%60%601%28System.Linq.Expressions.Expression%29> is called, or has enumerable results, in which case <xref:System.Linq.IQueryProvider.CreateQuery%60%601%28System.Linq.Expressions.Expression%29> is called.  
   
@@ -2473,7 +2473,7 @@
    
   
 ## Examples  
- The following code example shows a situation in which it is useful to call <xref:System.Linq.Queryable.DefaultIfEmpty%60%601%28System.Linq.IQueryable%7B%60%600%7D%2C%60%600%29> in a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query. A default value is passed to <xref:System.Linq.Queryable.DefaultIfEmpty%60%601%28System.Linq.IQueryable%7B%60%600%7D%2C%60%600%29> in this example.  
+ The following code example shows a situation in which it is useful to call <xref:System.Linq.Queryable.DefaultIfEmpty%60%601%28System.Linq.IQueryable%7B%60%600%7D%2C%60%600%29> in a LINQ query. A default value is passed to <xref:System.Linq.Queryable.DefaultIfEmpty%60%601%28System.Linq.IQueryable%7B%60%600%7D%2C%60%600%29> in this example.  
   
  [!code-csharp[System.Linq.Queryable#25](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.Linq.Queryable/CS/queryable.cs#25)]
  [!code-vb[System.Linq.Queryable#25](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.Linq.Queryable/VB/queryable.vb#25)]  
diff --git a/xml/System.Runtime.CompilerServices/ExecutionScope.xml b/xml/System.Runtime.CompilerServices/ExecutionScope.xml
index 62a1a0333b9..dd3a04fe533 100644
--- a/xml/System.Runtime.CompilerServices/ExecutionScope.xml
+++ b/xml/System.Runtime.CompilerServices/ExecutionScope.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Runtime.CompilerServices.ExecutionScope> type is used by the expression tree compiler, which is an internal component of the [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression tree API, and by the dynamic methods that it generates.  
+ The <xref:System.Runtime.CompilerServices.ExecutionScope> type is used by the expression tree compiler, which is an internal component of the LINQ expression tree API, and by the dynamic methods that it generates.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Xml.Linq/Extensions.xml b/xml/System.Xml.Linq/Extensions.xml
index 0f4ccfd6c9f..c308e540831 100644
--- a/xml/System.Xml.Linq/Extensions.xml
+++ b/xml/System.Xml.Linq/Extensions.xml
@@ -39,7 +39,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Most of the LINQ to XML extension methods are axis methods that are used in [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] queries. The methods in this class operate on collections and return collections. These methods enumerate the source collection, call the appropriate axis method on each item in the collection, and concatenate the results.  
+ Most of the LINQ to XML extension methods are axis methods that are used in LINQ queries. The methods in this class operate on collections and return collections. These methods enumerate the source collection, call the appropriate axis method on each item in the collection, and concatenate the results.  
   
  The two <xref:System.Xml.Linq.Extensions.Remove%2A> extension methods are not axis methods, however. These methods remove attributes or nodes from the XML tree.  
   
diff --git a/xml/System.Xml.Linq/XContainer.xml b/xml/System.Xml.Linq/XContainer.xml
index 8bc21251290..20535ebb3a2 100644
--- a/xml/System.Xml.Linq/XContainer.xml
+++ b/xml/System.Xml.Linq/XContainer.xml
@@ -181,7 +181,7 @@ Console.WriteLine(xmlTree)
    
   
 ## Examples  
- The following example creates two XML trees, and then uses this method to add an <xref:System.Xml.Linq.XElement> object to one of them. It also adds the results of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query to the XML tree.  
+ The following example creates two XML trees, and then uses this method to add an <xref:System.Xml.Linq.XElement> object to one of them. It also adds the results of a LINQ query to the XML tree.  
   
 ```csharp  
 XElement srcTree = new XElement("Root",  
@@ -328,7 +328,7 @@ Console.WriteLine(xmlTree)
    
   
 ## Examples  
- The following example creates two XML trees, uses this method to add an <xref:System.Xml.Linq.XElement> object to one of them. It also adds the results of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query to the XML tree.  
+ The following example creates two XML trees, uses this method to add an <xref:System.Xml.Linq.XElement> object to one of them. It also adds the results of a LINQ query to the XML tree.  
   
 ```csharp  
 XElement srcTree = new XElement("Root",  
@@ -543,7 +543,7 @@ Console.WriteLine(xmlTree)
    
   
 ## Examples  
- The following example creates two XML trees, uses this method to add an <xref:System.Xml.Linq.XElement> object as the first element to one of them. It also adds the results of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query to the XML tree.  
+ The following example creates two XML trees, uses this method to add an <xref:System.Xml.Linq.XElement> object as the first element to one of them. It also adds the results of a LINQ query to the XML tree.  
   
 ```csharp  
 XElement srcTree = new XElement("Root",  
@@ -689,7 +689,7 @@ Console.WriteLine(xmlTree)
    
   
 ## Examples  
- The following example creates two XML trees, and uses this method to add an <xref:System.Xml.Linq.XElement> object as the first element to one of them. It also adds the results of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query to the XML tree.  
+ The following example creates two XML trees, and uses this method to add an <xref:System.Xml.Linq.XElement> object as the first element to one of them. It also adds the results of a LINQ query to the XML tree.  
   
 ```csharp  
 XElement srcTree = new XElement("Root",  
@@ -2368,7 +2368,7 @@ Console.WriteLine(root)
 ## Examples  
  The following example creates an XML tree that contains children nodes. It then replaces all of the children nodes with a single element.  
   
- To see an example of replacing the children nodes with the results of a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] query, see <xref:System.Xml.Linq.XContainer.ReplaceNodes%2A>.  
+ To see an example of replacing the children nodes with the results of a LINQ query, see <xref:System.Xml.Linq.XContainer.ReplaceNodes%2A>.  
   
 ```csharp  
 XElement root = new XElement("Root",  
diff --git a/xml/index.xml b/xml/index.xml
index 8c4eb41ccf9..d564f9a4fd8 100644
--- a/xml/index.xml
+++ b/xml/index.xml
@@ -224308,7 +224308,7 @@
         </Parameters>
         <Docs>
           <param name="source">The source <see cref="T:System.Data.DataTable" /> to make enumerable.</param>
-          <summary>Returns an <see cref="T:System.Collections.Generic.IEnumerable`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression or method query.</summary>
+          <summary>Returns an <see cref="T:System.Collections.Generic.IEnumerable`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a LINQ expression or method query.</summary>
         </Docs>
         <Link Type="System.Data.DataTableExtensions" Member="M:System.Data.DataTableExtensions.AsEnumerable(System.Data.DataTable)" />
       </Member>
@@ -224842,7 +224842,7 @@
         <Docs>
           <typeparam name="TRow">The type to convert the elements of the source to.</typeparam>
           <param name="source">The source <see cref="T:System.Data.TypedTableBase`1" /> to make enumerable.</param>
-          <summary>Enumerates the data row elements of the <see cref="T:System.Data.TypedTableBase`1" /> and returns an <see cref="T:System.Data.EnumerableRowCollection`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] expression or method query.</summary>
+          <summary>Enumerates the data row elements of the <see cref="T:System.Data.TypedTableBase`1" /> and returns an <see cref="T:System.Data.EnumerableRowCollection`1" /> object, where the generic parameter <paramref name="T" /> is <see cref="T:System.Data.DataRow" />. This object can be used in a LINQ expression or method query.</summary>
         </Docs>
         <Link Type="System.Data.TypedTableBaseExtensions" Member="M:System.Data.TypedTableBaseExtensions.AsEnumerable``1(System.Data.TypedTableBase{``0})" />
       </Member>
diff --git a/xml/ns-System.Linq.xml b/xml/ns-System.Linq.xml
index 9ecdf5e9ea8..67b57f4164a 100644
--- a/xml/ns-System.Linq.xml
+++ b/xml/ns-System.Linq.xml
@@ -7,9 +7,9 @@
 ## Remarks
  The <xref:System.Linq> namespace is in the System.Core assembly (in System.Core.dll).
 
- The <xref:System.Linq.Enumerable> class contains [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] standard query operators that operate on objects that implement <xref:System.Collections.Generic.IEnumerable%601>.
+ The <xref:System.Linq.Enumerable> class contains LINQ standard query operators that operate on objects that implement <xref:System.Collections.Generic.IEnumerable%601>.
 
- The <xref:System.Linq.Queryable> class contains [!INCLUDE[vbteclinq](~/includes/vbteclinq-md.md)] standard query operators that operate on objects that implement <xref:System.Linq.IQueryable%601>.
+ The <xref:System.Linq.Queryable> class contains LINQ standard query operators that operate on objects that implement <xref:System.Linq.IQueryable%601>.
 
  For more information, see [LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/).
 

From 701a5f80b2fa6a12f5bea940adace9fd78781e28 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:22:29 -0800
Subject: [PATCH 191/236] vbteclinqext

---
 xml/System.Data/DataRowExtensions.xml   | 14 +++++++-------
 xml/System.Data/DataTableExtensions.xml |  2 +-
 2 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/System.Data/DataRowExtensions.xml b/xml/System.Data/DataRowExtensions.xml
index e917279b36f..d1ef7f079a3 100644
--- a/xml/System.Data/DataRowExtensions.xml
+++ b/xml/System.Data/DataRowExtensions.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> API has been extended with two new methods of the <xref:System.Data.DataRow> class, <xref:System.Data.DataRowExtensions.Field%2A> and <xref:System.Data.DataRowExtensions.SetField%2A>. You can use these to form [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expressions and method queries against <xref:System.Data.DataTable> objects. They are the recommended methods to use for accessing column values within [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expressions and method queries. For more information, see [Generic Field and SetField Methods](/dotnet/framework/data/adonet/generic-field-and-setfield-methods-linq-to-dataset).  
+ The <xref:System.Data.DataSet> API has been extended with two new methods of the <xref:System.Data.DataRow> class, <xref:System.Data.DataRowExtensions.Field%2A> and <xref:System.Data.DataRowExtensions.SetField%2A>. You can use these to form Language-Integrated Query (LINQ) expressions and method queries against <xref:System.Data.DataTable> objects. They are the recommended methods to use for accessing column values within Language-Integrated Query (LINQ) expressions and method queries. For more information, see [Generic Field and SetField Methods](/dotnet/framework/data/adonet/generic-field-and-setfield-methods-linq-to-dataset).  
   
  ]]></format>
     </remarks>
@@ -95,7 +95,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> does not support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> does not support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is <xref:System.DBNull.Value> and `T` is a reference type or nullable type, the return type will be **null**. The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
@@ -152,7 +152,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is **null** and `T` is a reference type or nullable type, then the return type will be **null**.  The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
@@ -209,7 +209,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class. A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> does not support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types. If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class. A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> does not support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types. If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is **null** and `T` is a reference type or nullable type, the return type will be **null**. The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
@@ -268,7 +268,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is null and `T` is a reference type or nullable type, then the return type will be **null**. The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
@@ -327,7 +327,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is null and `T` is a reference type or nullable type, then the return type will be **null**. The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
@@ -386,7 +386,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
+ The <xref:System.Data.DataSet> class represents **null** values with the <xref:System.DBNull.Value> instance of the <xref:System.DBNull> class.  A Language-Integrated Query (LINQ) expression that accessed a column with a **null** value would generate a <xref:System.InvalidCastException> at run time. Additionally, <xref:System.Data.DataSet> doesn't support nullable types. The <xref:System.Data.DataRowExtensions.Field%2A> method provides support for accessing columns as nullable types.  If the underlying value in the <xref:System.Data.DataSet> is <xref:System.DBNull.Value>, the returned nullable type will have a value of **null**.  
   
  If the value of the specified <xref:System.Data.DataColumn> is null and `T` is a reference type or nullable type, then the return type will be **null**. The <xref:System.Data.DataRowExtensions.Field%2A> method will not return <xref:System.DBNull.Value>.  
   
diff --git a/xml/System.Data/DataTableExtensions.xml b/xml/System.Data/DataTableExtensions.xml
index 3c3b7f7e440..eeb06aa62c8 100644
--- a/xml/System.Data/DataTableExtensions.xml
+++ b/xml/System.Data/DataTableExtensions.xml
@@ -204,7 +204,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- [!INCLUDE[vbteclinqext](~/includes/vbteclinqext-md.md)] queries work on data sources that implement the <xref:System.Collections.Generic.IEnumerable%601> interface or the <xref:System.Linq.IQueryable> interface.  The <xref:System.Data.DataTable> class does not implement either interface, so you must call the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method to use the <xref:System.Data.DataTable> as a source in the `From` clause of a LINQ query. You can also obtain custom, domain-specific operators, such as <xref:System.Data.DataTableExtensions.CopyToDataTable%2A>, by returning an <xref:System.Collections.Generic.IEnumerable%601> object.  
+ Language-Integrated Query (LINQ) queries work on data sources that implement the <xref:System.Collections.Generic.IEnumerable%601> interface or the <xref:System.Linq.IQueryable> interface.  The <xref:System.Data.DataTable> class does not implement either interface, so you must call the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method to use the <xref:System.Data.DataTable> as a source in the `From` clause of a LINQ query. You can also obtain custom, domain-specific operators, such as <xref:System.Data.DataTableExtensions.CopyToDataTable%2A>, by returning an <xref:System.Collections.Generic.IEnumerable%601> object.  
   
  The enumerable object returned by the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method is permanently bound to the <xref:System.Data.DataTable> that produced it. Multiple calls to the <xref:System.Data.DataTableExtensions.AsEnumerable%2A> method will return multiple, independent queryable objects that are all bound to the source <xref:System.Data.DataTable>.  
   

From a751204c98f632c1e4053ce465e0ff302eb01361 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:22:55 -0800
Subject: [PATCH 192/236] vcprvc

---
 xml/System.Windows.Forms/Control.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Windows.Forms/Control.xml b/xml/System.Windows.Forms/Control.xml
index 59bfc1348fa..56d088483eb 100644
--- a/xml/System.Windows.Forms/Control.xml
+++ b/xml/System.Windows.Forms/Control.xml
@@ -9522,7 +9522,7 @@ MyControl.Font = New Font(MyControl.Font, _
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Forms.Control.Name%2A> property can be used at run time to evaluate the object by name rather than type and programmatic name. Because the <xref:System.Windows.Forms.Control.Name%2A> property returns a <xref:System.String> type, it can be evaluated in case-style logic statements (`Select` statement in Visual Basic, `switch` statement in Visual C# and [!INCLUDE[vcprvc](~/includes/vcprvc-md.md)]).  
+ The <xref:System.Windows.Forms.Control.Name%2A> property can be used at run time to evaluate the object by name rather than type and programmatic name. Because the <xref:System.Windows.Forms.Control.Name%2A> property returns a <xref:System.String> type, it can be evaluated in case-style logic statements (`Select` statement in Visual Basic, `switch` statement in Visual C# and Visual C++).  
   
    
   

From 9f9078959fc2363427c3139e4bb21ba9fd9ba874 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:23:23 -0800
Subject: [PATCH 193/236] vcprvclong

---
 xml/System/Type.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/xml/System/Type.xml b/xml/System/Type.xml
index 431e3211d9f..9a84ad2ef7c 100644
--- a/xml/System/Type.xml
+++ b/xml/System/Type.xml
@@ -7059,7 +7059,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, by using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, use the <xref:System.Type.GetProperty%28System.String%2CSystem.Reflection.BindingFlags%29> method overload and add the <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> flag to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7181,7 +7181,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
 -   A derived type declares a property that hides an inherited property with the same name, using the `new` modifier (`Shadows` in Visual Basic). To resolve the ambiguity, include <xref:System.Reflection.BindingFlags.DeclaredOnly?displayProperty=nameWithType> to restrict the search to members that are not inherited.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7274,7 +7274,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7370,7 +7370,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7475,7 +7475,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7575,7 +7575,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   
@@ -7736,7 +7736,7 @@ The <xref:System.Type.GetProperties%2A> method does not return properties in a p
  If the current <xref:System.Type> represents a type parameter in the definition of a generic type or generic method, this method searches the properties of the class constraint.  
   
 ## Indexers and Default Properties  
- Visual Basic 2005, Visual C# 2005, and [!INCLUDE[vcprvclong](~/includes/vcprvclong-md.md)] have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
+ Visual Basic 2005, Visual C# 2005, and Visual C++ 2005 have simplified syntax for accessing indexed properties and allow one indexed property to be a default for its type. For example, if the variable `myList` refers to an <xref:System.Collections.ArrayList>, the syntax `myList[3]` (`myList(3)` in Visual Basic) retrieves the element with the index of 3. You can overload the property.  
   
  In C#, this feature is called an indexer and cannot be referred to by name. By default, a C# indexer appears in metadata as an indexed property named "Item". However, a class library developer can use the <xref:System.Runtime.CompilerServices.IndexerNameAttribute> attribute to change the name of the indexer in the metadata. For example, the <xref:System.String> class has an indexer named <xref:System.String.Chars%2A>. Indexed properties created using languages other than C# can have names other than Item, as well.  
   

From 25baef74789fd10e296031e53f10443e6a2d1b46 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:27:52 -0800
Subject: [PATCH 194/236] vs-dev10-long

---
 xml/Microsoft.Build.Evaluation/Toolset.xml              | 4 ++--
 xml/System.Configuration/Configuration.xml              | 4 ++--
 xml/System.Diagnostics.Contracts/Contract.xml           | 2 +-
 xml/System.Web.DynamicData/FieldTemplateUserControl.xml | 2 +-
 xml/System.Web.DynamicData/MetaModel.xml                | 2 +-
 xml/System/AppDomainSetup.xml                           | 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/xml/Microsoft.Build.Evaluation/Toolset.xml b/xml/Microsoft.Build.Evaluation/Toolset.xml
index a5d30088bd9..5135a660b72 100644
--- a/xml/Microsoft.Build.Evaluation/Toolset.xml
+++ b/xml/Microsoft.Build.Evaluation/Toolset.xml
@@ -183,9 +183,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] is installed, use the base toolset and return a sub toolset version of "10.0".  
+ If Visual Studio 2010 is installed, use the base toolset and return a sub toolset version of "10.0".  
   
- Otherwise, use the highest-versioned sub toolset found. Sub toolsets with numbered versions are ordered numerically; any additional sub toolsets are prepended to the beginning of the list in the order found. Returns null if there is no sub toolset available and [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] is not installed.  
+ Otherwise, use the highest-versioned sub toolset found. Sub toolsets with numbered versions are ordered numerically; any additional sub toolsets are prepended to the beginning of the list in the order found. Returns null if there is no sub toolset available and Visual Studio 2010 is not installed.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Configuration/Configuration.xml b/xml/System.Configuration/Configuration.xml
index c843581704e..78f266a19d1 100644
--- a/xml/System.Configuration/Configuration.xml
+++ b/xml/System.Configuration/Configuration.xml
@@ -168,7 +168,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property enables a consumer of the .NET Framework configuration system to set a function delegate that is used to transform assembly strings found in configuration files. [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] uses this property when a project is targeted for an earlier version of the .NET Framework. The function makes sure that assembly strings are formatted correctly for the targeted version of the .NET Framework when configuration files are updated.  
+ This property enables a consumer of the .NET Framework configuration system to set a function delegate that is used to transform assembly strings found in configuration files. Visual Studio 2010 uses this property when a project is targeted for an earlier version of the .NET Framework. The function makes sure that assembly strings are formatted correctly for the targeted version of the .NET Framework when configuration files are updated.  
   
  ]]></format>
         </remarks>
@@ -1102,7 +1102,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This property enables a consumer of the .NET Framework configuration system to set a function delegate that is used to transform type strings found in configuration files. [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] uses this property when a project is targeted for an earlier version of the .NET Framework. The function makes sure that type strings are formatted correctly for the targeted version of the .NET Framework when configuration files are updated.  
+ This property enables a consumer of the .NET Framework configuration system to set a function delegate that is used to transform type strings found in configuration files. Visual Studio 2010 uses this property when a project is targeted for an earlier version of the .NET Framework. The function makes sure that type strings are formatted correctly for the targeted version of the .NET Framework when configuration files are updated.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Diagnostics.Contracts/Contract.xml b/xml/System.Diagnostics.Contracts/Contract.xml
index 9294264d588..7266e6de269 100644
--- a/xml/System.Diagnostics.Contracts/Contract.xml
+++ b/xml/System.Diagnostics.Contracts/Contract.xml
@@ -41,7 +41,7 @@
  For tools and detailed instructions for using code contracts, see [Code Contracts](https://marketplace.visualstudio.com/items?itemName=RiSEResearchinSoftwareEngineering.CodeContractsforNET) on the Visual Studio Marketplace.  
   
 > [!IMPORTANT]
->  You must use a binary rewriter to insert run-time enforcement of contracts. Otherwise, contracts such as the <xref:System.Diagnostics.Contracts.Contract.Ensures%2A?displayProperty=nameWithType> method can only be tested statically and will not throw exceptions during run time if a contract is violated. You can download the binary rewriter CCRewrite from [Code Contracts](https://marketplace.visualstudio.com/items?itemName=RiSEResearchinSoftwareEngineering.CodeContractsforNET) on the Visual Studio Marketplace. CCRewrite comes with a Visual Studio add-in that enables you to activate run-time contract enforcement from the project **Properties** page. The binary rewriter and the Visual Studio add-in do not ship with [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] or the Windows SDK.  
+>  You must use a binary rewriter to insert run-time enforcement of contracts. Otherwise, contracts such as the <xref:System.Diagnostics.Contracts.Contract.Ensures%2A?displayProperty=nameWithType> method can only be tested statically and will not throw exceptions during run time if a contract is violated. You can download the binary rewriter CCRewrite from [Code Contracts](https://marketplace.visualstudio.com/items?itemName=RiSEResearchinSoftwareEngineering.CodeContractsforNET) on the Visual Studio Marketplace. CCRewrite comes with a Visual Studio add-in that enables you to activate run-time contract enforcement from the project **Properties** page. The binary rewriter and the Visual Studio add-in do not ship with Visual Studio 2010 or the Windows SDK.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.DynamicData/FieldTemplateUserControl.xml b/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
index ef639c0cc28..18f98644e38 100644
--- a/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
+++ b/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
@@ -90,7 +90,7 @@ public partial class ForeignKeyField :
   
  To compile the example code, you need the following:  
   
--   [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
+-   Visual Studio 2010 or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
   
 -   A Dynamic Data Web site. For more information, see [Walkthrough: Creating a New Dynamic Data Web Site Using Scaffolding](https://msdn.microsoft.com/library/1564aef2-9103-436a-9806-c8ad7abd616a).  
   
diff --git a/xml/System.Web.DynamicData/MetaModel.xml b/xml/System.Web.DynamicData/MetaModel.xml
index 8b0fa69c658..af2842948db 100644
--- a/xml/System.Web.DynamicData/MetaModel.xml
+++ b/xml/System.Web.DynamicData/MetaModel.xml
@@ -49,7 +49,7 @@
   
  To compile the example, you need the following:  
   
--   [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
+-   Visual Studio 2010 or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
   
 -   A Dynamic Data Web site. For more information, see [Walkthrough: Creating a New Dynamic Data Web Site Using Scaffolding](https://msdn.microsoft.com/library/1564aef2-9103-436a-9806-c8ad7abd616a).  
   
diff --git a/xml/System/AppDomainSetup.xml b/xml/System/AppDomainSetup.xml
index 9f614425ad2..9d7e49b1bcf 100644
--- a/xml/System/AppDomainSetup.xml
+++ b/xml/System/AppDomainSetup.xml
@@ -1538,7 +1538,7 @@
 ## Remarks  
  Set this property to tell the currently running version of the .NET Framework that the application domain will be used to load and run assemblies that have been compiled for the target version and profile. If the currently running version of the .NET Framework has optional behaviors that affect the compatibility of code that was compiled with the target version, it can enable or disable those behaviors, as appropriate, to improve compatibility. This can be useful when an application supports add-ins compiled with multiple versions of the .NET Framework by running them in separate application domains.  
   
- For client applications, the value of the <xref:System.AppDomainSetup.TargetFrameworkName%2A> property is inferred from the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute. In [!INCLUDE[vs_dev10_long](~/includes/vs-dev10-long-md.md)] and later, this attribute is added to the assembly automatically based on the setting of the project's **Target Framework** property.  
+ For client applications, the value of the <xref:System.AppDomainSetup.TargetFrameworkName%2A> property is inferred from the <xref:System.Runtime.Versioning.TargetFrameworkAttribute> attribute. In Visual Studio 2010 and later, this attribute is added to the assembly automatically based on the setting of the project's **Target Framework** property.  
   
  ]]></format>
         </remarks>

From 5c33bf4ff9def1603c44475a61759377e084255a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:28:51 -0800
Subject: [PATCH 195/236] vs-orcas-ext

---
 xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml b/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
index 57f3732b7f1..03cccaf8f47 100644
--- a/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
+++ b/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
@@ -65,7 +65,7 @@
   
  To compile the example, you need the following:  
   
--   [!INCLUDE[vs_orcas_ext](~/includes/vs-orcas-ext-md.md)] Service Pack 1 or [!INCLUDE[vwd_exp_orcas_long](~/includes/vwd-exp-orcas-long-md.md)] SP1.  
+-   Microsoft Visual Studio 2008 Service Pack 1 or [!INCLUDE[vwd_exp_orcas_long](~/includes/vwd-exp-orcas-long-md.md)] SP1.  
   
 -   A data-driven Web site. This enables you to create a data context for the database and the class that contains the data field to customize. For more information, see `Walkthrough: Creating a New Dynamic Data Web Site using Scaffolding`.  
   

From 1afc65c9abc87f0c047d54fe7f4fbc15b35eeb5a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:29:44 -0800
Subject: [PATCH 196/236] vs-orcas-long

---
 xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml     | 2 +-
 .../TypedDataSetGenerator+GenerateOption.xml                  | 4 ++--
 .../TypedDataSetSchemaImporterExtensionFx35.xml               | 4 ++--
 xml/System.Windows/SplashScreen.xml                           | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
index 00f99a0dd63..f674d16a784 100644
--- a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
@@ -37,7 +37,7 @@
 
  In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the [GenerateApplicationManifest Task](/visualstudio/msbuild/generateapplicationmanifest-task) requires an `EntryPoint` when an application manifest is generated. (Assembly or native manifests do not require an `EntryPoint`.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
 
- In [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)], [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] does not issue this error when the `EntryPoint` task parameter is not specified. Instead, the \<customHostSpecified> tag is inserted as a child of the \<entryPoint> tag, for example, as follows.
+ In Visual Studio 2008, [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] does not issue this error when the `EntryPoint` task parameter is not specified. Instead, the \<customHostSpecified> tag is inserted as a child of the \<entryPoint> tag, for example, as follows.
 
 ```xml
 <entryPoint xmlns="urn:schemas-
diff --git a/xml/System.Data.Design/TypedDataSetGenerator+GenerateOption.xml b/xml/System.Data.Design/TypedDataSetGenerator+GenerateOption.xml
index e265745fe04..0ada838852b 100644
--- a/xml/System.Data.Design/TypedDataSetGenerator+GenerateOption.xml
+++ b/xml/System.Data.Design/TypedDataSetGenerator+GenerateOption.xml
@@ -30,7 +30,7 @@
  The <xref:System.Data.Design.TypedDataSetGenerator.GenerateOption> enumeration enables you to implement new features in typed datasets without needing to create additional overloads to the `TypedDataSetGenerator.Generate` method.  
   
 > [!NOTE]
->  LINQ to DataSet and hierarchical update are features that were added in [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)].  
+>  LINQ to DataSet and hierarchical update are features that were added in Visual Studio 2008.  
 >   
 >  Also see [Hierarchical Update Overview](/previous-versions/visualstudio/visual-studio-2013/bb384567(v=vs.120)).  
   
@@ -98,7 +98,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Generates typed datasets that are compatible with typed datasets generated in versions of Visual Studio earlier than [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)].</summary>
+        <summary>Generates typed datasets that are compatible with typed datasets generated in versions of Visual Studio earlier than Visual Studio 2008.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Data.Design/TypedDataSetSchemaImporterExtensionFx35.xml b/xml/System.Data.Design/TypedDataSetSchemaImporterExtensionFx35.xml
index bc8f92c53c6..3b612708c1d 100644
--- a/xml/System.Data.Design/TypedDataSetSchemaImporterExtensionFx35.xml
+++ b/xml/System.Data.Design/TypedDataSetSchemaImporterExtensionFx35.xml
@@ -23,7 +23,7 @@
  `System.Data.Design.TypedDataSetSchemaImporterExtensionFx35` calls the protected constructor of <xref:System.Data.Design.TypedDataSetSchemaImporterExtension> to generate typed datasets for the .NET Framework version 3.5 and enable LINQ to DataSet and hierarchical update.  
   
 > [!NOTE]
->  LINQ to DataSet and hierarchical update are features that were added in [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)].  
+>  LINQ to DataSet and hierarchical update are features that were added in Visual Studio 2008.  
 >   
 >  Also see [Hierarchical Update Overview](/previous-versions/bb384567(v=vs.140)) and [LINQ to DataSet](/dotnet/framework/data/adonet/linq-to-dataset).  
   
@@ -55,7 +55,7 @@
  <xref:System.Data.Design.TypedDataSetSchemaImporterExtensionFx35> calls the protected constructor of <xref:System.Data.Design.TypedDataSetSchemaImporterExtension> to generate typed datasets for .NET Framework version 3.5 and enable LINQ to DataSet and hierarchical update.  
   
 > [!NOTE]
->  LINQ to Dataset and hierarchical update are features in [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)]. See [LINQ to DataSet](/dotnet/framework/data/adonet/linq-to-dataset) and [Hierarchical Update Overview](/previous-versions/visualstudio/visual-studio-2013/bb384567(v=vs.120)).  
+>  LINQ to Dataset and hierarchical update are features in Visual Studio 2008. See [LINQ to DataSet](/dotnet/framework/data/adonet/linq-to-dataset) and [Hierarchical Update Overview](/previous-versions/visualstudio/visual-studio-2013/bb384567(v=vs.120)).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows/SplashScreen.xml b/xml/System.Windows/SplashScreen.xml
index 1390a449013..ed286dfbd49 100644
--- a/xml/System.Windows/SplashScreen.xml
+++ b/xml/System.Windows/SplashScreen.xml
@@ -34,7 +34,7 @@
  You cannot include placeholder text in the splash screen that is later added by your code. If you want to include text in the splash screen, you must add it to the image file.  
   
 > [!NOTE]
->  It is not necessary to write any code to display a splash screen. Starting in [!INCLUDE[vs_orcas_long](~/includes/vs-orcas-long-md.md)] SP1, you can quickly configure a splash screen with default settings. For more information, see [How to: Add a Splash Screen to a WPF Application](/dotnet/framework/wpf/app-development/how-to-add-a-splash-screen-to-a-wpf-application).  
+>  It is not necessary to write any code to display a splash screen. Starting in Visual Studio 2008 SP1, you can quickly configure a splash screen with default settings. For more information, see [How to: Add a Splash Screen to a WPF Application](/dotnet/framework/wpf/app-development/how-to-add-a-splash-screen-to-a-wpf-application).  
   
  The <xref:System.Windows.SplashScreen> class displays the splash screen as soon as possible after the application is started. The splash screen is displayed by using native code, before the WPF application instance is created. The splash screen is displayed in the center of the screen. When the application is loaded, the splash screen fades.  
   

From f0b1205d896be3ddad4021c5a152e50bc0cb588a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:33:34 -0800
Subject: [PATCH 197/236] vs-ordesigner-long

---
 xml/System.Web.UI.WebControls/LinqDataSource.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Web.UI.WebControls/LinqDataSource.xml b/xml/System.Web.UI.WebControls/LinqDataSource.xml
index 68186c739a7..e71e95b18c0 100644
--- a/xml/System.Web.UI.WebControls/LinqDataSource.xml
+++ b/xml/System.Web.UI.WebControls/LinqDataSource.xml
@@ -97,7 +97,7 @@
   
  When you are retrieving data from an in-memory data collection, you set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the class that contains the data collection. You set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property or field that returns the data collection. For example, you might have a class named `Person` that contains a property named `FavoriteCities` that returns an array of string values. In that case, you set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to `Person` and set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to `FavoriteCities`.  
   
- When you are querying a database, you must first create entity classes that represent the database and its tables. You can use the [!INCLUDE[vs_ordesigner_long](~/includes/vs-ordesigner-long-md.md)] or the SqlMetal.exe utility to generate these classes. You then set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the class that represents the database and set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property that represents the database table.  
+ When you are querying a database, you must first create entity classes that represent the database and its tables. You can use the Object Relational Designer or the SqlMetal.exe utility to generate these classes. You then set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the class that represents the database and set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property that represents the database table.  
   
 <a name="order_of_operations"></a>   
 ## Order of Operations  

From a78599a2426082453d76c7b449dad660cbd5cbc3 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:33:52 -0800
Subject: [PATCH 198/236] vs-ordesigner-short

---
 xml/System.Web.UI.WebControls/LinqDataSource.xml | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Web.UI.WebControls/LinqDataSource.xml b/xml/System.Web.UI.WebControls/LinqDataSource.xml
index e71e95b18c0..2ca319117ef 100644
--- a/xml/System.Web.UI.WebControls/LinqDataSource.xml
+++ b/xml/System.Web.UI.WebControls/LinqDataSource.xml
@@ -216,7 +216,7 @@
    
   
 ## Examples  
- The following example shows a <xref:System.Web.UI.WebControls.LinqDataSource> control that retrieves data from an entity class named `Products`. The entity class could have been generated by using the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)] or the SqlMetal.exe utility. The <xref:System.Web.UI.WebControls.LinqDataSource.Where%2A> property is set to return only records that have a value in the `Price` property greater than 50. A <xref:System.Web.UI.WebControls.GridView> control is bound to the <xref:System.Web.UI.WebControls.LinqDataSource> control to display the data.  
+ The following example shows a <xref:System.Web.UI.WebControls.LinqDataSource> control that retrieves data from an entity class named `Products`. The entity class could have been generated by using the O/R Designer or the SqlMetal.exe utility. The <xref:System.Web.UI.WebControls.LinqDataSource.Where%2A> property is set to return only records that have a value in the `Price` property greater than 50. A <xref:System.Web.UI.WebControls.GridView> control is bound to the <xref:System.Web.UI.WebControls.LinqDataSource> control to display the data.  
   
  [!code-aspx-csharp[System.Web.UI.WebControls.LinqDataSource_Simple#5](~/samples/snippets/csharp/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Simple/cs/Default5.aspx#5)]
  [!code-aspx-vb[System.Web.UI.WebControls.LinqDataSource_Simple#5](~/samples/snippets/visualbasic/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Simple/vb/Default5.aspx#5)]  
@@ -631,7 +631,7 @@
 ## Remarks  
  When you use the <xref:System.Web.UI.WebControls.LinqDataSource> control to retrieve data from either an in-memory data collection or a database, you must specify two properties. The first is a data context class that represents the data source. The second is a property in the data context class that contains the data. You set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the name of the data context class and you set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the data collection that contains the data.  
   
- For example, when you retrieve data from a database, set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the name of the class that represents the database. Also set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property that represents the table in the database. To generate classes from a database, use the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)] or the SqlMetal.exe utility to automatically generate those classes.  
+ For example, when you retrieve data from a database, set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the name of the class that represents the database. Also set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property that represents the table in the database. To generate classes from a database, use the O/R Designer or the SqlMetal.exe utility to automatically generate those classes.  
   
  When you retrieve data from an in-memory data collection such as an array, set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to the name of the class that contains the array property. Then set the <xref:System.Web.UI.WebControls.LinqDataSource.TableName%2A> property to the property that gets the array.  
   
@@ -642,12 +642,12 @@
    
   
 ## Examples  
- The following example shows how to set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to a class that contains an array of strings. It also shows how to set the property to a class (generated by the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)]) that represents a database.  
+ The following example shows how to set the <xref:System.Web.UI.WebControls.LinqDataSource.ContextTypeName%2A> property to a class that contains an array of strings. It also shows how to set the property to a class (generated by the O/R Designer) that represents a database.  
   
  [!code-aspx-csharp[System.Web.UI.WebControls.LinqDataSource_Overview#2](~/samples/snippets/csharp/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Overview/cs/Default.aspx#2)]
  [!code-aspx-vb[System.Web.UI.WebControls.LinqDataSource_Overview#2](~/samples/snippets/visualbasic/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Overview/vb/Default.aspx#2)]  
   
- The class named `ExampleDataContext` that represents the database table is not shown in this example. For this example to work, you must create this class by adding a LINQ To SQL class named Example.dbml and dragging a table named Movie onto the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)]. A class named `ExampleDataContext` with a property named `Movies` is generated.  
+ The class named `ExampleDataContext` that represents the database table is not shown in this example. For this example to work, you must create this class by adding a LINQ To SQL class named Example.dbml and dragging a table named Movie onto the O/R Designer. A class named `ExampleDataContext` with a property named `Movies` is generated.  
   
  The following example shows the class named `MovieLibrary` that is referenced in the <xref:System.Web.UI.WebControls.LinqDataSource> control.  
   
@@ -2180,7 +2180,7 @@ protected void LinqDataSource_Selecting(object sender,
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, when update and delete operations have been enabled, the <xref:System.Web.UI.WebControls.LinqDataSource> control stores the original values for all the records in view state. The <xref:System.Web.UI.WebControls.LinqDataSource> control stores values for all primary keys and all properties not marked with `UpdateCheck.Never` in the `Column` attribute. You set the `UpdateCheck` property of the `Column` attribute in the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)].  
+ By default, when update and delete operations have been enabled, the <xref:System.Web.UI.WebControls.LinqDataSource> control stores the original values for all the records in view state. The <xref:System.Web.UI.WebControls.LinqDataSource> control stores values for all primary keys and all properties not marked with `UpdateCheck.Never` in the `Column` attribute. You set the `UpdateCheck` property of the `Column` attribute in the O/R Designer.  
   
  Before LINQ to SQL updates or deletes data, it checks the values in view state against the current values in the data source. If the values do not match, the data source record has changed. In that case, LINQ to SQL throws an exception and does not continue with the update or delete operation. For more information about LINQ to SQL, see [LINQ to SQL](/dotnet/framework/data/adonet/sql/linq/).  
   
@@ -2346,7 +2346,7 @@ protected void LinqDataSource_Selecting(object sender,
  [!code-aspx-csharp[System.Web.UI.WebControls.LinqDataSource_Overview#2](~/samples/snippets/csharp/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Overview/cs/Default.aspx#2)]
  [!code-aspx-vb[System.Web.UI.WebControls.LinqDataSource_Overview#2](~/samples/snippets/visualbasic/VS_Snippets_WebNet/System.Web.UI.WebControls.LinqDataSource_Overview/vb/Default.aspx#2)]  
   
- The class named `ExampleDataContext` that represents the database table is not shown in this example. For this example to work, you must create this class by adding a LINQ to SQL class named Example.dbml and dragging a table named Movie onto the [!INCLUDE[vs_ordesigner_short](~/includes/vs-ordesigner-short-md.md)]. A class named `ExampleDataContext` with a property named `Movies` is generated.  
+ The class named `ExampleDataContext` that represents the database table is not shown in this example. For this example to work, you must create this class by adding a LINQ to SQL class named Example.dbml and dragging a table named Movie onto the O/R Designer. A class named `ExampleDataContext` with a property named `Movies` is generated.  
   
  The following example shows the class named `MovieLibrary` that is referenced in the <xref:System.Web.UI.WebControls.LinqDataSource> control.  
   

From 692ffda985bd5af7582e94207c9685d882d4ed26 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:34:14 -0800
Subject: [PATCH 199/236] vs2010

---
 .../IMultiTargetingSupportService.xml                         | 4 ++--
 .../IRegisterMetadata.xml                                     | 2 +-
 .../ToolboxItemWrapper.xml                                    | 2 +-
 .../IWorkflowDesignerStorageService.xml                       | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
index 4056957f9a6..849f5019ab9 100644
--- a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
+++ b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
@@ -16,9 +16,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- *Multi-targeting* is the ability to find the right version of the loaded assembly that corresponds to the target .NET Framework version of the current workflow project in [!INCLUDE[vs2010](~/includes/vs2010-md.md)].  
+ *Multi-targeting* is the ability to find the right version of the loaded assembly that corresponds to the target .NET Framework version of the current workflow project in Visual Studio 2010.  
   
- This interface is implemented and used internally by [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components to resolve .NET Framework assemblies in a multi-targeting aware fashion within the [!INCLUDE[vs2010](~/includes/vs2010-md.md)] hosting application. The [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
+ This interface is implemented and used internally by [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components to resolve .NET Framework assemblies in a multi-targeting aware fashion within the Visual Studio 2010 hosting application. The [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml b/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
index bcc8a885e33..844e6551557 100644
--- a/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
+++ b/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
@@ -16,7 +16,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> types provide a way to encapsulate the association of design-time attributes to run-time types in a loosely coupled fashion. An application hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] can use the <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> interface to register the attributes for the activity. For instance, [!INCLUDE[vs2010](~/includes/vs2010-md.md)] searches for types that implement <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> when assemblies that contain these types are loaded in addition to also looking for types in the *.design assemblies.  
+ <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> types provide a way to encapsulate the association of design-time attributes to run-time types in a loosely coupled fashion. An application hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] can use the <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> interface to register the attributes for the activity. For instance, Visual Studio 2010 searches for types that implement <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> when assemblies that contain these types are loaded in addition to also looking for types in the *.design assemblies.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml b/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
index 00f7a4e8110..bc21be2eb4d 100644
--- a/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
+++ b/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
@@ -23,7 +23,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This wrapper class provides support for the categorization of toolbox items when re-hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)]outside of [!INCLUDE[vs2010](~/includes/vs2010-md.md)].  
+ This wrapper class provides support for the categorization of toolbox items when re-hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)]outside of Visual Studio 2010.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml b/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
index 4281878c223..0928e344db7 100644
--- a/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
+++ b/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
@@ -16,7 +16,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This interface is implemented and used internally by [!INCLUDE[vs2010](~/includes/vs2010-md.md)], which is the primary host of the [!INCLUDE[wfd2](~/includes/wfd2-md.md)].  
+ This interface is implemented and used internally by Visual Studio 2010, which is the primary host of the [!INCLUDE[wfd2](~/includes/wfd2-md.md)].  
   
  ]]></format>
     </remarks>

From d2f6727489b023ff398b24b0516fdaf0014a86ea Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:34:43 -0800
Subject: [PATCH 200/236] vsprvsext

---
 .../AssemblyDescriptionAttribute.xml          |  2 +-
 .../AssemblyKeyFileAttribute.xml              |  2 +-
 .../RegistrationServices.xml                  |  2 +-
 ...gnTimeResourceProviderFactoryAttribute.xml |  2 +-
 .../ExtenderControlDesigner.xml               |  2 +-
 .../DeclarativeCatalogPart.xml                | 48 +++++++++----------
 .../PageCatalogPart.xml                       | 48 +++++++++----------
 .../WebPartManager.xml                        |  2 +-
 .../WebPartPersonalization.xml                |  2 +-
 xml/System.Windows.Forms/ListView.xml         |  2 +-
 ...stem.DirectoryServices.ActiveDirectory.xml |  2 +-
 11 files changed, 57 insertions(+), 57 deletions(-)

diff --git a/xml/System.Reflection/AssemblyDescriptionAttribute.xml b/xml/System.Reflection/AssemblyDescriptionAttribute.xml
index 39730ce017e..a6dd593dcf7 100644
--- a/xml/System.Reflection/AssemblyDescriptionAttribute.xml
+++ b/xml/System.Reflection/AssemblyDescriptionAttribute.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you create a project in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)], this attribute is automatically applied with an empty string value. You can set its value in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] by selecting the **Properties** for the project from the **File** menu, and then by clicking **Assembly Information**. The attribute is saved in the AssemblyInfo file in your project, and it must be removed before you can specify it in code; otherwise, you will get an error that the attribute cannot be applied multiple times.  
+ When you create a project in Microsoft Visual Studio 2005, this attribute is automatically applied with an empty string value. You can set its value in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] by selecting the **Properties** for the project from the **File** menu, and then by clicking **Assembly Information**. The attribute is saved in the AssemblyInfo file in your project, and it must be removed before you can specify it in code; otherwise, you will get an error that the attribute cannot be applied multiple times.  
   
  When you right-click the assembly file in File Explorer, this attribute appears as the **Comments** value on the **Version** tab of the file properties dialog box.  
   
diff --git a/xml/System.Reflection/AssemblyKeyFileAttribute.xml b/xml/System.Reflection/AssemblyKeyFileAttribute.xml
index dcdb02609e4..98764d9c692 100644
--- a/xml/System.Reflection/AssemblyKeyFileAttribute.xml
+++ b/xml/System.Reflection/AssemblyKeyFileAttribute.xml
@@ -125,7 +125,7 @@ sn -k TestPublicKey.snk
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- There is no default path for the <xref:System.Reflection.AssemblyKeyFileAttribute> constructor. The value set by the constructor is interpreted by the linker, or by [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)], that invokes the linker.  
+ There is no default path for the <xref:System.Reflection.AssemblyKeyFileAttribute> constructor. The value set by the constructor is interpreted by the linker, or by Microsoft Visual Studio 2005, that invokes the linker.  
   
  The default setting for the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool assumes that the key file is in the current directory. In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the Visual Basic and Visual C# compilers build and link to subdirectories of the project directory, so if you put the key file in the project directory the relative path might be "..\\..\keyfile.snk" or "..\keyfile.snk" in Visual Basic, or "..\\\\..\\\keyfile.snk" or "..\\\keyfile.snk" in C#. For C#, this attribute can be set in the project properties.  
   
diff --git a/xml/System.Runtime.InteropServices/RegistrationServices.xml b/xml/System.Runtime.InteropServices/RegistrationServices.xml
index 9a6abdcbc91..9e83f992990 100644
--- a/xml/System.Runtime.InteropServices/RegistrationServices.xml
+++ b/xml/System.Runtime.InteropServices/RegistrationServices.xml
@@ -43,7 +43,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Registration is needed when the objects within an assembly are being used by COM clients. The [Regasm.exe (Assembly Registration Tool)](/dotnet/framework/tools/regasm-exe-assembly-registration-tool) and [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] use methods exposed by the <xref:System.Runtime.InteropServices.RegistrationServices> class to add or remove COM-enabling registry entries for managed assemblies.  
+ Registration is needed when the objects within an assembly are being used by COM clients. The [Regasm.exe (Assembly Registration Tool)](/dotnet/framework/tools/regasm-exe-assembly-registration-tool) and Microsoft Visual Studio 2005 use methods exposed by the <xref:System.Runtime.InteropServices.RegistrationServices> class to add or remove COM-enabling registry entries for managed assemblies.  
   
  You can use the following methods to assist you in preparing a registration file:  
   
diff --git a/xml/System.Web.Compilation/DesignTimeResourceProviderFactoryAttribute.xml b/xml/System.Web.Compilation/DesignTimeResourceProviderFactoryAttribute.xml
index 9fb04c4d119..529f284e969 100644
--- a/xml/System.Web.Compilation/DesignTimeResourceProviderFactoryAttribute.xml
+++ b/xml/System.Web.Compilation/DesignTimeResourceProviderFactoryAttribute.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.Compilation.DesignTimeResourceProviderFactoryAttribute> class allows a <xref:System.Web.Compilation.ResourceProviderFactory> object to specify the type of the associated <xref:System.Web.UI.Design.DesignTimeResourceProviderFactory> object. The <xref:System.Web.UI.Design.DesignTimeResourceProviderFactory> class is used to create design-time providers for reading and writing resources. Within [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)], a developer can use the **Generate Local Resource** command on the **Tools** menu to create resources during design time.  
+ The <xref:System.Web.Compilation.DesignTimeResourceProviderFactoryAttribute> class allows a <xref:System.Web.Compilation.ResourceProviderFactory> object to specify the type of the associated <xref:System.Web.UI.Design.DesignTimeResourceProviderFactory> object. The <xref:System.Web.UI.Design.DesignTimeResourceProviderFactory> class is used to create design-time providers for reading and writing resources. Within Microsoft Visual Studio 2005, a developer can use the **Generate Local Resource** command on the **Tools** menu to create resources during design time.  
   
    
   
diff --git a/xml/System.Web.UI.Design/ExtenderControlDesigner.xml b/xml/System.Web.UI.Design/ExtenderControlDesigner.xml
index daf46bff509..cbf304bf45f 100644
--- a/xml/System.Web.UI.Design/ExtenderControlDesigner.xml
+++ b/xml/System.Web.UI.Design/ExtenderControlDesigner.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.ExtenderControlDesigner> class enables you to interact with extender controls on the page at design time in an IDE such as [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)]. Only control developers and IDE developers have to interact with this class directly.  
+ The <xref:System.Web.UI.Design.ExtenderControlDesigner> class enables you to interact with extender controls on the page at design time in an IDE such as Microsoft Visual Studio 2005. Only control developers and IDE developers have to interact with this class directly.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.WebControls.WebParts/DeclarativeCatalogPart.xml b/xml/System.Web.UI.WebControls.WebParts/DeclarativeCatalogPart.xml
index 2d51c3b7dc8..1b22abd3bd1 100644
--- a/xml/System.Web.UI.WebControls.WebParts/DeclarativeCatalogPart.xml
+++ b/xml/System.Web.UI.WebControls.WebParts/DeclarativeCatalogPart.xml
@@ -47,7 +47,7 @@
   
  The <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> control has a useful property that allows developers to set up a catalog of controls that can be used throughout an entire site. Rather than declare individual server controls within a <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> control, a developer can set the <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart.WebPartsListUserControlPath%2A> property value to the path of a user control that contains the list of server controls that should be in the catalog. At run time, the server controls referenced in the user control are loaded in the catalog. In this way, multiple pages or sites could reference the same user control to create a catalog. When the user control's list of server controls is updated, it would update all catalogs based on the user control.  
   
- The <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> class has a number of public properties that override the inherited properties. Most of these properties are not actually used for rendering the control; they are overridden only so that special code attributes can be set on them to hide them from design tools like [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)]. You should not use these hidden properties, as they have no effect on rendering. The fact that they are hidden from IntelliSense and the Properties pane in Visual Studio helps developers avoid using them by mistake. All these hidden properties are noted as such in their respective Help topics.  
+ The <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> class has a number of public properties that override the inherited properties. Most of these properties are not actually used for rendering the control; they are overridden only so that special code attributes can be set on them to hide them from design tools like Microsoft Visual Studio 2005. You should not use these hidden properties, as they have no effect on rendering. The fact that they are hidden from IntelliSense and the Properties pane in Visual Studio helps developers avoid using them by mistake. All these hidden properties are noted as such in their respective Help topics.  
   
  The <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> class also has several methods. The <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart.GetAvailableWebPartDescriptions%2A> method retrieves a <xref:System.Web.UI.WebControls.WebParts.WebPartDescription> object for each <xref:System.Web.UI.WebControls.WebParts.WebPart> control in the catalog, which enables a <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart> control to display information about each server control without having to create an instance of it. Another method is the <xref:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart.GetWebPart%2A> method. This method gets an instance of a particular <xref:System.Web.UI.WebControls.WebParts.WebPart> control, based on the description passed to the method.  
   
@@ -158,7 +158,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that represents a keyboard key used for quick keyboard navigation to a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -209,7 +209,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that is used for the background color of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -260,7 +260,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the URL to an image used as the background for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -311,7 +311,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that is used as the color of the border around a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -362,7 +362,7 @@
         <ReturnType>System.Web.UI.WebControls.BorderStyle</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.BorderStyle" /> that determines the type of border and title display for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -413,7 +413,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> that determines the width of the border around a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -468,7 +468,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the name of a cascading style sheet (CSS) class used to assign style characteristics to a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -519,7 +519,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the ID of a <see cref="T:System.Web.UI.WebControls.Button" /> control that serves as the default button on a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -570,7 +570,7 @@
         <ReturnType>System.Web.UI.WebControls.ContentDirection</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.ContentDirection" /> that indicates the direction in which the content flows in a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -621,7 +621,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether a control is currently enabled or disabled.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -676,7 +676,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether themes can be used on a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -728,7 +728,7 @@
         <ReturnType>System.Web.UI.WebControls.FontInfo</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.FontInfo" /> that indicates the font used for a control's content.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -779,7 +779,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that determines the foreground color for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -962,7 +962,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the text at the head of a section of grouped child controls within the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1013,7 +1013,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> value that indicates the height of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1064,7 +1064,7 @@
         <ReturnType>System.Web.UI.WebControls.HorizontalAlign</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.HorizontalAlign" /> that indicates the type of horizontal alignment used in rendering the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1140,7 +1140,7 @@
         <ReturnType>System.Web.UI.WebControls.ScrollBars</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.ScrollBars" /> that is used if needed within the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1199,7 +1199,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the ID of a skin for the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1251,7 +1251,7 @@
         <ReturnType>System.Int16</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A short number that serves as the index of this control in the tab order.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1343,7 +1343,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the content of a ToolTip.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1394,7 +1394,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether the control is visible.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1600,7 +1600,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> that indicates the width of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1651,7 +1651,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the <see cref="T:System.Web.UI.WebControls.WebParts.DeclarativeCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether long lines in the control can wrap.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Web.UI.WebControls.WebParts/PageCatalogPart.xml b/xml/System.Web.UI.WebControls.WebParts/PageCatalogPart.xml
index d3bcdf9e1fb..6743b33adfa 100644
--- a/xml/System.Web.UI.WebControls.WebParts/PageCatalogPart.xml
+++ b/xml/System.Web.UI.WebControls.WebParts/PageCatalogPart.xml
@@ -50,7 +50,7 @@
   
  The <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart> class has only one usable property, the <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart.Title%2A> property, which overrides the base property so that a default title can be provided for the page catalog if no value is supplied.  
   
- The remaining properties for the <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart> class override the inherited properties, but are not actually used for rendering the control. They are overridden only so that special code attributes can be set on them to hide them from design tools like [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)]. You should not use these hidden properties, because they have no effect on rendering. The fact that they are hidden from IntelliSense and the Properties pane in Visual Studio helps developers avoid using them by mistake. All these hidden properties are noted as such in their respective Help topics.  
+ The remaining properties for the <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart> class override the inherited properties, but are not actually used for rendering the control. They are overridden only so that special code attributes can be set on them to hide them from design tools like Microsoft Visual Studio 2005. You should not use these hidden properties, because they have no effect on rendering. The fact that they are hidden from IntelliSense and the Properties pane in Visual Studio helps developers avoid using them by mistake. All these hidden properties are noted as such in their respective Help topics.  
   
  The <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart> class also has several important methods. The <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart.GetAvailableWebPartDescriptions%2A> method retrieves a <xref:System.Web.UI.WebControls.WebParts.WebPartDescription> object for each <xref:System.Web.UI.WebControls.WebParts.WebPart> control in the page catalog, which enables a <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart> control to display information about each server control without having to create an instance of that control. Another method is the <xref:System.Web.UI.WebControls.WebParts.PageCatalogPart.GetWebPart%2A> method. This method gets an instance of a particular <xref:System.Web.UI.WebControls.WebParts.WebPart> control, based on the description passed to the method.  
   
@@ -159,7 +159,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that represents a keyboard key used for quick keyboard navigation to a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -210,7 +210,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that is used for the background color of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -261,7 +261,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the URL to an image used as the background for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -312,7 +312,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that is used as the color of the border around a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -363,7 +363,7 @@
         <ReturnType>System.Web.UI.WebControls.BorderStyle</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.BorderStyle" /> that determines the type of border and title display for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -414,7 +414,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> that determines the width of the border around a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -469,7 +469,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the name of a cascading style sheet (CSS) class used to assign style characteristics to a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -520,7 +520,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the ID of a <see cref="T:System.Web.UI.WebControls.Button" /> control that serves as the default button on a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -571,7 +571,7 @@
         <ReturnType>System.Web.UI.WebControls.ContentDirection</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.ContentDirection" /> that indicates the direction in which the content flows in a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -622,7 +622,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether a control is currently enabled or disabled.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -677,7 +677,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether themes can be used on a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -729,7 +729,7 @@
         <ReturnType>System.Web.UI.WebControls.FontInfo</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.FontInfo" /> that indicates the font used for a control's content.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -780,7 +780,7 @@
         <ReturnType>System.Drawing.Color</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Drawing.Color" /> that determines the foreground color for a control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -963,7 +963,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the text at the head of a section of grouped child controls within the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1014,7 +1014,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> value that indicates the height of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1065,7 +1065,7 @@
         <ReturnType>System.Web.UI.WebControls.HorizontalAlign</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.HorizontalAlign" /> that indicates the type of horizontal alignment used in rendering the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1191,7 +1191,7 @@
         <ReturnType>System.Web.UI.WebControls.ScrollBars</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.ScrollBars" /> that is used if needed within the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1250,7 +1250,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the ID of a skin for the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1302,7 +1302,7 @@
         <ReturnType>System.Int16</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A short number that serves as the index of this control in the tab order.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1394,7 +1394,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A string that contains the content of a ToolTip.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1445,7 +1445,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether the control is visible.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1496,7 +1496,7 @@
         <ReturnType>System.Web.UI.WebControls.Unit</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A <see cref="T:System.Web.UI.WebControls.Unit" /> that indicates the width of the control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -1547,7 +1547,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer tools.</summary>
+        <summary>This inherited property is not used by the Web Parts control set when rendering a <see cref="T:System.Web.UI.WebControls.WebParts.PageCatalogPart" /> control. The property is overridden only for the purpose of preventing it from appearing in Microsoft Visual Studio 2005 designer tools.</summary>
         <value>A Boolean value that indicates whether long lines in the control can wrap.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml b/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml
index cfbc87ccd9c..156fcae4d3d 100644
--- a/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml
+++ b/xml/System.Web.UI.WebControls.WebParts/WebPartManager.xml
@@ -3010,7 +3010,7 @@
  The designed way to use these internal methods is to access them through the <xref:System.Web.UI.WebControls.WebParts.WebPartManager.Internals%2A> property. Because the property is protected, you can only access it and call the methods within an instance of the <xref:System.Web.UI.WebControls.WebParts.WebPartManagerInternals> class by inheriting from the <xref:System.Web.UI.WebControls.WebParts.WebPartManager> class.  
   
 > [!NOTE]
->  This property is hidden from IntelliSense in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)]. However, in a derived <xref:System.Web.UI.WebControls.WebParts.WebPartManager> class, you can still access the property and its various members.  
+>  This property is hidden from IntelliSense in Microsoft Visual Studio 2005. However, in a derived <xref:System.Web.UI.WebControls.WebParts.WebPartManager> class, you can still access the property and its various members.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls.WebParts/WebPartPersonalization.xml b/xml/System.Web.UI.WebControls.WebParts/WebPartPersonalization.xml
index 2712c970638..80bf01aea17 100644
--- a/xml/System.Web.UI.WebControls.WebParts/WebPartPersonalization.xml
+++ b/xml/System.Web.UI.WebControls.WebParts/WebPartPersonalization.xml
@@ -45,7 +45,7 @@
 
 -   A Web.config file with a section that provides an example of authorizing a user to modify personalization state and to enter shared scope.
 
- The following code creates an aspx page  with a <xref:System.Web.UI.WebControls.WebParts.WebPartManager> and two Web Part zones and displays the `Color.ascx` and `Persmode.ascx` controls. The page loads a login page that is used to get the current user information. Use the ASP.NET Web Site Administration Tool in [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] to create users to access the page. See the Web.config file for an example of a user granted authorization in the configuration file to change scope and modify state information.
+ The following code creates an aspx page  with a <xref:System.Web.UI.WebControls.WebParts.WebPartManager> and two Web Part zones and displays the `Color.ascx` and `Persmode.ascx` controls. The page loads a login page that is used to get the current user information. Use the ASP.NET Web Site Administration Tool in Microsoft Visual Studio 2005 to create users to access the page. See the Web.config file for an example of a user granted authorization in the configuration file to change scope and modify state information.
 
  [!code-aspx-csharp[WebParts_WebPartPersonalization#1](~/samples/snippets/csharp/VS_Snippets_WebNet/WebParts_WebPartPersonalization/CS/Defaultcs.aspx#1)]
  [!code-aspx-vb[WebParts_WebPartPersonalization#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/WebParts_WebPartPersonalization/VB/Defaultvb.aspx#1)]
diff --git a/xml/System.Windows.Forms/ListView.xml b/xml/System.Windows.Forms/ListView.xml
index f7448b02f1f..4a57ebe2d24 100644
--- a/xml/System.Windows.Forms/ListView.xml
+++ b/xml/System.Windows.Forms/ListView.xml
@@ -6074,7 +6074,7 @@ When this property is set to `false`, selected items in the <xref:System.Windows
  Changes to the <xref:System.Windows.Forms.ListView> control in the .NET Framework 2.0 enable custom state images to be set to indicate whether an item is checked or unchecked or in an indeterminate state. With the addition of this feature, the .NET Framework 2.0 has different behavior than the .NET Framework 1.1. If you have created applications that depend on the behavior in the .NET Framework 1.1, be sure that the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property is set to `true`, which is the default value. In order to fully take advantage of custom state images, set <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> to `false`.
 
 > [!NOTE]
->  If you are using the [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] designer, the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property will be set to `false`.
+>  If you are using the Microsoft Visual Studio 2005 designer, the <xref:System.Windows.Forms.ListView.UseCompatibleStateImageBehavior%2A> property will be set to `false`.
 
  ]]></format>
         </remarks>
diff --git a/xml/ns-System.DirectoryServices.ActiveDirectory.xml b/xml/ns-System.DirectoryServices.ActiveDirectory.xml
index 6936d235283..ae443dfa929 100644
--- a/xml/ns-System.DirectoryServices.ActiveDirectory.xml
+++ b/xml/ns-System.DirectoryServices.ActiveDirectory.xml
@@ -9,7 +9,7 @@
 
  The <xref:System.DirectoryServices.ActiveDirectory> namespace is intended for use by application developers who are familiar with .NET programming using Visual Basic or C#. Knowledge of directory services programming is also helpful.
 
- <xref:System.DirectoryServices.ActiveDirectory> is part of [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] and is supported on any operating system that [!INCLUDE[vsprvsext](~/includes/vsprvsext-md.md)] is compatible with.
+ <xref:System.DirectoryServices.ActiveDirectory> is part of Microsoft Visual Studio 2005 and is supported on any operating system that Microsoft Visual Studio 2005 is compatible with.
 
  Many of the classes, methods, and properties in the <xref:System.DirectoryServices.ActiveDirectory> namespace use the <xref:System.Security.Permissions.SecurityAction.LinkDemand> code access security option. This means that the code access security demand only occurs during just-in- time compilation and that the demand is performed only on the calling assembly and not up the entire call stack. Because of this, callers should not pass objects created from this namespace at runtime to untrusted code.
 

From 9d31d40a0daea718f2f50710842d873d070dc00c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:35:13 -0800
Subject: [PATCH 201/236] vsprvslong

---
 .../GenerateApplicationManifest.xml                  |  2 +-
 .../LocalFileSettingsProvider.xml                    |  2 +-
 xml/System.Diagnostics/ConsoleTraceListener.xml      |  2 +-
 xml/System.Diagnostics/DebuggerHiddenAttribute.xml   |  2 +-
 .../DebuggerNonUserCodeAttribute.xml                 |  2 +-
 .../DebuggerStepperBoundaryAttribute.xml             |  2 +-
 .../DebuggerVisualizerAttribute.xml                  |  2 +-
 xml/System.Diagnostics/EventLog.xml                  |  6 +++---
 xml/System.Diagnostics/EventLogTraceListener.xml     |  2 +-
 xml/System.Diagnostics/PerformanceCounter.xml        |  4 ++--
 xml/System.Diagnostics/Process.xml                   |  2 +-
 xml/System.IO/FileSystemWatcher.xml                  |  8 ++++----
 .../AssemblyDescriptionAttribute.xml                 |  2 +-
 xml/System.Reflection/AssemblyKeyFileAttribute.xml   |  2 +-
 xml/System.Reflection/AssemblyVersionAttribute.xml   |  2 +-
 xml/System.Timers/Timer.xml                          |  4 ++--
 .../BaseDataBoundControlDesigner.xml                 |  2 +-
 .../ParameterEditorUserControl.xml                   |  2 +-
 .../RepeaterDesigner.xml                             |  2 +-
 .../AppSettingsExpressionEditor.xml                  |  2 +-
 xml/System.Web.UI.Design/ClientScriptItem.xml        |  4 ++--
 .../ConnectionStringsExpressionEditor.xml            |  2 +-
 xml/System.Web.UI.Design/ControlDesigner.xml         | 12 ++++++------
 xml/System.Web.UI.Design/ControlDesignerState.xml    |  2 +-
 xml/System.Web.UI.Design/DataFieldConverter.xml      |  2 +-
 xml/System.Web.UI.Design/DataMemberConverter.xml     |  2 +-
 xml/System.Web.UI.Design/DataSourceConverter.xml     |  2 +-
 xml/System.Web.UI.Design/DataSourceDesigner.xml      |  8 ++++----
 xml/System.Web.UI.Design/DesignerAutoFormat.xml      |  8 ++++----
 .../DesignerAutoFormatCollection.xml                 |  2 +-
 xml/System.Web.UI.Design/DesignerRegion.xml          |  2 +-
 .../DesignerRegionCollection.xml                     |  4 ++--
 xml/System.Web.UI.Design/ExpressionEditor.xml        |  2 +-
 .../ExpressionsCollectionConverter.xml               |  2 +-
 .../ExpressionsCollectionEditor.xml                  |  4 ++--
 .../HierarchicalDataSourceDesigner.xml               |  4 ++--
 xml/System.Web.UI.Design/HtmlControlDesigner.xml     |  2 +-
 .../IDataBindingSchemaProvider.xml                   |  2 +-
 xml/System.Web.UI.Design/IFolderProjectItem.xml      |  6 +++---
 .../IHierarchicalDataSourceDesigner.xml              |  4 ++--
 .../ResourceExpressionEditor.xml                     |  2 +-
 .../ResourceExpressionEditorSheet.xml                |  2 +-
 .../RouteUrlExpressionEditor.xml                     |  2 +-
 .../RouteValueExpressionEditor.xml                   |  2 +-
 xml/System.Web.UI.Design/TemplateDefinition.xml      |  4 ++--
 xml/System.Web.UI.Design/TemplateGroup.xml           |  2 +-
 xml/System.Web.UI.Design/TemplateGroupCollection.xml |  2 +-
 .../TemplateModeChangedEventArgs.xml                 |  2 +-
 .../TemplatedControlDesigner.xml                     |  2 +-
 xml/System.Web.UI.Design/ViewEvent.xml               |  2 +-
 xml/System.Web.UI.Design/WebFormsRootDesigner.xml    |  6 +++---
 xml/System.Web.UI.MobileControls/Form.xml            |  2 +-
 xml/System.Web.UI/UserControl.xml                    |  2 +-
 xml/System.Windows.Forms/DataGridView.xml            |  6 +++---
 xml/System.Windows.Forms/PropertyGrid.xml            |  4 ++--
 55 files changed, 86 insertions(+), 86 deletions(-)

diff --git a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
index f674d16a784..8634fff8ecf 100644
--- a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
@@ -35,7 +35,7 @@
 ## Remarks
  `EntryPoint` is an optional <xref:Microsoft.Build.Framework.ITaskItem>`[]` parameter that indicates the entry point for the generated manifest assembly. For a ClickOnce deployment manifest, this input specifies the ClickOnce application manifest.
 
- In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the [GenerateApplicationManifest Task](/visualstudio/msbuild/generateapplicationmanifest-task) requires an `EntryPoint` when an application manifest is generated. (Assembly or native manifests do not require an `EntryPoint`.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
+ In Visual Studio 2005, the [GenerateApplicationManifest Task](/visualstudio/msbuild/generateapplicationmanifest-task) requires an `EntryPoint` when an application manifest is generated. (Assembly or native manifests do not require an `EntryPoint`.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
 
  In Visual Studio 2008, [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] does not issue this error when the `EntryPoint` task parameter is not specified. Instead, the \<customHostSpecified> tag is inserted as a child of the \<entryPoint> tag, for example, as follows.
 
diff --git a/xml/System.Configuration/LocalFileSettingsProvider.xml b/xml/System.Configuration/LocalFileSettingsProvider.xml
index 8a240a402e8..c447bd76428 100644
--- a/xml/System.Configuration/LocalFileSettingsProvider.xml
+++ b/xml/System.Configuration/LocalFileSettingsProvider.xml
@@ -396,7 +396,7 @@
   
 2.  XML serialization is used.  
   
- However, you can specify a preferred serialization mechanism by using the <xref:System.Configuration.SettingsSerializeAsAttribute>. <xref:System.Configuration.LocalFileSettingsProvider> does not support binary serialization in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ However, you can specify a preferred serialization mechanism by using the <xref:System.Configuration.SettingsSerializeAsAttribute>. <xref:System.Configuration.LocalFileSettingsProvider> does not support binary serialization in Visual Studio 2005.  
   
  If a user-scoped settings property is set back to its default value explicitly, then the local file settings provider will remove the entry for the associated setting from the user configuration file. The next read access for this property will simply use the default value.  
   
diff --git a/xml/System.Diagnostics/ConsoleTraceListener.xml b/xml/System.Diagnostics/ConsoleTraceListener.xml
index a268586a292..e8bfe0d7199 100644
--- a/xml/System.Diagnostics/ConsoleTraceListener.xml
+++ b/xml/System.Diagnostics/ConsoleTraceListener.xml
@@ -51,7 +51,7 @@
   
  To write trace and debug messages to the console for a specific section of code, initialize a <xref:System.Diagnostics.ConsoleTraceListener> object and add it to the <xref:System.Diagnostics.Trace.Listeners%2A> collection. Instrument the section of code that contains messages using the <xref:System.Diagnostics.Trace> or <xref:System.Diagnostics.Debug> classes. At the end of the code section, remove the <xref:System.Diagnostics.ConsoleTraceListener> object from the <xref:System.Diagnostics.Trace.Listeners%2A> collection, and call the <xref:System.Diagnostics.TextWriterTraceListener.Close%2A> method on the <xref:System.Diagnostics.ConsoleTraceListener>.  
   
- To direct all trace and debug messages to the console while the application executes, add a <xref:System.Diagnostics.ConsoleTraceListener> object to the application configuration file. Edit the configuration file that corresponds to the name of your application, or the app.config file in a [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] project. In this file, insert an element for a <xref:System.Diagnostics.ConsoleTraceListener>.  
+ To direct all trace and debug messages to the console while the application executes, add a <xref:System.Diagnostics.ConsoleTraceListener> object to the application configuration file. Edit the configuration file that corresponds to the name of your application, or the app.config file in a Visual Studio 2005 project. In this file, insert an element for a <xref:System.Diagnostics.ConsoleTraceListener>.  
   
  The following example adds a <xref:System.Diagnostics.ConsoleTraceListener> object named `configConsoleListener` to the <xref:System.Diagnostics.Trace.Listeners%2A> collection.  
   
diff --git a/xml/System.Diagnostics/DebuggerHiddenAttribute.xml b/xml/System.Diagnostics/DebuggerHiddenAttribute.xml
index e5aae23591e..e7972c1f504 100644
--- a/xml/System.Diagnostics/DebuggerHiddenAttribute.xml
+++ b/xml/System.Diagnostics/DebuggerHiddenAttribute.xml
@@ -60,7 +60,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, the [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] debugger does not stop in a method marked with this attribute and does not allow a breakpoint to be set in the method. Other debugger attributes recognized by the [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] debugger are the <xref:System.Diagnostics.DebuggerNonUserCodeAttribute> and the <xref:System.Diagnostics.DebuggerStepThroughAttribute>.  
+ The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, the Visual Studio 2005 debugger does not stop in a method marked with this attribute and does not allow a breakpoint to be set in the method. Other debugger attributes recognized by the Visual Studio 2005 debugger are the <xref:System.Diagnostics.DebuggerNonUserCodeAttribute> and the <xref:System.Diagnostics.DebuggerStepThroughAttribute>.  
   
  For more information about using attributes, see [Attributes](/dotnet/standard/attributes/).  
   
diff --git a/xml/System.Diagnostics/DebuggerNonUserCodeAttribute.xml b/xml/System.Diagnostics/DebuggerNonUserCodeAttribute.xml
index 6e52e763db7..c1531a14a15 100644
--- a/xml/System.Diagnostics/DebuggerNonUserCodeAttribute.xml
+++ b/xml/System.Diagnostics/DebuggerNonUserCodeAttribute.xml
@@ -62,7 +62,7 @@
  Designer provided types and members that are not part of the code specifically created by the user can complicate the debugging experience. This attribute suppresses the display of these adjunct types and members in the debugger window and automatically steps through, rather than into, designer provided code.  When the debugger encounters this attribute when stepping through user code, the user experience is to not see the designer provided code and to step to the next user-supplied code statement.  
   
 > [!NOTE]
->  The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the debugger does not display an element with this attribute in the debugger window, does not stop in a method with this attribute, and does not allow a breakpoint to be set in the method.  
+>  The common language runtime attaches no semantics to this attribute. It is provided for use by source code debuggers. For example, in Visual Studio 2005, the debugger does not display an element with this attribute in the debugger window, does not stop in a method with this attribute, and does not allow a breakpoint to be set in the method.  
   
  The debugger behavior when the <xref:System.Diagnostics.DebuggerNonUserCodeAttribute> is present is similar to using a combination of the <xref:System.Diagnostics.DebuggerHiddenAttribute> attribute, which hides the code from the debugger, and the <xref:System.Diagnostics.DebuggerStepThroughAttribute> attribute, which tells the debugger to step through, rather than into, the code it is applied to.  
   
diff --git a/xml/System.Diagnostics/DebuggerStepperBoundaryAttribute.xml b/xml/System.Diagnostics/DebuggerStepperBoundaryAttribute.xml
index 37e915972c1..b235c782355 100644
--- a/xml/System.Diagnostics/DebuggerStepperBoundaryAttribute.xml
+++ b/xml/System.Diagnostics/DebuggerStepperBoundaryAttribute.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> attribute is used as an escape from the effect of a <xref:System.Diagnostics.DebuggerNonUserCodeAttribute>. When executing within the boundaries of the <xref:System.Diagnostics.DebuggerNonUserCodeAttribute>, designer-provided code is executed as a step-through until the next user supplied code is encountered. When context switches are made on a thread, the next user-supplied code module stepped into may not relate to the code that was in the process of being debugged. To avoid this debugging experience, use the <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> to escape from stepping through code to running code. For example, in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], encountering a <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> while stepping through code using the F10 key (or **Step Over** command) has the same effect as pressing the F5 key or using the **Start Debugging** command.  
+ The <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> attribute is used as an escape from the effect of a <xref:System.Diagnostics.DebuggerNonUserCodeAttribute>. When executing within the boundaries of the <xref:System.Diagnostics.DebuggerNonUserCodeAttribute>, designer-provided code is executed as a step-through until the next user supplied code is encountered. When context switches are made on a thread, the next user-supplied code module stepped into may not relate to the code that was in the process of being debugged. To avoid this debugging experience, use the <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> to escape from stepping through code to running code. For example, in Visual Studio 2005, encountering a <xref:System.Diagnostics.DebuggerStepperBoundaryAttribute> while stepping through code using the F10 key (or **Step Over** command) has the same effect as pressing the F5 key or using the **Start Debugging** command.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Diagnostics/DebuggerVisualizerAttribute.xml b/xml/System.Diagnostics/DebuggerVisualizerAttribute.xml
index 1d405cf334f..a1592fcad4e 100644
--- a/xml/System.Diagnostics/DebuggerVisualizerAttribute.xml
+++ b/xml/System.Diagnostics/DebuggerVisualizerAttribute.xml
@@ -54,7 +54,7 @@
  This attribute can be used at the assembly level. Typically the attribute constructors take two types.  The two types are a visualizer and a visualizer object source, specified as types or as fully qualified assembly type names. The second option is provided so that the visualizer assembly does not need to be referenced by the assembly containing the <xref:System.Diagnostics.DebuggerVisualizerAttribute>. This allows a component creator to ship the visualizer in a DLL to be called only at debug time. The <xref:System.Diagnostics.DebuggerVisualizerAttribute.Description%2A> property specifies the visualizer description that appears in the drop-down box. The target parameters specify the type that is the target of the visualizer. For more information about visualizers, see [Create Custom Visualizers of Data](/visualstudio/debugger/create-custom-visualizers-of-data).  
   
 > [!NOTE]
->  Visualizer and visualizer object source implementation is dependent upon the hosting debugger.  For information on creating a visualizer for [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], see [How to: Write a Visualizer](/visualstudio/debugger/create-custom-visualizers-of-data).  
+>  Visualizer and visualizer object source implementation is dependent upon the hosting debugger.  For information on creating a visualizer for Visual Studio 2005, see [How to: Write a Visualizer](/visualstudio/debugger/create-custom-visualizers-of-data).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Diagnostics/EventLog.xml b/xml/System.Diagnostics/EventLog.xml
index 2c35e964ff4..e1855669fa4 100644
--- a/xml/System.Diagnostics/EventLog.xml
+++ b/xml/System.Diagnostics/EventLog.xml
@@ -472,7 +472,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to start the initialization of a component used on a form or by another component. The <xref:System.Diagnostics.EventLog.EndInit%2A> method ends the initialization. Using the <xref:System.Diagnostics.EventLog.BeginInit%2A> and <xref:System.Diagnostics.EventLog.EndInit%2A> methods prevent the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to start the initialization of a component used on a form or by another component. The <xref:System.Diagnostics.EventLog.EndInit%2A> method ends the initialization. Using the <xref:System.Diagnostics.EventLog.BeginInit%2A> and <xref:System.Diagnostics.EventLog.EndInit%2A> methods prevent the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -1586,7 +1586,7 @@ SVC_UPDATE.EXE
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to end the initialization of a component used on a form or by another component. The <xref:System.Diagnostics.EventLog.BeginInit%2A> method starts the initialization. Using the <xref:System.Diagnostics.EventLog.BeginInit%2A> and <xref:System.Diagnostics.EventLog.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to end the initialization of a component used on a form or by another component. The <xref:System.Diagnostics.EventLog.BeginInit%2A> method starts the initialization. Using the <xref:System.Diagnostics.EventLog.BeginInit%2A> and <xref:System.Diagnostics.EventLog.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -3163,7 +3163,7 @@ SVC_UPDATE.EXE
   
  When the <xref:System.Diagnostics.EventLog.EntryWritten> event is handled by a visual Windows Forms component, such as a button, accessing the component through the system thread pool might not work, or might result in an exception. Avoid this by setting <xref:System.Diagnostics.EventLog.SynchronizingObject%2A> to a Windows Forms component, which causes the methods handling the <xref:System.Diagnostics.EventLog.EntryWritten> event to be called on the same thread on which the component was created.  
   
- If the <xref:System.Diagnostics.EventLog> is used inside [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] in a Windows Forms designer, <xref:System.Diagnostics.EventLog.SynchronizingObject%2A> is automatically set to the control containing the <xref:System.Diagnostics.EventLog>. For example, if you place an <xref:System.Diagnostics.EventLog> on a designer for Form1 (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.Diagnostics.EventLog.SynchronizingObject%2A> property of <xref:System.Diagnostics.EventLog> is set to the instance of Form1.  
+ If the <xref:System.Diagnostics.EventLog> is used inside Visual Studio 2005 in a Windows Forms designer, <xref:System.Diagnostics.EventLog.SynchronizingObject%2A> is automatically set to the control containing the <xref:System.Diagnostics.EventLog>. For example, if you place an <xref:System.Diagnostics.EventLog> on a designer for Form1 (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.Diagnostics.EventLog.SynchronizingObject%2A> property of <xref:System.Diagnostics.EventLog> is set to the instance of Form1.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Diagnostics/EventLogTraceListener.xml b/xml/System.Diagnostics/EventLogTraceListener.xml
index ef7075cc2bd..933d6704c45 100644
--- a/xml/System.Diagnostics/EventLogTraceListener.xml
+++ b/xml/System.Diagnostics/EventLogTraceListener.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- An instance of this <xref:System.Diagnostics.EventLogTraceListener> can be added to the <xref:System.Diagnostics.Debug.Listeners%2A?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace.Listeners%2A?displayProperty=nameWithType>, or <xref:System.Diagnostics.TraceSource.Listeners%2A?displayProperty=nameWithType> collections to send output from tracing or debugging to an <xref:System.Diagnostics.EventLog>. You can add the instance in your code or specify it in the application configuration file. To add an <xref:System.Diagnostics.EventLogTraceListener> using an application configuration file, edit the file that corresponds to the name of your application or the app.config file in a [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] project. In this file, insert an element for a <xref:System.Diagnostics.EventLogTraceListener?displayProperty=nameWithType> type.  
+ An instance of this <xref:System.Diagnostics.EventLogTraceListener> can be added to the <xref:System.Diagnostics.Debug.Listeners%2A?displayProperty=nameWithType>, <xref:System.Diagnostics.Trace.Listeners%2A?displayProperty=nameWithType>, or <xref:System.Diagnostics.TraceSource.Listeners%2A?displayProperty=nameWithType> collections to send output from tracing or debugging to an <xref:System.Diagnostics.EventLog>. You can add the instance in your code or specify it in the application configuration file. To add an <xref:System.Diagnostics.EventLogTraceListener> using an application configuration file, edit the file that corresponds to the name of your application or the app.config file in a Visual Studio 2005 project. In this file, insert an element for a <xref:System.Diagnostics.EventLogTraceListener?displayProperty=nameWithType> type.  
   
  The following example adds a <xref:System.Diagnostics.EventLogTraceListener> object named `myListener` to the <xref:System.Diagnostics.Trace.Listeners%2A?displayProperty=nameWithType> collection. The `initializeData` parameter specifies the name of the event log source that is to be passed to the <xref:System.Diagnostics.EventLogTraceListener.%23ctor%28System.String%29> constructor.  
   
diff --git a/xml/System.Diagnostics/PerformanceCounter.xml b/xml/System.Diagnostics/PerformanceCounter.xml
index ecabe424ebd..0a4c1ed3fc1 100644
--- a/xml/System.Diagnostics/PerformanceCounter.xml
+++ b/xml/System.Diagnostics/PerformanceCounter.xml
@@ -654,7 +654,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to start the initialization of a component that is used on a form or by another component. The <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> method ends the initialization. Using the <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> and <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> methods prevents the component from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to start the initialization of a component that is used on a form or by another component. The <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> method ends the initialization. Using the <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> and <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> methods prevents the component from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -1218,7 +1218,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to end the initialization of a component that is used on a form or by another component. The <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> method starts the initialization. Using the <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> and <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> methods prevents the component from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to end the initialization of a component that is used on a form or by another component. The <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> method starts the initialization. Using the <xref:System.Diagnostics.PerformanceCounter.BeginInit%2A> and <xref:System.Diagnostics.PerformanceCounter.EndInit%2A> methods prevents the component from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml
index cbe5987cc50..a269ccfeed2 100644
--- a/xml/System.Diagnostics/Process.xml
+++ b/xml/System.Diagnostics/Process.xml
@@ -5750,7 +5750,7 @@ The file specified in the <paramref name="fileName" /> could not be found.
   
  When the <xref:System.Diagnostics.Process.Exited> event is handled by a visual Windows Forms component, such as a <xref:System.Windows.Forms.Button>, accessing the component through the system thread pool might not work, or might result in an exception. Avoid this by setting <xref:System.Diagnostics.Process.SynchronizingObject%2A> to a Windows Forms component, which causes the methods handling the <xref:System.Diagnostics.Process.Exited> event to be called on the same thread on which the component was created.  
   
- If the <xref:System.Diagnostics.Process> is used inside [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] in a Windows Forms designer, <xref:System.Diagnostics.Process.SynchronizingObject%2A> is automatically set to the control that contains the <xref:System.Diagnostics.Process>. For example, if you place a <xref:System.Diagnostics.Process> on a designer for `Form1` (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.Diagnostics.Process.SynchronizingObject%2A> property of <xref:System.Diagnostics.Process> is set to the instance of `Form1`:  
+ If the <xref:System.Diagnostics.Process> is used inside Visual Studio 2005 in a Windows Forms designer, <xref:System.Diagnostics.Process.SynchronizingObject%2A> is automatically set to the control that contains the <xref:System.Diagnostics.Process>. For example, if you place a <xref:System.Diagnostics.Process> on a designer for `Form1` (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.Diagnostics.Process.SynchronizingObject%2A> property of <xref:System.Diagnostics.Process> is set to the instance of `Form1`:  
   
  [!code-cpp[Process_SynchronizingObject#2](~/samples/snippets/cpp/VS_Snippets_CLR/Process_SynchronizingObject/CPP/remarks.cpp#2)]
  [!code-csharp[Process_SynchronizingObject#2](~/samples/snippets/csharp/VS_Snippets_CLR/Process_SynchronizingObject/CS/remarks.cs#2)]
diff --git a/xml/System.IO/FileSystemWatcher.xml b/xml/System.IO/FileSystemWatcher.xml
index 8772e9d6250..3720daef19e 100644
--- a/xml/System.IO/FileSystemWatcher.xml
+++ b/xml/System.IO/FileSystemWatcher.xml
@@ -418,7 +418,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to start the initialization of a component used on a form or used by another component. The <xref:System.IO.FileSystemWatcher.EndInit%2A> method ends the initialization. Using the <xref:System.IO.FileSystemWatcher.BeginInit%2A> and <xref:System.IO.FileSystemWatcher.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to start the initialization of a component used on a form or used by another component. The <xref:System.IO.FileSystemWatcher.EndInit%2A> method ends the initialization. Using the <xref:System.IO.FileSystemWatcher.BeginInit%2A> and <xref:System.IO.FileSystemWatcher.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -803,7 +803,7 @@
       <Docs>
         <summary>Gets or sets a value indicating whether the component is enabled.</summary>
         <value>
-          <see langword="true" /> if the component is enabled; otherwise, <see langword="false" />. The default is <see langword="false" />. If you are using the component on a designer in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the default is <see langword="true" />.</value>
+          <see langword="true" /> if the component is enabled; otherwise, <see langword="false" />. The default is <see langword="false" />. If you are using the component on a designer in Visual Studio 2005, the default is <see langword="true" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -873,7 +873,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to end the initialization of a component used on a form or used by another component. The <xref:System.IO.FileSystemWatcher.BeginInit%2A> method starts the initialization. Using the <xref:System.IO.FileSystemWatcher.BeginInit%2A> and <xref:System.IO.FileSystemWatcher.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to end the initialization of a component used on a form or used by another component. The <xref:System.IO.FileSystemWatcher.BeginInit%2A> method starts the initialization. Using the <xref:System.IO.FileSystemWatcher.BeginInit%2A> and <xref:System.IO.FileSystemWatcher.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -1935,7 +1935,7 @@ Public Delegate Sub RenamedEventHandler(sender As Object, e As RenamedEventArgs)
   
  When the <xref:System.IO.FileSystemWatcher.Changed>, <xref:System.IO.FileSystemWatcher.Created>, <xref:System.IO.FileSystemWatcher.Deleted>, and <xref:System.IO.FileSystemWatcher.Renamed> events are handled by a visual Windows Forms component, such as a <xref:System.Windows.Forms.Button>, accessing the component through the system thread pool might not work, or may result in an exception. Avoid this by setting <xref:System.IO.FileSystemWatcher.SynchronizingObject%2A> to a Windows Forms component, which causes the methods that handle the <xref:System.IO.FileSystemWatcher.Changed>, <xref:System.IO.FileSystemWatcher.Created>, <xref:System.IO.FileSystemWatcher.Deleted>, and <xref:System.IO.FileSystemWatcher.Renamed> events to be called on the same thread on which the component was created.  
   
- If the <xref:System.IO.FileSystemWatcher> is used inside [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] in a Windows Forms designer, <xref:System.IO.FileSystemWatcher.SynchronizingObject%2A> automatically sets to the control that contains the <xref:System.IO.FileSystemWatcher>. For example, if you place a <xref:System.IO.FileSystemWatcher> on a designer for Form1 (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.IO.FileSystemWatcher.SynchronizingObject%2A> property of <xref:System.IO.FileSystemWatcher> is set to the instance of Form1.  
+ If the <xref:System.IO.FileSystemWatcher> is used inside Visual Studio 2005 in a Windows Forms designer, <xref:System.IO.FileSystemWatcher.SynchronizingObject%2A> automatically sets to the control that contains the <xref:System.IO.FileSystemWatcher>. For example, if you place a <xref:System.IO.FileSystemWatcher> on a designer for Form1 (which inherits from <xref:System.Windows.Forms.Form>) the <xref:System.IO.FileSystemWatcher.SynchronizingObject%2A> property of <xref:System.IO.FileSystemWatcher> is set to the instance of Form1.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Reflection/AssemblyDescriptionAttribute.xml b/xml/System.Reflection/AssemblyDescriptionAttribute.xml
index a6dd593dcf7..678e04904a5 100644
--- a/xml/System.Reflection/AssemblyDescriptionAttribute.xml
+++ b/xml/System.Reflection/AssemblyDescriptionAttribute.xml
@@ -56,7 +56,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you create a project in Microsoft Visual Studio 2005, this attribute is automatically applied with an empty string value. You can set its value in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] by selecting the **Properties** for the project from the **File** menu, and then by clicking **Assembly Information**. The attribute is saved in the AssemblyInfo file in your project, and it must be removed before you can specify it in code; otherwise, you will get an error that the attribute cannot be applied multiple times.  
+ When you create a project in Microsoft Visual Studio 2005, this attribute is automatically applied with an empty string value. You can set its value in Visual Studio 2005 by selecting the **Properties** for the project from the **File** menu, and then by clicking **Assembly Information**. The attribute is saved in the AssemblyInfo file in your project, and it must be removed before you can specify it in code; otherwise, you will get an error that the attribute cannot be applied multiple times.  
   
  When you right-click the assembly file in File Explorer, this attribute appears as the **Comments** value on the **Version** tab of the file properties dialog box.  
   
diff --git a/xml/System.Reflection/AssemblyKeyFileAttribute.xml b/xml/System.Reflection/AssemblyKeyFileAttribute.xml
index 98764d9c692..12850f8c0ab 100644
--- a/xml/System.Reflection/AssemblyKeyFileAttribute.xml
+++ b/xml/System.Reflection/AssemblyKeyFileAttribute.xml
@@ -127,7 +127,7 @@ sn -k TestPublicKey.snk
 ## Remarks  
  There is no default path for the <xref:System.Reflection.AssemblyKeyFileAttribute> constructor. The value set by the constructor is interpreted by the linker, or by Microsoft Visual Studio 2005, that invokes the linker.  
   
- The default setting for the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool assumes that the key file is in the current directory. In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], the Visual Basic and Visual C# compilers build and link to subdirectories of the project directory, so if you put the key file in the project directory the relative path might be "..\\..\keyfile.snk" or "..\keyfile.snk" in Visual Basic, or "..\\\\..\\\keyfile.snk" or "..\\\keyfile.snk" in C#. For C#, this attribute can be set in the project properties.  
+ The default setting for the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool assumes that the key file is in the current directory. In Visual Studio 2005, the Visual Basic and Visual C# compilers build and link to subdirectories of the project directory, so if you put the key file in the project directory the relative path might be "..\\..\keyfile.snk" or "..\keyfile.snk" in Visual Basic, or "..\\\\..\\\keyfile.snk" or "..\\\keyfile.snk" in C#. For C#, this attribute can be set in the project properties.  
   
 > [!CAUTION]
 >  Because the path and file name persist, ensure that the string you use with `AssemblyKeyFileAttribute` does not contain sensitive information.  
diff --git a/xml/System.Reflection/AssemblyVersionAttribute.xml b/xml/System.Reflection/AssemblyVersionAttribute.xml
index aeaf3b23d9a..191e99b0b05 100644
--- a/xml/System.Reflection/AssemblyVersionAttribute.xml
+++ b/xml/System.Reflection/AssemblyVersionAttribute.xml
@@ -75,7 +75,7 @@
 > [!NOTE]
 >  If you specify an asterisk for the build number, you cannot specify a revision number.  
   
- The assembly major and minor versions are used as the type library version number when the assembly is exported. Some COM hosts do not accept type libraries with the version number 0.0. Therefore, if you want to expose an assembly to COM clients, set the assembly version explicitly to 1.0 in the `AssemblyVersionAttribute` page for projects created outside [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] and with no `AssemblyVersionAttribute` specified. Do this even when the assembly version is 0.0. All projects created in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] have a default assembly version of 1.0.*.  
+ The assembly major and minor versions are used as the type library version number when the assembly is exported. Some COM hosts do not accept type libraries with the version number 0.0. Therefore, if you want to expose an assembly to COM clients, set the assembly version explicitly to 1.0 in the `AssemblyVersionAttribute` page for projects created outside Visual Studio 2005 and with no `AssemblyVersionAttribute` specified. Do this even when the assembly version is 0.0. All projects created in Visual Studio 2005 have a default assembly version of 1.0.*.  
   
  To get the name of an assembly you have loaded, call <xref:System.Reflection.Assembly.GetName%2A> on the assembly to get an <xref:System.Reflection.AssemblyName>, and then get the <xref:System.Reflection.AssemblyName.Version%2A> property. To get the name of an assembly you have not loaded, call <xref:System.Reflection.AssemblyName.GetAssemblyName%2A> from your client application to check the assembly version that your application uses.  
   
diff --git a/xml/System.Timers/Timer.xml b/xml/System.Timers/Timer.xml
index 95a4a99fe44..abf94172301 100644
--- a/xml/System.Timers/Timer.xml
+++ b/xml/System.Timers/Timer.xml
@@ -351,7 +351,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to start the initialization of a component that is used on a form or by another component. The <xref:System.Timers.Timer.EndInit%2A> method ends the initialization. Using the <xref:System.Timers.Timer.BeginInit%2A> and <xref:System.Timers.Timer.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to start the initialization of a component that is used on a form or by another component. The <xref:System.Timers.Timer.EndInit%2A> method ends the initialization. Using the <xref:System.Timers.Timer.BeginInit%2A> and <xref:System.Timers.Timer.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
@@ -653,7 +653,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] design environment uses this method to end the initialization of a component that is used on a form or by another component. The <xref:System.Timers.Timer.BeginInit%2A> method starts the initialization. Using the <xref:System.Timers.Timer.BeginInit%2A> and <xref:System.Timers.Timer.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
+ The Visual Studio 2005 design environment uses this method to end the initialization of a component that is used on a form or by another component. The <xref:System.Timers.Timer.BeginInit%2A> method starts the initialization. Using the <xref:System.Timers.Timer.BeginInit%2A> and <xref:System.Timers.Timer.EndInit%2A> methods prevents the control from being used before it is fully initialized.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design.WebControls/BaseDataBoundControlDesigner.xml b/xml/System.Web.UI.Design.WebControls/BaseDataBoundControlDesigner.xml
index 121ca8731a5..713870db50a 100644
--- a/xml/System.Web.UI.Design.WebControls/BaseDataBoundControlDesigner.xml
+++ b/xml/System.Web.UI.Design.WebControls/BaseDataBoundControlDesigner.xml
@@ -597,7 +597,7 @@
         <param name="configure">
           <see langword="true" /> to enable editing of the configuration, or <see langword="false" /> to disable configuration editing.</param>
         <param name="dataSourceID">The ID of a <see cref="T:System.Web.UI.DataSourceControl" /> control on the page.</param>
-        <summary>In a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], displays a dialog box to assist the user in creating a data source.</summary>
+        <summary>In a design host, such as Visual Studio 2005, displays a dialog box to assist the user in creating a data source.</summary>
         <returns>A <see cref="T:System.Windows.Forms.DialogResult" /> object.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Web.UI.WebControls.BaseDataBoundControl" />
diff --git a/xml/System.Web.UI.Design.WebControls/ParameterEditorUserControl.xml b/xml/System.Web.UI.Design.WebControls/ParameterEditorUserControl.xml
index 7f608020f32..924198bfc97 100644
--- a/xml/System.Web.UI.Design.WebControls/ParameterEditorUserControl.xml
+++ b/xml/System.Web.UI.Design.WebControls/ParameterEditorUserControl.xml
@@ -64,7 +64,7 @@
         <Parameter Name="serviceProvider" Type="System.IServiceProvider" />
       </Parameters>
       <Docs>
-        <param name="serviceProvider">An <see cref="T:System.IServiceProvider" /> interface to the current design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].</param>
+        <param name="serviceProvider">An <see cref="T:System.IServiceProvider" /> interface to the current design host, such as Visual Studio 2005.</param>
         <summary>Initializes a new instance of the <see cref="T:System.Web.UI.Design.WebControls.ParameterEditorUserControl" /> class using the specified <see cref="T:System.IServiceProvider" />.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Web.UI.Design.WebControls/RepeaterDesigner.xml b/xml/System.Web.UI.Design.WebControls/RepeaterDesigner.xml
index 67ce85d3cf5..c7a4465360c 100644
--- a/xml/System.Web.UI.Design.WebControls/RepeaterDesigner.xml
+++ b/xml/System.Web.UI.Design.WebControls/RepeaterDesigner.xml
@@ -279,7 +279,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Called by a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] after a user selects a data source at design time.</summary>
+        <summary>Called by a design host such as Visual Studio 2005 after a user selects a data source at design time.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.Web.UI.Design/AppSettingsExpressionEditor.xml b/xml/System.Web.UI.Design/AppSettingsExpressionEditor.xml
index 240c3988788..9b7c604d98a 100644
--- a/xml/System.Web.UI.Design/AppSettingsExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/AppSettingsExpressionEditor.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  The <xref:System.Web.UI.Design.AppSettingsExpressionEditor> class is derived from the <xref:System.Web.UI.Design.ExpressionEditor> class and provides an implementation for evaluating and associating an application setting reference with a control property at design time. For example, you can bind the value of a control property to the application setting expression `AppSettings:mySettingKeyName`, which indicates that the control property value is set using the `mySettingKeyName` value in the `appSettings` section of the Web configuration file.  
   
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.AppSettingsExpressionEditor> class to select an application setting from the `appSettings` configuration section, and then evaluates the selected expression for design-time rendering.  
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.AppSettingsExpressionEditor> class to select an application setting from the `appSettings` configuration section, and then evaluates the selected expression for design-time rendering.  
   
  When you browse to the <xref:System.Web.UI.Design.HtmlControlDesigner.Expressions%2A> property for a control in the design-time properties grid, the visual designer displays a dialog box to set expressions that provide the run-time value for a control property. You can select the expression type based on a list of expression prefixes. When you select the **AppSettings** expression prefix from the list, the visual designer host uses the associated <xref:System.Web.UI.Design.ExpressionEditorSheet> object to provide design-time editing functionality of `appSettings` expressions and uses <xref:System.Web.UI.Design.AppSettingsExpressionEditor> methods to evaluate and convert the expression string based on the syntax for an application setting expression. The visual designer host uses the evaluated expression result to assign control property values that are rendered on the design surface.  
   
diff --git a/xml/System.Web.UI.Design/ClientScriptItem.xml b/xml/System.Web.UI.Design/ClientScriptItem.xml
index 12bbf8d4a28..7b3159669e4 100644
--- a/xml/System.Web.UI.Design/ClientScriptItem.xml
+++ b/xml/System.Web.UI.Design/ClientScriptItem.xml
@@ -72,7 +72,7 @@
         <param name="source">The <see langword="src" /> attribute value for the <see langword="script" /> element, specifying an external source location for the client script contents.</param>
         <param name="language">The <see langword="language" /> attribute value for the <see langword="script" /> element, specifying the language of the script statements.</param>
         <param name="type">The type attribute value for the <see langword="script" /> element, indicating the MIME type for the associated scripting engine.</param>
-        <param name="id">The ID for the <see langword="script" /> element. This argument is required by the design host (for example, [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)]).</param>
+        <param name="id">The ID for the <see langword="script" /> element. This argument is required by the design host (for example, Visual Studio 2005).</param>
         <summary>Initializes a new instance of the <see cref="T:System.Web.UI.Design.ClientScriptItem" /> class using the provided parameters.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -94,7 +94,7 @@
   
      When a client script block does not specify the script type, the client browser determines the type.  
   
--   For `id`, the design host (for example, [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)]) will throw an <xref:System.ArgumentNullException>.  
+-   For `id`, the design host (for example, Visual Studio 2005) will throw an <xref:System.ArgumentNullException>.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/ConnectionStringsExpressionEditor.xml b/xml/System.Web.UI.Design/ConnectionStringsExpressionEditor.xml
index c527902ea0d..f8d70248b52 100644
--- a/xml/System.Web.UI.Design/ConnectionStringsExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/ConnectionStringsExpressionEditor.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.ConnectionStringsExpressionEditor> class to select a connection string from the `connectionStrings` configuration section.  
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.ConnectionStringsExpressionEditor> class to select a connection string from the `connectionStrings` configuration section.  
   
  The <xref:System.Web.UI.Design.ConnectionStringsExpressionEditor> class is derived from the <xref:System.Web.UI.Design.ExpressionEditor> class, and although it is public for technical reasons, there is no advantage in deriving from it.  
   
diff --git a/xml/System.Web.UI.Design/ControlDesigner.xml b/xml/System.Web.UI.Design/ControlDesigner.xml
index 11fc68655aa..a655a897b5f 100644
--- a/xml/System.Web.UI.Design/ControlDesigner.xml
+++ b/xml/System.Web.UI.Design/ControlDesigner.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.ControlDesigner> class provides a base control designer class that can be inherited from and extended to provide design-time support for a Web server control in a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ The <xref:System.Web.UI.Design.ControlDesigner> class provides a base control designer class that can be inherited from and extended to provide design-time support for a Web server control in a design host, such as Visual Studio 2005.  
   
  The object model for working with design-time rendering is improved over earlier versions, with the following new base classes to provide access to the simplified object model:  
   
@@ -43,7 +43,7 @@
 -   The <xref:System.Web.UI.Design.DesignerAutoFormatStyle> class.  
   
 ## Action Lists (Smart Tags)  
- Action lists are menus of important or widely used tasks that a page developer who uses a control can perform in a design-time user interface (UI), such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)]. For example, the design-time view of your control could provide a menu of available tasks. This includes a task to format the control automatically. To learn about action lists, start with the following features:  
+ Action lists are menus of important or widely used tasks that a page developer who uses a control can perform in a design-time user interface (UI), such as Visual Studio 2005. For example, the design-time view of your control could provide a menu of available tasks. This includes a task to format the control automatically. To learn about action lists, start with the following features:  
   
 -   The <xref:System.Web.UI.Design.ControlDesigner.ActionLists%2A> property.  
   
@@ -244,7 +244,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A complete Web server control includes not only the control, but also, possibly, a corresponding control designer class that is derived from the <xref:System.Web.UI.Design.ControlDesigner> class and a formatting class that is derived from the <xref:System.Web.UI.Design.DesignerAutoFormat> class. The <xref:System.Web.UI.Design.ControlDesigner.AutoFormats%2A> property is a collection of instances of the <xref:System.Web.UI.Design.DesignerAutoFormat> class. For a working example of automatic formatting in [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], see <xref:System.Web.UI.WebControls.Calendar>.  
+ A complete Web server control includes not only the control, but also, possibly, a corresponding control designer class that is derived from the <xref:System.Web.UI.Design.ControlDesigner> class and a formatting class that is derived from the <xref:System.Web.UI.Design.DesignerAutoFormat> class. The <xref:System.Web.UI.Design.ControlDesigner.AutoFormats%2A> property is a collection of instances of the <xref:System.Web.UI.Design.DesignerAutoFormat> class. For a working example of automatic formatting in Visual Studio 2005, see <xref:System.Web.UI.WebControls.Calendar>.  
   
    
   
@@ -1245,7 +1245,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A Web server control is in template mode when a read-only template is currently being viewed or an editable template is being edited in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ A Web server control is in template mode when a read-only template is currently being viewed or an editable template is being edited in a design host such as Visual Studio 2005.  
   
  The <xref:System.Web.UI.Design.ControlDesigner> class supplies a default <xref:System.Web.UI.Design.ViewEventHandler> object to update the <xref:System.Web.UI.Design.ControlDesigner.InTemplateMode%2A> value when the template mode changes for the associated control. Custom designers that are derived from the <xref:System.Web.UI.Design.TemplatedControlDesigner> class can override the <xref:System.Web.UI.Design.TemplatedControlDesigner.OnTemplateModeChanged%2A> method to perform additional processing when the template editing mode changes for a control in the design host.  
   
@@ -1399,7 +1399,7 @@
    
   
 ## Examples  
- The following code example demonstrates how to create a simple composite control with a <xref:System.Web.UI.WebControls.Label> and a <xref:System.Web.UI.WebControls.TextBox> control, together with properties to set the label text, and also the <xref:System.Web.UI.WebControls.TextBox.Text%2A>, <xref:System.Web.UI.WebControls.WebControl.Width%2A>, and <xref:System.Web.UI.WebControls.WebControl.BackColor%2A> properties of the <xref:System.Web.UI.WebControls.TextBox> control. An associated control designer class creates three <xref:System.ComponentModel.Design.DesignerActionMethodItem> commands, each of which sets two properties on the control. By using the <xref:System.Web.UI.Design.ControlDesigner.InvokeTransactedChange%2A> method, you can use the undo functionality of the design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], to roll back each completed transaction as a unit.  
+ The following code example demonstrates how to create a simple composite control with a <xref:System.Web.UI.WebControls.Label> and a <xref:System.Web.UI.WebControls.TextBox> control, together with properties to set the label text, and also the <xref:System.Web.UI.WebControls.TextBox.Text%2A>, <xref:System.Web.UI.WebControls.WebControl.Width%2A>, and <xref:System.Web.UI.WebControls.WebControl.BackColor%2A> properties of the <xref:System.Web.UI.WebControls.TextBox> control. An associated control designer class creates three <xref:System.ComponentModel.Design.DesignerActionMethodItem> commands, each of which sets two properties on the control. By using the <xref:System.Web.UI.Design.ControlDesigner.InvokeTransactedChange%2A> method, you can use the undo functionality of the design host, such as Visual Studio 2005, to roll back each completed transaction as a unit.  
   
  [!code-csharp[DesignerInvokeTransactedChange#1](~/samples/snippets/csharp/VS_Snippets_WebNet/DesignerInvokeTransactedChange/CS/InvokeTransactedChangeSample.cs#1)]
  [!code-vb[DesignerInvokeTransactedChange#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/DesignerInvokeTransactedChange/VB/InvokeTransactedChangeSample.vb#1)]  
@@ -2420,7 +2420,7 @@
 ## Examples  
  The following code example demonstrates how to create a control designer class that derives from the <xref:System.Web.UI.Design.ControlDesigner> class. This control designer supports a control with four possible templates.  
   
- To try it, compile the code, and then, in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], view the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
+ To try it, compile the code, and then, in a design host such as Visual Studio 2005, view the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
   
  [!code-csharp[DesignerTemplateGroupSample#1](~/samples/snippets/csharp/VS_Snippets_WebNet/DesignerTemplateGroupSample/CS/TemplateGroupsSample.cs#1)]
  [!code-vb[DesignerTemplateGroupSample#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/DesignerTemplateGroupSample/VB/TemplateGroupsSample.vb#1)]  
diff --git a/xml/System.Web.UI.Design/ControlDesignerState.xml b/xml/System.Web.UI.Design/ControlDesignerState.xml
index 95e85b325da..84e1badbc0d 100644
--- a/xml/System.Web.UI.Design/ControlDesignerState.xml
+++ b/xml/System.Web.UI.Design/ControlDesignerState.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.ControlDesignerState> class is a wrapper for the <xref:System.ComponentModel.Design.IComponentDesignerStateService> interface, which is the interface between a designer and a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ The <xref:System.Web.UI.Design.ControlDesignerState> class is a wrapper for the <xref:System.ComponentModel.Design.IComponentDesignerStateService> interface, which is the interface between a designer and a design host, such as Visual Studio 2005.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.Design/DataFieldConverter.xml b/xml/System.Web.UI.Design/DataFieldConverter.xml
index 23a8dcecace..1d38ee67ec3 100644
--- a/xml/System.Web.UI.Design/DataFieldConverter.xml
+++ b/xml/System.Web.UI.Design/DataFieldConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  <xref:System.Web.UI.Design.DataFieldConverter> can retrieve a list of data fields from the current data source of a design-time component.  
   
- This type converter is used by [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] to provide the values that appear in the list of data fields in the Properties window.  
+ This type converter is used by Visual Studio 2005 to provide the values that appear in the list of data fields in the Properties window.  
   
 > [!CAUTION]
 >  You should never access a type converter directly. Instead, call the appropriate converter by using <xref:System.ComponentModel.TypeDescriptor>. For more information, see the examples in the <xref:System.ComponentModel.TypeConverter> base class.  
diff --git a/xml/System.Web.UI.Design/DataMemberConverter.xml b/xml/System.Web.UI.Design/DataMemberConverter.xml
index 859accd53b7..165a38a4cc8 100644
--- a/xml/System.Web.UI.Design/DataMemberConverter.xml
+++ b/xml/System.Web.UI.Design/DataMemberConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  <xref:System.Web.UI.Design.DataMemberConverter> provides methods that can retrieve a list of data members from the current data source of a design-time component.  
   
- This type converter is used by [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] to provide the values that appear in the list of data members in the Properties window.  
+ This type converter is used by Visual Studio 2005 to provide the values that appear in the list of data members in the Properties window.  
   
 > [!CAUTION]
 >  You should never access a type converter directly. Instead, call the appropriate converter by using <xref:System.ComponentModel.TypeDescriptor>. For more information, see the examples in the <xref:System.ComponentModel.TypeConverter> base class.  
diff --git a/xml/System.Web.UI.Design/DataSourceConverter.xml b/xml/System.Web.UI.Design/DataSourceConverter.xml
index d339edda640..f347c3de539 100644
--- a/xml/System.Web.UI.Design/DataSourceConverter.xml
+++ b/xml/System.Web.UI.Design/DataSourceConverter.xml
@@ -23,7 +23,7 @@
 ## Remarks  
  <xref:System.Web.UI.Design.DataSourceConverter> provides methods that can be used to retrieve a list of data sources accessible to the current design-time component.  
   
- This type converter is used by [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] to provide the values that appear in the list of data sources in the **Properties** window.  
+ This type converter is used by Visual Studio 2005 to provide the values that appear in the list of data sources in the **Properties** window.  
   
 > [!CAUTION]
 >  You should never access a type converter directly. Instead, call the appropriate converter by using <xref:System.ComponentModel.TypeDescriptor>. For more information, see the examples in the <xref:System.ComponentModel.TypeConverter> base class.  
diff --git a/xml/System.Web.UI.Design/DataSourceDesigner.xml b/xml/System.Web.UI.Design/DataSourceDesigner.xml
index f6ba4d9d561..1223e774e98 100644
--- a/xml/System.Web.UI.Design/DataSourceDesigner.xml
+++ b/xml/System.Web.UI.Design/DataSourceDesigner.xml
@@ -168,7 +168,7 @@
 ## Remarks  
  Use the <xref:System.Web.UI.Design.DataSourceDesigner.CanConfigure%2A> property in a custom class to enable or disable design-time configuration for a specific data source.  
   
- A design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] uses the <xref:System.Web.UI.Design.DataSourceDesigner.CanConfigure%2A> property to determine whether a command to configure the data source appears in the action list menu at design time.  
+ A design host such as Visual Studio 2005 uses the <xref:System.Web.UI.Design.DataSourceDesigner.CanConfigure%2A> property to determine whether a command to configure the data source appears in the action list menu at design time.  
   
  ]]></format>
         </remarks>
@@ -205,9 +205,9 @@
 ## Remarks  
  Use the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property in a derived class to enable or disable the ability to refresh the schema at design time for a specific data source. If your application requires an invariant data structure and the schema will never change, you want the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property to return `false`.  
   
- A design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] uses the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property to determine whether a command to refresh the schema appears in the action list menu at design time.  
+ A design host such as Visual Studio 2005 uses the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property to determine whether a command to refresh the schema appears in the action list menu at design time.  
   
- In a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you can see the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property in action by completing the following process:  
+ In a design host such as Visual Studio 2005, you can see the <xref:System.Web.UI.Design.DataSourceDesigner.CanRefreshSchema%2A> property in action by completing the following process:  
   
 1.  On your page, place a <xref:System.Web.UI.WebControls.SqlDataSource> or an <xref:System.Web.UI.WebControls.AccessDataSource> control.  
   
@@ -251,7 +251,7 @@
 ## Remarks  
  The <xref:System.Web.UI.Design.DataSourceDesigner.Configure%2A> method is not supported in the <xref:System.Web.UI.Design.DataSourceDesigner> class; however, it can be overridden by custom data source designers inheriting from the <xref:System.Web.UI.Design.DataSourceDesigner> class.  
   
- In a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you can see the <xref:System.Web.UI.Design.DataSourceDesigner.Configure%2A> method in action by completing the following process:  
+ In a design host such as Visual Studio 2005, you can see the <xref:System.Web.UI.Design.DataSourceDesigner.Configure%2A> method in action by completing the following process:  
   
 1.  Put a <xref:System.Web.UI.WebControls.SqlDataSource> or an <xref:System.Web.UI.WebControls.AccessDataSource> control on your page.  
   
diff --git a/xml/System.Web.UI.Design/DesignerAutoFormat.xml b/xml/System.Web.UI.Design/DesignerAutoFormat.xml
index e6e9ee0a03c..ad21553096c 100644
--- a/xml/System.Web.UI.Design/DesignerAutoFormat.xml
+++ b/xml/System.Web.UI.Design/DesignerAutoFormat.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Web.UI.Design.DesignerAutoFormat> provides a base class that can be inherited from and extended to display a formatted custom Web server control at design time in a visual designer tool such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ <xref:System.Web.UI.Design.DesignerAutoFormat> provides a base class that can be inherited from and extended to display a formatted custom Web server control at design time in a visual designer tool such as Visual Studio 2005.  
   
  A control developer provides automatic formatting in order to help developers who use the control to select a preferred display. A custom <xref:System.Web.UI.Design.DesignerAutoFormat> object works with a custom control designer to provide automatic formatting at design time for a custom control. For example, the <xref:System.Web.UI.WebControls.Calendar> control provides a variety of formats that can be applied by a developer at design time.  
   
@@ -38,7 +38,7 @@
   
 -   The <xref:System.Web.UI.Design.DesignerAutoFormat.Apply%2A> method, which applies the named format to the specified control.  
   
--   The <xref:System.Web.UI.Design.DesignerAutoFormat.GetPreviewControl%2A> method, which provides a copy of the control for previewing in an **AutoFormat** dialog box of a visual designer such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+-   The <xref:System.Web.UI.Design.DesignerAutoFormat.GetPreviewControl%2A> method, which provides a copy of the control for previewing in an **AutoFormat** dialog box of a visual designer such as Visual Studio 2005.  
   
 -   The <xref:System.Web.UI.Design.DesignerAutoFormat.Name%2A> property, which provides the text to display in a list of formats in a visual designer.  
   
@@ -171,7 +171,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.DesignerAutoFormat.GetPreviewControl%2A> method is used by visual designers, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], in an **AutoFormat** dialog box to display a formatted run-time preview of the control at design time before applying the format to the actual control.  
+ The <xref:System.Web.UI.Design.DesignerAutoFormat.GetPreviewControl%2A> method is used by visual designers, such as Visual Studio 2005, in an **AutoFormat** dialog box to display a formatted run-time preview of the control at design time before applying the format to the actual control.  
   
  Regardless of the setting of the <xref:System.Web.UI.Design.SupportsPreviewControlAttribute> attribute for the <xref:System.Web.UI.Design.ControlDesigner> object, the <xref:System.Web.UI.Design.DesignerAutoFormat.GetPreviewControl%2A> method returns a copy of the control in the `runtimeControl` parameter.  
   
@@ -218,7 +218,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A visual designer, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.DesignerAutoFormat.Name%2A> property from each <xref:System.Web.UI.Design.DesignerAutoFormat> object in the <xref:System.Web.UI.Design.ControlDesigner.AutoFormats%2A> collection of a <xref:System.Web.UI.Design.ControlDesigner> to create a list of available automatic style formats.  
+ A visual designer, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.DesignerAutoFormat.Name%2A> property from each <xref:System.Web.UI.Design.DesignerAutoFormat> object in the <xref:System.Web.UI.Design.ControlDesigner.AutoFormats%2A> collection of a <xref:System.Web.UI.Design.ControlDesigner> to create a list of available automatic style formats.  
   
    
   
diff --git a/xml/System.Web.UI.Design/DesignerAutoFormatCollection.xml b/xml/System.Web.UI.Design/DesignerAutoFormatCollection.xml
index 21e0db40cb1..0a2f449f5a5 100644
--- a/xml/System.Web.UI.Design/DesignerAutoFormatCollection.xml
+++ b/xml/System.Web.UI.Design/DesignerAutoFormatCollection.xml
@@ -407,7 +407,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.DesignerAutoFormatCollection.PreviewSize%2A> property examines each format in the collection and returns the largest height and the largest width in a <xref:System.Drawing.Size> structure. A visual designer, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.DesignerAutoFormatCollection.PreviewSize%2A> to determine the initial size of the **AutoFormat** dialog box. The minimum size is 200-by-200 pixels.  
+ The <xref:System.Web.UI.Design.DesignerAutoFormatCollection.PreviewSize%2A> property examines each format in the collection and returns the largest height and the largest width in a <xref:System.Drawing.Size> structure. A visual designer, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.DesignerAutoFormatCollection.PreviewSize%2A> to determine the initial size of the **AutoFormat** dialog box. The minimum size is 200-by-200 pixels.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/DesignerRegion.xml b/xml/System.Web.UI.Design/DesignerRegion.xml
index 622930e0a55..c10ef14cd68 100644
--- a/xml/System.Web.UI.Design/DesignerRegion.xml
+++ b/xml/System.Web.UI.Design/DesignerRegion.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.DesignerRegion> object represents a region of content within the design-time markup that is generated by a <xref:System.Web.UI.Design.ControlDesigner> implementation. A control developer uses designer regions in a custom <xref:System.Web.UI.Design.ControlDesigner> implementation to define separate areas within the design-time markup for the associated control and to provide editing and event handling for the area. A visual designer, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], can use designer regions to display the separate areas of a control on the design surface and to raise user events for the region to the control designer. Designer regions can simplify a control designer implementation because many region-based features are provided by the base designer classes and the visual designer.  
+ The <xref:System.Web.UI.Design.DesignerRegion> object represents a region of content within the design-time markup that is generated by a <xref:System.Web.UI.Design.ControlDesigner> implementation. A control developer uses designer regions in a custom <xref:System.Web.UI.Design.ControlDesigner> implementation to define separate areas within the design-time markup for the associated control and to provide editing and event handling for the area. A visual designer, such as Visual Studio 2005, can use designer regions to display the separate areas of a control on the design surface and to raise user events for the region to the control designer. Designer regions can simplify a control designer implementation because many region-based features are provided by the base designer classes and the visual designer.  
   
  The <xref:System.Web.UI.Design.DesignerRegion> class provides the base functionality for designer regions, such as the ability to click, select, and highlight a region in the design surface. Use a <xref:System.Web.UI.Design.DesignerRegion> object in a control designer implementation to define a region that does not require editing. Use the derived <xref:System.Web.UI.Design.EditableDesignerRegion> class in a control designer implementation to define a region with editable content at design time. Use the derived <xref:System.Web.UI.Design.TemplatedEditableDesignerRegion> class in a control designer implementation to define an editable region that represents a template in a control.  
   
diff --git a/xml/System.Web.UI.Design/DesignerRegionCollection.xml b/xml/System.Web.UI.Design/DesignerRegionCollection.xml
index ba370f3feb4..eff071dbce5 100644
--- a/xml/System.Web.UI.Design/DesignerRegionCollection.xml
+++ b/xml/System.Web.UI.Design/DesignerRegionCollection.xml
@@ -30,7 +30,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.ControlDesigner> class, and any derived class, uses the <xref:System.Web.UI.Design.DesignerRegionCollection> class to contain and enumerate the designer regions for the control in a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ The <xref:System.Web.UI.Design.ControlDesigner> class, and any derived class, uses the <xref:System.Web.UI.Design.DesignerRegionCollection> class to contain and enumerate the designer regions for the control in a design host, such as Visual Studio 2005.  
   
  For example, the <xref:System.Web.UI.Design.ControlDesigner.GetDesignTimeHtml%2A?displayProperty=nameWithType> method can be used to define and add regions to the collection.  
   
@@ -137,7 +137,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.DesignerRegionCollection.%23ctor%2A> constructor creates an empty collection and sets the <xref:System.Web.UI.Design.DesignerRegionCollection.Owner%2A> property to the specified control designer object. The visual designer, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.DesignerRegionCollection.%23ctor%2A> constructor to initialize a designer region collection for a specific control designer.  
+ The <xref:System.Web.UI.Design.DesignerRegionCollection.%23ctor%2A> constructor creates an empty collection and sets the <xref:System.Web.UI.Design.DesignerRegionCollection.Owner%2A> property to the specified control designer object. The visual designer, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.DesignerRegionCollection.%23ctor%2A> constructor to initialize a designer region collection for a specific control designer.  
   
  You can add elements to the collection by using the <xref:System.Web.UI.Design.DesignerRegionCollection.Add%2A> or <xref:System.Web.UI.Design.DesignerRegionCollection.Insert%2A> method.  
   
diff --git a/xml/System.Web.UI.Design/ExpressionEditor.xml b/xml/System.Web.UI.Design/ExpressionEditor.xml
index 9e9061cab21..ca9a4d42277 100644
--- a/xml/System.Web.UI.Design/ExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/ExpressionEditor.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.ExpressionEditor> class to present custom expression editor sheets to the user, and then evaluate the selected expression for design-time rendering.  
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.ExpressionEditor> class to present custom expression editor sheets to the user, and then evaluate the selected expression for design-time rendering.  
   
  When you browse the <xref:System.Web.UI.Design.HtmlControlDesigner.Expressions%2A> property for a control in the design-time Properties grid, the visual designer displays a dialog box to set expressions for a control property. You can select the expression type based on a list of expression prefixes. When you select an expression prefix from the list, the visual designer uses the associated <xref:System.Web.UI.Design.ExpressionEditor> and <xref:System.Web.UI.Design.ExpressionEditorSheet> objects to set, evaluate, and convert the expression string based on the syntax for that type of expression. The visual designer sets the expression for the associated control property, and then uses the evaluated expression result to assign control property values that are rendered on the design surface.  
   
diff --git a/xml/System.Web.UI.Design/ExpressionsCollectionConverter.xml b/xml/System.Web.UI.Design/ExpressionsCollectionConverter.xml
index f906b37a8a0..2997c2b047a 100644
--- a/xml/System.Web.UI.Design/ExpressionsCollectionConverter.xml
+++ b/xml/System.Web.UI.Design/ExpressionsCollectionConverter.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  The <xref:System.Web.UI.Design.ExpressionsCollectionConverter> class converts an <xref:System.Web.UI.ExpressionBindingCollection> to a string for the property-editing grid at design time, which always appears as an empty string ("").  
   
- A designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
+ A designer host, such as Visual Studio 2005, uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
   
 > [!NOTE]
 >  You should never access a type converter directly. This implementation of <xref:System.ComponentModel.TypeConverter> is intended only for use by an <xref:System.Web.UI.ExpressionBindingCollection> object at design time.  
diff --git a/xml/System.Web.UI.Design/ExpressionsCollectionEditor.xml b/xml/System.Web.UI.Design/ExpressionsCollectionEditor.xml
index 4130f225bbf..67a88bf916a 100644
--- a/xml/System.Web.UI.Design/ExpressionsCollectionEditor.xml
+++ b/xml/System.Web.UI.Design/ExpressionsCollectionEditor.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  An instance of the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> class is a <xref:System.Drawing.Design.UITypeEditor> object that can be used at design time to select and edit a collection of expression bindings, and assign the expressions to a control property.  
   
- A designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> class to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
+ A designer host, such as Visual Studio 2005, uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> class to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
   
  ]]></format>
     </remarks>
@@ -93,7 +93,7 @@
 ## Remarks  
  The <xref:System.Web.UI.Design.ExpressionsCollectionEditor.EditValue%2A> method launches the user interface for editing the `value` object. The designer host calls the <xref:System.Web.UI.Design.ExpressionsCollectionEditor.EditValue%2A> method when you attempt to edit the value of a property that this editor is associated with. The input service provider is used to obtain any editing services that are required within the <xref:System.Web.UI.Design.ExpressionsCollectionEditor.EditValue%2A>.  
   
- A designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> class to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
+ A designer host, such as Visual Studio 2005, uses the <xref:System.Web.Compilation.ExpressionBuilder> and <xref:System.Web.UI.Design.ExpressionEditor> class implementations with the <xref:System.Web.UI.Design.ExpressionsCollectionEditor> and <xref:System.Web.UI.Design.ExpressionsCollectionConverter> classes to set the expression bindings for control properties at design time, and the <xref:System.Web.UI.Design.ControlPersister> class to persist the expressions for run time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type. The expression string is bound to the control property at design time, and then used at run time to determine the value for the property.  
   
  If users cancel the user interface without modifying the expression binding collection, the <xref:System.Web.UI.Design.ExpressionsCollectionEditor.EditValue%2A> method returns the input `value` parameter.  
   
diff --git a/xml/System.Web.UI.Design/HierarchicalDataSourceDesigner.xml b/xml/System.Web.UI.Design/HierarchicalDataSourceDesigner.xml
index 3b6f264a0eb..ebd894d0e4e 100644
--- a/xml/System.Web.UI.Design/HierarchicalDataSourceDesigner.xml
+++ b/xml/System.Web.UI.Design/HierarchicalDataSourceDesigner.xml
@@ -114,7 +114,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses this property to determine whether to show a **Configure** command in the Smart-Tag menu in design view.  
+ A design host, such as Visual Studio 2005, uses this property to determine whether to show a **Configure** command in the Smart-Tag menu in design view.  
   
  ]]></format>
         </remarks>
@@ -149,7 +149,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses this property to determine whether to show a **Refresh Schema** command in the Smart-Tag menu in design view.  
+ A design host, such as Visual Studio 2005, uses this property to determine whether to show a **Refresh Schema** command in the Smart-Tag menu in design view.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/HtmlControlDesigner.xml b/xml/System.Web.UI.Design/HtmlControlDesigner.xml
index e1fdb4ee87b..3f8d16bb700 100644
--- a/xml/System.Web.UI.Design/HtmlControlDesigner.xml
+++ b/xml/System.Web.UI.Design/HtmlControlDesigner.xml
@@ -229,7 +229,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.Compilation.ExpressionBuilder> class to get the <xref:System.Web.UI.Design.ExpressionEditor> class to get the <xref:System.Web.UI.Design.ExpressionEditorSheet> to set expressions for control properties at design time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type.  
+ The design host, such as Visual Studio 2005, uses the <xref:System.Web.Compilation.ExpressionBuilder> class to get the <xref:System.Web.UI.Design.ExpressionEditor> class to get the <xref:System.Web.UI.Design.ExpressionEditorSheet> to set expressions for control properties at design time. Expression strings reference a localizable resource, an application setting, a connection string, or a custom expression type.  
   
  The <xref:System.Web.UI.Design.HtmlControlDesigner.Expressions%2A> collection contains an <xref:System.Web.UI.ExpressionBinding> element for each control property that has an associated expression string. Each <xref:System.Web.UI.ExpressionBinding.ExpressionPrefix%2A> property for each element indicates the associated expression builder implementation. The expression string is parsed and evaluated by its associated <xref:System.Web.Compilation.ExpressionBuilder> to determine the control property value at run time.  
   
diff --git a/xml/System.Web.UI.Design/IDataBindingSchemaProvider.xml b/xml/System.Web.UI.Design/IDataBindingSchemaProvider.xml
index d59f81ec0f1..fceab7b216d 100644
--- a/xml/System.Web.UI.Design/IDataBindingSchemaProvider.xml
+++ b/xml/System.Web.UI.Design/IDataBindingSchemaProvider.xml
@@ -17,7 +17,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.IDataBindingSchemaProvider> class is implemented by design hosts, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], that host the data-binding dialog box to show schema.  
+ The <xref:System.Web.UI.Design.IDataBindingSchemaProvider> class is implemented by design hosts, such as Visual Studio 2005, that host the data-binding dialog box to show schema.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.Design/IFolderProjectItem.xml b/xml/System.Web.UI.Design/IFolderProjectItem.xml
index dbc03496e3c..eaecd1c5da7 100644
--- a/xml/System.Web.UI.Design/IFolderProjectItem.xml
+++ b/xml/System.Web.UI.Design/IFolderProjectItem.xml
@@ -41,7 +41,7 @@
       <Docs>
         <param name="name">The name of the document.</param>
         <param name="content">An array of type <see cref="T:System.Byte" /> containing the document contents.</param>
-        <summary>Adds a document to a project folder in a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].</summary>
+        <summary>Adds a document to a project folder in a design host, such as Visual Studio 2005.</summary>
         <returns>An <see cref="T:System.Web.UI.Design.IDocumentProjectItem" /> representing the added document.</returns>
         <remarks>To be added.</remarks>
         <altmember cref="T:System.Web.UI.Design.IDocumentProjectItem" />
@@ -70,7 +70,7 @@
       </Parameters>
       <Docs>
         <param name="name">The name for the new folder.</param>
-        <summary>Creates a new folder in a project folder of a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].</summary>
+        <summary>Creates a new folder in a project folder of a design host, such as Visual Studio 2005.</summary>
         <returns>An <see cref="T:System.Web.UI.Design.IFolderProjectItem" /> representing the new folder.</returns>
         <remarks>To be added.</remarks>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/37899azc(v=vs.100)">Extending Design-Time Support</related>
@@ -94,7 +94,7 @@
         <ReturnType>System.Collections.ICollection</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a collection of items in a project folder in a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].</summary>
+        <summary>Gets a collection of items in a project folder in a design host, such as Visual Studio 2005.</summary>
         <value>An <see cref="T:System.Collections.ICollection" /> containing the items in the project folder of the design host.</value>
         <remarks>To be added.</remarks>
         <related type="Article" href="https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/37899azc(v=vs.100)">Extending Design-Time Support</related>
diff --git a/xml/System.Web.UI.Design/IHierarchicalDataSourceDesigner.xml b/xml/System.Web.UI.Design/IHierarchicalDataSourceDesigner.xml
index 2d16ec5d969..6d7f9d88a7a 100644
--- a/xml/System.Web.UI.Design/IHierarchicalDataSourceDesigner.xml
+++ b/xml/System.Web.UI.Design/IHierarchicalDataSourceDesigner.xml
@@ -51,7 +51,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.IHierarchicalDataSourceDesigner.CanConfigure%2A> property is used by a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], to determine whether to display a **Configure** command at design time.  
+ The <xref:System.Web.UI.Design.IHierarchicalDataSourceDesigner.CanConfigure%2A> property is used by a design host, such as Visual Studio 2005, to determine whether to display a **Configure** command at design time.  
   
  ]]></format>
         </remarks>
@@ -87,7 +87,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.IHierarchicalDataSourceDesigner.CanRefreshSchema%2A> property is used by a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], to determine whether to display a **Refresh Schema** command at design time.  
+ The <xref:System.Web.UI.Design.IHierarchicalDataSourceDesigner.CanRefreshSchema%2A> property is used by a design host, such as Visual Studio 2005, to determine whether to display a **Refresh Schema** command at design time.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/ResourceExpressionEditor.xml b/xml/System.Web.UI.Design/ResourceExpressionEditor.xml
index 9e5329b24f7..4e4d5320746 100644
--- a/xml/System.Web.UI.Design/ResourceExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/ResourceExpressionEditor.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  The <xref:System.Web.UI.Design.ResourceExpressionEditor> class derives from the <xref:System.Web.UI.Design.ExpressionEditor> class and provides an implementation for evaluating and associating a resource reference with a control property at design time. For example, you can bind the value of a control property to the resource expression `Resources:submitText`, which indicates that the control property value is set using the resource named `submitText`.  
   
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.ResourceExpressionEditor> class to specify a resource class, key, and designer default value for a resource expression, and then evaluate the selected resource expression for design-time rendering.  
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.ResourceExpressionEditor> class to specify a resource class, key, and designer default value for a resource expression, and then evaluate the selected resource expression for design-time rendering.  
   
  When you browse the <xref:System.Web.UI.Design.HtmlControlDesigner.Expressions%2A> property for a control in the design-time properties grid, the visual designer displays a dialog box to set expressions that provide the run-time value for a control property. You can select the expression type based on a list of expression prefixes. When you select the **Resources** expression prefix in the list, the visual designer uses the <xref:System.Web.UI.Design.ResourceExpressionEditor> methods to set, evaluate, and convert the expression based on the resource expression syntax. The visual designer uses the evaluated expression result to assign control property values that are rendered on the design surface.  
   
diff --git a/xml/System.Web.UI.Design/ResourceExpressionEditorSheet.xml b/xml/System.Web.UI.Design/ResourceExpressionEditorSheet.xml
index 3e2cb8ded7d..59a4a77106f 100644
--- a/xml/System.Web.UI.Design/ResourceExpressionEditorSheet.xml
+++ b/xml/System.Web.UI.Design/ResourceExpressionEditorSheet.xml
@@ -123,7 +123,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], global resource files are located in the App_GlobalResources folder.  
+ In Visual Studio 2005, global resource files are located in the App_GlobalResources folder.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.Design/RouteUrlExpressionEditor.xml b/xml/System.Web.UI.Design/RouteUrlExpressionEditor.xml
index 6434a553d0d..c901ca389bf 100644
--- a/xml/System.Web.UI.Design/RouteUrlExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/RouteUrlExpressionEditor.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.RouteUrlExpressionEditor> class to compose a `RouteUrl` markup expression.
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.RouteUrlExpressionEditor> class to compose a `RouteUrl` markup expression.
 
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.Design/RouteValueExpressionEditor.xml b/xml/System.Web.UI.Design/RouteValueExpressionEditor.xml
index 870ca81d800..d4dd182833f 100644
--- a/xml/System.Web.UI.Design/RouteValueExpressionEditor.xml
+++ b/xml/System.Web.UI.Design/RouteValueExpressionEditor.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- A visual designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], uses the <xref:System.Web.UI.Design.RouteValueExpressionEditor> class to compose a `RouteValue` markup expression.
+ A visual designer host, such as Visual Studio 2005, uses the <xref:System.Web.UI.Design.RouteValueExpressionEditor> class to compose a `RouteValue` markup expression.
 
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.Design/TemplateDefinition.xml b/xml/System.Web.UI.Design/TemplateDefinition.xml
index 5045c1ed8d3..13f62f61034 100644
--- a/xml/System.Web.UI.Design/TemplateDefinition.xml
+++ b/xml/System.Web.UI.Design/TemplateDefinition.xml
@@ -20,14 +20,14 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.TemplateDefinition> class provides a base template definition class that can be inherited from and extended for a control designer to use in providing support for templated controls in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)]. A design host uses the properties and methods of the <xref:System.Web.UI.Design.TemplateDefinition> class to facilitate creating and editing a template at design time.  
+ The <xref:System.Web.UI.Design.TemplateDefinition> class provides a base template definition class that can be inherited from and extended for a control designer to use in providing support for templated controls in a design host such as Visual Studio 2005. A design host uses the properties and methods of the <xref:System.Web.UI.Design.TemplateDefinition> class to facilitate creating and editing a template at design time.  
   
    
   
 ## Examples  
  The following code example demonstrates how to derive a custom class from the <xref:System.Web.UI.Design.ControlDesigner> class. This control designer supports a control with four possible templates.  
   
- To try it, add a reference to the System.Design.dll assembly, compile the code, and then, in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], look at the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
+ To try it, add a reference to the System.Design.dll assembly, compile the code, and then, in a design host such as Visual Studio 2005, look at the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
   
  [!code-csharp[DesignerTemplateGroupSample#1](~/samples/snippets/csharp/VS_Snippets_WebNet/DesignerTemplateGroupSample/CS/TemplateGroupsSample.cs#1)]
  [!code-vb[DesignerTemplateGroupSample#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/DesignerTemplateGroupSample/VB/TemplateGroupsSample.vb#1)]  
diff --git a/xml/System.Web.UI.Design/TemplateGroup.xml b/xml/System.Web.UI.Design/TemplateGroup.xml
index 682c75b263e..e9fafc9c95a 100644
--- a/xml/System.Web.UI.Design/TemplateGroup.xml
+++ b/xml/System.Web.UI.Design/TemplateGroup.xml
@@ -22,7 +22,7 @@
 ## Examples  
  The following code example demonstrates how to create a control designer class that derives from the <xref:System.Web.UI.Design.ControlDesigner> class. This control designer supports a control with four possible templates.  
   
- To try it, compile the code, and then, in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], look at the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
+ To try it, compile the code, and then, in a design host such as Visual Studio 2005, look at the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
   
  [!code-csharp[DesignerTemplateGroupSample#1](~/samples/snippets/csharp/VS_Snippets_WebNet/DesignerTemplateGroupSample/CS/TemplateGroupsSample.cs#1)]
  [!code-aspx-csharp[DesignerTemplateGroupSample#2](~/samples/snippets/csharp/VS_Snippets_WebNet/DesignerTemplateGroupSample/CS/TemplateGroupsSample.aspx#2)]  
diff --git a/xml/System.Web.UI.Design/TemplateGroupCollection.xml b/xml/System.Web.UI.Design/TemplateGroupCollection.xml
index e000dab7147..44a8c9b69e8 100644
--- a/xml/System.Web.UI.Design/TemplateGroupCollection.xml
+++ b/xml/System.Web.UI.Design/TemplateGroupCollection.xml
@@ -30,7 +30,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.ControlDesigner> class, and any derived class, defines the <xref:System.Web.UI.Design.ControlDesigner.TemplateGroups%2A> property as a <xref:System.Web.UI.Design.TemplateGroupCollection> object. The <xref:System.Web.UI.Design.TemplateGroupCollection> property is typically used only by a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ The <xref:System.Web.UI.Design.ControlDesigner> class, and any derived class, defines the <xref:System.Web.UI.Design.ControlDesigner.TemplateGroups%2A> property as a <xref:System.Web.UI.Design.TemplateGroupCollection> object. The <xref:System.Web.UI.Design.TemplateGroupCollection> property is typically used only by a design host such as Visual Studio 2005.  
   
  The collection dynamically increases in size as objects are added. Indexes in this collection are zero-based. Use the <xref:System.Web.UI.Design.TemplateGroupCollection.Count%2A> property to determine how many groups are in the collection.  
   
diff --git a/xml/System.Web.UI.Design/TemplateModeChangedEventArgs.xml b/xml/System.Web.UI.Design/TemplateModeChangedEventArgs.xml
index 67f5fcf28d4..4b50ebbc8fc 100644
--- a/xml/System.Web.UI.Design/TemplateModeChangedEventArgs.xml
+++ b/xml/System.Web.UI.Design/TemplateModeChangedEventArgs.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.IControlDesignerView.ViewEvent> event is raised by a designer host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], for certain actions on a control on the design surface. For example, an event is raised when you enter or exit template editing mode for a control.  
+ The <xref:System.Web.UI.Design.IControlDesignerView.ViewEvent> event is raised by a designer host, such as Visual Studio 2005, for certain actions on a control on the design surface. For example, an event is raised when you enter or exit template editing mode for a control.  
   
  The <xref:System.Web.UI.Design.ControlDesigner> class supplies a default delegate to handle the <xref:System.Web.UI.Design.IControlDesignerView.ViewEvent> event. When you exit or enter template editing mode, the designer host initializes a <xref:System.Web.UI.Design.ViewEventArgs> object for a <xref:System.Web.UI.Design.ViewEvent.TemplateModeChanged> event type, and then sets the <xref:System.Web.UI.Design.ViewEventArgs.EventArgs%2A> property with a <xref:System.Web.UI.Design.TemplateModeChangedEventArgs> object.  
   
diff --git a/xml/System.Web.UI.Design/TemplatedControlDesigner.xml b/xml/System.Web.UI.Design/TemplatedControlDesigner.xml
index 8c735837a13..811117f4662 100644
--- a/xml/System.Web.UI.Design/TemplatedControlDesigner.xml
+++ b/xml/System.Web.UI.Design/TemplatedControlDesigner.xml
@@ -23,7 +23,7 @@
 ## Examples  
  The following code example demonstrates how to create a control designer class that uses templates and derives from the <xref:System.Web.UI.Design.ControlDesigner> class.  
   
- To run the example, compile the code, and then in a design host such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], view the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
+ To run the example, compile the code, and then in a design host such as Visual Studio 2005, view the page in Design view. Select the control, click the action list to select a template to modify, and then use the drag-and-drop feature to move controls into the template.  
   
 > [!NOTE]
 >  Your project must have a reference to the `System.Design` assembly.  
diff --git a/xml/System.Web.UI.Design/ViewEvent.xml b/xml/System.Web.UI.Design/ViewEvent.xml
index 0f9cbd67297..ec1b4100343 100644
--- a/xml/System.Web.UI.Design/ViewEvent.xml
+++ b/xml/System.Web.UI.Design/ViewEvent.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Web.UI.Design.ViewEvent> object is provided to the designer component by the design host, for example [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], when raising an event caused by certain user actions on the design-time view of a control. The <xref:System.Web.UI.Design.IControlDesignerView.ViewEvent?displayProperty=nameWithType> event is handled by a <xref:System.Web.UI.Design.ViewEventHandler> delegate method, which takes a <xref:System.Web.UI.Design.ViewEventArgs> object as a parameter. The <xref:System.Web.UI.Design.ViewEventArgs.EventType%2A> property of the <xref:System.Web.UI.Design.ViewEventArgs> class is a <xref:System.Web.UI.Design.ViewEvent> object. The <xref:System.Web.UI.Design.ViewEventHandler> delegate method compares the <xref:System.Web.UI.Design.ViewEventArgs.EventType%2A> property to the static <xref:System.Web.UI.Design.ViewEvent> fields to determine which type of action raised the event. For example, an event is raised under the following circumstances:  
+ A <xref:System.Web.UI.Design.ViewEvent> object is provided to the designer component by the design host, for example Visual Studio 2005, when raising an event caused by certain user actions on the design-time view of a control. The <xref:System.Web.UI.Design.IControlDesignerView.ViewEvent?displayProperty=nameWithType> event is handled by a <xref:System.Web.UI.Design.ViewEventHandler> delegate method, which takes a <xref:System.Web.UI.Design.ViewEventArgs> object as a parameter. The <xref:System.Web.UI.Design.ViewEventArgs.EventType%2A> property of the <xref:System.Web.UI.Design.ViewEventArgs> class is a <xref:System.Web.UI.Design.ViewEvent> object. The <xref:System.Web.UI.Design.ViewEventHandler> delegate method compares the <xref:System.Web.UI.Design.ViewEventArgs.EventType%2A> property to the static <xref:System.Web.UI.Design.ViewEvent> fields to determine which type of action raised the event. For example, an event is raised under the following circumstances:  
   
 -   You click a region on the design surface.  
   
diff --git a/xml/System.Web.UI.Design/WebFormsRootDesigner.xml b/xml/System.Web.UI.Design/WebFormsRootDesigner.xml
index 7e83c4064ce..51495dd0622 100644
--- a/xml/System.Web.UI.Design/WebFormsRootDesigner.xml
+++ b/xml/System.Web.UI.Design/WebFormsRootDesigner.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], must provide its own derived version of the <xref:System.Web.UI.Design.WebFormsRootDesigner> class to control designers through the <xref:System.Web.UI.Design.ControlDesigner.RootDesigner%2A> property of the designer. Control designers use the <xref:System.Web.UI.Design.ControlDesigner.RootDesigner%2A> property to access and manipulate the containing Web Forms page at design time.  
+ A design host, such as Visual Studio 2005, must provide its own derived version of the <xref:System.Web.UI.Design.WebFormsRootDesigner> class to control designers through the <xref:System.Web.UI.Design.ControlDesigner.RootDesigner%2A> property of the designer. Control designers use the <xref:System.Web.UI.Design.ControlDesigner.RootDesigner%2A> property to access and manipulate the containing Web Forms page at design time.  
   
  ]]></format>
     </remarks>
@@ -207,14 +207,14 @@
         <Parameter Name="serviceProvider" Type="System.IServiceProvider" />
       </Parameters>
       <Docs>
-        <param name="serviceProvider">A design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], cast as an <see cref="T:System.IServiceProvider" />.</param>
+        <param name="serviceProvider">A design host, such as Visual Studio 2005, cast as an <see cref="T:System.IServiceProvider" />.</param>
         <summary>Returns a design-time <see cref="T:System.ComponentModel.Design.DesignerActionService" /> object.</summary>
         <returns>A design-time designer action service object.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.Design.WebFormsRootDesigner.CreateDesignerActionService%2A> method is called by a control designer and provides a way for action items for the control designer to be implemented in the Web Forms page through a design host, such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].  
+ The <xref:System.Web.UI.Design.WebFormsRootDesigner.CreateDesignerActionService%2A> method is called by a control designer and provides a way for action items for the control designer to be implemented in the Web Forms page through a design host, such as Visual Studio 2005.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.MobileControls/Form.xml b/xml/System.Web.UI.MobileControls/Form.xml
index 95de3dee513..7b74b0fd0d3 100644
--- a/xml/System.Web.UI.MobileControls/Form.xml
+++ b/xml/System.Web.UI.MobileControls/Form.xml
@@ -311,7 +311,7 @@
 ## Examples  
  The following code example demonstrates how to use the <xref:System.Web.UI.MobileControls.Form.ControlToPaginate%2A> property of the <xref:System.Web.UI.MobileControls.Form> class to specify which control to paginate.  
   
- The example creates a page with two forms. One form has a very long string that on some devices must be paginated to give the user access to the entire text. In order to see the pagination in action, you must view the example on a device that handles pagination. In [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you can use one of the device emulators available with the **Device Emulator Manager** on the **Tools** menu.  
+ The example creates a page with two forms. One form has a very long string that on some devices must be paginated to give the user access to the entire text. In order to see the pagination in action, you must view the example on a device that handles pagination. In Visual Studio 2005, you can use one of the device emulators available with the **Device Emulator Manager** on the **Tools** menu.  
   
 > [!NOTE]
 >  The following code example uses the single-file code model and may not work correctly if copied directly into a code-behind file. This code example must be copied into an empty text file that has an .aspx extension. For more information, see [ASP.NET Web Forms Page Syntax Overview](https://docs.microsoft.com/previous-versions/aspnet/k33801s3(v=vs.100)).  
diff --git a/xml/System.Web.UI/UserControl.xml b/xml/System.Web.UI/UserControl.xml
index 8e244375743..26385874d5c 100644
--- a/xml/System.Web.UI/UserControl.xml
+++ b/xml/System.Web.UI/UserControl.xml
@@ -385,7 +385,7 @@
           <format type="text/markdown"><![CDATA[
 
 ## Examples
- The following example calls the <xref:System.Web.UI.UserControl.DesignerInitialize%2A> method during the `Page_Init` stage of request processing. This makes the user control available to a RAD designer such as [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)].
+ The following example calls the <xref:System.Web.UI.UserControl.DesignerInitialize%2A> method during the `Page_Init` stage of request processing. This makes the user control available to a RAD designer such as Visual Studio 2005.
 
  [!code-csharp[UserControl1#1](~/samples/snippets/csharp/VS_Snippets_WebNet/UserControl1/CS/usercontrol1.cs.aspx#1)]
  [!code-vb[UserControl1#1](~/samples/snippets/visualbasic/VS_Snippets_WebNet/UserControl1/VB/usercontrol1.vb.aspx#1)]
diff --git a/xml/System.Windows.Forms/DataGridView.xml b/xml/System.Windows.Forms/DataGridView.xml
index ad6fd88faf7..a52dd8ed842 100644
--- a/xml/System.Windows.Forms/DataGridView.xml
+++ b/xml/System.Windows.Forms/DataGridView.xml
@@ -4132,7 +4132,7 @@ The <xref:System.Windows.Forms.DataGridView> control replaces and extends the <x
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can handle this event to customize the appearance of cells in the control. You can paint entire cells yourself, or paint specific parts of cells and use the <xref:System.Windows.Forms.DataGridViewCellPaintingEventArgs.PaintBackground%2A?displayProperty=nameWithType> or <xref:System.Windows.Forms.DataGridViewCellPaintingEventArgs.PaintContent%2A?displayProperty=nameWithType> methods to paint other parts. You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
+ You can handle this event to customize the appearance of cells in the control. You can paint entire cells yourself, or paint specific parts of cells and use the <xref:System.Windows.Forms.DataGridViewCellPaintingEventArgs.PaintBackground%2A?displayProperty=nameWithType> or <xref:System.Windows.Forms.DataGridViewCellPaintingEventArgs.PaintContent%2A?displayProperty=nameWithType> methods to paint other parts. You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using Visual Studio 2005, you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
   
  When handling this event, you should access the cell through the parameters of the event handler, rather than access the cell directly.  
   
@@ -17246,7 +17246,7 @@ The <xref:System.Windows.Forms.DataGridView> control replaces and extends the <x
   
 -   <xref:System.Windows.Forms.DataGridViewRowPostPaintEventArgs.PaintHeader%2A> 
   
- You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
+ You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using Visual Studio 2005, you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
   
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).
 
@@ -17296,7 +17296,7 @@ The <xref:System.Windows.Forms.DataGridView> control replaces and extends the <x
   
 -   <xref:System.Windows.Forms.DataGridViewRowPrePaintEventArgs.PaintHeader%2A> 
   
- You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)], you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
+ You can also use the <xref:System.Windows.Forms.VisualStyles.VisualStyleRenderer> class to paint standard controls using the current theme. For more information, see [Rendering Controls with Visual Styles](/dotnet/framework/winforms/controls/rendering-controls-with-visual-styles). If you are using Visual Studio 2005, you also have access to a large library of standard images that you can use with the <xref:System.Windows.Forms.DataGridView> control.  
   
  For more information about how to handle events, see [Handling and Raising Events](/dotnet/standard/events/).
 
diff --git a/xml/System.Windows.Forms/PropertyGrid.xml b/xml/System.Windows.Forms/PropertyGrid.xml
index d364be058f9..81dc65948b3 100644
--- a/xml/System.Windows.Forms/PropertyGrid.xml
+++ b/xml/System.Windows.Forms/PropertyGrid.xml
@@ -3670,7 +3670,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  This member is an explicit interface member implementation. It can be used only when the <xref:System.Windows.Forms.PropertyGrid> instance is cast to an <xref:System.Windows.Forms.ComponentModel.Com2Interop.IComPropertyBrowser> interface.  
   
- [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] saves some of the <xref:System.Windows.Forms.PropertyGrid> control states, such as the <xref:System.Windows.Forms.PropertyGrid.PropertySort%2A> and <xref:System.Windows.Forms.PropertyGrid.HelpVisible%2A> properties, to the registry and loads them the next time the user runs the application.  
+ Visual Studio 2005 saves some of the <xref:System.Windows.Forms.PropertyGrid> control states, such as the <xref:System.Windows.Forms.PropertyGrid.PropertySort%2A> and <xref:System.Windows.Forms.PropertyGrid.HelpVisible%2A> properties, to the registry and loads them the next time the user runs the application.  
   
  ]]></format>
         </remarks>
@@ -3709,7 +3709,7 @@ This member is an explicit interface member implementation. It can be used only
 ## Remarks  
  This member is an explicit interface member implementation. It can be used only when the <xref:System.Windows.Forms.PropertyGrid> instance is cast to an <xref:System.Windows.Forms.ComponentModel.Com2Interop.IComPropertyBrowser> interface.  
   
- [!INCLUDE[vsprvslong](~/includes/vsprvslong-md.md)] saves some of the <xref:System.Windows.Forms.PropertyGrid> control states, such as the <xref:System.Windows.Forms.PropertyGrid.PropertySort%2A> and <xref:System.Windows.Forms.PropertyGrid.HelpVisible%2A> properties, to the registry and loads them the next time the user runs the application.  
+ Visual Studio 2005 saves some of the <xref:System.Windows.Forms.PropertyGrid> control states, such as the <xref:System.Windows.Forms.PropertyGrid.PropertySort%2A> and <xref:System.Windows.Forms.PropertyGrid.HelpVisible%2A> properties, to the registry and loads them the next time the user runs the application.  
   
  ]]></format>
         </remarks>

From b862f3e41d875f5d5defa46be0009a41b097520c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:35:37 -0800
Subject: [PATCH 202/236] vstecado

---
 xml/System.Data.Linq/DataContext.xml                    | 2 +-
 xml/System.Data.Metadata.Edm/MetadataProperty.xml       | 2 +-
 xml/System.Data.Metadata.Edm/ParameterTypeSemantics.xml | 2 +-
 xml/System.Web.UI.WebControls/ContextDataSource.xml     | 2 +-
 xml/ns-System.Data.EntityClient.xml                     | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Data.Linq/DataContext.xml b/xml/System.Data.Linq/DataContext.xml
index f67b7536b35..f4e3c47b324 100644
--- a/xml/System.Data.Linq/DataContext.xml
+++ b/xml/System.Data.Linq/DataContext.xml
@@ -1499,7 +1499,7 @@ Next
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The primary scenario for this property is interoperability with relational [!INCLUDE[vstecado](~/includes/vstecado-md.md)] code. For example, use this property when you write your own `Create`/`Update`/`Delete` methods to set the `Transaction` property on the ADO `Command` object.  
+ The primary scenario for this property is interoperability with relational ADO.NET code. For example, use this property when you write your own `Create`/`Update`/`Delete` methods to set the `Transaction` property on the ADO `Command` object.  
   
  Note the following:  
   
diff --git a/xml/System.Data.Metadata.Edm/MetadataProperty.xml b/xml/System.Data.Metadata.Edm/MetadataProperty.xml
index 1e693eec517..964a1b32473 100644
--- a/xml/System.Data.Metadata.Edm/MetadataProperty.xml
+++ b/xml/System.Data.Metadata.Edm/MetadataProperty.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can access every item in the [!INCLUDE[vstecado](~/includes/vstecado-md.md)] metadata hierarchy as a strongly typed property bag. The <xref:System.Data.Metadata.Edm.EdmType> class provides properties called <xref:System.Data.Metadata.Edm.EdmType.Name%2A>, <xref:System.Data.Metadata.Edm.EdmType.NamespaceName%2A>, and so on. The <xref:System.Data.Metadata.Edm.EdmType> class also inherits a <xref:System.Data.Metadata.Edm.MetadataItem.MetadataProperties%2A> property, which is a collection of <xref:System.Data.Metadata.Edm.MetadataProperty> objects. When the application creates an instance of the <xref:System.Data.Metadata.Edm.EdmType> class, the <xref:System.Data.Metadata.Edm.MetadataItem.MetadataProperties%2A> property automatically contains a collection of <xref:System.Data.Metadata.Edm.MetadataProperty> objects for <xref:System.Data.Metadata.Edm.EdmType.Name%2A> property, <xref:System.Data.Metadata.Edm.EdmType.NamespaceName%2A> property, and so on.  
+ You can access every item in the ADO.NET metadata hierarchy as a strongly typed property bag. The <xref:System.Data.Metadata.Edm.EdmType> class provides properties called <xref:System.Data.Metadata.Edm.EdmType.Name%2A>, <xref:System.Data.Metadata.Edm.EdmType.NamespaceName%2A>, and so on. The <xref:System.Data.Metadata.Edm.EdmType> class also inherits a <xref:System.Data.Metadata.Edm.MetadataItem.MetadataProperties%2A> property, which is a collection of <xref:System.Data.Metadata.Edm.MetadataProperty> objects. When the application creates an instance of the <xref:System.Data.Metadata.Edm.EdmType> class, the <xref:System.Data.Metadata.Edm.MetadataItem.MetadataProperties%2A> property automatically contains a collection of <xref:System.Data.Metadata.Edm.MetadataProperty> objects for <xref:System.Data.Metadata.Edm.EdmType.Name%2A> property, <xref:System.Data.Metadata.Edm.EdmType.NamespaceName%2A> property, and so on.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Data.Metadata.Edm/ParameterTypeSemantics.xml b/xml/System.Data.Metadata.Edm/ParameterTypeSemantics.xml
index eaf2e371a9a..615a61078d1 100644
--- a/xml/System.Data.Metadata.Edm/ParameterTypeSemantics.xml
+++ b/xml/System.Data.Metadata.Edm/ParameterTypeSemantics.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class specifies type semantics for promotability, implicit conversion, and explicit conversion for the provider primitive types. [!INCLUDE[vstecado](~/includes/vstecado-md.md)] reads this information from the storage provider manifest file into the <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class. Then, [!INCLUDE[vstecado](~/includes/vstecado-md.md)] uses the <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class to determine the appropriate function definitions based on the parameter types.  
+ The <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class specifies type semantics for promotability, implicit conversion, and explicit conversion for the provider primitive types. ADO.NET reads this information from the storage provider manifest file into the <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class. Then, ADO.NET uses the <xref:System.Data.Metadata.Edm.ParameterTypeSemantics> class to determine the appropriate function definitions based on the parameter types.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Web.UI.WebControls/ContextDataSource.xml b/xml/System.Web.UI.WebControls/ContextDataSource.xml
index bb85ab28549..0f28f3a5700 100644
--- a/xml/System.Web.UI.WebControls/ContextDataSource.xml
+++ b/xml/System.Web.UI.WebControls/ContextDataSource.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.UI.WebControls.ContextDataSource> class is a base class that can be used to create any data source control that supports the Entity Framework, LINQ-to-SQL, [!INCLUDE[vstecado](~/includes/vstecado-md.md)] Data Services, or other data provider. The <xref:System.Web.UI.WebControls.ContextDataSource> class is derived from <xref:System.Web.UI.WebControls.QueryableDataSource>. The <xref:System.Web.UI.WebControls.QueryableDataSource> class provides a <xref:System.Web.UI.WebControls.ContextDataSource.ContextTypeName%2A> property that represents the context type that the data source control works with. For example, the context type for the <xref:System.Web.UI.WebControls.LinqDataSource> class is the <xref:System.Data.Linq.DataContext> object.  
+ The <xref:System.Web.UI.WebControls.ContextDataSource> class is a base class that can be used to create any data source control that supports the Entity Framework, LINQ-to-SQL, ADO.NET Data Services, or other data provider. The <xref:System.Web.UI.WebControls.ContextDataSource> class is derived from <xref:System.Web.UI.WebControls.QueryableDataSource>. The <xref:System.Web.UI.WebControls.QueryableDataSource> class provides a <xref:System.Web.UI.WebControls.ContextDataSource.ContextTypeName%2A> property that represents the context type that the data source control works with. For example, the context type for the <xref:System.Web.UI.WebControls.LinqDataSource> class is the <xref:System.Data.Linq.DataContext> object.  
   
  ]]></format>
     </remarks>
diff --git a/xml/ns-System.Data.EntityClient.xml b/xml/ns-System.Data.EntityClient.xml
index 555e908aa71..e63c430b257 100644
--- a/xml/ns-System.Data.EntityClient.xml
+++ b/xml/ns-System.Data.EntityClient.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[
 
 ## Remarks
- The `EntityClient` provider uses storage-specific [!INCLUDE[vstecado](~/includes/vstecado-md.md)] Data Provider classes and mapping metadata for interacting with entity data models. `EntityClient` translates operations performed on conceptual entities into operations performed on physical data sources. It translates result sets returned from physical data sources into conceptual entities.
+ The `EntityClient` provider uses storage-specific ADO.NET Data Provider classes and mapping metadata for interacting with entity data models. `EntityClient` translates operations performed on conceptual entities into operations performed on physical data sources. It translates result sets returned from physical data sources into conceptual entities.
 
 > [!NOTE]
 >  For more information about how to use this namespace in Entity Framework applications, see [ADO.NET Entity Framework](/dotnet/framework/data/adonet/ef/).

From 696b0c5e8937e4103698960b9873c6188d282cac Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:36:09 -0800
Subject: [PATCH 203/236] vstecasp

---
 .../WebClass.xml                              | 16 +++++++--------
 .../WebClassContainingClassNotOptional.xml    |  4 ++--
 .../WebClassCouldNotFindEvent.xml             |  6 +++---
 ...WebClassNextItemCannotBeCurrentWebItem.xml |  4 ++--
 .../WebClassNextItemRespondNotFound.xml       |  4 ++--
 .../WebClassUserWebClassNameNotOptional.xml   |  4 ++--
 .../WebClassWebClassFileNameNotOptional.xml   |  4 ++--
 .../WebClassWebItemNotValid.xml               |  4 ++--
 .../WebItem.xml                               | 12 +++++------
 .../WebItemAssociatedWebClassNotOptional.xml  |  4 ++--
 .../WebItemClosingTagNotFound.xml             |  4 ++--
 .../WebItemCouldNotLoadEmbeddedResource.xml   |  4 ++--
 .../WebItemCouldNotLoadTemplateFile.xml       |  4 ++--
 .../WebItemNameNotOptional.xml                |  4 ++--
 .../WebItemNoTemplateSpecified.xml            |  4 ++--
 .../WebItemTooManyNestedTags.xml              |  4 ++--
 ...ItemUnexpectedErrorReadingTemplateFile.xml |  4 ++--
 .../AsyncOperationManager.xml                 |  2 +-
 xml/System.Drawing.Design/ToolboxService.xml  |  4 ++--
 .../ClaimsAuthorizationModule.xml             |  2 +-
 .../SessionAuthenticationModule.xml           |  6 +++---
 .../WSFederationAuthenticationModule.xml      | 10 +++++-----
 ...pNetCompatibilityRequirementsAttribute.xml | 20 +++++++++----------
 .../AspNetCompatibilityRequirementsMode.xml   |  6 +++---
 .../PrincipalPermissionMode.xml               |  2 +-
 .../DispatchRuntime.xml                       |  2 +-
 .../ServiceHostingEnvironment.xml             |  2 +-
 ...tFormsAuthenticationMembershipProvider.xml |  2 +-
 .../ClientRoleProvider.xml                    |  2 +-
 .../ClientSettingsProvider.xml                |  2 +-
 ...erLevelBuildProviderAppliesToAttribute.xml |  2 +-
 .../ScriptingRoleServiceSection.xml           |  4 ++--
 xml/System.Web.Hosting/HostingEnvironment.xml |  4 ++--
 .../IListenerChannelCallback.xml              |  2 +-
 xml/System.Web.Routing/PageRouteHandler.xml   |  2 +-
 xml/System.Web.UI.HtmlControls/HtmlForm.xml   |  6 +++---
 .../RangeExpression.xml                       |  2 +-
 .../SearchExpression.xml                      |  2 +-
 .../QueryExtender.xml                         |  4 ++--
 xml/System.Web/IisTraceListener.xml           |  2 +-
 xml/System.Web/RequestNotificationStatus.xml  |  6 +++---
 xml/ns-System.Drawing.Drawing2D.xml           |  2 +-
 42 files changed, 95 insertions(+), 95 deletions(-)

diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClass.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClass.xml
index 9610e5918c3..86d6cb686e5 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClass.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClass.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When a Visual Basic 6.0 `WebClass` project is upgraded to Visual Basic, it is converted to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ When a Visual Basic 6.0 `WebClass` project is upgraded to Visual Basic, it is converted to an ASP.NET Web-site project.  
   
  Declarations are added to your project: one for the `WebClass` and one for each `WebItem` and `Template` in the `WebClass` project. A `Page_Load` event procedure is added to the project. This creates first a `WebClass` object and then <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> objects for each `WebItem` and `Template` associated with the Visual Basic 6.0 `WebClass` project. Finally, in the `Page_Load` event procedure, you will see a call to the `WebClass` Compatibility runtime: <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass.ProcessEvents%2A>. This enables the runtime to render the <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> specified in the Request URL. This code is the only new code added to your upgraded project and serves only to emulate the underlying behavior of the Visual Basic 6.0 `WebClass` runtime.  
   
@@ -64,7 +64,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -104,7 +104,7 @@
 ## Remarks  
  Read-only.  
   
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -144,7 +144,7 @@
 ## Remarks  
  Used to shift processing from one <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> to another during a single request.  
   
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -179,7 +179,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -221,7 +221,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -267,7 +267,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -304,7 +304,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassContainingClassNotOptional.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassContainingClassNotOptional.xml
index cbcdd5ab7b9..bb068c7d5f8 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassContainingClassNotOptional.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassContainingClassNotOptional.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassCouldNotFindEvent.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassCouldNotFindEvent.xml
index 1e4ca1ce8bc..c4402c9c0bf 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassCouldNotFindEvent.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassCouldNotFindEvent.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -65,7 +65,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -98,7 +98,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemCannotBeCurrentWebItem.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemCannotBeCurrentWebItem.xml
index f0650146994..e099553076c 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemCannotBeCurrentWebItem.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemCannotBeCurrentWebItem.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemRespondNotFound.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemRespondNotFound.xml
index d88a17b5f20..feaa16a2a97 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemRespondNotFound.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassNextItemRespondNotFound.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassUserWebClassNameNotOptional.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassUserWebClassNameNotOptional.xml
index ff9b95e5728..7684d4c2351 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassUserWebClassNameNotOptional.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassUserWebClassNameNotOptional.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebClassFileNameNotOptional.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebClassFileNameNotOptional.xml
index 1e97573d7f0..7cf33ec2cba 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebClassFileNameNotOptional.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebClassFileNameNotOptional.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebItemNotValid.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebItemNotValid.xml
index b7c8075288d..7c989cdff53 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebItemNotValid.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebClassWebItemNotValid.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -60,7 +60,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItem.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItem.xml
index a7e82bb1e84..95d7783ee05 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItem.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItem.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When a Visual Basic 6.0 `WebClass` project is upgraded to Visual Basic, it is converted to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ When a Visual Basic 6.0 `WebClass` project is upgraded to Visual Basic, it is converted to an ASP.NET Web site project.  
   
  Declarations are added to your project: one for the `WebClass` and one for each of the `WebItems` and `Templates` in the `WebClass` project. A `Page_Load` event procedure is added to the project, creating first a <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> object and then `WebItem` objects for each of the `WebItems` and `Templates` associated with the Visual Basic 6.0 `WebClass` project. Finally, in the `Page_Load` event procedure, you will see a call to the `WebClass` Compatibility runtime: <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass.ProcessEvents%2A>. This enables the runtime to render the <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> specified in the Request URL. This code is the only new code added to your upgraded project and only serves to emulate the underlying behavior of the Visual Basic 6.0 `WebClass` runtime.  
   
@@ -64,7 +64,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -104,7 +104,7 @@
 ## Remarks  
  Read-only.  
   
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -147,7 +147,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -189,7 +189,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -225,7 +225,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebItem> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemAssociatedWebClassNotOptional.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemAssociatedWebClassNotOptional.xml
index 259088aa785..4a54c12ff90 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemAssociatedWebClassNotOptional.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemAssociatedWebClassNotOptional.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemClosingTagNotFound.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemClosingTagNotFound.xml
index 36aeca6d01d..849a21e471e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemClosingTagNotFound.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemClosingTagNotFound.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -60,7 +60,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadEmbeddedResource.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadEmbeddedResource.xml
index 25733bd5b40..71359f69407 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadEmbeddedResource.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadEmbeddedResource.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadTemplateFile.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadTemplateFile.xml
index 5ddbed2440f..ef6d05be397 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadTemplateFile.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemCouldNotLoadTemplateFile.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNameNotOptional.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNameNotOptional.xml
index 9dc144b4d1b..29e1cd6948e 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNameNotOptional.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNameNotOptional.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNoTemplateSpecified.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNoTemplateSpecified.xml
index e217771d212..0c08b39bb81 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNoTemplateSpecified.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemNoTemplateSpecified.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemTooManyNestedTags.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemTooManyNestedTags.xml
index 6922ef6ea93..b46dd509576 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemTooManyNestedTags.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemTooManyNestedTags.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -56,7 +56,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 `WebClass` project to an ASP.NET Web site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemUnexpectedErrorReadingTemplateFile.xml b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemUnexpectedErrorReadingTemplateFile.xml
index 93a14a898fb..d951f36a4f6 100644
--- a/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemUnexpectedErrorReadingTemplateFile.xml
+++ b/xml/Microsoft.VisualBasic.Compatibility.VB6/WebItemUnexpectedErrorReadingTemplateFile.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
@@ -60,7 +60,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Web-site project.  
+ The <xref:Microsoft.VisualBasic.Compatibility.VB6.WebClass> class is used by the upgrade tools to upgrade a Visual Basic 6.0 WebClass project to an ASP.NET Web-site project.  
   
  [!INCLUDE[Note_compatibility](~/includes/note-compatibility-md.md)]  
   
diff --git a/xml/System.ComponentModel/AsyncOperationManager.xml b/xml/System.ComponentModel/AsyncOperationManager.xml
index 9841e1a8230..c3751e76e88 100644
--- a/xml/System.ComponentModel/AsyncOperationManager.xml
+++ b/xml/System.ComponentModel/AsyncOperationManager.xml
@@ -37,7 +37,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If your class needs to provide asynchronous behavior according to the [Event-based Asynchronous Pattern Overview](/dotnet/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-overview), you will encounter a number of concurrency management issues. Among these is the requirement to ensure that event handlers are called on a thread or context that is appropriate for the application model (for example, Windows Forms applications, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications, console applications, and so on). The <xref:System.ComponentModel.AsyncOperationManager> provides a convenient way to create a class that runs properly under all application models supported by the .NET Framework.  
+ If your class needs to provide asynchronous behavior according to the [Event-based Asynchronous Pattern Overview](/dotnet/standard/asynchronous-programming-patterns/event-based-asynchronous-pattern-overview), you will encounter a number of concurrency management issues. Among these is the requirement to ensure that event handlers are called on a thread or context that is appropriate for the application model (for example, Windows Forms applications, ASP.NET applications, console applications, and so on). The <xref:System.ComponentModel.AsyncOperationManager> provides a convenient way to create a class that runs properly under all application models supported by the .NET Framework.  
   
  The <xref:System.ComponentModel.AsyncOperationManager> class has one method, <xref:System.ComponentModel.AsyncOperationManager.CreateOperation%2A>, which returns an <xref:System.ComponentModel.AsyncOperation?displayProperty=nameWithType> that can be used to track the duration of a particular asynchronous task. The <xref:System.ComponentModel.AsyncOperation?displayProperty=nameWithType> for a task can be used to alert clients when a task completes. It can also be used to post progress updates and incremental results without terminating the operation.  
   
diff --git a/xml/System.Drawing.Design/ToolboxService.xml b/xml/System.Drawing.Design/ToolboxService.xml
index 8fe2bca0b3d..9dead3a942c 100644
--- a/xml/System.Drawing.Design/ToolboxService.xml
+++ b/xml/System.Drawing.Design/ToolboxService.xml
@@ -144,7 +144,7 @@
         <block subset="none" type="overrides">
           <para>A linked toolbox item is one whose existence is tied to the storage of a particular designer host. So, in a typical project system, a designer host is associated with a particular file. A toolbox item linked to a designer host would automatically be deleted from the toolbox when the designer host's source file is deleted or removed from the project.  
   
- Linked toolbox items make possible scenarios such as disabling the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] toolbox items when the Windows Forms designer is open.</para>
+ Linked toolbox items make possible scenarios such as disabling the ASP.NET toolbox items when the Windows Forms designer is open.</para>
         </block>
       </Docs>
     </Member>
@@ -188,7 +188,7 @@
         <block subset="none" type="overrides">
           <para>A linked toolbox item is one whose existence is tied to the storage of a particular designer host. So, in a typical project system, a designer host is associated with a particular file. A toolbox item linked to a designer host would automatically be deleted from the toolbox when the designer host's source file is deleted or removed from the project.  
   
- Linked toolbox items make possible scenarios such as disabling the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] toolbox items when the Windows Forms designer is open.</para>
+ Linked toolbox items make possible scenarios such as disabling the ASP.NET toolbox items when the Windows Forms designer is open.</para>
         </block>
         <altmember cref="T:System.ComponentModel.Design.IDesignerHost" />
       </Docs>
diff --git a/xml/System.IdentityModel.Services/ClaimsAuthorizationModule.xml b/xml/System.IdentityModel.Services/ClaimsAuthorizationModule.xml
index 755212df31d..1e548875f9d 100644
--- a/xml/System.IdentityModel.Services/ClaimsAuthorizationModule.xml
+++ b/xml/System.IdentityModel.Services/ClaimsAuthorizationModule.xml
@@ -136,7 +136,7 @@
       </Parameters>
       <Docs>
         <param name="context">The application object that contains this module.</param>
-        <summary>Initializes the module and prepares it to handle events from its [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] application object.</summary>
+        <summary>Initializes the module and prepares it to handle events from its ASP.NET application object.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.IdentityModel.Services/SessionAuthenticationModule.xml b/xml/System.IdentityModel.Services/SessionAuthenticationModule.xml
index c1858965130..a4bd4a4c819 100644
--- a/xml/System.IdentityModel.Services/SessionAuthenticationModule.xml
+++ b/xml/System.IdentityModel.Services/SessionAuthenticationModule.xml
@@ -275,7 +275,7 @@
       </Parameters>
       <Docs>
         <param name="context">The HTTP application object that contains this module.</param>
-        <summary>Initializes the module and prepares it to handle events from the module's [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] application object.</summary>
+        <summary>Initializes the module and prepares it to handle events from the module's ASP.NET application object.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -368,7 +368,7 @@
       <Docs>
         <param name="sender">The source for the event. This will be an <see cref="T:System.Web.HttpApplication" /> object.</param>
         <param name="eventArgs">The data for the event.</param>
-        <summary>Handles the <see cref="E:System.Web.HttpApplication.AuthenticateRequest" /> event from the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline.</summary>
+        <summary>Handles the <see cref="E:System.Web.HttpApplication.AuthenticateRequest" /> event from the ASP.NET pipeline.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -416,7 +416,7 @@
       <Docs>
         <param name="sender">The source for the event. This will be an <see cref="T:System.Web.HttpApplication" /> object.</param>
         <param name="e">The data for the event.</param>
-        <summary>Handles the <see cref="E:System.Web.HttpApplication.PostAuthenticateRequest" /> event from the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline.</summary>
+        <summary>Handles the <see cref="E:System.Web.HttpApplication.PostAuthenticateRequest" /> event from the ASP.NET pipeline.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.IdentityModel.Services/WSFederationAuthenticationModule.xml b/xml/System.IdentityModel.Services/WSFederationAuthenticationModule.xml
index b94e8fdb7a4..d3e91663118 100644
--- a/xml/System.IdentityModel.Services/WSFederationAuthenticationModule.xml
+++ b/xml/System.IdentityModel.Services/WSFederationAuthenticationModule.xml
@@ -877,7 +877,7 @@
       </Parameters>
       <Docs>
         <param name="context">The HTTP application object that contains this module.</param>
-        <summary>Initializes the module and prepares it to handle events from the module's [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] application object.</summary>
+        <summary>Initializes the module and prepares it to handle events from the module's ASP.NET application object.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1026,12 +1026,12 @@
       <Docs>
         <param name="sender">The source for the event. This will be an <see cref="T:System.Web.HttpApplication" /> object.</param>
         <param name="args">The data for the event.</param>
-        <summary>Handles the <see cref="E:System.Web.HttpApplication.AuthenticateRequest" /> event from the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline.</summary>
+        <summary>Handles the <see cref="E:System.Web.HttpApplication.AuthenticateRequest" /> event from the ASP.NET pipeline.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest%2A> method implements the WS-Federation request processing pipeline. It is added to the <xref:System.Web.HttpApplication.AuthenticateRequest?displayProperty=nameWithType> event in the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline by the <xref:System.IdentityModel.Services.WSFederationAuthenticationModule.InitializeModule%2A> method.  
+ The <xref:System.IdentityModel.Services.WSFederationAuthenticationModule.OnAuthenticateRequest%2A> method implements the WS-Federation request processing pipeline. It is added to the <xref:System.Web.HttpApplication.AuthenticateRequest?displayProperty=nameWithType> event in the ASP.NET pipeline by the <xref:System.IdentityModel.Services.WSFederationAuthenticationModule.InitializeModule%2A> method.  
   
  The method performs the following:  
   
@@ -1115,7 +1115,7 @@
       <Docs>
         <param name="sender">The source for the event. This will be an <see cref="T:System.Web.HttpApplication" /> object.</param>
         <param name="args">The data for the event.</param>
-        <summary>Handles the <see cref="E:System.Web.HttpApplication.EndRequest" /> event from the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline.</summary>
+        <summary>Handles the <see cref="E:System.Web.HttpApplication.EndRequest" /> event from the ASP.NET pipeline.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1148,7 +1148,7 @@
       <Docs>
         <param name="sender">The source for the event. This will be an <see cref="T:System.Web.HttpApplication" /> object.</param>
         <param name="e">The data for the event.</param>
-        <summary>Handles the <see cref="E:System.Web.HttpApplication.PostAuthenticateRequest" /> event from the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] pipeline.</summary>
+        <summary>Handles the <see cref="E:System.Web.HttpApplication.PostAuthenticateRequest" /> event from the ASP.NET pipeline.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsAttribute.xml b/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsAttribute.xml
index dd5018186a1..59dd0f04acf 100644
--- a/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsAttribute.xml
+++ b/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsAttribute.xml
@@ -30,13 +30,13 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When applied to a service implementation class, this attribute indicates whether this service requires or supports [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode to be enabled for the hosting application domain (AppDomain).  
+ When applied to a service implementation class, this attribute indicates whether this service requires or supports ASP.NET compatibility mode to be enabled for the hosting application domain (AppDomain).  
   
  AppDomains hosting WCF services can run in two different hosting modes:  
   
--   Mixed Transports Mode (Default): In this mode, WCF services do not participate in the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] HTTP pipeline. This guarantees that a WCF service behaves consistently, independent of hosting environment and transport.  
+-   Mixed Transports Mode (Default): In this mode, WCF services do not participate in the ASP.NET HTTP pipeline. This guarantees that a WCF service behaves consistently, independent of hosting environment and transport.  
   
--   [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Compatibility Mode: In this mode, WCF services participate in the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] HTTP pipeline in a manner similar to ASMX services. [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] features such as File Authorization, UrlAuthorization, and HTTP Session State are applicable to WCF services running in this mode.  
+-   ASP.NET Compatibility Mode: In this mode, WCF services participate in the ASP.NET HTTP pipeline in a manner similar to ASMX services. ASP.NET features such as File Authorization, UrlAuthorization, and HTTP Session State are applicable to WCF services running in this mode.  
   
  The hosting mode is controlled by the application-level configuration flag `aspNetCompatibilityEnabled`.  
   
@@ -46,11 +46,11 @@
   
  `</system.serviceModel>`  
   
- This flag is `false` by default and thus WCF services run in the Mixed Transports Mode unless you explicitly opt into the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode.  
+ This flag is `false` by default and thus WCF services run in the Mixed Transports Mode unless you explicitly opt into the ASP.NET compatibility mode.  
   
  For more information about ASP.NET compatibility mode, see [&lt;serviceHostingEnvironment&gt;](/dotnet/framework/configure-apps/file-schema/wcf/servicehostingenvironment).  
   
- Use the <xref:System.ServiceModel.Activation.AspNetCompatibilityRequirementsAttribute.RequirementsMode%2A> property to do this. At runtime, applications can detect if [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode is enabled by checking the value of the static property <xref:System.ServiceModel.ServiceHostingEnvironment.AspNetCompatibilityEnabled%2A>.  
+ Use the <xref:System.ServiceModel.Activation.AspNetCompatibilityRequirementsAttribute.RequirementsMode%2A> property to do this. At runtime, applications can detect if ASP.NET compatibility mode is enabled by checking the value of the static property <xref:System.ServiceModel.ServiceHostingEnvironment.AspNetCompatibilityEnabled%2A>.  
   
    
   
@@ -114,15 +114,15 @@
         <ReturnType>System.ServiceModel.Activation.AspNetCompatibilityRequirementsMode</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the level of [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility required by the service.</summary>
-        <value>The <see cref="T:System.ServiceModel.Activation.AspNetCompatibilityRequirementsMode" /> that indicates the services required degree of [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility. The default value is <see cref="F:System.ServiceModel.Activation.AspNetCompatibilityRequirementsMode.Allowed" />.</value>
+        <summary>Gets or sets the level of ASP.NET compatibility required by the service.</summary>
+        <value>The <see cref="T:System.ServiceModel.Activation.AspNetCompatibilityRequirementsMode" /> that indicates the services required degree of ASP.NET compatibility. The default value is <see cref="F:System.ServiceModel.Activation.AspNetCompatibilityRequirementsMode.Allowed" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
  Use the <xref:System.ServiceModel.Activation.AspNetCompatibilityRequirementsAttribute.RequirementsMode%2A> property to set the hosting mode in code. This can also be done by setting an application-level configuration flag `aspNetCompatibilityEnabled`. For more information, see [&lt;serviceHostingEnvironment&gt;](/dotnet/framework/configure-apps/file-schema/wcf/servicehostingenvironment).  
   
- At runtime, applications can detect whether [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode is enabled by checking the value of the static property <xref:System.ServiceModel.ServiceHostingEnvironment.AspNetCompatibilityEnabled%2A>.  
+ At runtime, applications can detect whether ASP.NET compatibility mode is enabled by checking the value of the static property <xref:System.ServiceModel.ServiceHostingEnvironment.AspNetCompatibilityEnabled%2A>.  
   
    
   
@@ -202,7 +202,7 @@
       <Docs>
         <param name="description">The <see cref="T:System.ServiceModel.Description.ServiceDescription" /> of the service.</param>
         <param name="serviceHostBase">The <see cref="T:System.ServiceModel.ServiceHostBase" /> for hosting the service.</param>
-        <summary>Checks that the type of hosting is consistent with the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility requirements.</summary>
+        <summary>Checks that the type of hosting is consistent with the ASP.NET compatibility requirements.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -213,7 +213,7 @@
         </remarks>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="description" /> is <see langword="null" />.</exception>
-        <exception cref="T:System.InvalidOperationException">The service hosting is not compatible with the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility requirements.</exception>
+        <exception cref="T:System.InvalidOperationException">The service hosting is not compatible with the ASP.NET compatibility requirements.</exception>
       </Docs>
     </Member>
     <Member MemberName="System.ServiceModel.Description.IServiceBehavior.Validate">
diff --git a/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsMode.xml b/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsMode.xml
index 4b0231d7e62..2d9aa62467d 100644
--- a/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsMode.xml
+++ b/xml/System.ServiceModel.Activation/AspNetCompatibilityRequirementsMode.xml
@@ -56,7 +56,7 @@ ASP.NET compatibility mode allows WCF services to use ASP features such as ident
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>WCF services can run in an application domain with [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode set to <see langword="true" /> or <see langword="false" />.</summary>
+        <summary>WCF services can run in an application domain with ASP.NET compatibility mode set to <see langword="true" /> or <see langword="false" />.</summary>
       </Docs>
     </Member>
     <Member MemberName="NotAllowed">
@@ -78,7 +78,7 @@ ASP.NET compatibility mode allows WCF services to use ASP features such as ident
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>WCF services must run in an application domain with [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode set to <see langword="false" />.</summary>
+        <summary>WCF services must run in an application domain with ASP.NET compatibility mode set to <see langword="false" />.</summary>
       </Docs>
     </Member>
     <Member MemberName="Required">
@@ -100,7 +100,7 @@ ASP.NET compatibility mode allows WCF services to use ASP features such as ident
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>WCF services must run in an application domain with [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] compatibility mode set to <see langword="true" />.</summary>
+        <summary>WCF services must run in an application domain with ASP.NET compatibility mode set to <see langword="true" />.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml b/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
index aae5fad6069..ca408113cfa 100644
--- a/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
+++ b/xml/System.ServiceModel.Description/PrincipalPermissionMode.xml
@@ -173,7 +173,7 @@ evaluationContext.Properties["Principal"]=new CustomPrincipal(identity);
       <MemberValue>2</MemberValue>
       <Docs>
         <summary>
-          <see cref="P:System.Threading.Thread.CurrentPrincipal" /> is set based on the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] role provider (<see cref="T:System.Web.Security.RoleProvider" />).</summary>
+          <see cref="P:System.Threading.Thread.CurrentPrincipal" /> is set based on the ASP.NET role provider (<see cref="T:System.Web.Security.RoleProvider" />).</summary>
       </Docs>
     </Member>
     <Member MemberName="UseWindowsGroups">
diff --git a/xml/System.ServiceModel.Dispatcher/DispatchRuntime.xml b/xml/System.ServiceModel.Dispatcher/DispatchRuntime.xml
index 6b6706ed701..0d149cf2e82 100644
--- a/xml/System.ServiceModel.Dispatcher/DispatchRuntime.xml
+++ b/xml/System.ServiceModel.Dispatcher/DispatchRuntime.xml
@@ -787,7 +787,7 @@
   
  When the value is <xref:System.ServiceModel.Description.PrincipalPermissionMode.UseWindowsGroups> the <xref:System.Threading.Thread.CurrentPrincipal%2A> property is populated with a <xref:System.Security.Principal.WindowsPrincipal> based on the user credentials of the incoming message.  
   
- When the value is <xref:System.ServiceModel.Description.PrincipalPermissionMode.UseAspNetRoles> the <xref:System.Threading.Thread.CurrentPrincipal%2A> property is populated with an <xref:System.Security.Principal.IPrincipal> object based on [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] role information.  
+ When the value is <xref:System.ServiceModel.Description.PrincipalPermissionMode.UseAspNetRoles> the <xref:System.Threading.Thread.CurrentPrincipal%2A> property is populated with an <xref:System.Security.Principal.IPrincipal> object based on ASP.NET role information.  
   
  When the value is <xref:System.ServiceModel.Description.PrincipalPermissionMode.Custom> the <xref:System.Threading.Thread.CurrentPrincipal%2A> property is populated by a custom <xref:System.IdentityModel.Policy.IAuthorizationPolicy> implementation.  
   
diff --git a/xml/System.ServiceModel/ServiceHostingEnvironment.xml b/xml/System.ServiceModel/ServiceHostingEnvironment.xml
index 9aa9ee31595..32421703df1 100644
--- a/xml/System.ServiceModel/ServiceHostingEnvironment.xml
+++ b/xml/System.ServiceModel/ServiceHostingEnvironment.xml
@@ -58,7 +58,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets a value that indicates whether this service is running in the context of the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] HTTP application pipeline.</summary>
+        <summary>Gets a value that indicates whether this service is running in the context of the ASP.NET HTTP application pipeline.</summary>
         <value>
           <see langword="true" /> if ASP.NET compatibility is enabled for the current AppDomain; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Web.ClientServices.Providers/ClientFormsAuthenticationMembershipProvider.xml b/xml/System.Web.ClientServices.Providers/ClientFormsAuthenticationMembershipProvider.xml
index a218e9615c0..bf9baeedd66 100644
--- a/xml/System.Web.ClientServices.Providers/ClientFormsAuthenticationMembershipProvider.xml
+++ b/xml/System.Web.ClientServices.Providers/ClientFormsAuthenticationMembershipProvider.xml
@@ -607,7 +607,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> using information in your application configuration file. This method recognizes the following authentication service configuration attributes:  
+ The ASP.NET extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientFormsAuthenticationMembershipProvider> using information in your application configuration file. This method recognizes the following authentication service configuration attributes:  
   
 -   `name`  
   
diff --git a/xml/System.Web.ClientServices.Providers/ClientRoleProvider.xml b/xml/System.Web.ClientServices.Providers/ClientRoleProvider.xml
index f117f474e18..6411b4e1291 100644
--- a/xml/System.Web.ClientServices.Providers/ClientRoleProvider.xml
+++ b/xml/System.Web.ClientServices.Providers/ClientRoleProvider.xml
@@ -352,7 +352,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientRoleProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientRoleProvider> using information in your application configuration file. This method recognizes the following role service configuration attributes:  
+ The ASP.NET extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientRoleProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientRoleProvider> using information in your application configuration file. This method recognizes the following role service configuration attributes:  
   
 -   `name`  
   
diff --git a/xml/System.Web.ClientServices.Providers/ClientSettingsProvider.xml b/xml/System.Web.ClientServices.Providers/ClientSettingsProvider.xml
index e83f5b9fe59..2c2e31be120 100644
--- a/xml/System.Web.ClientServices.Providers/ClientSettingsProvider.xml
+++ b/xml/System.Web.ClientServices.Providers/ClientSettingsProvider.xml
@@ -271,7 +271,7 @@
 ## Remarks  
  This method is used internally by the application settings system and it not meant to be used by your application code.  
   
- The [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientSettingsProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientSettingsProvider> by using information in your application configuration file. This method recognizes the following Web settings service configuration attributes:  
+ The ASP.NET extensibility model calls the <xref:System.Web.ClientServices.Providers.ClientSettingsProvider.Initialize%2A> method to initialize the <xref:System.Web.ClientServices.Providers.ClientSettingsProvider> by using information in your application configuration file. This method recognizes the following Web settings service configuration attributes:  
   
 -   name  
   
diff --git a/xml/System.Web.Compilation/FolderLevelBuildProviderAppliesToAttribute.xml b/xml/System.Web.Compilation/FolderLevelBuildProviderAppliesToAttribute.xml
index 5c47902fb4e..c9d232bcd1b 100644
--- a/xml/System.Web.Compilation/FolderLevelBuildProviderAppliesToAttribute.xml
+++ b/xml/System.Web.Compilation/FolderLevelBuildProviderAppliesToAttribute.xml
@@ -27,7 +27,7 @@
 ## Remarks  
  The <xref:System.Web.Configuration.FolderLevelBuildProvider> class parses and generates code during compilation for a resource that has a specific file. The <xref:System.Web.Compilation.FolderLevelBuildProviderAppliesToAttribute> attribute defines the location scope for which the <xref:System.Web.Configuration.FolderLevelBuildProvider> object will be called.  
   
- By setting the <xref:System.Web.Compilation.FolderLevelBuildProviderAppliesToAttribute> attribute, you can limit a <xref:System.Web.Configuration.FolderLevelBuildProvider> object to certain [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] directories, such as App_Code.  
+ By setting the <xref:System.Web.Compilation.FolderLevelBuildProviderAppliesToAttribute> attribute, you can limit a <xref:System.Web.Configuration.FolderLevelBuildProvider> object to certain ASP.NET directories, such as App_Code.  
   
  If you do not apply a <xref:System.Web.Compilation.FolderLevelBuildProviderAppliesToAttribute> attribute to a <xref:System.Web.Configuration.FolderLevelBuildProvider> class, by default, the attribute targets all directories.  
   
diff --git a/xml/System.Web.Configuration/ScriptingRoleServiceSection.xml b/xml/System.Web.Configuration/ScriptingRoleServiceSection.xml
index 2581030d62f..404c905ab68 100644
--- a/xml/System.Web.Configuration/ScriptingRoleServiceSection.xml
+++ b/xml/System.Web.Configuration/ScriptingRoleServiceSection.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.Configuration.ScriptingRoleServiceSection> class enables you to programmatically access and modify the `roleService` element of the configuration section for using AJAX functionality in [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)].  
+ The <xref:System.Web.Configuration.ScriptingRoleServiceSection> class enables you to programmatically access and modify the `roleService` element of the configuration section for using AJAX functionality in ASP.NET.  
   
  The role service is typically used to retrieve role information for the user who is logged on by using an asynchronous Web service call.  
   
@@ -97,7 +97,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether the role service is enabled for an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] application that uses AJAX features.</summary>
+        <summary>Gets or sets a value that indicates whether the role service is enabled for an ASP.NET application that uses AJAX features.</summary>
         <value>
           <see langword="true" /> if the role service is enabled; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>To be added.</remarks>
diff --git a/xml/System.Web.Hosting/HostingEnvironment.xml b/xml/System.Web.Hosting/HostingEnvironment.xml
index ee76f608d40..b7dce6327b5 100644
--- a/xml/System.Web.Hosting/HostingEnvironment.xml
+++ b/xml/System.Web.Hosting/HostingEnvironment.xml
@@ -77,7 +77,7 @@
         <ReturnType>System.Web.Hosting.IApplicationHost</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>This property supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This property supports the ASP.NET infrastructure and is not intended to be used directly from your code.</summary>
         <value>An object that contains information about the application host.</value>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/migration-guide/versions-and-dependencies">.NET Framework versions and dependencies</related>
@@ -617,7 +617,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>This method supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This method supports the ASP.NET infrastructure and is not intended to be used directly from your code.</summary>
         <remarks>To be added.</remarks>
         <related type="Article" href="/dotnet/framework/migration-guide/versions-and-dependencies">.NET Framework versions and dependencies</related>
       </Docs>
diff --git a/xml/System.Web.Hosting/IListenerChannelCallback.xml b/xml/System.Web.Hosting/IListenerChannelCallback.xml
index b6c69570b7f..f1bd23e5eb8 100644
--- a/xml/System.Web.Hosting/IListenerChannelCallback.xml
+++ b/xml/System.Web.Hosting/IListenerChannelCallback.xml
@@ -154,7 +154,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.  
+ This method supports the ASP.NET infrastructure and is not intended to be used directly from your code.  
   
  <xref:System.Web.Hosting.IListenerChannelCallback.ReportMessageReceived%2A> is introduced in the .NET Framework 3.5. For more information, see [Versions and Dependencies](/dotnet/framework/migration-guide/versions-and-dependencies).  
   
diff --git a/xml/System.Web.Routing/PageRouteHandler.xml b/xml/System.Web.Routing/PageRouteHandler.xml
index 8da0fbdfd6d..881f6a5c25d 100644
--- a/xml/System.Web.Routing/PageRouteHandler.xml
+++ b/xml/System.Web.Routing/PageRouteHandler.xml
@@ -178,7 +178,7 @@
 </configuration>
 ```
 
- For a request URL that contains `Category/food/show` after the domain name, if the route URL pattern is `Category/{action}/{categoryName}` and the physical page is Categoriespage.aspx, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applies the permissions defined in the previous example in one of the following ways:
+ For a request URL that contains `Category/food/show` after the domain name, if the route URL pattern is `Category/{action}/{categoryName}` and the physical page is Categoriespage.aspx, ASP.NET applies the permissions defined in the previous example in one of the following ways:
 
 -   If the <xref:System.Web.Routing.PageRouteHandler.CheckPhysicalUrlAccess%2A> property is `false`, all users are granted access, because all users are granted access to the URL pattern that starts with `category`.
 
diff --git a/xml/System.Web.UI.HtmlControls/HtmlForm.xml b/xml/System.Web.UI.HtmlControls/HtmlForm.xml
index 45d492c719b..c923ca1cebc 100644
--- a/xml/System.Web.UI.HtmlControls/HtmlForm.xml
+++ b/xml/System.Web.UI.HtmlControls/HtmlForm.xml
@@ -148,13 +148,13 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the control identifier that is generated by [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] for the <see cref="T:System.Web.UI.HtmlControls.HtmlForm" /> control.</summary>
-        <value>The control identifier generated by [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] for the <see cref="T:System.Web.UI.HtmlControls.HtmlForm" /> control.</value>
+        <summary>Gets the control identifier that is generated by ASP.NET for the <see cref="T:System.Web.UI.HtmlControls.HtmlForm" /> control.</summary>
+        <value>The control identifier generated by ASP.NET for the <see cref="T:System.Web.UI.HtmlControls.HtmlForm" /> control.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- To prevent naming conflicts when multiple instances of a control are rendered, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] automatically generates a unique <xref:System.Web.UI.HtmlControls.HtmlForm.ClientID%2A> value for each control on a page. For more information, see the <xref:System.Web.UI.Control.ClientID%2A?displayProperty=nameWithType> property.  
+ To prevent naming conflicts when multiple instances of a control are rendered, ASP.NET automatically generates a unique <xref:System.Web.UI.HtmlControls.HtmlForm.ClientID%2A> value for each control on a page. For more information, see the <xref:System.Web.UI.Control.ClientID%2A?displayProperty=nameWithType> property.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.UI.WebControls.Expressions/RangeExpression.xml b/xml/System.Web.UI.WebControls.Expressions/RangeExpression.xml
index f1799f7dddd..ae35c435147 100644
--- a/xml/System.Web.UI.WebControls.Expressions/RangeExpression.xml
+++ b/xml/System.Web.UI.WebControls.Expressions/RangeExpression.xml
@@ -21,7 +21,7 @@
 ## Remarks  
  The <xref:System.Web.UI.WebControls.QueryExtender> control provides the ability to filter data in a Web page by using classes in the <xref:System.Web.UI.WebControls.Expressions> namespace. These classes include the <xref:System.Web.UI.WebControls.Expressions.RangeExpression> class.  
   
- The <xref:System.Web.UI.WebControls.Expressions.RangeExpression> class searches a data column using a pair of values that define the range. You use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.DataField%2A> property to specify the column to search. You use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.MinType%2A> property to specify whether to include or exclude the minimum in the search results, and you use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.MaxType%2A> property to specify whether to include or exclude the maximum value. The maximum and minimum values can be specified in [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] controls and the values can then be passed to the <xref:System.Web.UI.WebControls.QueryExtender> control as parameters in <xref:System.Web.UI.WebControls.ControlParameter> controls. The results are typically displayed in a data-bound control.  
+ The <xref:System.Web.UI.WebControls.Expressions.RangeExpression> class searches a data column using a pair of values that define the range. You use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.DataField%2A> property to specify the column to search. You use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.MinType%2A> property to specify whether to include or exclude the minimum in the search results, and you use the <xref:System.Web.UI.WebControls.Expressions.RangeExpression.MaxType%2A> property to specify whether to include or exclude the maximum value. The maximum and minimum values can be specified in ASP.NET controls and the values can then be passed to the <xref:System.Web.UI.WebControls.QueryExtender> control as parameters in <xref:System.Web.UI.WebControls.ControlParameter> controls. The results are typically displayed in a data-bound control.  
   
    
   
diff --git a/xml/System.Web.UI.WebControls.Expressions/SearchExpression.xml b/xml/System.Web.UI.WebControls.Expressions/SearchExpression.xml
index aed1eefcf71..08c06dd7e2b 100644
--- a/xml/System.Web.UI.WebControls.Expressions/SearchExpression.xml
+++ b/xml/System.Web.UI.WebControls.Expressions/SearchExpression.xml
@@ -21,7 +21,7 @@
 ## Remarks  
  The <xref:System.Web.UI.WebControls.QueryExtender> control provides the ability to filter data in a Web page by using the <xref:System.Web.UI.WebControls.Expressions.SearchExpression> class. The <xref:System.Web.UI.WebControls.Expressions.SearchExpression> class compares a specified string in a field or fields to a value that you supply. The expression performs a "starts with", "contains", or "ends with" search. You must specify values for the <xref:System.Web.UI.WebControls.Expressions.SearchExpression.SearchType%2A> and the <xref:System.Web.UI.WebControls.Expressions.SearchExpression.DataFields%2A> properties in order to indicate the type of search you want to perform and the data fields that you want to search. If the LINQ provider that you use in the <xref:System.Web.UI.WebControls.QueryExtender> control supports case sensitivity, you can use the <xref:System.Web.UI.WebControls.Expressions.SearchExpression.ComparisonType%2A> property to enable or ignore case sensitivity.  
   
- The value to search can be provided by an [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] control. To specify this, you set the <xref:System.Web.UI.WebControls.ControlParameter.ControlID%2A> property of the <xref:System.Web.UI.WebControls.ControlParameter> class in the <xref:System.Web.UI.WebControls.Expressions.SearchExpression> object to the ID of a [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] control. For example, if the value to search is entered in a text box, the <xref:System.Web.UI.WebControls.ControlParameter.ControlID%2A> property must be set to the ID of the text box control. You can use the <xref:System.Web.UI.WebControls.Expressions.SearchExpression> class in combination with the other expressions that the <xref:System.Web.UI.WebControls.QueryExtender> supports, such as the <xref:System.Web.UI.WebControls.Expressions.RangeExpression> filter. For example, you can search for product names that contain the string "tea" and a list price between 100 and 200.  
+ The value to search can be provided by an ASP.NET control. To specify this, you set the <xref:System.Web.UI.WebControls.ControlParameter.ControlID%2A> property of the <xref:System.Web.UI.WebControls.ControlParameter> class in the <xref:System.Web.UI.WebControls.Expressions.SearchExpression> object to the ID of a ASP.NET control. For example, if the value to search is entered in a text box, the <xref:System.Web.UI.WebControls.ControlParameter.ControlID%2A> property must be set to the ID of the text box control. You can use the <xref:System.Web.UI.WebControls.Expressions.SearchExpression> class in combination with the other expressions that the <xref:System.Web.UI.WebControls.QueryExtender> supports, such as the <xref:System.Web.UI.WebControls.Expressions.RangeExpression> filter. For example, you can search for product names that contain the string "tea" and a list price between 100 and 200.  
   
    
   
diff --git a/xml/System.Web.UI.WebControls/QueryExtender.xml b/xml/System.Web.UI.WebControls/QueryExtender.xml
index adba926b920..6a15a18c45d 100644
--- a/xml/System.Web.UI.WebControls/QueryExtender.xml
+++ b/xml/System.Web.UI.WebControls/QueryExtender.xml
@@ -71,7 +71,7 @@
   
  Filtering typically requires that you create a `Where` clause to apply to the command that queries the data source. However, the `Where` property of the data source control might not expose the full functionality that is available. For example, the QueryExtender control enables you to query a table by searching for strings at the beginning, end or anywhere in .data field.  
   
- To expose the full functionality that is available in LINQ and to make filtering data easier, [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] provides the <xref:System.Web.UI.WebControls.QueryExtender> control. The <xref:System.Web.UI.WebControls.QueryExtender> control has the following benefits:  
+ To expose the full functionality that is available in LINQ and to make filtering data easier, ASP.NET provides the <xref:System.Web.UI.WebControls.QueryExtender> control. The <xref:System.Web.UI.WebControls.QueryExtender> control has the following benefits:  
   
 -   It provides a richer filtering experience than writing a `Where` clause. For example, you can search a Products table for Boolean values by using the <xref:System.Web.UI.WebControls.Expressions.PropertyExpression> filter without writing a query.  
   
@@ -83,7 +83,7 @@
 ## Filter Options  
  The <xref:System.Web.UI.WebControls.QueryExtender> control supports a variety of options that you can use to filter data. The control lets you search strings, search numeric values in a specified range, and compare a property value in a table to a specified value. The control also lets you sort the data and provide custom queries.  
   
- These options are provided as LINQ expressions in the <xref:System.Web.UI.WebControls.QueryExtender> control. The <xref:System.Web.UI.WebControls.QueryExtender> control also supports expressions that are specific to [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] Dynamic Data applications.  
+ These options are provided as LINQ expressions in the <xref:System.Web.UI.WebControls.QueryExtender> control. The <xref:System.Web.UI.WebControls.QueryExtender> control also supports expressions that are specific to ASP.NET Dynamic Data applications.  
   
  The following table lists the options that you can use to filter data in the <xref:System.Web.UI.WebControls.QueryExtender> control.  
   
diff --git a/xml/System.Web/IisTraceListener.xml b/xml/System.Web/IisTraceListener.xml
index 91ca0b4a7e0..6a0c65f0ab1 100644
--- a/xml/System.Web/IisTraceListener.xml
+++ b/xml/System.Web/IisTraceListener.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.IisTraceListener> class connects the tracing mechanism of [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] to IIS 7.0. This listener class enables developers who create [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] applications and who implement the <xref:System.Web.IHttpModule> and <xref:System.Web.IHttpHandler> interfaces to raise page-level, module-level, or handler-level events to the IIS 7.0 infrastructure when tracing is enabled.  
+ The <xref:System.Web.IisTraceListener> class connects the tracing mechanism of ASP.NET to IIS 7.0. This listener class enables developers who create ASP.NET applications and who implement the <xref:System.Web.IHttpModule> and <xref:System.Web.IHttpHandler> interfaces to raise page-level, module-level, or handler-level events to the IIS 7.0 infrastructure when tracing is enabled.  
   
 > [!NOTE]
 >  This listener class does not route IIS 7.0 events to ASP.NET classes. This includes the <xref:System.Web.UI.Page> class and classes that implement the <xref:System.Web.IHttpModule> or <xref:System.Web.IHttpHandler> interface.  
diff --git a/xml/System.Web/RequestNotificationStatus.xml b/xml/System.Web/RequestNotificationStatus.xml
index f7326b14c03..83388470ed5 100644
--- a/xml/System.Web/RequestNotificationStatus.xml
+++ b/xml/System.Web/RequestNotificationStatus.xml
@@ -44,7 +44,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the ASP.NET infrastructure and is not intended to be used directly from your code.</summary>
         <forInternalUseOnly />
       </Docs>
     </Member>
@@ -66,7 +66,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the ASP.NET infrastructure and is not intended to be used directly from your code.</summary>
         <forInternalUseOnly />
       </Docs>
     </Member>
@@ -88,7 +88,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>This member supports the [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] infrastructure and is not intended to be used directly from your code.</summary>
+        <summary>This member supports the ASP.NET infrastructure and is not intended to be used directly from your code.</summary>
         <forInternalUseOnly />
       </Docs>
     </Member>
diff --git a/xml/ns-System.Drawing.Drawing2D.xml b/xml/ns-System.Drawing.Drawing2D.xml
index a7866cc98f7..ba141f8a2d7 100644
--- a/xml/ns-System.Drawing.Drawing2D.xml
+++ b/xml/ns-System.Drawing.Drawing2D.xml
@@ -19,7 +19,7 @@
 |-   Enumerations related to filling shapes and paths|The <xref:System.Drawing.Drawing2D.HatchStyle> enumeration specifies fill styles for a <xref:System.Drawing.Drawing2D.HatchBrush>. The <xref:System.Drawing.Drawing2D.Blend> class specifies a blend pattern for a <xref:System.Drawing.Drawing2D.LinearGradientBrush>. The <xref:System.Drawing.Drawing2D.FillMode> enumeration specifies the fill style for a <xref:System.Drawing.Drawing2D.GraphicsPath>.|
 
 > [!CAUTION]
->  Classes in the <xref:System.Drawing.Drawing2D> namespace are not supported for use in a Windows or [!INCLUDE[vstecasp](~/includes/vstecasp-md.md)] service. Attempting to use these classes in one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.
+>  Classes in the <xref:System.Drawing.Drawing2D> namespace are not supported for use in a Windows or ASP.NET service. Attempting to use these classes in one of these application types may produce unexpected problems, such as diminished service performance and run-time exceptions.
 
  ]]></format>
     </remarks>

From 2fb6c196ce69372d79b6ab1d164c99a4227ffb51 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:36:30 -0800
Subject: [PATCH 204/236] vstecasplong

---
 xml/System.Web.Configuration/ProfileGroupSettings.xml       | 2 +-
 xml/System.Web.Configuration/ProfilePropertySettings.xml    | 2 +-
 .../ProfilePropertySettingsCollection.xml                   | 2 +-
 xml/System.Web.Configuration/ProfileSection.xml             | 4 ++--
 .../RootProfilePropertySettingsCollection.xml               | 2 +-
 xml/System.Web.UI/Page.xml                                  | 6 +++---
 6 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/xml/System.Web.Configuration/ProfileGroupSettings.xml b/xml/System.Web.Configuration/ProfileGroupSettings.xml
index d2cdcd828b3..efa2573df01 100644
--- a/xml/System.Web.Configuration/ProfileGroupSettings.xml
+++ b/xml/System.Web.Configuration/ProfileGroupSettings.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  The <xref:System.Web.Configuration.ProfileGroupSettings> class provides a way to programmatically create, access, and modify groups of properties added to the `group` subsection of the `profile` section of a configuration file.  
   
- The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
+ The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
   
    
   
diff --git a/xml/System.Web.Configuration/ProfilePropertySettings.xml b/xml/System.Web.Configuration/ProfilePropertySettings.xml
index 9fb3461a778..a6453bcd7c8 100644
--- a/xml/System.Web.Configuration/ProfilePropertySettings.xml
+++ b/xml/System.Web.Configuration/ProfilePropertySettings.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  The <xref:System.Web.Configuration.ProfilePropertySettings> class provides a way to programmatically create, access, and modify the definition of an individual property added to the `properties` subsection of the `profile` section of a configuration file.  
   
- The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about profile properties, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)). For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
+ The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about profile properties, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)). For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
   
    
   
diff --git a/xml/System.Web.Configuration/ProfilePropertySettingsCollection.xml b/xml/System.Web.Configuration/ProfilePropertySettingsCollection.xml
index 59cde5c420a..1481ce31043 100644
--- a/xml/System.Web.Configuration/ProfilePropertySettingsCollection.xml
+++ b/xml/System.Web.Configuration/ProfilePropertySettingsCollection.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A> property. For more information about profile properties, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)). For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
+ The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `properties` subsection of the `profile` section of the configuration file. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A> property. For more information about profile properties, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)). For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
   
    
   
diff --git a/xml/System.Web.Configuration/ProfileSection.xml b/xml/System.Web.Configuration/ProfileSection.xml
index 0cb4119dfaf..682970ff4a9 100644
--- a/xml/System.Web.Configuration/ProfileSection.xml
+++ b/xml/System.Web.Configuration/ProfileSection.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.Configuration.ProfileSection> class provides a way to programmatically access and modify the content of the configuration file `profile` section. The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `profile` section of the configuration file. The class allows you to access and modify the values for individual profiles. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
+ The <xref:System.Web.Configuration.ProfileSection> class provides a way to programmatically access and modify the content of the configuration file `profile` section. The `profile` section of the configuration file specifies a schema for user profiles. At run time, the ASP.NET compilation system uses the information specified in the `profile` section to generate a class called `ProfileCommon`, which is derived from <xref:System.Web.Profile.ProfileBase>. The `ProfileCommon` class definition is based on the properties defined in the `profile` section of the configuration file. The class allows you to access and modify the values for individual profiles. An instance of this class is created for each user profile, and you can access the individual profile values in your code through the <xref:System.Web.HttpContext.Profile%2A?displayProperty=nameWithType> property. For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
   
    
   
@@ -291,7 +291,7 @@ local Microsoft SQL Server database" />
 > [!NOTE]
 >  If you provide a type reference in the <xref:System.Web.Configuration.ProfileSection.Inherits%2A> property, you can define properties in your custom types that are not defined with a `property` element.  
   
- For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
+ For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties Overview](https://docs.microsoft.com/previous-versions/aspnet/2y3fs9xs(v=vs.100)).  
   
    
   
diff --git a/xml/System.Web.Configuration/RootProfilePropertySettingsCollection.xml b/xml/System.Web.Configuration/RootProfilePropertySettingsCollection.xml
index 0dd054c9d92..6aeef3882fc 100644
--- a/xml/System.Web.Configuration/RootProfilePropertySettingsCollection.xml
+++ b/xml/System.Web.Configuration/RootProfilePropertySettingsCollection.xml
@@ -26,7 +26,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Web.Configuration.RootProfilePropertySettingsCollection> class is both a root-level <xref:System.Web.Configuration.ProfilePropertySettingsCollection> collection and a container for a <xref:System.Web.Configuration.ProfileGroupSettingsCollection> collection. These collections allow you to create named groups of more <xref:System.Web.Configuration.ProfilePropertySettingsCollection> collections, each containing individual named <xref:System.Web.Configuration.ProfilePropertySettings> objects. For more information about the profile features added to [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], see [ASP.NET Profile Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/at64shx3(v=vs.85)).  
+ The <xref:System.Web.Configuration.RootProfilePropertySettingsCollection> class is both a root-level <xref:System.Web.Configuration.ProfilePropertySettingsCollection> collection and a container for a <xref:System.Web.Configuration.ProfileGroupSettingsCollection> collection. These collections allow you to create named groups of more <xref:System.Web.Configuration.ProfilePropertySettingsCollection> collections, each containing individual named <xref:System.Web.Configuration.ProfilePropertySettings> objects. For more information about the profile features added to ASP.NET 2.0, see [ASP.NET Profile Properties](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.0/at64shx3(v=vs.85)).  
   
  The <xref:System.Web.Configuration.ProfileSection.PropertySettings%2A> property is a <xref:System.Web.Configuration.RootProfilePropertySettingsCollection> object that contains all the properties defined within the `properties` subsection of the `profile` section of the configuration file.  
   
diff --git a/xml/System.Web.UI/Page.xml b/xml/System.Web.UI/Page.xml
index 4308a474034..37274542ca2 100644
--- a/xml/System.Web.UI/Page.xml
+++ b/xml/System.Web.UI/Page.xml
@@ -887,7 +887,7 @@
 ## Remarks
  Use the <xref:System.Web.UI.Page.ClientScript%2A> property to get a <xref:System.Web.UI.ClientScriptManager> object that can be used to manage, register, and add script to a Web page. For more information, see the <xref:System.Web.UI.ClientScriptManager> class.
 
- The <xref:System.Web.UI.ClientScriptManager> class is new in [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)] and replaces <xref:System.Web.UI.Page> class methods for managing scripts that are now deprecated.
+ The <xref:System.Web.UI.ClientScriptManager> class is new in ASP.NET 2.0 and replaces <xref:System.Web.UI.Page> class methods for managing scripts that are now deprecated.
 
 
 
@@ -6309,7 +6309,7 @@ int year = Convert.ToInt32(Page.RouteData.Values["year"])
  When this method is invoked, it iterates through the validation controls contained in the <xref:System.Web.UI.ValidatorCollection> object associated with the <xref:System.Web.UI.Page.Validators%2A?displayProperty=nameWithType> property and invokes the validation logic for each validation control in the current validation group. The validation group is determined by the control that posted the page to the server. If no validation group is specified, then no validation group is used.
 
 > [!NOTE]
->  The behavior of page validation has changed. In [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], controls no longer call the <xref:System.Web.UI.Page.Validate?displayProperty=nameWithType> method; they use the <xref:System.Web.UI.Page.Validate%28System.String%29?displayProperty=nameWithType> method instead. If you use the <xref:System.Web.UI.Page.Validate?displayProperty=nameWithType> method on an [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)] page, validation groups are ignored and all controls are validated.
+>  The behavior of page validation has changed. In ASP.NET 2.0, controls no longer call the <xref:System.Web.UI.Page.Validate?displayProperty=nameWithType> method; they use the <xref:System.Web.UI.Page.Validate%28System.String%29?displayProperty=nameWithType> method instead. If you use the <xref:System.Web.UI.Page.Validate?displayProperty=nameWithType> method on an ASP.NET 2.0 page, validation groups are ignored and all controls are validated.
 
 
 
@@ -6325,7 +6325,7 @@ int year = Convert.ToInt32(Page.RouteData.Values["year"])
  ]]></format>
         </remarks>
         <block subset="none" type="overrides">
-          <para>The <see cref="M:System.Web.UI.Page.Validate" /> method is not used by [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)]. When you are using [!INCLUDE[vstecasplong](~/includes/vstecasplong-md.md)], override the <see cref="M:System.Web.UI.Page.Validate(System.String)" /> method to change page validation behavior.</para>
+          <para>The <see cref="M:System.Web.UI.Page.Validate" /> method is not used by ASP.NET 2.0. When you are using ASP.NET 2.0, override the <see cref="M:System.Web.UI.Page.Validate(System.String)" /> method to change page validation behavior.</para>
         </block>
         <altmember cref="T:System.Web.UI.ValidatorCollection" />
         <altmember cref="P:System.Web.UI.Page.Validators" />

From aef653b0a66cb153016ba365285382b4b0fa337f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:36:52 -0800
Subject: [PATCH 205/236] vstecmsbuild

---
 xml/Microsoft.Build.BuildEngine/BuildItem.xml               | 2 +-
 xml/Microsoft.Build.BuildEngine/Engine.xml                  | 6 +++---
 xml/Microsoft.Build.BuildEngine/InternalLoggerException.xml | 2 +-
 xml/Microsoft.Build.BuildEngine/Project.xml                 | 2 +-
 xml/Microsoft.Build.BuildEngine/Utilities.xml               | 4 ++--
 xml/Microsoft.Build.Framework/ILogger.xml                   | 2 +-
 xml/Microsoft.Build.Framework/OutputAttribute.xml           | 2 +-
 xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml  | 2 +-
 xml/Microsoft.Build.Framework/TaskFinishedEventArgs.xml     | 2 +-
 xml/Microsoft.Build.Framework/TaskStartedEventArgs.xml      | 2 +-
 xml/Microsoft.Build.Tasks/CallTarget.xml                    | 2 +-
 xml/Microsoft.Build.Tasks/CreateProperty.xml                | 2 +-
 xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml   | 2 +-
 xml/Microsoft.Build.Tasks/MSBuild.xml                       | 2 +-
 .../ResolveNonMSBuildProjectOutput.xml                      | 2 +-
 xml/Microsoft.Build.Tasks/SGen.xml                          | 2 +-
 xml/Microsoft.Build.Tasks/Warning.xml                       | 2 +-
 17 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/xml/Microsoft.Build.BuildEngine/BuildItem.xml b/xml/Microsoft.Build.BuildEngine/BuildItem.xml
index f5f1d297588..2ba14b2637a 100644
--- a/xml/Microsoft.Build.BuildEngine/BuildItem.xml
+++ b/xml/Microsoft.Build.BuildEngine/BuildItem.xml
@@ -655,7 +655,7 @@
         <param name="metadataName">The item metadata name.</param>
         <param name="metadataValue">The item metadata value.</param>
         <param name="treatMetadataValueAsLiteral">
-          <see langword="true" /> to treat the metadata as a literal value by escaping all [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] special characters; otherwise, <see langword="false" />.</param>
+          <see langword="true" /> to treat the metadata as a literal value by escaping all MSBuild special characters; otherwise, <see langword="false" />.</param>
         <summary>Assigns the specified value to the specified item metadata, and optionally treats the metadata as a literal value.</summary>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/Microsoft.Build.BuildEngine/Engine.xml b/xml/Microsoft.Build.BuildEngine/Engine.xml
index 27a6340c0d8..0ebdb2dc3d6 100644
--- a/xml/Microsoft.Build.BuildEngine/Engine.xml
+++ b/xml/Microsoft.Build.BuildEngine/Engine.xml
@@ -240,9 +240,9 @@
         <param name="globalProperties">A <see cref="T:Microsoft.Build.BuildEngine.BuildPropertyGroup" /> that represents properties to be passed to the child engine.</param>
         <param name="locations">A <see cref="T:Microsoft.Build.BuildEngine.ToolsetDefinitionLocations" /> enumeration specifies the location of the Toolset definition.</param>
         <param name="numberOfCpus">An integer that specifies the number of CPUs or cores in the system.</param>
-        <param name="localNodeProviderParameters">A string of parameters that are used to configure the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine. You must format the parameters as <paramref name="ParameterName" />=<paramref name="ParameterValue" />. The valid semicolon-separated, optional parameters are as follows:  
+        <param name="localNodeProviderParameters">A string of parameters that are used to configure the MSBuild engine. You must format the parameters as <paramref name="ParameterName" />=<paramref name="ParameterValue" />. The valid semicolon-separated, optional parameters are as follows:  
   
- <see langword="MSBUILDLOCATION" /> Indicates where the build process can find MSBuild.exe. This path enables the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine to locate MSBuild.exe and start it as a local node. <see langword="MSBUILDLOCATION" /> is the only essential parameter for a host. The default value is C:\Windows\Microsoft.Net\Framework\v3.5\\.  
+ <see langword="MSBUILDLOCATION" /> Indicates where the build process can find MSBuild.exe. This path enables the MSBuild engine to locate MSBuild.exe and start it as a local node. <see langword="MSBUILDLOCATION" /> is the only essential parameter for a host. The default value is C:\Windows\Microsoft.Net\Framework\v3.5\\.  
   
  <see langword="NODEREUSE" /> Indicates whether the child nodes should remain after the build finishes, in case they can be used later by another build. The nodes are discarded automatically after one minute of non-use. The default value is <see langword="true" />.</param>
         <summary>Initializes a new instance of the <see cref="T:Microsoft.Build.BuildEngine.Engine" /> class.</summary>
@@ -279,7 +279,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] 3.5, the "BinPath" is superseded by the "ToolsPath." Therefore, in the .Targets file, use MSBuildToolsPath rather than MBBuildBinPath. In the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] object model, "BinPath" relates to the Toolset you are running. The steps to get the path from the build engine are as follows:  
+ In MSBuild 3.5, the "BinPath" is superseded by the "ToolsPath." Therefore, in the .Targets file, use MSBuildToolsPath rather than MBBuildBinPath. In the MSBuild object model, "BinPath" relates to the Toolset you are running. The steps to get the path from the build engine are as follows:  
   
 1.  Get the default tools version.  
   
diff --git a/xml/Microsoft.Build.BuildEngine/InternalLoggerException.xml b/xml/Microsoft.Build.BuildEngine/InternalLoggerException.xml
index c35b97f3d24..93bdebb143e 100644
--- a/xml/Microsoft.Build.BuildEngine/InternalLoggerException.xml
+++ b/xml/Microsoft.Build.BuildEngine/InternalLoggerException.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This exception can only be thrown by the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine.  
+ This exception can only be thrown by the MSBuild engine.  
   
  This exception stops the build.  
   
diff --git a/xml/Microsoft.Build.BuildEngine/Project.xml b/xml/Microsoft.Build.BuildEngine/Project.xml
index ab178444217..6a4cd52f9c7 100644
--- a/xml/Microsoft.Build.BuildEngine/Project.xml
+++ b/xml/Microsoft.Build.BuildEngine/Project.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:Microsoft.Build.BuildEngine.Project> represents an [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] project. It is a container for items, properties and targets. It can load project content from in-memory XML or from an XML file, and can save to an XML file, preserving most white space and all XML comments.  
+ A <xref:Microsoft.Build.BuildEngine.Project> represents an MSBuild project. It is a container for items, properties and targets. It can load project content from in-memory XML or from an XML file, and can save to an XML file, preserving most white space and all XML comments.  
   
  Every <xref:Microsoft.Build.BuildEngine.Project> must be associated with an <xref:Microsoft.Build.BuildEngine.Engine> to access shared information. During a build, the <xref:Microsoft.Build.BuildEngine.Engine> object keeps track of which projects are currently building.  
   
diff --git a/xml/Microsoft.Build.BuildEngine/Utilities.xml b/xml/Microsoft.Build.BuildEngine/Utilities.xml
index 63f141a6306..f5b594dc687 100644
--- a/xml/Microsoft.Build.BuildEngine/Utilities.xml
+++ b/xml/Microsoft.Build.BuildEngine/Utilities.xml
@@ -42,13 +42,13 @@
       </Parameters>
       <Docs>
         <param name="unescapedExpression">The string to convert.</param>
-        <summary>Converts the specified string into a syntax that allows the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine to interpret the character literally.</summary>
+        <summary>Converts the specified string into a syntax that allows the MSBuild engine to interpret the character literally.</summary>
         <returns>The converted value of the specified string.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Certain characters have special meaning in [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] project files. Examples of the characters include semicolons (;) and asterisks (*). In order to use these special characters as literals, they must be specified with the syntax %nn, where nn represents the ASCII hexadecimal value of the character. This method performs that conversion.  
+ Certain characters have special meaning in MSBuild project files. Examples of the characters include semicolons (;) and asterisks (*). In order to use these special characters as literals, they must be specified with the syntax %nn, where nn represents the ASCII hexadecimal value of the character. This method performs that conversion.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Build.Framework/ILogger.xml b/xml/Microsoft.Build.Framework/ILogger.xml
index 654ada6bbcd..7936434c193 100644
--- a/xml/Microsoft.Build.Framework/ILogger.xml
+++ b/xml/Microsoft.Build.Framework/ILogger.xml
@@ -28,7 +28,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- All logger classes must implement this interface to be recognized by the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine.  
+ All logger classes must implement this interface to be recognized by the MSBuild engine.  
   
  Instead of implementing this interface directly, you can also derive your class from the helper class, <xref:Microsoft.Build.Utilities.Logger>, which provides default implementations of some <xref:Microsoft.Build.Framework.ILogger> members.  
   
diff --git a/xml/Microsoft.Build.Framework/OutputAttribute.xml b/xml/Microsoft.Build.Framework/OutputAttribute.xml
index 96d8a7015dd..98a829faeeb 100644
--- a/xml/Microsoft.Build.Framework/OutputAttribute.xml
+++ b/xml/Microsoft.Build.Framework/OutputAttribute.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine will only allow task properties marked with this attribute to output data from a task. Project authors can only use properties marked with this attribute in the `Output` element of a project file. All other task properties are treated as inputs to a task.  
+ The MSBuild engine will only allow task properties marked with this attribute to output data from a task. Project authors can only use properties marked with this attribute in the `Output` element of a project file. All other task properties are treated as inputs to a task.  
   
  For more information about using attributes, see [Extending Metadata Using Attributes](/dotnet/standard/attributes/).  
   
diff --git a/xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml b/xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml
index 9e83f0c0c76..f43c0278ede 100644
--- a/xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml
+++ b/xml/Microsoft.Build.Framework/RequiredRuntimeAttribute.xml
@@ -36,7 +36,7 @@
  A task marked with the <xref:Microsoft.Build.Framework.RequiredRuntimeAttribute> indicates that it has a stricter runtime requirement than a regular task. It alerts MSBuild that it may need to start a separate process for the task if the current CLR runtime version does not match the required version.  
   
 > [!NOTE]
->  This attribute is currently non-functional because only one version of the CLR (2.0) is capable of running either [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] version 2.0 or 3.5.  
+>  This attribute is currently non-functional because only one version of the CLR (2.0) is capable of running either MSBuild version 2.0 or 3.5.  
   
  For more information about using attributes, see [Extending Metadata Using Attributes](/dotnet/standard/attributes/).  
   
diff --git a/xml/Microsoft.Build.Framework/TaskFinishedEventArgs.xml b/xml/Microsoft.Build.Framework/TaskFinishedEventArgs.xml
index 62cfb9b659a..7428182a5f6 100644
--- a/xml/Microsoft.Build.Framework/TaskFinishedEventArgs.xml
+++ b/xml/Microsoft.Build.Framework/TaskFinishedEventArgs.xml
@@ -232,7 +232,7 @@
         <summary>
             MSBuild file where this task was defined.   
             </summary>
-        <value>The [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] file where the task is defined.</value>
+        <value>The MSBuild file where the task is defined.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/Microsoft.Build.Framework/TaskStartedEventArgs.xml b/xml/Microsoft.Build.Framework/TaskStartedEventArgs.xml
index b74c5174070..764aa9b0958 100644
--- a/xml/Microsoft.Build.Framework/TaskStartedEventArgs.xml
+++ b/xml/Microsoft.Build.Framework/TaskStartedEventArgs.xml
@@ -196,7 +196,7 @@
         <summary>
             MSBuild file where this task was defined.   
             </summary>
-        <value>The [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] file where the task was defined.</value>
+        <value>The MSBuild file where the task was defined.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/Microsoft.Build.Tasks/CallTarget.xml b/xml/Microsoft.Build.Tasks/CallTarget.xml
index 18476382b45..3647c30a8f0 100644
--- a/xml/Microsoft.Build.Tasks/CallTarget.xml
+++ b/xml/Microsoft.Build.Tasks/CallTarget.xml
@@ -153,7 +153,7 @@
             if one target fails, you can still continue with the remaining targets.
             </summary>
         <value>
-          <see langword="true" /> if the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine is called once per target; <see langword="false" /> if the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine is called once to build all targets.</value>
+          <see langword="true" /> if the MSBuild engine is called once per target; <see langword="false" /> if the MSBuild engine is called once to build all targets.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>
diff --git a/xml/Microsoft.Build.Tasks/CreateProperty.xml b/xml/Microsoft.Build.Tasks/CreateProperty.xml
index d6d796e6747..f62ff2b7f6a 100644
--- a/xml/Microsoft.Build.Tasks/CreateProperty.xml
+++ b/xml/Microsoft.Build.Tasks/CreateProperty.xml
@@ -227,7 +227,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use this property only when you want to avoid having the output property set by [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] when it skips the enclosing target because the outputs are up-to-date.  
+ Use this property only when you want to avoid having the output property set by MSBuild when it skips the enclosing target because the outputs are up-to-date.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
index 8634fff8ecf..9c9255c33b7 100644
--- a/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
+++ b/xml/Microsoft.Build.Tasks/GenerateApplicationManifest.xml
@@ -37,7 +37,7 @@
 
  In Visual Studio 2005, the [GenerateApplicationManifest Task](/visualstudio/msbuild/generateapplicationmanifest-task) requires an `EntryPoint` when an application manifest is generated. (Assembly or native manifests do not require an `EntryPoint`.) This requirement is enforced by the build error "MSB3185: EntryPoint not specified for manifest."
 
- In Visual Studio 2008, [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] does not issue this error when the `EntryPoint` task parameter is not specified. Instead, the \<customHostSpecified> tag is inserted as a child of the \<entryPoint> tag, for example, as follows.
+ In Visual Studio 2008, MSBuild does not issue this error when the `EntryPoint` task parameter is not specified. Instead, the \<customHostSpecified> tag is inserted as a child of the \<entryPoint> tag, for example, as follows.
 
 ```xml
 <entryPoint xmlns="urn:schemas-
diff --git a/xml/Microsoft.Build.Tasks/MSBuild.xml b/xml/Microsoft.Build.Tasks/MSBuild.xml
index d6333a62677..3a73bf82c98 100644
--- a/xml/Microsoft.Build.Tasks/MSBuild.xml
+++ b/xml/Microsoft.Build.Tasks/MSBuild.xml
@@ -399,7 +399,7 @@
             if one target fails, you can still continue with the remaining targets.
             </summary>
         <value>
-          <see langword="true" /> if the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] task invokes each target in the list passed to [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] one at a time; <see langword="false" /> if the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] task invokes all targets in the list at the same time.</value>
+          <see langword="true" /> if the MSBuild task invokes each target in the list passed to MSBuild one at a time; <see langword="false" /> if the MSBuild task invokes all targets in the list at the same time.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/Microsoft.Build.Tasks/ResolveNonMSBuildProjectOutput.xml b/xml/Microsoft.Build.Tasks/ResolveNonMSBuildProjectOutput.xml
index 2b5042dbf5d..e24217337f0 100644
--- a/xml/Microsoft.Build.Tasks/ResolveNonMSBuildProjectOutput.xml
+++ b/xml/Microsoft.Build.Tasks/ResolveNonMSBuildProjectOutput.xml
@@ -258,7 +258,7 @@
             Since VS only pre-resolves non-MSBuild projects, this means that project references in this list
             are in the MSBuild format.
             </summary>
-        <value>Project reference items that are in the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] format.</value>
+        <value>Project reference items that are in the MSBuild format.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
diff --git a/xml/Microsoft.Build.Tasks/SGen.xml b/xml/Microsoft.Build.Tasks/SGen.xml
index c1084274359..7e891026276 100644
--- a/xml/Microsoft.Build.Tasks/SGen.xml
+++ b/xml/Microsoft.Build.Tasks/SGen.xml
@@ -567,7 +567,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this property is `true`, the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine will execute the `SGen` task and generate a serialization assembly. If this property is false, the [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] engine will not execute the `SGen` task.  
+ If this property is `true`, the MSBuild engine will execute the `SGen` task and generate a serialization assembly. If this property is false, the MSBuild engine will not execute the `SGen` task.  
   
  ]]></format>
         </remarks>
diff --git a/xml/Microsoft.Build.Tasks/Warning.xml b/xml/Microsoft.Build.Tasks/Warning.xml
index 17a516f7e26..f723a74214b 100644
--- a/xml/Microsoft.Build.Tasks/Warning.xml
+++ b/xml/Microsoft.Build.Tasks/Warning.xml
@@ -280,7 +280,7 @@
         <summary>
             Error message
             </summary>
-        <value>The warning text that [!INCLUDE[vstecmsbuild](~/includes/vstecmsbuild-md.md)] logs.</value>
+        <value>The warning text that MSBuild logs.</value>
         <remarks>To be added.</remarks>
         <forInternalUseOnly />
       </Docs>

From 03c8bd838c2fab079bc02c2bc4648a8ec2027661 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:37:12 -0800
Subject: [PATCH 206/236] vmd-exp-dev10-long

---
 xml/System.Web.DynamicData/FieldTemplateUserControl.xml | 2 +-
 xml/System.Web.DynamicData/MetaModel.xml                | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Web.DynamicData/FieldTemplateUserControl.xml b/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
index 18f98644e38..5abbc4a9566 100644
--- a/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
+++ b/xml/System.Web.DynamicData/FieldTemplateUserControl.xml
@@ -90,7 +90,7 @@ public partial class ForeignKeyField :
   
  To compile the example code, you need the following:  
   
--   Visual Studio 2010 or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
+-   Visual Studio 2010 or Visual Web Developer 2010 Express.  
   
 -   A Dynamic Data Web site. For more information, see [Walkthrough: Creating a New Dynamic Data Web Site Using Scaffolding](https://msdn.microsoft.com/library/1564aef2-9103-436a-9806-c8ad7abd616a).  
   
diff --git a/xml/System.Web.DynamicData/MetaModel.xml b/xml/System.Web.DynamicData/MetaModel.xml
index af2842948db..93907b6a450 100644
--- a/xml/System.Web.DynamicData/MetaModel.xml
+++ b/xml/System.Web.DynamicData/MetaModel.xml
@@ -49,7 +49,7 @@
   
  To compile the example, you need the following:  
   
--   Visual Studio 2010 or [!INCLUDE[vwd_exp_dev10_long](~/includes/vwd-exp-dev10-long-md.md)].  
+-   Visual Studio 2010 or Visual Web Developer 2010 Express.  
   
 -   A Dynamic Data Web site. For more information, see [Walkthrough: Creating a New Dynamic Data Web Site Using Scaffolding](https://msdn.microsoft.com/library/1564aef2-9103-436a-9806-c8ad7abd616a).  
   

From 4dd80f44a686bb8ff722e11f0f1685649267f667 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:37:49 -0800
Subject: [PATCH 207/236] vwd-exp-orcas-long

---
 xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml b/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
index 03cccaf8f47..c210f75f583 100644
--- a/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
+++ b/xml/System.ComponentModel.DataAnnotations/RangeAttribute.xml
@@ -65,7 +65,7 @@
   
  To compile the example, you need the following:  
   
--   Microsoft Visual Studio 2008 Service Pack 1 or [!INCLUDE[vwd_exp_orcas_long](~/includes/vwd-exp-orcas-long-md.md)] SP1.  
+-   Microsoft Visual Studio 2008 Service Pack 1 or Visual Web Developer 2008 Express Edition SP1.  
   
 -   A data-driven Web site. This enables you to create a data context for the database and the class that contains the data field to customize. For more information, see `Walkthrough: Creating a New Dynamic Data Web Site using Scaffolding`.  
   

From 09df7d9a8394d15bb4582b69f77cf45887f8e684 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:38:08 -0800
Subject: [PATCH 208/236] vwprvw

---
 xml/System.Web/HttpContext.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Web/HttpContext.xml b/xml/System.Web/HttpContext.xml
index de7de2334f2..2b63ec8198a 100644
--- a/xml/System.Web/HttpContext.xml
+++ b/xml/System.Web/HttpContext.xml
@@ -785,7 +785,7 @@ End Sub
  The <xref:System.Web.HttpContext.GetGlobalResourceObject%2A> method returns a global resource by using the culture that is specified in the <xref:System.Globalization.CultureInfo.CurrentUICulture%2A> property.
 
 > [!NOTE]
->  In some editing environments, such as [!INCLUDE[vwprvw](~/includes/vwprvw-md.md)], the editor might throw a design-time <xref:System.Resources.MissingManifestResourceException> exception if you use a period (.) in the global resource-key name. However, this does not affect your ability to edit or save the file, and you can ignore the error.
+>  In some editing environments, such as Visual Web Developer, the editor might throw a design-time <xref:System.Resources.MissingManifestResourceException> exception if you use a period (.) in the global resource-key name. However, this does not affect your ability to edit or save the file, and you can ignore the error.
 
  ]]></format>
         </remarks>

From e5a103e299510b271aee336c014ff67f9b7e6df8 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:38:27 -0800
Subject: [PATCH 209/236] wf1

---
 .../IMultiTargetingSupportService.xml                           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
index 849f5019ab9..4a5d7a0b487 100644
--- a/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
+++ b/xml/System.Activities.Presentation.Hosting/IMultiTargetingSupportService.xml
@@ -18,7 +18,7 @@
 ## Remarks  
  *Multi-targeting* is the ability to find the right version of the loaded assembly that corresponds to the target .NET Framework version of the current workflow project in Visual Studio 2010.  
   
- This interface is implemented and used internally by [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components to resolve .NET Framework assemblies in a multi-targeting aware fashion within the Visual Studio 2010 hosting application. The [!INCLUDE[wf1](~/includes/wf1-md.md)] designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
+ This interface is implemented and used internally by WF designer components to resolve .NET Framework assemblies in a multi-targeting aware fashion within the Visual Studio 2010 hosting application. The WF designer components use the implementation of this interface only when additional assemblies need to be loaded dynamically into the editing `AppDomain`.  
   
  ]]></format>
     </remarks>

From 7d2f0643bf17537f9a0b78b47492b3ab843011d6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:38:45 -0800
Subject: [PATCH 210/236] wfd1

---
 .../IRegisterMetadata.xml                        |  2 +-
 .../AttachedProperty.xml                         |  2 +-
 .../ToolboxControl.xml                           |  4 ++--
 .../ToolboxItemWrapper.xml                       |  2 +-
 .../DesignerView.xml                             | 16 ++++++++--------
 .../EditingContext.xml                           |  2 +-
 .../TypeResolvingOptionsAttribute.xml            |  2 +-
 .../WorkflowDesigner.xml                         |  2 +-
 8 files changed, 16 insertions(+), 16 deletions(-)

diff --git a/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml b/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
index 844e6551557..b2988215434 100644
--- a/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
+++ b/xml/System.Activities.Presentation.Metadata/IRegisterMetadata.xml
@@ -16,7 +16,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> types provide a way to encapsulate the association of design-time attributes to run-time types in a loosely coupled fashion. An application hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] can use the <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> interface to register the attributes for the activity. For instance, Visual Studio 2010 searches for types that implement <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> when assemblies that contain these types are loaded in addition to also looking for types in the *.design assemblies.  
+ <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> types provide a way to encapsulate the association of design-time attributes to run-time types in a loosely coupled fashion. An application hosting the Windows Workflow Designer can use the <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> interface to register the attributes for the activity. For instance, Visual Studio 2010 searches for types that implement <xref:System.Activities.Presentation.Metadata.IRegisterMetadata> when assemblies that contain these types are loaded in addition to also looking for types in the *.design assemblies.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation.Model/AttachedProperty.xml b/xml/System.Activities.Presentation.Model/AttachedProperty.xml
index 122371afee5..66400032670 100644
--- a/xml/System.Activities.Presentation.Model/AttachedProperty.xml
+++ b/xml/System.Activities.Presentation.Model/AttachedProperty.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This is used by the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] in order to keep track of interesting pieces of data during an editing session for data that is otherwise transient, that will (mostly) be discarded at the end of an editing session. <xref:System.Activities.Presentation.Model.AttachedProperty> is useful as items in the `View` can bind to the values and react to changes. For instance, this is the way that the selected item template is displayed (it keys off of an attached property for selection).  
+ This is used by the Windows Workflow Designer in order to keep track of interesting pieces of data during an editing session for data that is otherwise transient, that will (mostly) be discarded at the end of an editing session. <xref:System.Activities.Presentation.Model.AttachedProperty> is useful as items in the `View` can bind to the values and react to changes. For instance, this is the way that the selected item template is displayed (it keys off of an attached property for selection).  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation.Toolbox/ToolboxControl.xml b/xml/System.Activities.Presentation.Toolbox/ToolboxControl.xml
index e4f2ce53008..b40d595ad76 100644
--- a/xml/System.Activities.Presentation.Toolbox/ToolboxControl.xml
+++ b/xml/System.Activities.Presentation.Toolbox/ToolboxControl.xml
@@ -33,7 +33,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This class provides support for representing the toolbox controls when re-hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] outside of Visual Studio. It implements <xref:System.Windows.Controls.Control>. The <xref:System.Activities.Presentation.Toolbox.ToolboxControl> contains a collection of toolbox categories that hold various categories of tools that can be accessed with the <xref:System.Activities.Presentation.Toolbox.ToolboxControl.Categories%2A> property. It also is able to retrieve the <xref:System.Activities.Presentation.WorkflowDesigner> with which it is associated using the <xref:System.Activities.Presentation.Toolbox.ToolboxControl.AssociatedDesigner%2A> property.  
+ This class provides support for representing the toolbox controls when re-hosting the Windows Workflow Designer outside of Visual Studio. It implements <xref:System.Windows.Controls.Control>. The <xref:System.Activities.Presentation.Toolbox.ToolboxControl> contains a collection of toolbox categories that hold various categories of tools that can be accessed with the <xref:System.Activities.Presentation.Toolbox.ToolboxControl.Categories%2A> property. It also is able to retrieve the <xref:System.Activities.Presentation.WorkflowDesigner> with which it is associated using the <xref:System.Activities.Presentation.Toolbox.ToolboxControl.AssociatedDesigner%2A> property.  
   
 > [!WARNING]
 >  For activities to load properly in the toolbox, the assembly that contains the activities must be loaded first. Use <xref:System.Reflection.Assembly.LoadFrom%2A> to load the activity type if it is contained in a different assembly; using <xref:System.Object.GetType%2A> instead will cause an exception to be thrown.  
@@ -85,7 +85,7 @@
         <ReturnType>System.Activities.Presentation.WorkflowDesigner</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] with which this toolbox control is associated.</summary>
+        <summary>Gets or sets the Windows Workflow Designer with which this toolbox control is associated.</summary>
         <value>The <see cref="T:System.Activities.Presentation.WorkflowDesigner" /> instance with which this toolbox control is associated.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml b/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
index bc21be2eb4d..14097f969ce 100644
--- a/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
+++ b/xml/System.Activities.Presentation.Toolbox/ToolboxItemWrapper.xml
@@ -23,7 +23,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This wrapper class provides support for the categorization of toolbox items when re-hosting the [!INCLUDE[wfd1](~/includes/wfd1-md.md)]outside of Visual Studio 2010.  
+ This wrapper class provides support for the categorization of toolbox items when re-hosting the Windows Workflow Designeroutside of Visual Studio 2010.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation.View/DesignerView.xml b/xml/System.Activities.Presentation.View/DesignerView.xml
index 3a89299cb80..650fdb3a600 100644
--- a/xml/System.Activities.Presentation.View/DesignerView.xml
+++ b/xml/System.Activities.Presentation.View/DesignerView.xml
@@ -341,7 +341,7 @@
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to create a new <see cref="T:System.Activities.Presentation.WorkflowViewElement" /> on the current [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface when dragging a workflow item from the Toolbox onto the designer surface.</summary>
+        <summary>The command used to create a new <see cref="T:System.Activities.Presentation.WorkflowViewElement" /> on the current Windows Workflow Designer surface when dragging a workflow item from the Toolbox onto the designer surface.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -401,7 +401,7 @@
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to cycle the various UI elements of the current [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface.</summary>
+        <summary>The command used to cycle the various UI elements of the current Windows Workflow Designer surface.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -561,7 +561,7 @@
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to navigate to the selected child of a composite activity and expand it to fill the full screen of the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface. The <paramref name="View full screen" /> context menu command initiates this action.</summary>
+        <summary>The command used to navigate to the selected child of a composite activity and expand it to fill the full screen of the Windows Workflow Designer surface. The <paramref name="View full screen" /> context menu command initiates this action.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -714,7 +714,7 @@
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to navigate to the parent activity of the selected child activity and expand it to fill the full screen of the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface. The <paramref name="View parent" /> context menu command initiates this action.</summary>
+        <summary>The command used to navigate to the parent activity of the selected child activity and expand it to fill the full screen of the Windows Workflow Designer surface. The <paramref name="View parent" /> context menu command initiates this action.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1598,7 +1598,7 @@
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to show or hide the argument designer. Clicking the <paramref name="Arguments" /> button on the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface initiates this action.</summary>
+        <summary>The command used to show or hide the argument designer. Clicking the <paramref name="Arguments" /> button on the Windows Workflow Designer surface initiates this action.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -1656,7 +1656,7 @@ DesignerView dView = des.Context.Services.GetService<DesignerView>();
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to show or hide the MiniMap control on the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface.</summary>
+        <summary>The command used to show or hide the MiniMap control on the Windows Workflow Designer surface.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1696,7 +1696,7 @@ DesignerView dView = des.Context.Services.GetService<DesignerView>();
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to show or hide the variable designer. Clicking the <paramref name="Variables" /> button on the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface initiates this action.</summary>
+        <summary>The command used to show or hide the variable designer. Clicking the <paramref name="Variables" /> button on the Windows Workflow Designer surface initiates this action.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
@@ -1833,7 +1833,7 @@ DesignerView dView = des.Context.Services.GetService<DesignerView>();
         <ReturnType>System.Windows.Input.ICommand</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>The command used to zoom in on the current [!INCLUDE[wfd1](~/includes/wfd1-md.md)] surface.</summary>
+        <summary>The command used to zoom in on the current Windows Workflow Designer surface.</summary>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Activities.Presentation/EditingContext.xml b/xml/System.Activities.Presentation/EditingContext.xml
index 0e3a4cb8b51..ca800441668 100644
--- a/xml/System.Activities.Presentation/EditingContext.xml
+++ b/xml/System.Activities.Presentation/EditingContext.xml
@@ -23,7 +23,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Activities.Presentation.EditingContext> represents the communication boundary that is shared between the hosting application and the [!INCLUDE[wfd1](~/includes/wfd1-md.md)]. The <xref:System.Activities.Presentation.EditingContext> was implemented as a concrete class for ease of use. Override <xref:System.Activities.Presentation.EditingContext.CreateServiceManager%2A> and <xref:System.Activities.Presentation.EditingContext.CreateContextItemManager%2A> to use customized managers derived from <xref:System.Activities.Presentation.ServiceManager> and <xref:System.Activities.Presentation.ContextItemManager>.  
+ The <xref:System.Activities.Presentation.EditingContext> represents the communication boundary that is shared between the hosting application and the Windows Workflow Designer. The <xref:System.Activities.Presentation.EditingContext> was implemented as a concrete class for ease of use. Override <xref:System.Activities.Presentation.EditingContext.CreateServiceManager%2A> and <xref:System.Activities.Presentation.EditingContext.CreateContextItemManager%2A> to use customized managers derived from <xref:System.Activities.Presentation.ServiceManager> and <xref:System.Activities.Presentation.ContextItemManager>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml b/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
index 0b3cf8288da..7ab46f2280f 100644
--- a/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
+++ b/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
@@ -108,7 +108,7 @@
         <ReturnType>System.Activities.Presentation.View.TypeResolvingOptions</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the options used to configure how a [!INCLUDE[wfd1](~/includes/wfd1-md.md)] initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</summary>
+        <summary>Gets or sets the options used to configure how a Windows Workflow Designer initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</summary>
         <value>An instance of <see cref="T:System.Activities.Presentation.View.TypeResolvingOptions" /> that specifies the options available for how a [!INCLUDE[wfd2](~/includes/wfd2-md.md)] initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Activities.Presentation/WorkflowDesigner.xml b/xml/System.Activities.Presentation/WorkflowDesigner.xml
index 04e71e21135..33006a3e082 100644
--- a/xml/System.Activities.Presentation/WorkflowDesigner.xml
+++ b/xml/System.Activities.Presentation/WorkflowDesigner.xml
@@ -159,7 +159,7 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Indicates whether the [!INCLUDE[wfd1](~/includes/wfd1-md.md)] is in error state.</summary>
+        <summary>Indicates whether the Windows Workflow Designer is in error state.</summary>
         <returns>
           <see langword="true" /> if the [!INCLUDE[wfd2](~/includes/wfd2-md.md)] is in error state; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>

From 088fa67ec8c8df3f5e329f1a74472a243044cc00 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:41:15 -0800
Subject: [PATCH 211/236] wfd2

---
 .../IWorkflowDesignerStorageService.xml                         | 2 +-
 .../TypeResolvingOptionsAttribute.xml                           | 2 +-
 xml/System.Activities.Presentation/WorkflowDesigner.xml         | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml b/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
index 0928e344db7..f9e38f905e8 100644
--- a/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
+++ b/xml/System.Activities.Presentation/IWorkflowDesignerStorageService.xml
@@ -16,7 +16,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This interface is implemented and used internally by Visual Studio 2010, which is the primary host of the [!INCLUDE[wfd2](~/includes/wfd2-md.md)].  
+ This interface is implemented and used internally by Visual Studio 2010, which is the primary host of the Workflow Designer.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml b/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
index 7ab46f2280f..02c8024db27 100644
--- a/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
+++ b/xml/System.Activities.Presentation/TypeResolvingOptionsAttribute.xml
@@ -109,7 +109,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the options used to configure how a Windows Workflow Designer initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</summary>
-        <value>An instance of <see cref="T:System.Activities.Presentation.View.TypeResolvingOptions" /> that specifies the options available for how a [!INCLUDE[wfd2](~/includes/wfd2-md.md)] initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</value>
+        <value>An instance of <see cref="T:System.Activities.Presentation.View.TypeResolvingOptions" /> that specifies the options available for how a Workflow Designer initializes type-resolver and type-browser dialogs to enable a user to select a type for arguments, variables, and generic type activities.</value>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Activities.Presentation/WorkflowDesigner.xml b/xml/System.Activities.Presentation/WorkflowDesigner.xml
index 33006a3e082..fb953bd731a 100644
--- a/xml/System.Activities.Presentation/WorkflowDesigner.xml
+++ b/xml/System.Activities.Presentation/WorkflowDesigner.xml
@@ -161,7 +161,7 @@
       <Docs>
         <summary>Indicates whether the Windows Workflow Designer is in error state.</summary>
         <returns>
-          <see langword="true" /> if the [!INCLUDE[wfd2](~/includes/wfd2-md.md)] is in error state; otherwise, <see langword="false" />.</returns>
+          <see langword="true" /> if the Workflow Designer is in error state; otherwise, <see langword="false" />.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>

From 4e04c4eb39d25cd1a9dc411f348c6a800414f165 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:41:50 -0800
Subject: [PATCH 212/236] win2kfamily

---
 xml/System.Diagnostics/Process.xml                          | 2 +-
 .../ReplicationCursor.xml                                   | 2 +-
 xml/System.DirectoryServices.Protocols/LocatorFlags.xml     | 4 ++--
 xml/System.DirectoryServices/DirectorySearcher.xml          | 2 +-
 xml/System.Drawing.Text/PrivateFontCollection.xml           | 2 +-
 xml/System.Messaging/MessageQueue.xml                       | 2 +-
 xml/System.Security.Principal/WellKnownSidType.xml          | 2 +-
 xml/System.Windows.Forms/Clipboard.xml                      | 6 +++---
 8 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Diagnostics/Process.xml b/xml/System.Diagnostics/Process.xml
index a269ccfeed2..5545557c71f 100644
--- a/xml/System.Diagnostics/Process.xml
+++ b/xml/System.Diagnostics/Process.xml
@@ -4290,7 +4290,7 @@ The calling process is a member of the associated process' descendant tree.</exc
  The <xref:System.Diagnostics.Process.ProcessName%2A> property holds an executable file name, such as Outlook, that does not include the .exe extension or the path. It is helpful for getting and manipulating all the processes that are associated with the same executable file.  
   
 > [!NOTE]
->  On [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] operating systems, the <xref:System.Diagnostics.Process.ProcessName%2A> property may be truncated to 15 characters if the process module information cannot be obtained.  
+>  On Windows 2000 operating systems, the <xref:System.Diagnostics.Process.ProcessName%2A> property may be truncated to 15 characters if the process module information cannot be obtained.  
   
  You can call <xref:System.Diagnostics.Process.GetProcessesByName%2A>, passing it an executable file name, to retrieve an array that contains every running instance on the specified computer. You can use this array, for example, to shut down all the running instances of the executable file.  
   
diff --git a/xml/System.DirectoryServices.ActiveDirectory/ReplicationCursor.xml b/xml/System.DirectoryServices.ActiveDirectory/ReplicationCursor.xml
index 918a893159b..9deb1dc30a2 100644
--- a/xml/System.DirectoryServices.ActiveDirectory/ReplicationCursor.xml
+++ b/xml/System.DirectoryServices.ActiveDirectory/ReplicationCursor.xml
@@ -48,7 +48,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">This property is not supported on [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">This property is not supported on Windows 2000.</exception>
         <altmember cref="T:System.DirectoryServices.ActiveDirectory.ReplicationCursor" />
       </Docs>
     </Member>
diff --git a/xml/System.DirectoryServices.Protocols/LocatorFlags.xml b/xml/System.DirectoryServices.Protocols/LocatorFlags.xml
index 476ad2867df..656c3d91664 100644
--- a/xml/System.DirectoryServices.Protocols/LocatorFlags.xml
+++ b/xml/System.DirectoryServices.Protocols/LocatorFlags.xml
@@ -66,7 +66,7 @@
       </ReturnValue>
       <MemberValue>32</MemberValue>
       <Docs>
-        <summary>Attempts to find a domain controller that supports directory service functions ([!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] or later). The value is equal to 32 or 0x20.</summary>
+        <summary>Attempts to find a domain controller that supports directory service functions (Windows 2000 or later). The value is equal to 32 or 0x20.</summary>
       </Docs>
     </Member>
     <Member MemberName="DirectoryServicesRequired">
@@ -88,7 +88,7 @@
       </ReturnValue>
       <MemberValue>16</MemberValue>
       <Docs>
-        <summary>Requires that the returned domain controller support [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] or later. The value is equal to 16 or 0x10.</summary>
+        <summary>Requires that the returned domain controller support Windows 2000 or later. The value is equal to 16 or 0x10.</summary>
       </Docs>
     </Member>
     <Member MemberName="ForceRediscovery">
diff --git a/xml/System.DirectoryServices/DirectorySearcher.xml b/xml/System.DirectoryServices/DirectorySearcher.xml
index d4ae2b65244..ef0e2d0f66f 100644
--- a/xml/System.DirectoryServices/DirectorySearcher.xml
+++ b/xml/System.DirectoryServices/DirectorySearcher.xml
@@ -1064,7 +1064,7 @@ SearchResultCollection res = src.FindAll();
 ## Remarks  
  To retrieve specific properties, add them to this collection before you begin the search. For example, `searcher.PropertiesToLoad.Add("phone");` will add the phone property to the list of properties to retrieve in the search.  
   
- The property "ADsPath" is always retrieved during the search. On [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] and earlier operating systems, the account that performs the search must be a member of the Administrators group to retrieve the ntSecurityDescriptor property. If this is not the case, the property value that is returned for ntSecurityDescriptor will be `null`. For more information, see the [NT-Security-Descriptor](/windows/desktop/adschema/a-ntsecuritydescriptor) article.  
+ The property "ADsPath" is always retrieved during the search. On Windows 2000 and earlier operating systems, the account that performs the search must be a member of the Administrators group to retrieve the ntSecurityDescriptor property. If this is not the case, the property value that is returned for ntSecurityDescriptor will be `null`. For more information, see the [NT-Security-Descriptor](/windows/desktop/adschema/a-ntsecuritydescriptor) article.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Drawing.Text/PrivateFontCollection.xml b/xml/System.Drawing.Text/PrivateFontCollection.xml
index b436f77b139..418b4e4eb23 100644
--- a/xml/System.Drawing.Text/PrivateFontCollection.xml
+++ b/xml/System.Drawing.Text/PrivateFontCollection.xml
@@ -104,7 +104,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Windows Forms applications support TrueType fonts and have limited support for OpenType fonts. If you try to use a font that is not supported, such as an unsupported OpenType font or a Bitmap font, an exception will occur. The <xref:System.Drawing.Text.PrivateFontCollection.AddFontFile%2A> is not supported on operating systems before [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)]. When using a private font on operating systems before [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)], the default font, typically Microsoft Sans Serif, will be substituted.  
+ Windows Forms applications support TrueType fonts and have limited support for OpenType fonts. If you try to use a font that is not supported, such as an unsupported OpenType font or a Bitmap font, an exception will occur. The <xref:System.Drawing.Text.PrivateFontCollection.AddFontFile%2A> is not supported on operating systems before Windows 2000. When using a private font on operating systems before Windows 2000, the default font, typically Microsoft Sans Serif, will be substituted.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Messaging/MessageQueue.xml b/xml/System.Messaging/MessageQueue.xml
index cbe967a0c4a..4b305a7910d 100644
--- a/xml/System.Messaging/MessageQueue.xml
+++ b/xml/System.Messaging/MessageQueue.xml
@@ -60,7 +60,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The Message Queuing technology allows applications running at different times to communicate across heterogeneous networks and systems that might be temporarily offline. Applications send, receive, or peek (read without removing) messages from queues. Message Queuing is an optional component of [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] and Windows NT, and must be installed separately.  
+ The Message Queuing technology allows applications running at different times to communicate across heterogeneous networks and systems that might be temporarily offline. Applications send, receive, or peek (read without removing) messages from queues. Message Queuing is an optional component of Windows 2000 and Windows NT, and must be installed separately.  
   
  The <xref:System.Messaging.MessageQueue> class is a wrapper around Message Queuing. There are multiple versions of Message Queuing, and using the <xref:System.Messaging.MessageQueue> class can result in slightly different behavior, depending on the operating system you are using. For information about specific features of each version of Message Queuing, see the topic "What's New in Message Queuing" in the Platform SDK in MSDN.  
   
diff --git a/xml/System.Security.Principal/WellKnownSidType.xml b/xml/System.Security.Principal/WellKnownSidType.xml
index 11163f0d21a..7a289cc6433 100644
--- a/xml/System.Security.Principal/WellKnownSidType.xml
+++ b/xml/System.Security.Principal/WellKnownSidType.xml
@@ -844,7 +844,7 @@
       </ReturnValue>
       <MemberValue>35</MemberValue>
       <Docs>
-        <summary>Indicates a SID that matches pre-[!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)] compatible accounts.</summary>
+        <summary>Indicates a SID that matches pre-Windows 2000 compatible accounts.</summary>
       </Docs>
     </Member>
     <Member MemberName="BuiltinPrintOperatorsSid">
diff --git a/xml/System.Windows.Forms/Clipboard.xml b/xml/System.Windows.Forms/Clipboard.xml
index 940840e99c2..418d4f27853 100644
--- a/xml/System.Windows.Forms/Clipboard.xml
+++ b/xml/System.Windows.Forms/Clipboard.xml
@@ -349,7 +349,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)]. Otherwise, this method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  Use this method to determine whether the Clipboard contains text data before retrieving it with the <xref:System.Windows.Forms.Clipboard.GetText%2A> method.  
   
@@ -732,7 +732,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method returns text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)]. Otherwise, this method returns text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method returns text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method returns text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  Use the <xref:System.Windows.Forms.Clipboard.ContainsText%2A> method to determine whether the Clipboard contains text data before retrieving it with this method.  
   
@@ -1345,7 +1345,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method adds text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and [!INCLUDE[Win2kFamily](~/includes/win2kfamily-md.md)]. Otherwise, this method adds text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method adds text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method adds text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  To retrieve text data from the Clipboard, first use the <xref:System.Windows.Forms.Clipboard.ContainsText%2A> method to determine whether the Clipboard contains text data before retrieving it with the <xref:System.Windows.Forms.Clipboard.GetText%2A> method.  
   

From e730090170b231f2f3083cc9039e46ab7ccc9c75 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:42:17 -0800
Subject: [PATCH 213/236] win7

---
 xml/System.Globalization/CompareInfo.xml      |  2 +-
 xml/System.Globalization/SortVersion.xml      |  4 ++--
 xml/System.Timers/Timer.xml                   |  2 +-
 .../IProcessHostPreloadClient.xml             |  4 ++--
 xml/System.Windows.Media/TextOptions.xml      |  2 +-
 xml/System.Windows.Shell/JumpItem.xml         |  2 +-
 xml/System.Windows.Shell/JumpList.xml         |  4 ++--
 xml/System.Windows.Shell/JumpPath.xml         |  2 +-
 xml/System.Windows.Shell/TaskbarItemInfo.xml  | 22 +++++++++----------
 .../TaskbarItemProgressState.xml              |  2 +-
 xml/System.Windows.Shell/ThumbButtonInfo.xml  |  8 +++----
 .../ThumbButtonInfoCollection.xml             |  2 +-
 xml/System.Windows/Window.xml                 |  6 ++---
 xml/ns-System.Windows.Shell.xml               |  2 +-
 14 files changed, 32 insertions(+), 32 deletions(-)

diff --git a/xml/System.Globalization/CompareInfo.xml b/xml/System.Globalization/CompareInfo.xml
index a0f79571f75..d1e553a9ea8 100644
--- a/xml/System.Globalization/CompareInfo.xml
+++ b/xml/System.Globalization/CompareInfo.xml
@@ -5160,7 +5160,7 @@ This method has greater overhead than other <xref:System.Globalization.CompareIn
 |.NET Framework version|Operating system|Unicode version|
 |----------------------------|----------------------|---------------------|
 |.NET Framework 4|All operating systems|Unicode 5.0|
-|.NET Framework 4.5 and later versions|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|
+|.NET Framework 4.5 and later versions|Windows 7|Unicode 5.0|
 |.NET Framework 4.5 and later versions|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.3|
 
  The <xref:System.Globalization.SortVersion> object returned by the <xref:System.Globalization.CompareInfo.Version%2A> property doesn't identify the precise Unicode version used to compare strings. It is useful only when comparing two <xref:System.Globalization.SortVersion> objects to determine whether they use the same Unicode version and culture to compare strings. For more information and an example, see the <xref:System.Globalization.SortVersion> reference page.
diff --git a/xml/System.Globalization/SortVersion.xml b/xml/System.Globalization/SortVersion.xml
index 9df4d5c8d6c..0d4bec4075c 100644
--- a/xml/System.Globalization/SortVersion.xml
+++ b/xml/System.Globalization/SortVersion.xml
@@ -52,7 +52,7 @@
 
  From the .NET Framework 2.0 Service Pack 1 through the .NET Framework 4, each version of the.NET Framework has included tables that contain sort weights and data on string normalization and that are based on a particular version of Unicode. In the .NET Framework 4.5, the presence of these tables depends on the operating system:  
   
--   On [!INCLUDE[win7](~/includes/win7-md.md)] and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
+-   On Windows 7 and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
   
 -   On [!INCLUDE[win8](~/includes/win8-md.md)], the .NET Framework delegates string comparison and ordering operations to the operating system.  
   
@@ -61,7 +61,7 @@
 |.NET Framework version|Operating system|Unicode version|  
 |----------------------------|----------------------|---------------------|  
 |.NET Framework 4|All operating systems|Unicode 5.0|  
-|.NET Framework 4.5 and later versions of the .NET Framework|[!INCLUDE[win7](~/includes/win7-md.md)]|Unicode 5.0|  
+|.NET Framework 4.5 and later versions of the .NET Framework|Windows 7|Unicode 5.0|  
 |.NET Framework 4.5 and later versions of the .NET Framework|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.0|  
   
  On [!INCLUDE[win8](~/includes/win8-md.md)], because the version of Unicode used in string comparison and ordering depends on the version of the operating system, the results of string comparison may differ even for applications that run on a specific version of the .NET Framework.  
diff --git a/xml/System.Timers/Timer.xml b/xml/System.Timers/Timer.xml
index abf94172301..7553fe0db80 100644
--- a/xml/System.Timers/Timer.xml
+++ b/xml/System.Timers/Timer.xml
@@ -729,7 +729,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You use the <xref:System.Timers.Timer.Interval%2A> property to determine the frequency at which the <xref:System.Timers.Timer.Elapsed> event is fired. Because the <xref:System.Timers.Timer> class depends on the system clock, it has the same resolution as the system clock. This means that the <xref:System.Timers.Timer.Elapsed> event will fire at an interval defined by the resolution of the system clock if the <xref:System.Timers.Timer.Interval%2A> property is less than the resolution of the system clock. The following example sets the <xref:System.Timers.Timer.Interval%2A> property to 5 milliseconds. When run on a [!INCLUDE[win7](~/includes/win7-md.md)] system whose system clock has a resolution of approximately 15 milliseconds, the event fires approximately every 15 milliseconds rather than every 5 milliseconds.  
+ You use the <xref:System.Timers.Timer.Interval%2A> property to determine the frequency at which the <xref:System.Timers.Timer.Elapsed> event is fired. Because the <xref:System.Timers.Timer> class depends on the system clock, it has the same resolution as the system clock. This means that the <xref:System.Timers.Timer.Elapsed> event will fire at an interval defined by the resolution of the system clock if the <xref:System.Timers.Timer.Interval%2A> property is less than the resolution of the system clock. The following example sets the <xref:System.Timers.Timer.Interval%2A> property to 5 milliseconds. When run on a Windows 7 system whose system clock has a resolution of approximately 15 milliseconds, the event fires approximately every 15 milliseconds rather than every 5 milliseconds.  
   
  [!code-csharp[System.Timers.Timer.Interval#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.timers.timer.interval/cs/interval2.cs#1)]
  [!code-vb[System.Timers.Timer.Interval#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.timers.timer.interval/vb/interval2.vb#1)]  
diff --git a/xml/System.Web.Hosting/IProcessHostPreloadClient.xml b/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
index 2e1a9023a3b..226dad1b9f4 100644
--- a/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
+++ b/xml/System.Web.Hosting/IProcessHostPreloadClient.xml
@@ -19,7 +19,7 @@
  This interface is intended primarily for use by WCF applications that are non-HTTP applications. ASP.NET developers who want to preload ASP.NET Web applications should use the simulated HTTP requests in IIS 7.0 combined with the `Application_Start` method in the Global.asax file.  
   
 > [!NOTE]
->  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and [!INCLUDE[win7](~/includes/win7-md.md)].  
+>  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and Windows 7.  
   
  ]]></format>
     </remarks>
@@ -53,7 +53,7 @@
  The value of `parameters` can be `null`, a zero-length array, or a populated array.  
   
 > [!NOTE]
->  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and [!INCLUDE[win7](~/includes/win7-md.md)].  
+>  The <xref:System.Web.Hosting.IProcessHostPreloadClient> type and its methods apply only to applications that run on IIS 7.0 and Windows 7.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Media/TextOptions.xml b/xml/System.Windows.Media/TextOptions.xml
index 88e7c1a5c5e..b6c6646267e 100644
--- a/xml/System.Windows.Media/TextOptions.xml
+++ b/xml/System.Windows.Media/TextOptions.xml
@@ -298,7 +298,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can tune the rendering of WPF ClearType text by using the [!INCLUDE[win7](~/includes/win7-md.md)] ClearType Text Tuner. To access the text tuner in [!INCLUDE[win7](~/includes/win7-md.md)], open the Control Panel, click **Appearance and Personalization**, click **Display**, and then click **Adjust ClearType text**.  
+ You can tune the rendering of WPF ClearType text by using the Windows 7 ClearType Text Tuner. To access the text tuner in Windows 7, open the Control Panel, click **Appearance and Personalization**, click **Display**, and then click **Adjust ClearType text**.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Shell/JumpItem.xml b/xml/System.Windows.Shell/JumpItem.xml
index a442a022d0a..677cc0b26b0 100644
--- a/xml/System.Windows.Shell/JumpItem.xml
+++ b/xml/System.Windows.Shell/JumpItem.xml
@@ -47,7 +47,7 @@
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the name of the category the <see cref="T:System.Windows.Shell.JumpItem" /> is grouped with in the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar Jump List.</summary>
+        <summary>Gets or sets the name of the category the <see cref="T:System.Windows.Shell.JumpItem" /> is grouped with in the Windows 7 taskbar Jump List.</summary>
         <value>The name of the category the <see cref="T:System.Windows.Shell.JumpItem" /> is grouped with. The default is <see langword="null" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
diff --git a/xml/System.Windows.Shell/JumpList.xml b/xml/System.Windows.Shell/JumpList.xml
index 199158b545b..e702ff65ea2 100644
--- a/xml/System.Windows.Shell/JumpList.xml
+++ b/xml/System.Windows.Shell/JumpList.xml
@@ -35,9 +35,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality for starting programs directly from the taskbar button by using Jump Lists. Jump Lists are also used in the [!INCLUDE[win7](~/includes/win7-md.md)] Start menu. You access a Jump List by right-clicking a taskbar button or by clicking the arrow next to a program in the Start menu. For more information about Jump Lists, see the [Taskbar](https://go.microsoft.com/fwlink/?LinkId=178478) section of the Windows User Experience Interaction Guidelines.  
+ The Windows 7 taskbar provides enhanced functionality for starting programs directly from the taskbar button by using Jump Lists. Jump Lists are also used in the Windows 7 Start menu. You access a Jump List by right-clicking a taskbar button or by clicking the arrow next to a program in the Start menu. For more information about Jump Lists, see the [Taskbar](https://go.microsoft.com/fwlink/?LinkId=178478) section of the Windows User Experience Interaction Guidelines.  
   
- The <xref:System.Windows.Shell.JumpList> class provides a managed wrapper for the Jump List functionality in the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar and manages the data passed to the Windows shell. The functionality exposed by the <xref:System.Windows.Shell.JumpList> class is not available in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. Applications that use the <xref:System.Windows.Shell.JumpList> class will run in other versions of Windows, but the Jump List will not be available. For more information about the Windows shell and native Jump List APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479).  
+ The <xref:System.Windows.Shell.JumpList> class provides a managed wrapper for the Jump List functionality in the Windows 7 taskbar and manages the data passed to the Windows shell. The functionality exposed by the <xref:System.Windows.Shell.JumpList> class is not available in versions of Windows earlier than Windows 7. Applications that use the <xref:System.Windows.Shell.JumpList> class will run in other versions of Windows, but the Jump List will not be available. For more information about the Windows shell and native Jump List APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479).  
   
  The following illustration shows the Jump List for Windows Media Player, with items in the **Tasks** and **Frequent** categories.  
   
diff --git a/xml/System.Windows.Shell/JumpPath.xml b/xml/System.Windows.Shell/JumpPath.xml
index 083dd106bb9..513261ddcd0 100644
--- a/xml/System.Windows.Shell/JumpPath.xml
+++ b/xml/System.Windows.Shell/JumpPath.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A <xref:System.Windows.Shell.JumpPath> is a reference to a file that can be opened from a [!INCLUDE[win7](~/includes/win7-md.md)] taskbar Jump List. If your application is not registered to handle the file type of the item, the file will not appear in the Jump List. For example, if you add a <xref:System.Windows.Shell.JumpPath> to a .txt file, your application must be registered to handle .txt files.  
+ A <xref:System.Windows.Shell.JumpPath> is a reference to a file that can be opened from a Windows 7 taskbar Jump List. If your application is not registered to handle the file type of the item, the file will not appear in the Jump List. For example, if you add a <xref:System.Windows.Shell.JumpPath> to a .txt file, your application must be registered to handle .txt files.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Shell/TaskbarItemInfo.xml b/xml/System.Windows.Shell/TaskbarItemInfo.xml
index 5bad9efa0d1..b17d5ba2cdf 100644
--- a/xml/System.Windows.Shell/TaskbarItemInfo.xml
+++ b/xml/System.Windows.Shell/TaskbarItemInfo.xml
@@ -20,19 +20,19 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Windows.Shell.TaskbarItemInfo> class provides a managed wrapper for [!INCLUDE[win7](~/includes/win7-md.md)] taskbar functionality. For more information about the Windows shell and native taskbar APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479). <xref:System.Windows.Shell.TaskbarItemInfo> is exposed as the <xref:System.Windows.Window.TaskbarItemInfo%2A?displayProperty=nameWithType> dependency property on a <xref:System.Windows.Window>.  
+ The <xref:System.Windows.Shell.TaskbarItemInfo> class provides a managed wrapper for Windows 7 taskbar functionality. For more information about the Windows shell and native taskbar APIs, see [Taskbar Extensions](https://go.microsoft.com/fwlink/?LinkId=178479). <xref:System.Windows.Shell.TaskbarItemInfo> is exposed as the <xref:System.Windows.Window.TaskbarItemInfo%2A?displayProperty=nameWithType> dependency property on a <xref:System.Windows.Window>.  
   
- The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality that enables you to use the taskbar item to communicate status to a user and expose common tasks when the window is minimized or hidden. The functionality that is exposed by the <xref:System.Windows.Shell.TaskbarItemInfo> class is unavailable in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. Applications that use the <xref:System.Windows.Shell.TaskbarItemInfo> class can still run in earlier versions of Windows; however, these taskbar enhancements are unavailable in the earlier versions.  
+ The Windows 7 taskbar provides enhanced functionality that enables you to use the taskbar item to communicate status to a user and expose common tasks when the window is minimized or hidden. The functionality that is exposed by the <xref:System.Windows.Shell.TaskbarItemInfo> class is unavailable in versions of Windows earlier than Windows 7. Applications that use the <xref:System.Windows.Shell.TaskbarItemInfo> class can still run in earlier versions of Windows; however, these taskbar enhancements are unavailable in the earlier versions.  
   
- In [!INCLUDE[win7](~/includes/win7-md.md)], some taskbar functionality might be unavailable, depending on the user's settings. For example, taskbar functionality is unavailable if Windows Aero is disabled or if the application is started with elevated permissions. Your application should provide other ways to interact with the user that do not depend on the enhanced taskbar functionality in [!INCLUDE[win7](~/includes/win7-md.md)].  
+ In Windows 7, some taskbar functionality might be unavailable, depending on the user's settings. For example, taskbar functionality is unavailable if Windows Aero is disabled or if the application is started with elevated permissions. Your application should provide other ways to interact with the user that do not depend on the enhanced taskbar functionality in Windows 7.  
   
- Program icons in the notification area, which is at the far right of the taskbar, are typically used to communicate application status to a user. By default, the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar hides program icons in the notification area. However, you can set the <xref:System.Windows.Shell.TaskbarItemInfo.Overlay%2A> property to add an image to the taskbar button to communicate status, such as online status in a messaging application. The overlay image lets users see the application status even if they cannot see the program icon in the notification area. You can also display the progress of running tasks in the taskbar button by setting the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> and <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> properties.  
+ Program icons in the notification area, which is at the far right of the taskbar, are typically used to communicate application status to a user. By default, the Windows 7 taskbar hides program icons in the notification area. However, you can set the <xref:System.Windows.Shell.TaskbarItemInfo.Overlay%2A> property to add an image to the taskbar button to communicate status, such as online status in a messaging application. The overlay image lets users see the application status even if they cannot see the program icon in the notification area. You can also display the progress of running tasks in the taskbar button by setting the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> and <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> properties.  
   
- The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar displays a thumbnail of the application when you move the mouse pointer over the taskbar button. By default the whole application window is shown. You can specify a particular part of the window to display in the thumbnail by setting the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbnailClipMargin%2A> property. You can also specify a <xref:System.Windows.Shell.TaskbarItemInfo.Description%2A> that is displayed in a tooltip above the taskbar thumbnail. The tooltip is displayed even when the thumbnail cannot be seen because of user settings.  
+ The Windows 7 taskbar displays a thumbnail of the application when you move the mouse pointer over the taskbar button. By default the whole application window is shown. You can specify a particular part of the window to display in the thumbnail by setting the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbnailClipMargin%2A> property. You can also specify a <xref:System.Windows.Shell.TaskbarItemInfo.Description%2A> that is displayed in a tooltip above the taskbar thumbnail. The tooltip is displayed even when the thumbnail cannot be seen because of user settings.  
   
  You can add buttons to the taskbar thumbnail to provide access to common tasks without switching to the application window. For example, Window Media Player provides Play, Pause, Forward, and Back buttons that let you control media playback from the taskbar thumbnail when the application is minimized. Buttons in the taskbar thumbnail are represented by <xref:System.Windows.Shell.ThumbButtonInfo> objects and are contained in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A> collection.  
   
- The following illustration shows the enhanced features of the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar.  
+ The following illustration shows the enhanced features of the Windows 7 taskbar.  
   
  ![Taskbar Item Info Sample](~/add/media/wpfshell-taskbariteminfo.png "Taskbar Item Info Sample")  
 Windows Taskbar Enhanced Features  
@@ -189,7 +189,7 @@ Windows Taskbar Description
 ## Remarks  
  You can add an image to the program icon in the taskbar button to communicate application status to the user. The overlay uses a static or animated <xref:System.Windows.Media.ImageSource> that is positioned over the bottom-right corner of the icon in the taskbar button. The overlay is not displayed if the user sets the taskbar to show small icons.  
   
- Program icons in the notification area, which is at the far right of the taskbar, are typically used to communicate application status to a user. In [!INCLUDE[win7](~/includes/win7-md.md)], program icons in the notification area are hidden by default, and are therefore, less useful for communicating status. You can use the taskbar button overlay in [!INCLUDE[win7](~/includes/win7-md.md)] to communicate status when the icon in the notification area is hidden. Your application can detect the version of Windows and provide notifications in a manner that is appropriate for the operating system.  
+ Program icons in the notification area, which is at the far right of the taskbar, are typically used to communicate application status to a user. In Windows 7, program icons in the notification area are hidden by default, and are therefore, less useful for communicating status. You can use the taskbar button overlay in Windows 7 to communicate status when the icon in the notification area is hidden. Your application can detect the version of Windows and provide notifications in a manner that is appropriate for the operating system.  
   
  Overlay images are rendered at the appropriate size. If the <xref:System.Windows.Media.ImageSource> represents an <xref:System.Drawing.Icon>, the appropriate bit depth is also used.  
   
@@ -260,7 +260,7 @@ Windows Taskbar Overlay
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can communicate the progress of long-running tasks by displaying a progress indicator in a [!INCLUDE[win7](~/includes/win7-md.md)] taskbar button. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. When the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> is <xref:System.Windows.Shell.TaskbarItemProgressState.Normal>, the indicator is green. When <xref:System.Windows.Shell.TaskbarItemProgressState.Paused>, the indicator is yellow. When <xref:System.Windows.Shell.TaskbarItemProgressState.Error>, the indicator is red. For these states, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines how much of the taskbar button is filled by the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for other values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>. <xref:System.Windows.Shell.TaskbarItemProgressState.Indeterminate> shows a pulsing green indicator across the entire taskbar button. No indicator is shown for <xref:System.Windows.Shell.TaskbarItemProgressState.None>.  
+ You can communicate the progress of long-running tasks by displaying a progress indicator in a Windows 7 taskbar button. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. When the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> is <xref:System.Windows.Shell.TaskbarItemProgressState.Normal>, the indicator is green. When <xref:System.Windows.Shell.TaskbarItemProgressState.Paused>, the indicator is yellow. When <xref:System.Windows.Shell.TaskbarItemProgressState.Error>, the indicator is red. For these states, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines how much of the taskbar button is filled by the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for other values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>. <xref:System.Windows.Shell.TaskbarItemProgressState.Indeterminate> shows a pulsing green indicator across the entire taskbar button. No indicator is shown for <xref:System.Windows.Shell.TaskbarItemProgressState.None>.  
   
  The following illustration shows the taskbar progress indicator in the <xref:System.Windows.Shell.TaskbarItemProgressState.Normal> state.  
   
@@ -325,7 +325,7 @@ Windows Taskbar Progress Indicator
 ## Remarks  
  The <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property is represented as a value between 0.0 and 1.0. Numbers smaller and larger are coerced to be within those bounds. <xref:System.Double.NaN> is coerced to 0.  
   
- You can communicate the progress of long-running tasks by displaying a progress indicator in a [!INCLUDE[win7](~/includes/win7-md.md)] taskbar button. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. If the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property is <xref:System.Windows.Shell.TaskbarItemProgressState.Normal>, <xref:System.Windows.Shell.TaskbarItemProgressState.Paused>, or <xref:System.Windows.Shell.TaskbarItemProgressState.Error>, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines the fullness of the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for some values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>. <xref:System.Windows.Shell.TaskbarItemProgressState.Indeterminate> shows a pulsing green indicator across the entire taskbar button. No indicator is shown for <xref:System.Windows.Shell.TaskbarItemProgressState.None>.  
+ You can communicate the progress of long-running tasks by displaying a progress indicator in a Windows 7 taskbar button. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. If the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property is <xref:System.Windows.Shell.TaskbarItemProgressState.Normal>, <xref:System.Windows.Shell.TaskbarItemProgressState.Paused>, or <xref:System.Windows.Shell.TaskbarItemProgressState.Error>, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines the fullness of the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for some values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>. <xref:System.Windows.Shell.TaskbarItemProgressState.Indeterminate> shows a pulsing green indicator across the entire taskbar button. No indicator is shown for <xref:System.Windows.Shell.TaskbarItemProgressState.None>.  
   
  The following illustration shows the taskbar progress indicator with a <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> of 82 percent.  
   
@@ -390,7 +390,7 @@ Windows Taskbar Progress Indicator
 ## Remarks  
  You can add buttons to the taskbar thumbnail to give users access to common tasks without requiring them to switch to the application window. For example, Windows Media Player provides Play, Pause, Forward, and Back buttons that let users control media playback from the taskbar thumbnail when the application is minimized. Buttons in the taskbar thumbnail are represented by <xref:System.Windows.Shell.ThumbButtonInfo> objects and are contained in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A> collection.  
   
- The [!INCLUDE[win7](~/includes/win7-md.md)] shell allows a maximum of seven buttons in the taskbar thumbnail. If more than seven <xref:System.Windows.Shell.ThumbButtonInfo> objects are added to the <xref:System.Windows.Shell.ThumbButtonInfoCollection>, the additional objects are treated as overflow. When a button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements, and no space is reserved for it. In this case, additional buttons from the <xref:System.Windows.Shell.ThumbButtonInfoCollection> overflow are displayed.  
+ The Windows 7 shell allows a maximum of seven buttons in the taskbar thumbnail. If more than seven <xref:System.Windows.Shell.ThumbButtonInfo> objects are added to the <xref:System.Windows.Shell.ThumbButtonInfoCollection>, the additional objects are treated as overflow. When a button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements, and no space is reserved for it. In this case, additional buttons from the <xref:System.Windows.Shell.ThumbButtonInfoCollection> overflow are displayed.  
   
  The following illustration shows the taskbar preview with a collection of two thumb buttons.  
   
@@ -452,7 +452,7 @@ Windows Taskbar Thumb Buttons
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar displays a scaled thumbnail of an application window's client area. You can set the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbnailClipMargin%2A> property to specify a cropped area of the client window that is displayed in the thumbnail. For example, this property is useful if you want to focus the thumbnail on the window content while you exclude the application toolbars. This property cannot be used to display content in the thumbnail that is not already visible in the application window.  
+ By default, the Windows 7 taskbar displays a scaled thumbnail of an application window's client area. You can set the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbnailClipMargin%2A> property to specify a cropped area of the client window that is displayed in the thumbnail. For example, this property is useful if you want to focus the thumbnail on the window content while you exclude the application toolbars. This property cannot be used to display content in the thumbnail that is not already visible in the application window.  
   
  You specify the area that is displayed in the thumbnail by setting the <xref:System.Windows.Thickness> of the border around the area. The border starts at the edge of the client window and extends inward by the specified amount. Content inside the border is displayed in the thumbnail.  
   
diff --git a/xml/System.Windows.Shell/TaskbarItemProgressState.xml b/xml/System.Windows.Shell/TaskbarItemProgressState.xml
index da285ace015..83f3dbb122f 100644
--- a/xml/System.Windows.Shell/TaskbarItemProgressState.xml
+++ b/xml/System.Windows.Shell/TaskbarItemProgressState.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- You can communicate the progress of long-running tasks by displaying a progress indicator in the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. If the <xref:System.Windows.Shell.TaskbarItemProgressState> is Normal, Paused, or Error, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines the completeness of the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for other values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>.  
+ You can communicate the progress of long-running tasks by displaying a progress indicator in the Windows 7 taskbar. The color of the indicator is determined by the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A> property, which contains one of the <xref:System.Windows.Shell.TaskbarItemProgressState> enumeration values. If the <xref:System.Windows.Shell.TaskbarItemProgressState> is Normal, Paused, or Error, the <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> property determines the completeness of the progress indicator. <xref:System.Windows.Shell.TaskbarItemInfo.ProgressValue%2A> is ignored for other values of <xref:System.Windows.Shell.TaskbarItemInfo.ProgressState%2A>.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Shell/ThumbButtonInfo.xml b/xml/System.Windows.Shell/ThumbButtonInfo.xml
index cfdf8c03d5d..5d049b48315 100644
--- a/xml/System.Windows.Shell/ThumbButtonInfo.xml
+++ b/xml/System.Windows.Shell/ThumbButtonInfo.xml
@@ -24,11 +24,11 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality that enables you to use the taskbar button to communicate status to a user and expose common tasks when the window is minimized or hidden. You can add buttons to the taskbar thumbnail to provide access to common tasks without switching to the application window. For example, Windows Media Player provides Play, Pause, Forward, and Back buttons that you can use to control media playback from the taskbar thumbnail when the application is minimized.  
+ The Windows 7 taskbar provides enhanced functionality that enables you to use the taskbar button to communicate status to a user and expose common tasks when the window is minimized or hidden. You can add buttons to the taskbar thumbnail to provide access to common tasks without switching to the application window. For example, Windows Media Player provides Play, Pause, Forward, and Back buttons that you can use to control media playback from the taskbar thumbnail when the application is minimized.  
   
- The <xref:System.Windows.Shell.ThumbButtonInfo> class contains properties that describe how the [!INCLUDE[win7](~/includes/win7-md.md)] shell displays the buttons in the taskbar thumbnail. It provides a managed wrapper around the native Windows API. <xref:System.Windows.Shell.ThumbButtonInfo> objects are contained in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A?displayProperty=nameWithType> collection.  
+ The <xref:System.Windows.Shell.ThumbButtonInfo> class contains properties that describe how the Windows 7 shell displays the buttons in the taskbar thumbnail. It provides a managed wrapper around the native Windows API. <xref:System.Windows.Shell.ThumbButtonInfo> objects are contained in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A?displayProperty=nameWithType> collection.  
   
- The enhanced taskbar functionality is not available in versions of Windows earlier than [!INCLUDE[win7](~/includes/win7-md.md)]. In [!INCLUDE[win7](~/includes/win7-md.md)], some functionality might not be available depending on the user's settings. For example, buttons are only shown in the taskbar thumbnail when Windows Aero is enabled. Your application should provide alternate ways of interacting with the user that are not dependent on the enhanced taskbar functionality.  
+ The enhanced taskbar functionality is not available in versions of Windows earlier than Windows 7. In Windows 7, some functionality might not be available depending on the user's settings. For example, buttons are only shown in the taskbar thumbnail when Windows Aero is enabled. Your application should provide alternate ways of interacting with the user that are not dependent on the enhanced taskbar functionality.  
   
  The following illustration shows a taskbar preview with two thumb buttons that provide access to the Play and Stop commands.  
   
@@ -637,7 +637,7 @@ Windows Taskbar Thumb Buttons
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, the thumbnail button is <xref:System.Windows.Visibility.Visible>. [!INCLUDE[win7](~/includes/win7-md.md)] allows a maximum of seven buttons in the taskbar thumbnail. When the <xref:System.Windows.Shell.ThumbButtonInfo.Visibility%2A> property is set to <xref:System.Windows.Visibility.Hidden>, the thumbnail button has no visible elements, but space is still reserved for it. When the thumbnail button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements and no space is reserved for it. In this case, additional thumbnail buttons in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A> collection are displayed.  
+ By default, the thumbnail button is <xref:System.Windows.Visibility.Visible>. Windows 7 allows a maximum of seven buttons in the taskbar thumbnail. When the <xref:System.Windows.Shell.ThumbButtonInfo.Visibility%2A> property is set to <xref:System.Windows.Visibility.Hidden>, the thumbnail button has no visible elements, but space is still reserved for it. When the thumbnail button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements and no space is reserved for it. In this case, additional thumbnail buttons in the <xref:System.Windows.Shell.TaskbarItemInfo.ThumbButtonInfos%2A> collection are displayed.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml b/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
index 6e8604921d9..66eeee6f4fe 100644
--- a/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
+++ b/xml/System.Windows.Shell/ThumbButtonInfoCollection.xml
@@ -25,7 +25,7 @@
 ## Remarks  
  <xref:System.Windows.Shell.ThumbButtonInfoCollection> is a strongly-typed <xref:System.Windows.FreezableCollection%601> that is used to support declarations in Extensible Application Markup Language (XAML).  
   
- The [!INCLUDE[win7](~/includes/win7-md.md)] shell allows a maximum of seven buttons in the taskbar preview. If more than seven <xref:System.Windows.Shell.ThumbButtonInfo> objects are added to the <xref:System.Windows.Shell.ThumbButtonInfoCollection>, the additional objects are treated as overflow. When a button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements and no space is reserved for it. In this case, additional buttons from the <xref:System.Windows.Shell.ThumbButtonInfoCollection> overflow are displayed.  
+ The Windows 7 shell allows a maximum of seven buttons in the taskbar preview. If more than seven <xref:System.Windows.Shell.ThumbButtonInfo> objects are added to the <xref:System.Windows.Shell.ThumbButtonInfoCollection>, the additional objects are treated as overflow. When a button is <xref:System.Windows.Visibility.Collapsed>, it does not have any visible elements and no space is reserved for it. In this case, additional buttons from the <xref:System.Windows.Shell.ThumbButtonInfoCollection> overflow are displayed.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows/Window.xml b/xml/System.Windows/Window.xml
index 884ba2e2aa0..74e84b057f6 100644
--- a/xml/System.Windows/Window.xml
+++ b/xml/System.Windows/Window.xml
@@ -2308,13 +2308,13 @@
         <ReturnType>System.Windows.Shell.TaskbarItemInfo</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar thumbnail for the <see cref="T:System.Windows.Window" />.</summary>
-        <value>The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar thumbnail for the <see cref="T:System.Windows.Window" />.</value>
+        <summary>Gets or sets the Windows 7 taskbar thumbnail for the <see cref="T:System.Windows.Window" />.</summary>
+        <value>The Windows 7 taskbar thumbnail for the <see cref="T:System.Windows.Window" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For more information about how to use the [!INCLUDE[win7](~/includes/win7-md.md)] taskbar thumbnail, see the <xref:System.Windows.Shell.TaskbarItemInfo> class.  
+ For more information about how to use the Windows 7 taskbar thumbnail, see the <xref:System.Windows.Shell.TaskbarItemInfo> class.  
   
  ]]></format>
         </remarks>
diff --git a/xml/ns-System.Windows.Shell.xml b/xml/ns-System.Windows.Shell.xml
index eda2d545b39..b4304870ce6 100644
--- a/xml/ns-System.Windows.Shell.xml
+++ b/xml/ns-System.Windows.Shell.xml
@@ -5,7 +5,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The [!INCLUDE[win7](~/includes/win7-md.md)] taskbar provides enhanced functionality that enables you to use the taskbar button to communicate status to a user and expose common tasks when the window is minimized or hidden. The functionality exposed by the types in the <xref:System.Windows.Shell> namespace is not available in versions of Windows prior to [!INCLUDE[win7](~/includes/win7-md.md)]. In [!INCLUDE[win7](~/includes/win7-md.md)], some functionality might not be available depending on the user's settings.  
+ The Windows 7 taskbar provides enhanced functionality that enables you to use the taskbar button to communicate status to a user and expose common tasks when the window is minimized or hidden. The functionality exposed by the types in the <xref:System.Windows.Shell> namespace is not available in versions of Windows prior to Windows 7. In Windows 7, some functionality might not be available depending on the user's settings.  
   
  ]]></format>
     </remarks>

From 63e85c7bc3f82e04440fd71822dd8ca1303bee7c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:42:42 -0800
Subject: [PATCH 214/236] win8-appname-long

---
 xml/System.Diagnostics/Debug.xml              |  2 +-
 xml/System.IO.Compression/BrotliStream.xml    | 10 +++---
 xml/System.IO.Compression/DeflateStream.xml   | 12 +++----
 xml/System.IO.Compression/GZipStream.xml      | 12 +++----
 xml/System.IO.Compression/ZipArchive.xml      |  2 +-
 xml/System.IO.Compression/ZipArchiveEntry.xml |  2 +-
 xml/System.IO.Compression/ZipFile.xml         |  2 +-
 .../ZipFileExtensions.xml                     |  2 +-
 .../IsolatedStorage.xml                       |  2 +-
 .../IsolatedStorageFile.xml                   |  2 +-
 .../IsolatedStorageFileStream.xml             |  2 +-
 xml/System.IO.Pipes/PipeStream.xml            |  8 ++---
 xml/System.IO/BufferedStream.xml              |  8 ++---
 xml/System.IO/FileStream.xml                  | 14 ++++----
 xml/System.IO/Stream.xml                      | 26 +++++++-------
 xml/System.Net/WebException.xml               |  2 +-
 xml/System.Reflection/TypeInfo.xml            |  6 ++--
 .../NeutralResourcesLanguageAttribute.xml     |  4 +--
 xml/System.Resources/ResourceManager.xml      | 34 +++++++++----------
 .../SatelliteContractVersionAttribute.xml     |  4 +--
 .../WindowsRuntimeDesignerContext.xml         |  2 +-
 .../ReturnValueNameAttribute.xml              |  2 +-
 .../CryptoStream.xml                          |  2 +-
 23 files changed, 81 insertions(+), 81 deletions(-)

diff --git a/xml/System.Diagnostics/Debug.xml b/xml/System.Diagnostics/Debug.xml
index d4bee25bc07..b3c3fafce8b 100644
--- a/xml/System.Diagnostics/Debug.xml
+++ b/xml/System.Diagnostics/Debug.xml
@@ -174,7 +174,7 @@
  When the application runs in user interface mode, it displays a message box that shows the call stack with file and line numbers. The message box contains three buttons: **Abort**, **Retry**, and **Ignore**. Clicking the **Abort** button terminates the application. Clicking **Retry** sends you to the code in the debugger if your application is running in a debugger, or offers to open a debugger if it is not. Clicking **Ignore** continues with the next instruction in the code.  
   
 > [!NOTE]
->  [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps do not support modal dialog boxes, so they behave the same in user interface mode and non-user interface mode. The message is written to the active trace listeners in debugging mode, or no message is written in release mode.  
+>  Windows 8.x Store apps do not support modal dialog boxes, so they behave the same in user interface mode and non-user interface mode. The message is written to the active trace listeners in debugging mode, or no message is written in release mode.  
   
 > [!NOTE]
 >  The display of the message box depends on the presence of the <xref:System.Diagnostics.DefaultTraceListener>. If the <xref:System.Diagnostics.DefaultTraceListener> is not in the <xref:System.Diagnostics.Trace.Listeners%2A> collection, the message box is not displayed. The <xref:System.Diagnostics.DefaultTraceListener> can be removed by the [&lt;clear&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/clear-element-for-listeners-for-trace), the [&lt;remove&gt;](/dotnet/framework/configure-apps/file-schema/trace-debug/remove-element-for-listeners-for-trace), or by calling the <xref:System.Diagnostics.TraceListenerCollection.Clear%2A> method on the <xref:System.Diagnostics.Trace.Listeners%2A> property (`System.Diagnostics.Trace.Listeners.Clear()`).  
diff --git a/xml/System.IO.Compression/BrotliStream.xml b/xml/System.IO.Compression/BrotliStream.xml
index 3dfa2e5ba36..71404b937a9 100644
--- a/xml/System.IO.Compression/BrotliStream.xml
+++ b/xml/System.IO.Compression/BrotliStream.xml
@@ -412,7 +412,7 @@
 
 ## Remarks
 
-The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
 
 This method disposes the Brotli stream by writing any changes to the backing store and closing the stream to release resources.   
 
@@ -731,7 +731,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -780,7 +780,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -963,7 +963,7 @@ If the write operation is successful, the position within the Brotli stream adva
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1012,7 +1012,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.BrotliStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Compression/DeflateStream.xml b/xml/System.IO.Compression/DeflateStream.xml
index 6d42b858f3b..736d6d7be7c 100644
--- a/xml/System.IO.Compression/DeflateStream.xml
+++ b/xml/System.IO.Compression/DeflateStream.xml
@@ -760,7 +760,7 @@ Copying begins at the current position in the current Deflate stream and does no
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -859,7 +859,7 @@ Copying begins at the current position in the current Deflate stream.
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the Deflate stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1318,7 +1318,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1372,7 +1372,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1640,7 +1640,7 @@ If the write operation is successful, the position within the Deflate stream adv
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1694,7 +1694,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.DeflateStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Compression/GZipStream.xml b/xml/System.IO.Compression/GZipStream.xml
index 4b2c3637ac3..f7691cc0dda 100644
--- a/xml/System.IO.Compression/GZipStream.xml
+++ b/xml/System.IO.Compression/GZipStream.xml
@@ -744,7 +744,7 @@ Copying begins at the current position in the current GZip stream, and does not
 
 ## Remarks
 
-The <xref:System.IO.Compression.GZipStream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Compression.GZipStream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -843,7 +843,7 @@ Copying begins at the current position in the current GZip stream.
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the GZip stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1304,7 +1304,7 @@ This method read a maximum of `buffer.Length` bytes from the current stream and
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1358,7 +1358,7 @@ If the operation is canceled before it completes, the returned task contains the
   
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1632,7 +1632,7 @@ If the write operation is successful, the position within the GZip stream advanc
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -1686,7 +1686,7 @@ If the operation is canceled before it completes, the returned task contains the
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Compression.GZipStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO.Compression/ZipArchive.xml b/xml/System.IO.Compression/ZipArchive.xml
index 4671dabdef3..8eca8c73489 100644
--- a/xml/System.IO.Compression/ZipArchive.xml
+++ b/xml/System.IO.Compression/ZipArchive.xml
@@ -51,7 +51,7 @@
   
  When you create a new entry, the file is compressed and added to the zip package. The <xref:System.IO.Compression.ZipArchive.CreateEntry%2A> method enables you to specify a directory hierarchy when adding the entry. You include the relative path of the new entry within the zip package. For example, creating a new entry with a relative path of `AddedFolder\NewFile.txt` creates a compressed text file in a directory named AddedFolder.  
   
- If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access four extension methods (from the <xref:System.IO.Compression.ZipFileExtensions> class) for the <xref:System.IO.Compression.ZipArchive> class: <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String)>, <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String,System.IO.Compression.CompressionLevel)>, <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String)>, and <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String,System.Boolean)> (available in .NET Core 2.0 and later versions). These extension methods enable you to compress and decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available for [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, you can compress and decompress files by using the <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream> class, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkID=246357) and [Decompressor](https://go.microsoft.com/fwlink/p/?LinkID=246358).  
+ If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access four extension methods (from the <xref:System.IO.Compression.ZipFileExtensions> class) for the <xref:System.IO.Compression.ZipArchive> class: <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String)>, <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String,System.IO.Compression.CompressionLevel)>, <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String)>, and <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String,System.Boolean)> (available in .NET Core 2.0 and later versions). These extension methods enable you to compress and decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available for Windows 8.x Store apps. In Windows 8.x Store apps, you can compress and decompress files by using the <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream> class, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkID=246357) and [Decompressor](https://go.microsoft.com/fwlink/p/?LinkID=246358).  
   
    
   
diff --git a/xml/System.IO.Compression/ZipArchiveEntry.xml b/xml/System.IO.Compression/ZipArchiveEntry.xml
index 4cfd12d88e6..9d0f88678e2 100644
--- a/xml/System.IO.Compression/ZipArchiveEntry.xml
+++ b/xml/System.IO.Compression/ZipArchiveEntry.xml
@@ -47,7 +47,7 @@
 |To open a stream to an individual file contained in a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Open%2A?displayProperty=nameWithType>|  
 |Delete a file from a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Delete%2A?displayProperty=nameWithType>|  
   
- If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in [!INCLUDE[win8](~/includes/win8-md.md)]. In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
+ If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in [!INCLUDE[win8](~/includes/win8-md.md)]. In Windows 8.x Store apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
   
    
   
diff --git a/xml/System.IO.Compression/ZipFile.xml b/xml/System.IO.Compression/ZipFile.xml
index b56d91ca397..d6c09744d39 100644
--- a/xml/System.IO.Compression/ZipFile.xml
+++ b/xml/System.IO.Compression/ZipFile.xml
@@ -53,7 +53,7 @@
 |To open a stream to an individual file contained in a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Open%2A?displayProperty=nameWithType>|  
 |Delete a file from a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Delete%2A?displayProperty=nameWithType>|  
   
- You cannot use the <xref:System.IO.Compression.ZipFile> or  <xref:System.IO.Compression.ZipFileExtensions> classes  in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, you should use the following classes to work with compressed files.  
+ You cannot use the <xref:System.IO.Compression.ZipFile> or  <xref:System.IO.Compression.ZipFileExtensions> classes  in Windows 8.x Store apps. In Windows 8.x Store apps, you should use the following classes to work with compressed files.  
   
 -   <xref:System.IO.Compression.ZipArchive>  
   
diff --git a/xml/System.IO.Compression/ZipFileExtensions.xml b/xml/System.IO.Compression/ZipFileExtensions.xml
index 020353b014e..f4beae63a46 100644
--- a/xml/System.IO.Compression/ZipFileExtensions.xml
+++ b/xml/System.IO.Compression/ZipFileExtensions.xml
@@ -45,7 +45,7 @@
 ## Remarks  
  The <xref:System.IO.Compression.ZipFileExtensions> class contains only static methods that extend the <xref:System.IO.Compression.ZipArchive> and <xref:System.IO.Compression.ZipArchiveEntry> classes. You do not create an instance of the <xref:System.IO.Compression.ZipFileExtensions> class; instead, you use these methods from instances of <xref:System.IO.Compression.ZipArchive> or <xref:System.IO.Compression.ZipArchiveEntry>.  
   
- To use the extension methods, you must reference the `System.IO.Compression.FileSystem` assembly in your project. The `System.IO.Compression.FileSystem` assembly is not available in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. Therefore, the <xref:System.IO.Compression.ZipFileExtensions> and <xref:System.IO.Compression.ZipFile> classes (both of which are in the `System.IO.Compression.FileSystem` assembly) are not available in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, you work with compressed files by using the methods in <xref:System.IO.Compression.ZipArchive>, <xref:System.IO.Compression.ZipArchiveEntry>, <xref:System.IO.Compression.DeflateStream>, and <xref:System.IO.Compression.GZipStream>.  
+ To use the extension methods, you must reference the `System.IO.Compression.FileSystem` assembly in your project. The `System.IO.Compression.FileSystem` assembly is not available in Windows 8.x Store apps. Therefore, the <xref:System.IO.Compression.ZipFileExtensions> and <xref:System.IO.Compression.ZipFile> classes (both of which are in the `System.IO.Compression.FileSystem` assembly) are not available in Windows 8.x Store apps. In Windows 8.x Store apps, you work with compressed files by using the methods in <xref:System.IO.Compression.ZipArchive>, <xref:System.IO.Compression.ZipArchiveEntry>, <xref:System.IO.Compression.DeflateStream>, and <xref:System.IO.Compression.GZipStream>.  
   
  The <xref:System.IO.Compression.ZipFileExtensions> class contains four methods that extend <xref:System.IO.Compression.ZipArchive>:  
   
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorage.xml b/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
index 87b86bc56da..beb7a302b85 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
@@ -50,7 +50,7 @@
  For information about file-based isolated storage, see the <xref:System.IO.IsolatedStorage.IsolatedStorageFile> class.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml b/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
index 55b9a87762e..39cae434ab6 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
@@ -62,7 +62,7 @@
  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
    
   
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml b/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
index be4538a5b7c..8fd967a2d60 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
@@ -58,7 +58,7 @@
  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
    
   
diff --git a/xml/System.IO.Pipes/PipeStream.xml b/xml/System.IO.Pipes/PipeStream.xml
index 43f2c78d0af..02e87f37530 100644
--- a/xml/System.IO.Pipes/PipeStream.xml
+++ b/xml/System.IO.Pipes/PipeStream.xml
@@ -1528,7 +1528,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
 
 Use the <xref:System.IO.Pipes.PipeStream.CanRead%2A> property to determine whether the current instance supports reading.  
 
@@ -1591,7 +1591,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -2190,7 +2190,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
 
 ## Remarks
 
-The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -2254,7 +2254,7 @@ The pipe handle has not been set. (Did your <see cref="T:System.IO.Pipes.PipeStr
   
 ## Remarks  
 
-The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The <xref:System.IO.Pipes.PipeStream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.Pipes.PipeStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO/BufferedStream.xml b/xml/System.IO/BufferedStream.xml
index c5d7344ed9d..117320bc8a1 100644
--- a/xml/System.IO/BufferedStream.xml
+++ b/xml/System.IO/BufferedStream.xml
@@ -778,7 +778,7 @@ bufStream->Close();
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
 
@@ -885,7 +885,7 @@ This method is called by the public <xref:System.ComponentModel.Component.Dispos
 
 ## Remarks
 
-The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -1416,7 +1416,7 @@ Use <xref:System.IO.BinaryReader> for reading primitive data types.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.BufferedStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -1891,7 +1891,7 @@ If the write operation is successful, the position within the buffered stream ad
 
 ## Remarks
 
-The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.BufferedStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
diff --git a/xml/System.IO/FileStream.xml b/xml/System.IO/FileStream.xml
index a3053cfa6cf..e7bffd16e73 100644
--- a/xml/System.IO/FileStream.xml
+++ b/xml/System.IO/FileStream.xml
@@ -54,7 +54,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.IO.FileStream> class to read from, write to, open, and close files on a file system, and to manipulate other file-related operating system handles, including pipes, standard input, and standard output. You can use the <xref:System.IO.FileStream.Read%2A>, <xref:System.IO.FileStream.Write%2A>, <xref:System.IO.Stream.CopyTo%2A>, and <xref:System.IO.FileStream.Flush%2A> methods to perform synchronous operations, or the <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A> methods to perform asynchronous operations. Use the asynchronous methods to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. <xref:System.IO.FileStream> buffers input and output for better performance.  
+ Use the <xref:System.IO.FileStream> class to read from, write to, open, and close files on a file system, and to manipulate other file-related operating system handles, including pipes, standard input, and standard output. You can use the <xref:System.IO.FileStream.Read%2A>, <xref:System.IO.FileStream.Write%2A>, <xref:System.IO.Stream.CopyTo%2A>, and <xref:System.IO.FileStream.Flush%2A> methods to perform synchronous operations, or the <xref:System.IO.FileStream.ReadAsync%2A>, <xref:System.IO.FileStream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.FileStream.FlushAsync%2A> methods to perform asynchronous operations. Use the asynchronous methods to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. <xref:System.IO.FileStream> buffers input and output for better performance.  
   
 > [!IMPORTANT]
 >  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
@@ -2059,7 +2059,7 @@ See <xref:System.IO.Stream.Close?displayProperty=nameWithType> for more informat
 
 ## Remarks
 
-The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `CopyToAsync` method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled?displayProperty=nameWithType> value for the <xref:System.Threading.Tasks.Task.Status?displayProperty=nameWithType> property.
 
@@ -2181,7 +2181,7 @@ For an example of copying between two streams, see the <xref:System.IO.Stream.Co
 
 ## Remarks
 
-The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `DisposeAsync` method lets you perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.
 
@@ -3288,7 +3288,7 @@ Use <xref:System.IO.BinaryReader> for reading primitive data types.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -3366,7 +3366,7 @@ The following example shows how to read from a file asynchronously.
 
 ## Remarks
 
-The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `ReadAsync` method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanRead%2A> property to determine whether the current instance supports reading.
 
@@ -3996,7 +3996,7 @@ If the write operation is successful, the position within the file stream advanc
 
 ## Remarks
 
-The `WriteAsync` method lets you perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
+The `WriteAsync` method lets you perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.
 
 Use the <xref:System.IO.FileStream.CanWrite%2A> property to determine whether the current instance supports writing.
 
@@ -4066,7 +4066,7 @@ If the operation is canceled before it completes, the returned task contains the
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.FileStream.WriteAsync%2A> method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.FileStream.WriteAsync%2A> method enables you to perform resource-intensive file operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.FileStream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
diff --git a/xml/System.IO/Stream.xml b/xml/System.IO/Stream.xml
index 840c8330ae2..a17fbaca178 100644
--- a/xml/System.IO/Stream.xml
+++ b/xml/System.IO/Stream.xml
@@ -98,9 +98,9 @@
   
  Disposing a <xref:System.IO.Stream> object flushes any buffered data, and essentially calls the <xref:System.IO.Stream.Flush%2A> method for you. <xref:System.IO.Stream.Dispose%2A> also releases operating system resources such as file handles, network connections, or memory used for any internal buffering. The <xref:System.IO.BufferedStream> class provides the capability of wrapping a buffered stream around another stream in order to improve read and write performance.  
   
- Starting with the .NET Framework 4.5, the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ Starting with the .NET Framework 4.5, the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
- When used in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)]. You can also convert a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)] to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
+ When used in a Windows 8.x Store app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)]. You can also convert a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)] to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
   
  Some stream implementations perform local buffering of the underlying data to improve performance. For such streams, you can use the <xref:System.IO.Stream.Flush%2A> or <xref:System.IO.Stream.FlushAsync%2A> method to clear any internal buffers and ensure that all data has been written to the underlying data source or repository.  
   
@@ -834,7 +834,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Copying begins at the current position in the current stream.  
   
@@ -907,7 +907,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Copying begins at the current position in the current stream.  
   
@@ -963,7 +963,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
   
@@ -1030,7 +1030,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.CopyToAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  If the operation is canceled before it completes, the returned task contains the <xref:System.Threading.Tasks.TaskStatus.Canceled> value for the <xref:System.Threading.Tasks.Task.Status%2A> property.  
   
@@ -1276,7 +1276,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+ The <xref:System.IO.Stream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
  
  This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.   
   
@@ -1987,7 +1987,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2054,7 +2054,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2135,7 +2135,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.ReadAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanRead%2A> property to determine whether the current instance supports reading.  
   
@@ -2658,7 +2658,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
@@ -2725,7 +2725,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
@@ -2806,7 +2806,7 @@ This member is an explicit interface member implementation. It can be used only
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
+ The <xref:System.IO.Stream.WriteAsync%2A> method enables you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
  Use the <xref:System.IO.Stream.CanWrite%2A> property to determine whether the current instance supports writing.  
   
diff --git a/xml/System.Net/WebException.xml b/xml/System.Net/WebException.xml
index fd63d7798c5..b92afca3ed6 100644
--- a/xml/System.Net/WebException.xml
+++ b/xml/System.Net/WebException.xml
@@ -619,7 +619,7 @@
  The value of <xref:System.Net.WebException.Status%2A> is one of the <xref:System.Net.WebExceptionStatus> values.  
   
 > [!WARNING]
->  The <xref:System.Net.WebExceptionStatus.ProxyNameResolutionFailure> error is not returned to [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps.  
+>  The <xref:System.Net.WebExceptionStatus.ProxyNameResolutionFailure> error is not returned to Windows 8.x Store apps.  
   
    
   
diff --git a/xml/System.Reflection/TypeInfo.xml b/xml/System.Reflection/TypeInfo.xml
index 616451c7181..3640b0117c7 100644
--- a/xml/System.Reflection/TypeInfo.xml
+++ b/xml/System.Reflection/TypeInfo.xml
@@ -81,7 +81,7 @@
    
   
 ## Examples  
- This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a Windows 8.x Store XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
@@ -584,7 +584,7 @@
    
   
 ## Examples  
- This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a Windows 8.x Store XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
@@ -701,7 +701,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Examples  
- This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
+ This example uses the reflection types and members in the .NET for Windows 8.x Store apps subset to retrieve the methods and properties of the <xref:System.Globalization.Calendar> type, including inherited methods and properties. To run this code, paste it into the code file for a Windows 8.x Store XAML app that contains a [Windows.UI.Xaml.Controls.Textblock](xref:Windows.UI.Xaml.Controls.TextBlock) control named `textblock1`.  
   
  [!code-csharp[System.ReflectionWinStoreApp#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.reflectionwinstoreapp/cs/mainpage.xaml.cs#1)]
  [!code-vb[System.ReflectionWinStoreApp#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.reflectionwinstoreapp/vb/mainpage.xaml.vb#1)]  
diff --git a/xml/System.Resources/NeutralResourcesLanguageAttribute.xml b/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
index b562ae936f2..35161dc7301 100644
--- a/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
+++ b/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
@@ -79,8 +79,8 @@
   
 -   If the default culture's resources are located in a satellite assembly rather than in the main app assembly, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute specifies the culture and the directory from which the runtime can load the resources.  
   
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps  
- In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps whose resources are loaded and retrieved by using the <xref:System.Resources.ResourceManager> class, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute defines the neutral culture whose resources are used in the event of a failed probe. It does not specify the location of the resources. By default, <xref:System.Resources.ResourceManager> uses the app's package resource index (PRI) file to locate the resources of the default culture. The neutral culture that is defined by the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is added to the end of the UI language list to simulate this effect.  
+## Windows 8.x Store Apps  
+ In Windows 8.x Store apps whose resources are loaded and retrieved by using the <xref:System.Resources.ResourceManager> class, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute defines the neutral culture whose resources are used in the event of a failed probe. It does not specify the location of the resources. By default, <xref:System.Resources.ResourceManager> uses the app's package resource index (PRI) file to locate the resources of the default culture. The neutral culture that is defined by the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is added to the end of the UI language list to simulate this effect.  
   
  If you load and retrieve resources by using the [!INCLUDE[wrt](~/includes/wrt-md.md)][Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class or the types in the [Windows.ApplicationModel.Resources.Core](https://go.microsoft.com/fwlink/p/?LinkId=238194) namespace, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is ignored.  
   
diff --git a/xml/System.Resources/ResourceManager.xml b/xml/System.Resources/ResourceManager.xml
index b56ab3fe3b7..e2a58ddd915 100644
--- a/xml/System.Resources/ResourceManager.xml
+++ b/xml/System.Resources/ResourceManager.xml
@@ -64,7 +64,7 @@
 
  The <xref:System.Resources.ResourceManager> class retrieves resources from a binary .resources file that is embedded in an assembly or from a standalone .resources file. If an app has been localized and localized resources have been deployed in [satellite assemblies](/dotnet/framework/resources/creating-satellite-assemblies-for-desktop-apps), it looks up culture-specific resources, provides resource fallback when a localized resource does not exist, and supports resource serialization.
 
- For more information about creating and managing resources in desktop apps and [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, see the following sections:
+ For more information about creating and managing resources in desktop apps and Windows 8.x Store apps, see the following sections:
 
 -   [Desktop Apps](#desktop)
 
@@ -311,14 +311,14 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
  If resources are needed for any assembly not listed under the `<satelliteassemblies>` node, the <xref:System.Resources.ResourceManager> class probes for cultures using standard probing rules.
 
 <a name="ws"></a>
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
+## Windows 8.x Store Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- For [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager> class retrieves resources from package resource index (PRI) files. A single PRI file (the application package PRI file) contains the resources for both the default culture and any localized cultures. You use the MakePRI utility to create a PRI file from one or more resource files that are in XML resource (.resw) format. For resources that are included in a Visual Studio project, Visual Studio handles the process of creating and packaging the PRI file automatically. You can then use the .NET Framework <xref:System.Resources.ResourceManager> class to access the app's or library's resources.
+ For Windows 8.x Store apps, the <xref:System.Resources.ResourceManager> class retrieves resources from package resource index (PRI) files. A single PRI file (the application package PRI file) contains the resources for both the default culture and any localized cultures. You use the MakePRI utility to create a PRI file from one or more resource files that are in XML resource (.resw) format. For resources that are included in a Visual Studio project, Visual Studio handles the process of creating and packaging the PRI file automatically. You can then use the .NET Framework <xref:System.Resources.ResourceManager> class to access the app's or library's resources.
 
- You can instantiate a <xref:System.Resources.ResourceManager> object for a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app in the same way that you do for a desktop app.
+ You can instantiate a <xref:System.Resources.ResourceManager> object for a Windows 8.x Store app in the same way that you do for a desktop app.
 
  You can then access the resources for a particular culture by passing the name of the resource to be retrieved to the <xref:System.Resources.ResourceManager.GetString%28System.String%29> method. By default, this method returns the resource for the culture determined by the current UI culture of the thread that made the call. You can also retrieve the resources for a specific culture by passing the name of the resource and a <xref:System.Globalization.CultureInfo> object that represents the culture whose resource is to be retrieved to the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method. If the resource for the current UI culture or the specified culture cannot be found, the resource manager uses a UI language fallback list to locate a suitable resource.
 
@@ -512,12 +512,12 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 
  If you're not using Visual Studio, you can create a class with no members whose namespace and name are the same as that of the default .resources file. The example provides an illustration.
 
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
+## Windows 8.x Store Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, <xref:System.Resources.ResourceManager> uses the `resourceSource` parameter to infer the assembly, base name, and the namespace where the resource items can be located within the app's package resource index (PRI) file. For example, given a type named MyCompany.MyProduct.MyType that is defined in `MyAssembly`, the resource manager looks for a resource set identifier named MyAssembly and looks for a scope MyCompany.MyProduct.MyType within that resource set. The resource manager searches for resource items under the default context (current culture, current high contrast setting, and so on) within this scope.
+ In Windows 8.x Store apps, <xref:System.Resources.ResourceManager> uses the `resourceSource` parameter to infer the assembly, base name, and the namespace where the resource items can be located within the app's package resource index (PRI) file. For example, given a type named MyCompany.MyProduct.MyType that is defined in `MyAssembly`, the resource manager looks for a resource set identifier named MyAssembly and looks for a scope MyCompany.MyProduct.MyType within that resource set. The resource manager searches for resource items under the default context (current culture, current high contrast setting, and so on) within this scope.
 
 
 
@@ -627,12 +627,12 @@ al /out:ru-RU\Greet.resources.dll /culture:ru-RU /embed: GreetingResources.ru-RU
 
  If the resource file identified by `baseName` cannot be found in `assembly`, the method instantiates a <xref:System.Resources.ResourceManager> object, but the attempt to retrieve a specific resource throws an exception, typically <xref:System.Resources.MissingManifestResourceException>. For information about diagnosing the cause of the exception, see the "Handling the MissingManifestResourceException Exception" section of the <xref:System.Resources.ResourceManager> class topic.
 
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
+## Windows 8.x Store Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the resource manager uses the simple name of the `assembly` parameter to look up a matching resource set in the app's package resource index (PRI) file. The `baseName` parameter is used to look up a resource item within the resource set. For example, the root name for PortableLibrary1.Resource1.de-DE.resources is PortableLibrary1.Resource1.
+ In Windows 8.x Store apps, the resource manager uses the simple name of the `assembly` parameter to look up a matching resource set in the app's package resource index (PRI) file. The `baseName` parameter is used to look up a resource item within the resource set. For example, the root name for PortableLibrary1.Resource1.de-DE.resources is PortableLibrary1.Resource1.
 
 
 
@@ -1723,12 +1723,12 @@ csc GetStream.cs /resource:AppResources.resources
 > [!CAUTION]
 >  This method can throw more exceptions than are listed. One reason this might occur is if a method that this method calls throws an exception.  For example, a <xref:System.IO.FileLoadException> exception might be thrown if an error was made deploying or installing a satellite assembly, or a <xref:System.Runtime.Serialization.SerializationException> exception might be thrown if a user-defined type throws a user-defined exception when the type is deserialized.
 
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
+## Windows 8.x Store Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%29> method returns the value of the `name` string resource, localized for the caller's current UI culture settings. The list of cultures is derived from the operating system's preferred UI language list. If the resource manager cannot match `name`, the method returns `null`.
+ In Windows 8.x Store apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%29> method returns the value of the `name` string resource, localized for the caller's current UI culture settings. The list of cultures is derived from the operating system's preferred UI language list. If the resource manager cannot match `name`, the method returns `null`.
 
 
 
@@ -1838,12 +1838,12 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 > [!CAUTION]
 >  This method can throw more exceptions than are listed. One reason this might occur is if a method that this method calls throws an exception.  For example, a <xref:System.IO.FileLoadException> exception might be thrown if an error was made deploying or installing a satellite assembly, or a <xref:System.Runtime.Serialization.SerializationException> exception might be thrown if a user-defined type throws a user-defined exception when the type is deserialized.
 
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps
+## Windows 8.x Store Apps
 
 > [!IMPORTANT]
->  Although the <xref:System.Resources.ResourceManager> class is supported in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. To retrieve resources from [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
+>  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- In [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method returns the value of the `name` string resource, localized for the culture specified by the `culture` parameter. If the resource is not localized for the `culture` culture, the lookup uses the entire [!INCLUDE[win8](~/includes/win8-md.md)] language fallback list, and stops after looking in the default culture. If the resource manager cannot match `name`, the method returns `null`.
+ In Windows 8.x Store apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method returns the value of the `name` string resource, localized for the culture specified by the `culture` parameter. If the resource is not localized for the `culture` culture, the lookup uses the entire [!INCLUDE[win8](~/includes/win8-md.md)] language fallback list, and stops after looking in the default culture. If the resource manager cannot match `name`, the method returns `null`.
 
 
 
diff --git a/xml/System.Resources/SatelliteContractVersionAttribute.xml b/xml/System.Resources/SatelliteContractVersionAttribute.xml
index 8fec58a1461..c025b254b62 100644
--- a/xml/System.Resources/SatelliteContractVersionAttribute.xml
+++ b/xml/System.Resources/SatelliteContractVersionAttribute.xml
@@ -68,8 +68,8 @@
   
  A vendor of a shared component uses a publisher policy assembly to make a compatibility statement about a particular version of a released assembly. A publisher policy assembly is a strongly named assembly that has a name in the format `policy.<major>.<minor>.<ComponentAssemblyName>`, and is registered in the [Global Assembly Cache (GAC)](/dotnet/framework/app-domains/gac). The publisher policy is generated from an XML configuration file (see the [\<bindingRedirect> Element](/dotnet/framework/configure-apps/file-schema/runtime/bindingredirect-element)) by using the [Al.exe (Assembly Linker)](/dotnet/framework/tools/al-exe-assembly-linker) tool. The Assembly Linker is used with the `/link` option to link the XML configuration file to a manifest assembly, which is then stored in the global assembly cache. The publisher policy assemblies can be used when a vendor ships a maintenance release (service pack) that contains bug fixes.  
   
-## [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] Apps  
- This attribute is ignored in [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps, because package resource index (PRI) files do not have versioning semantics. In addition, the [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] packaging model requires all resources to ship in the same package, with no possibility of redeploying satellite assemblies or PRI files.  
+## Windows 8.x Store Apps  
+ This attribute is ignored in Windows 8.x Store apps, because package resource index (PRI) files do not have versioning semantics. In addition, the Windows 8.x Store packaging model requires all resources to ship in the same package, with no possibility of redeploying satellite assemblies or PRI files.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml b/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
index 8aebec92e2c..cb3bef41078 100644
--- a/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
+++ b/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
@@ -19,7 +19,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This feature is used only in developer mode for [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] apps. It enables designers to supply isolated binding contexts as required, during iterative development of assemblies.  
+ This feature is used only in developer mode for Windows 8.x Store apps. It enables designers to supply isolated binding contexts as required, during iterative development of assemblies.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
index 3a2113a26b3..9365cc09e9e 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In a [!INCLUDE[wrt](~/includes/wrt-md.md)] component, all the parameters of a method and the return value must have names. By default, [Winmdexp.exe (Windows Runtime Metadata Export Tool)](/dotnet/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool) gives the return value the name "value". When you use a component in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app written in JavaScript, you can use this name to retrieve the return value. For example, suppose a component defines a method that has a return value and two `out` parameters (`ByRef` parameters with the <xref:System.Runtime.InteropServices.OutAttribute> attribute in Visual Basic):  
+ In a [!INCLUDE[wrt](~/includes/wrt-md.md)] component, all the parameters of a method and the return value must have names. By default, [Winmdexp.exe (Windows Runtime Metadata Export Tool)](/dotnet/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool) gives the return value the name "value". When you use a component in a Windows 8.x Store app written in JavaScript, you can use this name to retrieve the return value. For example, suppose a component defines a method that has a return value and two `out` parameters (`ByRef` parameters with the <xref:System.Runtime.InteropServices.OutAttribute> attribute in Visual Basic):  
   
 ```csharp  
 public static int ComputeAverage([ReadOnlyArray()] int[] input,  
diff --git a/xml/System.Security.Cryptography/CryptoStream.xml b/xml/System.Security.Cryptography/CryptoStream.xml
index 1fba4011299..e1ec2688042 100644
--- a/xml/System.Security.Cryptography/CryptoStream.xml
+++ b/xml/System.Security.Cryptography/CryptoStream.xml
@@ -579,7 +579,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The <xref:System.Security.Cryptography.CryptoStream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a [!INCLUDE[win8_appname_long](~/includes/win8-appname-long-md.md)] app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
+ The <xref:System.Security.Cryptography.CryptoStream.DisposeAsync%2A> method enables you to perform a resource-intensive dispose operation without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#. 
  
  This method disposes the stream by writing any changes to the backing store and closing the stream to release resources.   
   

From 5d09d9b24f652482ebe56f3d44463c4561f5288f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:43:20 -0800
Subject: [PATCH 215/236] win8-appstore-long

---
 xml/System.Diagnostics/Debug.xml | 2 +-
 xml/System.IO/Directory.xml      | 2 +-
 xml/System.IO/StreamReader.xml   | 2 +-
 xml/System.IO/StreamWriter.xml   | 2 +-
 xml/System/Object.xml            | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Diagnostics/Debug.xml b/xml/System.Diagnostics/Debug.xml
index b3c3fafce8b..3fc0ef5cef3 100644
--- a/xml/System.Diagnostics/Debug.xml
+++ b/xml/System.Diagnostics/Debug.xml
@@ -167,7 +167,7 @@
  By default, the <xref:System.Diagnostics.Debug.Assert%2A?displayProperty=nameWithType> method works only in debug builds. Use the <xref:System.Diagnostics.Trace.Assert%2A?displayProperty=nameWithType> method if you want to do assertions in release builds. For more information, see [Assertions in Managed Code](/visualstudio/debugger/assertions-in-managed-code).  
   
 > [!IMPORTANT]
->  The `Assert` methods are not available for [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] apps.  
+>  The `Assert` methods are not available for Windows Store apps.  
   
  Typically, the <xref:System.Diagnostics.Debug.Assert%28System.Boolean%29> method is used to identify logic errors during program development. <xref:System.Diagnostics.Debug.Assert%2A> evaluates the condition. If the result is `false`, it sends a failure message to the <xref:System.Diagnostics.Debug.Listeners%2A> collection. You can customize this behavior by adding a <xref:System.Diagnostics.TraceListener> to, or removing one from, the <xref:System.Diagnostics.Debug.Listeners%2A> collection.  
   
diff --git a/xml/System.IO/Directory.xml b/xml/System.IO/Directory.xml
index b09296553ea..16e4fbdc2dd 100644
--- a/xml/System.IO/Directory.xml
+++ b/xml/System.IO/Directory.xml
@@ -83,7 +83,7 @@
   
  For a list of common I/O tasks, see [Common I/O Tasks](/dotnet/standard/io/common-i-o-tasks).  
   
- <xref:System.IO.Directory> and <xref:System.IO.DirectoryInfo> are not supported for use in [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] apps. For information about how to access files and folders in [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] apps, see [Accessing data and files (Windows Store apps)](https://msdn.microsoft.com/library/windows/apps/hh758319.aspx).  
+ <xref:System.IO.Directory> and <xref:System.IO.DirectoryInfo> are not supported for use in Windows Store apps. For information about how to access files and folders in Windows Store apps, see [Accessing data and files (Windows Store apps)](https://msdn.microsoft.com/library/windows/apps/hh758319.aspx).  
   
    
   
diff --git a/xml/System.IO/StreamReader.xml b/xml/System.IO/StreamReader.xml
index 59222622f1d..0682f13bdca 100644
--- a/xml/System.IO/StreamReader.xml
+++ b/xml/System.IO/StreamReader.xml
@@ -83,7 +83,7 @@
    
   
 ## Examples  
- The following example uses an instance of <xref:System.IO.StreamReader> to read text from a file. The constructor used in this example is not supported for use in [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] Apps.  
+ The following example uses an instance of <xref:System.IO.StreamReader> to read text from a file. The constructor used in this example is not supported for use in Windows Store Apps.  
   
  [!code-cpp[readtextfile#1](~/samples/snippets/cpp/VS_Snippets_CLR/ReadTextFile/CPP/readtextfile.cpp#1)]
  [!code-csharp[readtextfile#1](~/samples/snippets/csharp/VS_Snippets_CLR/ReadTextFile/CS/readtextfile.cs#1)]
diff --git a/xml/System.IO/StreamWriter.xml b/xml/System.IO/StreamWriter.xml
index 48d9240c7b3..b99058f1321 100644
--- a/xml/System.IO/StreamWriter.xml
+++ b/xml/System.IO/StreamWriter.xml
@@ -78,7 +78,7 @@
    
   
 ## Examples  
- The following example shows how to use a <xref:System.IO.StreamWriter> object to write a file that lists the directories on the C drive, and then uses a <xref:System.IO.StreamReader> object to read and display each directory name. A good practice is to use these objects in a `using` statement so that the unmanaged resources are correctly disposed. The `using` statement automatically calls <xref:System.IDisposable.Dispose%2A> on the object when the code that is using it has completed. The constructor used in this example is not supported for use in [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] Apps.  
+ The following example shows how to use a <xref:System.IO.StreamWriter> object to write a file that lists the directories on the C drive, and then uses a <xref:System.IO.StreamReader> object to read and display each directory name. A good practice is to use these objects in a `using` statement so that the unmanaged resources are correctly disposed. The `using` statement automatically calls <xref:System.IDisposable.Dispose%2A> on the object when the code that is using it has completed. The constructor used in this example is not supported for use in Windows Store Apps.  
   
  [!code-csharp[StreamReadWrite#1](~/samples/snippets/csharp/VS_Snippets_CLR/streamreadwrite/cs/program.cs#1)]
  [!code-vb[StreamReadWrite#1](~/samples/snippets/visualbasic/VS_Snippets_CLR/streamreadwrite/vb/module1.vb#1)]  
diff --git a/xml/System/Object.xml b/xml/System/Object.xml
index 20121edd976..bbbbffd4d82 100644
--- a/xml/System/Object.xml
+++ b/xml/System/Object.xml
@@ -1141,7 +1141,7 @@ and the <xref:System.IDisposable> interface. The <xref:System.IDisposable.Dispos
  When managed objects are called by native code or by code written in languages such as JavaScript or C++/CX, they appear to implement [IStringable](xref:Windows.Foundation.IStringable). The common language runtime automatically routes calls from [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) to <xref:System.Object.ToString%2A?displayProperty=nameWithType> if [IStringable](xref:Windows.Foundation.IStringable) is not implemented on the managed object.  
   
 > [!WARNING]
->  Because the common language runtime auto-implements [IStringable](xref:Windows.Foundation.IStringable) for all managed types in [!INCLUDE[win8_appstore_long](~/includes/win8-appstore-long-md.md)] apps, we recommend that you do not provide your own `IStringable` implementation. Implementing `IStringable` may result in unintended behavior when calling `ToString` from the [!INCLUDE[wrt](~/includes/wrt-md.md)], C++/CX, or JavaScript.  
+>  Because the common language runtime auto-implements [IStringable](xref:Windows.Foundation.IStringable) for all managed types in Windows Store apps, we recommend that you do not provide your own `IStringable` implementation. Implementing `IStringable` may result in unintended behavior when calling `ToString` from the [!INCLUDE[wrt](~/includes/wrt-md.md)], C++/CX, or JavaScript.  
   
  If you do choose to implement [IStringable](xref:Windows.Foundation.IStringable) in a public managed type that's exported in a [!INCLUDE[wrt](~/includes/wrt-md.md)] component, the following restrictions apply:  
   

From 73c2d2bd816390facbb85138e402d87150f1f43c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:43:40 -0800
Subject: [PATCH 216/236] win8

---
 xml/System.Diagnostics/ProcessModule.xml               |  2 +-
 xml/System.Globalization/CompareInfo.xml               |  2 +-
 xml/System.Globalization/IdnMapping.xml                | 10 +++++-----
 xml/System.Globalization/SortVersion.xml               |  6 +++---
 xml/System.IO.Compression/ZipArchiveEntry.xml          |  2 +-
 xml/System.Resources/ResourceManager.xml               |  2 +-
 xml/System.Web.Configuration/CompilationSection.xml    |  6 +++---
 .../MachineKeyCompatibilityMode.xml                    |  2 +-
 xml/System/Exception.xml                               |  2 +-
 xml/ns-System.Net.Http.xml                             |  2 +-
 10 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/xml/System.Diagnostics/ProcessModule.xml b/xml/System.Diagnostics/ProcessModule.xml
index c493d9db43c..019e5f057f2 100644
--- a/xml/System.Diagnostics/ProcessModule.xml
+++ b/xml/System.Diagnostics/ProcessModule.xml
@@ -189,7 +189,7 @@
  The module's entry point is the location of the function that is called during process startup, thread startup, process shutdown, and thread shutdown. While the entry point is not the address of the DllMain function, it should be close enough for most purposes.  
   
 > [!NOTE]
->  Due to changes in the way that Windows loads assemblies, <xref:System.Diagnostics.ProcessModule.EntryPointAddress%2A> will always return 0 on [!INCLUDE[win8](~/includes/win8-md.md)] or [!INCLUDE[win81](~/includes/win81-md.md)] and should not be relied on for those platforms.  
+>  Due to changes in the way that Windows loads assemblies, <xref:System.Diagnostics.ProcessModule.EntryPointAddress%2A> will always return 0 on Windows 8 or [!INCLUDE[win81](~/includes/win81-md.md)] and should not be relied on for those platforms.  
   
    
   
diff --git a/xml/System.Globalization/CompareInfo.xml b/xml/System.Globalization/CompareInfo.xml
index d1e553a9ea8..e0abde4fbc8 100644
--- a/xml/System.Globalization/CompareInfo.xml
+++ b/xml/System.Globalization/CompareInfo.xml
@@ -5161,7 +5161,7 @@ This method has greater overhead than other <xref:System.Globalization.CompareIn
 |----------------------------|----------------------|---------------------|
 |.NET Framework 4|All operating systems|Unicode 5.0|
 |.NET Framework 4.5 and later versions|Windows 7|Unicode 5.0|
-|.NET Framework 4.5 and later versions|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.3|
+|.NET Framework 4.5 and later versions|Windows 8 and later Windows operating system versions|Unicode 6.3|
 
  The <xref:System.Globalization.SortVersion> object returned by the <xref:System.Globalization.CompareInfo.Version%2A> property doesn't identify the precise Unicode version used to compare strings. It is useful only when comparing two <xref:System.Globalization.SortVersion> objects to determine whether they use the same Unicode version and culture to compare strings. For more information and an example, see the <xref:System.Globalization.SortVersion> reference page.
 
diff --git a/xml/System.Globalization/IdnMapping.xml b/xml/System.Globalization/IdnMapping.xml
index 7aa2045e751..e9387b022c9 100644
--- a/xml/System.Globalization/IdnMapping.xml
+++ b/xml/System.Globalization/IdnMapping.xml
@@ -53,7 +53,7 @@
 > [!IMPORTANT]
 >  In the .NET Framework 4.5, the <xref:System.Globalization.IdnMapping> class supports different versions of the IDNA standard, depending on the operating system in use:  
 >   
-> - When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).
+> - When run on Windows 8, it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).
 > - When run on earlier versions of the Windows operating system, it supports the 2003 version of the standard outlined by [RFC 3490: Internationalizing Domain Names in Applications (IDNA)](https://go.microsoft.com/fwlink/?LinkId=158110).
 >   
 >  See [Unicode Technical Standard #46: IDNA Compatibility Processing](https://go.microsoft.com/fwlink/?LinkId=232459) for the differences in the way these standards handle particular sets of characters.  
@@ -164,7 +164,7 @@
  A registered domain name cannot contain unassigned code points. Consequently, the default value of the <xref:System.Globalization.IdnMapping.AllowUnassigned%2A> property is `false`. The IDNA specification permits unassigned code points only in queries for matching strings (that is, in domain name lookup). For more information about the use of unassigned code points in domain names, see [RFC 3454, "Preparation of Internationalized Strings (stringprep)"](https://go.microsoft.com/fwlink/?LinkId=231873) and [RFC 5891, "Internationalized Domain Names in Applications (IDNA): Protocol"](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
 > [!IMPORTANT]
->  If the <xref:System.Globalization.IdnMapping.AllowUnassigned%2A> property is `false`, the behavior associated with the property depends on the underlying operating system. On [!INCLUDE[win8](~/includes/win8-md.md)], the <xref:System.Globalization.IdnMapping> class conforms to IDNA 2008, which is based on the Unicode 6.0 standard. On previous versions of Windows, the <xref:System.Globalization.IdnMapping> class is based on IDNA 2003, which is based on Unicode 3.*x*. Some code points that were unassigned in IDNA 2003 have been assigned characters and are supported in IDNA 2008. For example, U+0221 was introduced in Unicode 4.0. On [!INCLUDE[win8](~/includes/win8-md.md)], it is encoded as "xn—6la". On previous versions of Windows, it throws an <xref:System.ArgumentException> exception.  
+>  If the <xref:System.Globalization.IdnMapping.AllowUnassigned%2A> property is `false`, the behavior associated with the property depends on the underlying operating system. On Windows 8, the <xref:System.Globalization.IdnMapping> class conforms to IDNA 2008, which is based on the Unicode 6.0 standard. On previous versions of Windows, the <xref:System.Globalization.IdnMapping> class is based on IDNA 2003, which is based on Unicode 3.*x*. Some code points that were unassigned in IDNA 2003 have been assigned characters and are supported in IDNA 2008. For example, U+0221 was introduced in Unicode 4.0. On Windows 8, it is encoded as "xn—6la". On previous versions of Windows, it throws an <xref:System.ArgumentException> exception.  
   
  ]]></format>
         </remarks>
@@ -303,7 +303,7 @@
         <block subset="none" type="usage">
           <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
--   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
+-   When run on Windows 8, it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
 -   When run on earlier versions of the Windows operating system, it supports the 2003 version of the standard outlined by [RFC 3490: Internationalizing Domain Names in Applications (IDNA)](https://go.microsoft.com/fwlink/?LinkId=158110).  
   
@@ -397,7 +397,7 @@
         <block subset="none" type="usage">
           <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
--   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
+-   When run on Windows 8, it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
 -   When run on earlier versions of the Windows operating system, it supports the 2003 version of the standard outlined by [RFC 3490: Internationalizing Domain Names in Applications (IDNA)](https://go.microsoft.com/fwlink/?LinkId=158110).  
   
@@ -495,7 +495,7 @@
         <block subset="none" type="usage">
           <para>In the .NET Framework 4.5, the <see cref="T:System.Globalization.IdnMapping" /> class supports different versions of the IDNA standard, depending on the operating system in use:  
   
--   When run on [!INCLUDE[win8](~/includes/win8-md.md)], it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
+-   When run on Windows 8, it supports the 2008 version of the IDNA standard outlined by [RFC 5891: Internationalized Domain Names in Applications (IDNA): Protocol](https://go.microsoft.com/fwlink/?LinkId=231875).  
   
 -   When run on earlier versions of the Windows operating system, it supports the 2003 version of the standard outlined by [RFC 3490: Internationalizing Domain Names in Applications (IDNA)](https://go.microsoft.com/fwlink/?LinkId=158110).  
   
diff --git a/xml/System.Globalization/SortVersion.xml b/xml/System.Globalization/SortVersion.xml
index 0d4bec4075c..1525eab9645 100644
--- a/xml/System.Globalization/SortVersion.xml
+++ b/xml/System.Globalization/SortVersion.xml
@@ -54,7 +54,7 @@
   
 -   On Windows 7 and previous versions of the Windows operating system, the tables continue to be used for comparing and ordering strings.  
   
--   On [!INCLUDE[win8](~/includes/win8-md.md)], the .NET Framework delegates string comparison and ordering operations to the operating system.  
+-   On Windows 8, the .NET Framework delegates string comparison and ordering operations to the operating system.  
   
  Consequently, the result of a string comparison can depend not only on the .NET Framework version, but also on the operating system version, as the following table shows. Note that this list of supported Unicode versions applies to character comparison and sorting only; it does not apply to classification of Unicode characters by category.  
   
@@ -62,9 +62,9 @@
 |----------------------------|----------------------|---------------------|  
 |.NET Framework 4|All operating systems|Unicode 5.0|  
 |.NET Framework 4.5 and later versions of the .NET Framework|Windows 7|Unicode 5.0|  
-|.NET Framework 4.5 and later versions of the .NET Framework|[!INCLUDE[win8](~/includes/win8-md.md)] and later Windows operating system versions|Unicode 6.0|  
+|.NET Framework 4.5 and later versions of the .NET Framework|Windows 8 and later Windows operating system versions|Unicode 6.0|  
   
- On [!INCLUDE[win8](~/includes/win8-md.md)], because the version of Unicode used in string comparison and ordering depends on the version of the operating system, the results of string comparison may differ even for applications that run on a specific version of the .NET Framework.  
+ On Windows 8, because the version of Unicode used in string comparison and ordering depends on the version of the operating system, the results of string comparison may differ even for applications that run on a specific version of the .NET Framework.  
 
 ### Sorting and string comparison in .NET Core
 
diff --git a/xml/System.IO.Compression/ZipArchiveEntry.xml b/xml/System.IO.Compression/ZipArchiveEntry.xml
index 9d0f88678e2..f80a2b6c88c 100644
--- a/xml/System.IO.Compression/ZipArchiveEntry.xml
+++ b/xml/System.IO.Compression/ZipArchiveEntry.xml
@@ -47,7 +47,7 @@
 |To open a stream to an individual file contained in a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Open%2A?displayProperty=nameWithType>|  
 |Delete a file from a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Delete%2A?displayProperty=nameWithType>|  
   
- If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in [!INCLUDE[win8](~/includes/win8-md.md)]. In Windows 8.x Store apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
+ If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in Windows 8. In Windows 8.x Store apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
   
    
   
diff --git a/xml/System.Resources/ResourceManager.xml b/xml/System.Resources/ResourceManager.xml
index e2a58ddd915..8a701c4f8c5 100644
--- a/xml/System.Resources/ResourceManager.xml
+++ b/xml/System.Resources/ResourceManager.xml
@@ -1843,7 +1843,7 @@ al /out:ru-RU\Showdate.resources.dll /culture:ru-RU /embed:DateStrings.ru-RU.res
 > [!IMPORTANT]
 >  Although the <xref:System.Resources.ResourceManager> class is supported in Windows 8.x Store apps, we do not recommend its use. Use this class only when you develop Portable Class Library projects that can be used with Windows 8.x Store apps. To retrieve resources from Windows 8.x Store apps, use the [Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class instead.
 
- In Windows 8.x Store apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method returns the value of the `name` string resource, localized for the culture specified by the `culture` parameter. If the resource is not localized for the `culture` culture, the lookup uses the entire [!INCLUDE[win8](~/includes/win8-md.md)] language fallback list, and stops after looking in the default culture. If the resource manager cannot match `name`, the method returns `null`.
+ In Windows 8.x Store apps, the <xref:System.Resources.ResourceManager.GetString%28System.String%2CSystem.Globalization.CultureInfo%29> method returns the value of the `name` string resource, localized for the culture specified by the `culture` parameter. If the resource is not localized for the `culture` culture, the lookup uses the entire Windows 8 language fallback list, and stops after looking in the default culture. If the resource manager cannot match `name`, the method returns `null`.
 
 
 
diff --git a/xml/System.Web.Configuration/CompilationSection.xml b/xml/System.Web.Configuration/CompilationSection.xml
index 0223cad6e0a..c3c344a17db 100644
--- a/xml/System.Web.Configuration/CompilationSection.xml
+++ b/xml/System.Web.Configuration/CompilationSection.xml
@@ -518,9 +518,9 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value that indicates whether an ASP.NET application can take advantage of [!INCLUDE[win8](~/includes/win8-md.md)] prefetch functionality.</summary>
+        <summary>Gets or sets a value that indicates whether an ASP.NET application can take advantage of Windows 8 prefetch functionality.</summary>
         <value>
-          <see langword="true" /> if an ASP.NET application can take advantage of [!INCLUDE[win8](~/includes/win8-md.md)] prefetch functionality; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
+          <see langword="true" /> if an ASP.NET application can take advantage of Windows 8 prefetch functionality; otherwise, <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
@@ -528,7 +528,7 @@
  Prefetch is a utility that is intended to improve application startup performance by loading application data into memory before it is demanded .  
   
 > [!NOTE]
->  The [!INCLUDE[win8](~/includes/win8-md.md)] prefetch service must be configured and running for this setting to be effective.  
+>  The Windows 8 prefetch service must be configured and running for this setting to be effective.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.Web.Configuration/MachineKeyCompatibilityMode.xml b/xml/System.Web.Configuration/MachineKeyCompatibilityMode.xml
index d53e9cc679d..22aab22b680 100644
--- a/xml/System.Web.Configuration/MachineKeyCompatibilityMode.xml
+++ b/xml/System.Web.Configuration/MachineKeyCompatibilityMode.xml
@@ -84,7 +84,7 @@
       </ReturnValue>
       <MemberValue>2</MemberValue>
       <Docs>
-        <summary>Use encryption methods that are available in .NET Framework version 4.5 and later versions. Compared to the encryption methods that are used for <see cref="F:System.Web.Configuration.MachineKeyCompatibilityMode.Framework20SP1" /> and <see cref="F:System.Web.Configuration.MachineKeyCompatibilityMode.Framework20SP2" />, the ciphertext that is generated by the default cryptographic routines is slightly smaller and is more resilient against certain classes of theoretical attacks. They also integrate with [!INCLUDE[win8](~/includes/win8-md.md)] directory key management in order to get required cryptographic keys. This option also enables you to specify custom cryptographic routines by writing a class that derives from <see cref="T:System.Security.Cryptography.DataProtector" /> and specifying the class name in the <see cref="P:System.Web.Configuration.MachineKeySection.DataProtectorType" /> property.  
+        <summary>Use encryption methods that are available in .NET Framework version 4.5 and later versions. Compared to the encryption methods that are used for <see cref="F:System.Web.Configuration.MachineKeyCompatibilityMode.Framework20SP1" /> and <see cref="F:System.Web.Configuration.MachineKeyCompatibilityMode.Framework20SP2" />, the ciphertext that is generated by the default cryptographic routines is slightly smaller and is more resilient against certain classes of theoretical attacks. They also integrate with Windows 8 directory key management in order to get required cryptographic keys. This option also enables you to specify custom cryptographic routines by writing a class that derives from <see cref="T:System.Security.Cryptography.DataProtector" /> and specifying the class name in the <see cref="P:System.Web.Configuration.MachineKeySection.DataProtectorType" /> property.  
   
  The following configuration requirements apply to this option:  
   
diff --git a/xml/System/Exception.xml b/xml/System/Exception.xml
index 7543484a26f..d75c2a3bd37 100644
--- a/xml/System/Exception.xml
+++ b/xml/System/Exception.xml
@@ -291,7 +291,7 @@ Stack Trace:
  [!code-vb[System.Exception.Class#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.exception.class/vb/example.vb#3)]  
   
 ## Windows Runtime and .NET Framework 4.5.1  
- In .NET for Windows 8.x Store apps for [!INCLUDE[win8](~/includes/win8-md.md)], some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
+ In .NET for Windows 8.x Store apps for Windows 8, some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
   
    
   
diff --git a/xml/ns-System.Net.Http.xml b/xml/ns-System.Net.Http.xml
index af320a8cbc4..d44819b20cd 100644
--- a/xml/ns-System.Net.Http.xml
+++ b/xml/ns-System.Net.Http.xml
@@ -49,7 +49,7 @@
 
  If an app using the <xref:System.Net.Http> and <xref:System.Net.Http.Headers> namespaces intends to download large amounts of data (50 megabytes or more), then the app should stream those downloads and not use the default buffering. If the default buffering is used the client memory usage will get very large, potentially resulting in substantially reduced performance.
 
- Classes in the <xref:System.Net.Http> and <xref:System.Net.Http.Headers> namespaces can be used to develop Windows Store apps or desktop apps. When used in a Windows Store app, classes in the <xref:System.Net.Http> and <xref:System.Net.Http.Headers> namespaces are affected by network isolation feature, part of the application security model used by the [!INCLUDE[win8](~/includes/win8-md.md)]. The appropriate network capabilities must be enabled in the app manifest for a Windows Store app for the system to allow network access by a Windows store app. For more information, see the [Network Isolation for Windows Store Apps](/dotnet/framework/network-programming/network-isolation-for-windows-store-apps).
+ Classes in the <xref:System.Net.Http> and <xref:System.Net.Http.Headers> namespaces can be used to develop Windows Store apps or desktop apps. When used in a Windows Store app, classes in the <xref:System.Net.Http> and <xref:System.Net.Http.Headers> namespaces are affected by network isolation feature, part of the application security model used by the Windows 8. The appropriate network capabilities must be enabled in the app manifest for a Windows Store app for the system to allow network access by a Windows store app. For more information, see the [Network Isolation for Windows Store Apps](/dotnet/framework/network-programming/network-isolation-for-windows-store-apps).
 
  ]]></format>
     </remarks>

From 85cc83f86ae3015f44e7a860f99ee7eea51b0da0 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:45:23 -0800
Subject: [PATCH 217/236] win81

---
 xml/System.Diagnostics/ProcessModule.xml                      | 2 +-
 xml/System.Security.Cryptography/RSACryptoServiceProvider.xml | 4 ++--
 xml/System/Exception.xml                                      | 4 ++--
 xml/System/Object.xml                                         | 2 +-
 4 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Diagnostics/ProcessModule.xml b/xml/System.Diagnostics/ProcessModule.xml
index 019e5f057f2..e68be4aac27 100644
--- a/xml/System.Diagnostics/ProcessModule.xml
+++ b/xml/System.Diagnostics/ProcessModule.xml
@@ -189,7 +189,7 @@
  The module's entry point is the location of the function that is called during process startup, thread startup, process shutdown, and thread shutdown. While the entry point is not the address of the DllMain function, it should be close enough for most purposes.  
   
 > [!NOTE]
->  Due to changes in the way that Windows loads assemblies, <xref:System.Diagnostics.ProcessModule.EntryPointAddress%2A> will always return 0 on Windows 8 or [!INCLUDE[win81](~/includes/win81-md.md)] and should not be relied on for those platforms.  
+>  Due to changes in the way that Windows loads assemblies, <xref:System.Diagnostics.ProcessModule.EntryPointAddress%2A> will always return 0 on Windows 8 or Windows 8.1 and should not be relied on for those platforms.  
   
    
   
diff --git a/xml/System.Security.Cryptography/RSACryptoServiceProvider.xml b/xml/System.Security.Cryptography/RSACryptoServiceProvider.xml
index 6187891e277..32ef58810ef 100644
--- a/xml/System.Security.Cryptography/RSACryptoServiceProvider.xml
+++ b/xml/System.Security.Cryptography/RSACryptoServiceProvider.xml
@@ -58,7 +58,7 @@
   
  The <xref:System.Security.Cryptography.RSACryptoServiceProvider> supports key sizes from 384 bits to 16384 bits in increments of 8 bits if you have the Microsoft Enhanced Cryptographic Provider installed.  It supports key sizes from 384 bits to 512 bits in increments of 8 bits if you have the Microsoft Base Cryptographic Provider installed.  
   
- Valid key sizes are dependent on the cryptographic service provider (CSP) that is used by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> instance. Windows CSPs enable keys sizes of 384 to 16384 bits for Windows versions prior to [!INCLUDE[win81](~/includes/win81-md.md)], and key sizes of 512 to 16384 bits for [!INCLUDE[win81](~/includes/win81-md.md)]. For more information, see [CryptGenKey](/windows/win32/api/wincrypt/nf-wincrypt-cryptgenkey) function in the Windows documentation.  
+ Valid key sizes are dependent on the cryptographic service provider (CSP) that is used by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> instance. Windows CSPs enable keys sizes of 384 to 16384 bits for Windows versions prior to Windows 8.1, and key sizes of 512 to 16384 bits for Windows 8.1. For more information, see [CryptGenKey](/windows/win32/api/wincrypt/nf-wincrypt-cryptgenkey) function in the Windows documentation.  
   
 ## Interoperation with the Microsoft Cryptographic API (CAPI)  
  Unlike the RSA implementation in unmanaged CAPI, the <xref:System.Security.Cryptography.RSACryptoServiceProvider> class reverses the order of an encrypted array of bytes after encryption and before decryption.  By default, data encrypted by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> class cannot be decrypted by the CAPI `CryptDecrypt` function and data encrypted by the CAPI `CryptEncrypt` method cannot be decrypted by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> class.  
@@ -1337,7 +1337,7 @@ If no key is loaded via the <xref:System.Security.Cryptography.RSACryptoServiceP
 ## Remarks  
  The <xref:System.Security.Cryptography.RSACryptoServiceProvider> supports key sizes from 384 bits to 16384 bits in increments of 8 bits if you have the Microsoft Enhanced Cryptographic Provider installed.  It supports key sizes from 384 bits to 512 bits in increments of 8 bits if you have the Microsoft Base Cryptographic Provider installed.  
   
- Valid key sizes are dependent on the cryptographic service provider (CSP) that is used by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> instance. Windows CSPs enable key sizes of 384 to 16384 bits for Windows versions prior to [!INCLUDE[win81](~/includes/win81-md.md)], and key sizes of 512 to 16384 bits for [!INCLUDE[win81](~/includes/win81-md.md)]. For more information, see [CryptGenKey](/windows/win32/api/wincrypt/nf-wincrypt-cryptgenkey) function in the Windows documentation.  
+ Valid key sizes are dependent on the cryptographic service provider (CSP) that is used by the <xref:System.Security.Cryptography.RSACryptoServiceProvider> instance. Windows CSPs enable key sizes of 384 to 16384 bits for Windows versions prior to Windows 8.1, and key sizes of 512 to 16384 bits for Windows 8.1. For more information, see [CryptGenKey](/windows/win32/api/wincrypt/nf-wincrypt-cryptgenkey) function in the Windows documentation.  
   
  The <xref:System.Security.Cryptography.RSACryptoServiceProvider> class does not allow you to change key sizes using the <xref:System.Security.Cryptography.RSACryptoServiceProvider.KeySize%2A> property.  Any value written to this property will fail to update the property without error.  To change the key size, use one of the constructor overloads.  
   
diff --git a/xml/System/Exception.xml b/xml/System/Exception.xml
index d75c2a3bd37..8efc9b0adbc 100644
--- a/xml/System/Exception.xml
+++ b/xml/System/Exception.xml
@@ -291,7 +291,7 @@ Stack Trace:
  [!code-vb[System.Exception.Class#3](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.exception.class/vb/example.vb#3)]  
   
 ## Windows Runtime and .NET Framework 4.5.1  
- In .NET for Windows 8.x Store apps for Windows 8, some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
+ In .NET for Windows 8.x Store apps for Windows 8, some exception information is typically lost when an exception is propagated through non-.NET Framework stack frames. Starting with the .NET Framework 4.5.1 and Windows 8.1, the common language runtime continues to use the original <xref:System.Exception> object that was thrown unless that exception was modified in a non-.NET Framework stack frame.  
   
    
   
@@ -1097,7 +1097,7 @@ Stack Trace:
  The value of the <xref:System.Exception.Message%2A> property is included in the information returned by <xref:System.Exception.ToString%2A>. The <xref:System.Exception.Message%2A> property is set only when creating an <xref:System.Exception>. If no message was supplied to the constructor for the current instance, the system supplies a default message that is formatted using the current system culture.  
   
 ## Windows Runtime and .NET Framework 4.5.1  
- Starting with the .NET Framework 4.5.1 and [!INCLUDE[win81](~/includes/win81-md.md)], the fidelity of error messages from exceptions that are propagated from Windows Runtime types and members that are not part of the .NET Framework is improved. In particular, exception messages from Visual C++ component extensions (C++/CX) are now propagated back into .NET Framework <xref:System.Exception> objects.  
+ Starting with the .NET Framework 4.5.1 and Windows 8.1, the fidelity of error messages from exceptions that are propagated from Windows Runtime types and members that are not part of the .NET Framework is improved. In particular, exception messages from Visual C++ component extensions (C++/CX) are now propagated back into .NET Framework <xref:System.Exception> objects.  
   
    
   
diff --git a/xml/System/Object.xml b/xml/System/Object.xml
index bbbbffd4d82..63ed66ffae4 100644
--- a/xml/System/Object.xml
+++ b/xml/System/Object.xml
@@ -1136,7 +1136,7 @@ and the <xref:System.IDisposable> interface. The <xref:System.IDisposable.Dispos
 > [!INCLUDE[wrt](~/includes/wrt-md.md)] classes that are written in C# or Visual Basic can override the <xref:System.Object.ToString%2A> method.  
   
 ### The [!INCLUDE[wrt](~/includes/wrt-md.md)] and the IStringable Interface  
- Starting with [!INCLUDE[win81](~/includes/win81-md.md)], the [!INCLUDE[wrt](~/includes/wrt-md.md)] includes an [IStringable](xref:Windows.Foundation.IStringable) interface whose single method, [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString), provides basic formatting support comparable to that provided by <xref:System.Object.ToString%2A?displayProperty=nameWithType>. To prevent ambiguity, you should not implement [IStringable](xref:Windows.Foundation.IStringable) on managed types.  
+ Starting with Windows 8.1, the [!INCLUDE[wrt](~/includes/wrt-md.md)] includes an [IStringable](xref:Windows.Foundation.IStringable) interface whose single method, [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString), provides basic formatting support comparable to that provided by <xref:System.Object.ToString%2A?displayProperty=nameWithType>. To prevent ambiguity, you should not implement [IStringable](xref:Windows.Foundation.IStringable) on managed types.  
   
  When managed objects are called by native code or by code written in languages such as JavaScript or C++/CX, they appear to implement [IStringable](xref:Windows.Foundation.IStringable). The common language runtime automatically routes calls from [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) to <xref:System.Object.ToString%2A?displayProperty=nameWithType> if [IStringable](xref:Windows.Foundation.IStringable) is not implemented on the managed object.  
   

From bafa0548f1113f30ac6f2f4d8b5ed34c65afd3ff Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:47:52 -0800
Subject: [PATCH 218/236] wince

---
 xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml b/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
index d448a221b28..e812a08ea47 100644
--- a/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
+++ b/xml/System.Runtime.InteropServices.ComTypes/CALLCONV.xml
@@ -62,7 +62,7 @@
   
 -   CC_SYSCALL is similar to CDECL in that arguments are pushed from right to left. The EAX, ECX, and EDX registers are not preserved.  
   
- These calling convention identifiers are used by the .NET Framework, the [!INCLUDE[wince](~/includes/wince-md.md)] platform, and by Automation.  
+ These calling convention identifiers are used by the .NET Framework, the Windows Embedded CE platform, and by Automation.  
  
  The common language runtime throws an exception when a COM method in native code returns an HRESULT. For more information, see [How to: Map HRESULTs and Exceptions](/dotnet/framework/interop/how-to-map-hresults-and-exceptions).  
   

From 2aca2bb56322838350a3794deca7d0e233139f1f Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:49:10 -0800
Subject: [PATCH 219/236] windowsver

---
 xml/Microsoft.Win32/SystemEvents.xml         | 2 +-
 xml/System.Windows.Forms/PageSetupDialog.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/Microsoft.Win32/SystemEvents.xml b/xml/Microsoft.Win32/SystemEvents.xml
index 71ae1f9c2d3..059babcae59 100644
--- a/xml/Microsoft.Win32/SystemEvents.xml
+++ b/xml/Microsoft.Win32/SystemEvents.xml
@@ -36,7 +36,7 @@
 >  Do not perform time-consuming processing on the thread that raises a system event handler because it might prevent other applications from functioning.  
   
 > [!NOTE]
->  Some system events might not be raised on [!INCLUDE[windowsver](~/includes/windowsver-md.md)]. Be sure to verify that your application works as expected on [!INCLUDE[windowsver](~/includes/windowsver-md.md)].  
+>  Some system events might not be raised on Windows Vista. Be sure to verify that your application works as expected on Windows Vista.  
   
    
   
diff --git a/xml/System.Windows.Forms/PageSetupDialog.xml b/xml/System.Windows.Forms/PageSetupDialog.xml
index c4c02c30c59..d9d77865def 100644
--- a/xml/System.Windows.Forms/PageSetupDialog.xml
+++ b/xml/System.Windows.Forms/PageSetupDialog.xml
@@ -267,7 +267,7 @@
 ## Remarks  
   
 > [!NOTE]
->  Setting this property to `true` has no effect if the application is running on [!INCLUDE[windowsver](~/includes/windowsver-md.md)]. The **Printer** button will not be shown.  
+>  Setting this property to `true` has no effect if the application is running on Windows Vista. The **Printer** button will not be shown.  
   
  ]]></format>
         </remarks>

From 36a88ca497f61a1ab352fa51f5e487256c003593 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:49:39 -0800
Subject: [PATCH 220/236] winnt4family

---
 xml/System.DirectoryServices/DirectoryEntry.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xml/System.DirectoryServices/DirectoryEntry.xml b/xml/System.DirectoryServices/DirectoryEntry.xml
index 83d1a385557..c0330c54dcd 100644
--- a/xml/System.DirectoryServices/DirectoryEntry.xml
+++ b/xml/System.DirectoryServices/DirectoryEntry.xml
@@ -1621,7 +1621,7 @@ DirectoryEntry domain = new DirectoryEntry("LDAP://" + str);
 ## Remarks  
  If the property is not initialized, <xref:System.DirectoryServices.DirectoryEntry.Properties%2A> calls the ADSI interface [IADs::Get](/windows/win32/api/iads/nf-iads-iads-get) method to retrieve the value from the cache. If the underling cache has not been loaded, [IADs::Get](/windows/win32/api/iads/nf-iads-iads-get) implicitly calls [IADs::GetInfo](/windows/win32/api/iads/nf-iads-iads-getinfo). This method loads the values of the supported properties that have not been set in the cache from the underlying directory store. Subsequent calls to <xref:System.DirectoryServices.DirectoryEntry.Properties%2A> retrieves the property values in the cache only. To control property cache loading, call <xref:System.DirectoryServices.DirectoryEntry.RefreshCache%2A>.  
   
- **Note** The <xref:System.DirectoryServices.DirectoryEntry.Properties%2A> property is not supported for use with the Active Directory Client Extension (DSClient) for [!INCLUDE[WinNt4Family](~/includes/winnt4family-md.md)].  
+ **Note** The <xref:System.DirectoryServices.DirectoryEntry.Properties%2A> property is not supported for use with the Active Directory Client Extension (DSClient) for Windows NT 4.0.  
   
  ]]></format>
         </remarks>

From 4051219f3687219d6a1766c79d2754fae5c81da1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:50:17 -0800
Subject: [PATCH 221/236] winxp

---
 xml/System.Net.Security/SslStream.xml                  |  2 +-
 xml/System.Windows.Forms/FileDialog.xml                |  6 +++---
 xml/System.Windows.Forms/FileDialogCustomPlace.xml     |  2 +-
 .../FileDialogCustomPlacesCollection.xml               |  2 +-
 xml/System/DateTime.xml                                | 10 +++++-----
 5 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/xml/System.Net.Security/SslStream.xml b/xml/System.Net.Security/SslStream.xml
index cb96ba4eaac..d85ac9e196e 100644
--- a/xml/System.Net.Security/SslStream.xml
+++ b/xml/System.Net.Security/SslStream.xml
@@ -2584,7 +2584,7 @@
 ## Remarks  
  A value of <xref:System.Security.Authentication.CipherAlgorithmType.Null> is required for the <xref:System.Net.Security.SslStream.CipherAlgorithm%2A> property when the <xref:System.Net.Security.EncryptionPolicy.NoEncryption> enumeration value is used to construct a <xref:System.Net.Security.SslStream> instance.  
   
- [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)] and [!INCLUDE[winxp](~/includes/winxp-md.md)] do not support the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value. So even if the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is used to construct the <xref:System.Net.Security.SslStream> instance, the <xref:System.Net.Security.EncryptionPolicy> property will be <xref:System.Security.Authentication.CipherAlgorithmType.None>. The <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is only returned on Windows Vista and later.  
+ [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)] and Windows XP do not support the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value. So even if the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is used to construct the <xref:System.Net.Security.SslStream> instance, the <xref:System.Net.Security.EncryptionPolicy> property will be <xref:System.Security.Authentication.CipherAlgorithmType.None>. The <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is only returned on Windows Vista and later.  
   
    
   
diff --git a/xml/System.Windows.Forms/FileDialog.xml b/xml/System.Windows.Forms/FileDialog.xml
index 2be4c196fa6..a3fc63d0978 100644
--- a/xml/System.Windows.Forms/FileDialog.xml
+++ b/xml/System.Windows.Forms/FileDialog.xml
@@ -170,9 +170,9 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this property is `false`, the <xref:System.Windows.Forms.FileDialog> class will have a [!INCLUDE[winxp](~/includes/winxp-md.md)]-style appearance and behavior on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)].  
+ If this property is `false`, the <xref:System.Windows.Forms.FileDialog> class will have a Windows XP-style appearance and behavior on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)].  
   
- On [!INCLUDE[winxp](~/includes/winxp-md.md)], this property does not have any effect.  
+ On Windows XP, this property does not have any effect.  
   
  ]]></format>
         </remarks>
@@ -335,7 +335,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- On [!INCLUDE[winxp](~/includes/winxp-md.md)], this property does not have any effect.  
+ On Windows XP, this property does not have any effect.  
   
    
   
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlace.xml b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
index e2309d079cb..569f500d5e7 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlace.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
@@ -29,7 +29,7 @@
 ## Remarks  
  The default open and save dialog boxes on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] have an area on the left side of the dialog box titled **Favorite Links**. This area is called custom places. This class represents a custom place.  
   
- On [!INCLUDE[winxp](~/includes/winxp-md.md)] or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
+ On Windows XP or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
index 2beac70b091..bebd16e4aef 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
@@ -30,7 +30,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- On [!INCLUDE[winxp](~/includes/winxp-md.md)] or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
+ On Windows XP or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
   
    
   
diff --git a/xml/System/DateTime.xml b/xml/System/DateTime.xml
index 7add75976c0..74cf1f1b88a 100644
--- a/xml/System/DateTime.xml
+++ b/xml/System/DateTime.xml
@@ -3885,7 +3885,7 @@ juillet 2009
   
  If the current <xref:System.DateTime> value represents either an ambiguous or an invalid time in the local time zone, the method returns `false`.  
   
- On [!INCLUDE[winxp](~/includes/winxp-md.md)] systems, the <xref:System.DateTime.IsDaylightSavingTime%2A> method recognizes only the current adjustment rule when determining whether the current instance is a daylight saving time. As a result, the method may not accurately report whether the current instance is a daylight saving time for periods before the current adjustment rule came into effect.  
+ On Windows XP systems, the <xref:System.DateTime.IsDaylightSavingTime%2A> method recognizes only the current adjustment rule when determining whether the current instance is a daylight saving time. As a result, the method may not accurately report whether the current instance is a daylight saving time for periods before the current adjustment rule came into effect.  
   
  ]]></format>
         </remarks>
@@ -7520,7 +7520,7 @@ In general, the ticks represent the time according to the time zone specified by
  The local time is equal to the Coordinated Universal Time (UTC) time plus the UTC offset. For more information about the UTC offset, see <xref:System.TimeZone.GetUtcOffset%2A?displayProperty=nameWithType>. The conversion also takes into account the daylight saving time rule that applies to the time represented by the current <xref:System.DateTime> object.  
   
 > [!IMPORTANT]
->  On [!INCLUDE[winxp](~/includes/winxp-md.md)] systems, the <xref:System.DateTime.ToLocalTime%2A> method recognizes only the current adjustment rule when converting from UTC to local time. As a result, conversions for periods before the current adjustment rule came into effect may not accurately reflect the difference between UTC and local time.  
+>  On Windows XP systems, the <xref:System.DateTime.ToLocalTime%2A> method recognizes only the current adjustment rule when converting from UTC to local time. As a result, conversions for periods before the current adjustment rule came into effect may not accurately reflect the difference between UTC and local time.  
   
  Starting with the .NET Framework version 2.0, the value returned by the <xref:System.DateTime.ToLocalTime%2A> method is determined by the <xref:System.DateTime.Kind%2A> property of the current <xref:System.DateTime> object. The following table describes the possible results.  
   
@@ -8326,7 +8326,7 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
  The Coordinated Universal Time (UTC) is equal to the local time minus the UTC offset. For more information about the UTC offset, see <xref:System.TimeZone.GetUtcOffset%2A?displayProperty=nameWithType>. The conversion also takes into account the daylight saving time rule that applies to the time represented by the current <xref:System.DateTime> object.  
   
 > [!IMPORTANT]
->  On [!INCLUDE[winxp](~/includes/winxp-md.md)] systems, the <xref:System.DateTime.ToUniversalTime%2A> method recognizes only the current adjustment rule when converting from local time to UTC. As a result, conversions for periods before the current adjustment rule came into effect may not accurately reflect the difference between local time and UTC.  
+>  On Windows XP systems, the <xref:System.DateTime.ToUniversalTime%2A> method recognizes only the current adjustment rule when converting from local time to UTC. As a result, conversions for periods before the current adjustment rule came into effect may not accurately reflect the difference between local time and UTC.  
   
  Starting with the .NET Framework version 2.0, the value returned by the <xref:System.DateTime.ToUniversalTime%2A> method is determined by the <xref:System.DateTime.Kind%2A> property of the current <xref:System.DateTime> object. The following table describes the possible results.  
   
@@ -8360,9 +8360,9 @@ The value of the current <xref:System.DateTime> object is formatted using the pa
         <block subset="none" type="usage">
           <para>The <see cref="M:System.DateTime.ToUniversalTime" /> method is sometimes used to convert a local time to UTC. The <see cref="M:System.DateTime.ToLocalTime" /> method is then called to restore the original local time. However, if the original time represents an invalid time in the local time zone, the two local time values will not be equal. For additional information and an example, see the <see cref="M:System.DateTime.ToLocalTime" /> method.  
   
- On [!INCLUDE[winxp](~/includes/winxp-md.md)] systems, the <see cref="M:System.DateTime.ToUniversalTime" /> method recognizes only the current adjustment rule for the local time zone, which it applies to all dates, including down-level dates (that is, dates that are earlier than the starting date of the current adjustment rule). Applications running on [!INCLUDE[winxp](~/includes/winxp-md.md)] that require historically accurate local date and time calculations must work around this behavior by using the <see cref="M:System.TimeZoneInfo.FindSystemTimeZoneById(System.String)" /> method to retrieve a <see cref="T:System.TimeZoneInfo" /> object that corresponds to the local time zone and calling its <see cref="M:System.TimeZoneInfo.ConvertTimeToUtc(System.DateTime,System.TimeZoneInfo)" /> method.  
+ On Windows XP systems, the <see cref="M:System.DateTime.ToUniversalTime" /> method recognizes only the current adjustment rule for the local time zone, which it applies to all dates, including down-level dates (that is, dates that are earlier than the starting date of the current adjustment rule). Applications running on Windows XP that require historically accurate local date and time calculations must work around this behavior by using the <see cref="M:System.TimeZoneInfo.FindSystemTimeZoneById(System.String)" /> method to retrieve a <see cref="T:System.TimeZoneInfo" /> object that corresponds to the local time zone and calling its <see cref="M:System.TimeZoneInfo.ConvertTimeToUtc(System.DateTime,System.TimeZoneInfo)" /> method.  
   
- The following example illustrates the difference between the <see cref="M:System.DateTime.ToUniversalTime" /> and <see cref="M:System.TimeZoneInfo.ConvertTimeToUtc(System.DateTime,System.TimeZoneInfo)" /> methods on a [!INCLUDE[winxp](~/includes/winxp-md.md)] system in the U.S. Pacific Time zone. The first two method calls apply the current time zone adjustment rule (which went into effect in 2007) to a date in 2006. The current adjustment rule provides for the transition to daylight saving time on the second Sunday of March; the previous rule, which was in effect in 2006, provided for the transition to daylight saving time to occur on the first Sunday of April. Only the third method call accurately performs this historical date and time conversion.  
+ The following example illustrates the difference between the <see cref="M:System.DateTime.ToUniversalTime" /> and <see cref="M:System.TimeZoneInfo.ConvertTimeToUtc(System.DateTime,System.TimeZoneInfo)" /> methods on a Windows XP system in the U.S. Pacific Time zone. The first two method calls apply the current time zone adjustment rule (which went into effect in 2007) to a date in 2006. The current adjustment rule provides for the transition to daylight saving time on the second Sunday of March; the previous rule, which was in effect in 2006, provided for the transition to daylight saving time to occur on the first Sunday of April. Only the third method call accurately performs this historical date and time conversion.  
   
  [!code-csharp[System.DateTime.ToUniversalTime#1](~/samples/snippets/csharp/VS_Snippets_CLR_System/system.datetime.touniversaltime/cs/touniversaltime.cs#1)]
  [!code-vb[System.DateTime.ToUniversalTime#1](~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.datetime.touniversaltime/vb/touniversaltime.vb#1)]</para>

From ae6c071bb827489abf6b45aa1419830d518ac126 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:50:50 -0800
Subject: [PATCH 222/236] winxpsvr

---
 xml/System.DirectoryServices.ActiveDirectory/Forest.xml       | 2 +-
 xml/System.IdentityModel/RsaSignatureCookieTransform.xml      | 2 +-
 xml/System.Net.Security/SslStream.xml                         | 2 +-
 xml/System.Windows.Forms/FileDialogCustomPlace.xml            | 2 +-
 xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.DirectoryServices.ActiveDirectory/Forest.xml b/xml/System.DirectoryServices.ActiveDirectory/Forest.xml
index 5d6be0d87e2..ea0be894607 100644
--- a/xml/System.DirectoryServices.ActiveDirectory/Forest.xml
+++ b/xml/System.DirectoryServices.ActiveDirectory/Forest.xml
@@ -1225,7 +1225,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- By default, new external and forest trusts in [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)] Active Directory Domain Services enforce SID filtering.  SID filtering is used to prevent attacks from malicious users who might try to grant elevated user rights to another user account.  Enforcing SID filtering on forest trusts does not prevent migrations to domains within the same forest from using SID history and will not affect your universal group access control strategy.  
+ By default, new external and forest trusts in Windows Server 2003 Active Directory Domain Services enforce SID filtering.  SID filtering is used to prevent attacks from malicious users who might try to grant elevated user rights to another user account.  Enforcing SID filtering on forest trusts does not prevent migrations to domains within the same forest from using SID history and will not affect your universal group access control strategy.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.IdentityModel/RsaSignatureCookieTransform.xml b/xml/System.IdentityModel/RsaSignatureCookieTransform.xml
index 719ca03a9df..31858c1da6e 100644
--- a/xml/System.IdentityModel/RsaSignatureCookieTransform.xml
+++ b/xml/System.IdentityModel/RsaSignatureCookieTransform.xml
@@ -216,7 +216,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- SHA256 is the default algorithm. This may require a minimum operating system of [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)] and .NET 3.5 SP1.  
+ SHA256 is the default algorithm. This may require a minimum operating system of Windows Server 2003 and .NET 3.5 SP1.  
   
  If SHA256 is not supported, set the <xref:System.IdentityModel.RsaSignatureCookieTransform.HashName%2A> property to "SHA1".  
 
diff --git a/xml/System.Net.Security/SslStream.xml b/xml/System.Net.Security/SslStream.xml
index d85ac9e196e..8c0260c27f7 100644
--- a/xml/System.Net.Security/SslStream.xml
+++ b/xml/System.Net.Security/SslStream.xml
@@ -2584,7 +2584,7 @@
 ## Remarks  
  A value of <xref:System.Security.Authentication.CipherAlgorithmType.Null> is required for the <xref:System.Net.Security.SslStream.CipherAlgorithm%2A> property when the <xref:System.Net.Security.EncryptionPolicy.NoEncryption> enumeration value is used to construct a <xref:System.Net.Security.SslStream> instance.  
   
- [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)] and Windows XP do not support the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value. So even if the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is used to construct the <xref:System.Net.Security.SslStream> instance, the <xref:System.Net.Security.EncryptionPolicy> property will be <xref:System.Security.Authentication.CipherAlgorithmType.None>. The <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is only returned on Windows Vista and later.  
+ Windows Server 2003 and Windows XP do not support the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value. So even if the <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is used to construct the <xref:System.Net.Security.SslStream> instance, the <xref:System.Net.Security.EncryptionPolicy> property will be <xref:System.Security.Authentication.CipherAlgorithmType.None>. The <xref:System.Security.Authentication.CipherAlgorithmType.Null> value is only returned on Windows Vista and later.  
   
    
   
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlace.xml b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
index 569f500d5e7..e0682513606 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlace.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
@@ -29,7 +29,7 @@
 ## Remarks  
  The default open and save dialog boxes on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] have an area on the left side of the dialog box titled **Favorite Links**. This area is called custom places. This class represents a custom place.  
   
- On Windows XP or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
+ On Windows XP or Windows Server 2003, this class does not have any effect.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
index bebd16e4aef..5301b130958 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
@@ -30,7 +30,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- On Windows XP or [!INCLUDE[winxpsvr](~/includes/winxpsvr-md.md)], this class does not have any effect.  
+ On Windows XP or Windows Server 2003, this class does not have any effect.  
   
    
   

From ed3e82827cb5ec56cb66d35a098c6cbf6338a08a Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:51:08 -0800
Subject: [PATCH 223/236] vinprlhext

---
 xml/System.Windows.Forms/FileDialog.xml            |  8 ++++----
 xml/System.Windows.Forms/FileDialogCustomPlace.xml | 14 +++++++-------
 .../FileDialogCustomPlacesCollection.xml           |  4 ++--
 3 files changed, 13 insertions(+), 13 deletions(-)

diff --git a/xml/System.Windows.Forms/FileDialog.xml b/xml/System.Windows.Forms/FileDialog.xml
index a3fc63d0978..bd9d09cf8bc 100644
--- a/xml/System.Windows.Forms/FileDialog.xml
+++ b/xml/System.Windows.Forms/FileDialog.xml
@@ -163,14 +163,14 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether this <see cref="T:System.Windows.Forms.FileDialog" /> instance should automatically upgrade appearance and behavior when running on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)].</summary>
+        <summary>Gets or sets a value indicating whether this <see cref="T:System.Windows.Forms.FileDialog" /> instance should automatically upgrade appearance and behavior when running on Windows Vista.</summary>
         <value>
-          <see langword="true" /> if this <see cref="T:System.Windows.Forms.FileDialog" /> instance should automatically upgrade appearance and behavior when running on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)]; otherwise, <see langword="false" />. The default is <see langword="true" />.</value>
+          <see langword="true" /> if this <see cref="T:System.Windows.Forms.FileDialog" /> instance should automatically upgrade appearance and behavior when running on Windows Vista; otherwise, <see langword="false" />. The default is <see langword="true" />.</value>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If this property is `false`, the <xref:System.Windows.Forms.FileDialog> class will have a Windows XP-style appearance and behavior on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)].  
+ If this property is `false`, the <xref:System.Windows.Forms.FileDialog> class will have a Windows XP-style appearance and behavior on Windows Vista.  
   
  On Windows XP, this property does not have any effect.  
   
@@ -808,7 +808,7 @@
   
  For more information about creating dynamic paths, see the <xref:System.Windows.Forms.FileDialog> class overview.  
   
- On [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)], if <xref:System.Windows.Forms.FileDialog.InitialDirectory%2A> is set to a full file name instead of just a directory path, the initial directory will default either to the application path, or to the directory from which the user last selected a file.  
+ On Windows Vista, if <xref:System.Windows.Forms.FileDialog.InitialDirectory%2A> is set to a full file name instead of just a directory path, the initial directory will default either to the application path, or to the directory from which the user last selected a file.  
   
    
   
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlace.xml b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
index e0682513606..c051a0076e3 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlace.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlace.xml
@@ -27,7 +27,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The default open and save dialog boxes on [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] have an area on the left side of the dialog box titled **Favorite Links**. This area is called custom places. This class represents a custom place.  
+ The default open and save dialog boxes on Windows Vista have an area on the left side of the dialog box titled **Favorite Links**. This area is called custom places. This class represents a custom place.  
   
  On Windows XP or Windows Server 2003, this class does not have any effect.  
   
@@ -69,13 +69,13 @@
         <Parameter Name="knownFolderGuid" Type="System.Guid" />
       </Parameters>
       <Docs>
-        <param name="knownFolderGuid">A <see cref="T:System.Guid" /> that represents a [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Windows.Forms.FileDialogCustomPlace" /> class with a custom place identified by a [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder GUID.</summary>
+        <param name="knownFolderGuid">A <see cref="T:System.Guid" /> that represents a Windows Vista Known Folder.</param>
+        <summary>Initializes a new instance of the <see cref="T:System.Windows.Forms.FileDialogCustomPlace" /> class with a custom place identified by a Windows Vista Known Folder GUID.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- For a list of the available [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.  
+ For a list of the available Windows Vista Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.  
   
    
   
@@ -145,8 +145,8 @@
         <ReturnType>System.Guid</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets the [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder GUID for the custom place.</summary>
-        <value>A <see cref="T:System.Guid" /> that indicates the [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder for the custom place. If the custom place was specified with a folder path, then an empty GUID is returned. For a list of the available [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.</value>
+        <summary>Gets or sets the Windows Vista Known Folder GUID for the custom place.</summary>
+        <value>A <see cref="T:System.Guid" /> that indicates the Windows Vista Known Folder for the custom place. If the custom place was specified with a folder path, then an empty GUID is returned. For a list of the available Windows Vista Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.</value>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Forms.FileDialog.CustomPlaces" />
       </Docs>
@@ -173,7 +173,7 @@
       </ReturnValue>
       <Docs>
         <summary>Gets or sets the folder path to the custom place.</summary>
-        <value>A folder path to the custom place. If the custom place was specified with a [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder GUID, then an empty string is returned.</value>
+        <value>A folder path to the custom place. If the custom place was specified with a Windows Vista Known Folder GUID, then an empty string is returned.</value>
         <remarks>To be added.</remarks>
         <altmember cref="P:System.Windows.Forms.FileDialog.CustomPlaces" />
       </Docs>
diff --git a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
index 5301b130958..f13f6247699 100644
--- a/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
+++ b/xml/System.Windows.Forms/FileDialogCustomPlacesCollection.xml
@@ -108,7 +108,7 @@
         <Parameter Name="knownFolderGuid" Type="System.Guid" />
       </Parameters>
       <Docs>
-        <param name="knownFolderGuid">A <see cref="T:System.Guid" /> that represents a [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folder.</param>
+        <param name="knownFolderGuid">A <see cref="T:System.Guid" /> that represents a Windows Vista Known Folder.</param>
         <summary>Adds a custom place to the <see cref="T:System.Windows.Forms.FileDialogCustomPlacesCollection" /> collection.</summary>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -116,7 +116,7 @@
 ## Remarks  
  The folder is added to custom places only for a particular <xref:System.Windows.Forms.FileDialog> and is not a system or application wide change.  
   
- The folders are positioned in the custom places in the order that they are added to the <xref:System.Windows.Forms.FileDialog>. The last one added will be at the top. If you add a custom place to the collection that does not exist on the computer running the application, the custom place will not be shown. GUIDs are case-insensitive. For a list of the available [!INCLUDE[wiprlhext](~/includes/wiprlhext-md.md)] Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.  
+ The folders are positioned in the custom places in the order that they are added to the <xref:System.Windows.Forms.FileDialog>. The last one added will be at the top. If you add a custom place to the collection that does not exist on the computer running the application, the custom place will not be shown. GUIDs are case-insensitive. For a list of the available Windows Vista Known Folders, see [Known Folder GUIDs for File Dialog Custom Places](/dotnet/framework/winforms/controls/known-folder-guids-for-file-dialog-custom-places) or the KnownFolders.h file in the Windows SDK.  
   
    
   

From e5a8329666cc48c8093565407254cc2dde530f31 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:52:03 -0800
Subject: [PATCH 224/236] wpfdesigner-current-long

---
 xml/System.Windows.Controls/DataGrid.xml  | 2 +-
 xml/System.Windows/DependencyProperty.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/xml/System.Windows.Controls/DataGrid.xml b/xml/System.Windows.Controls/DataGrid.xml
index f2e469a43e6..04030249b0d 100644
--- a/xml/System.Windows.Controls/DataGrid.xml
+++ b/xml/System.Windows.Controls/DataGrid.xml
@@ -111,7 +111,7 @@
    
   
 ## Examples  
- The following example shows how to bind a <xref:System.Windows.Controls.DataGrid> to a <xref:System.Data.DataTable> and use column auto-generation. The <xref:System.Data.DataTable> is populated by using the <xref:System.Data.Common.DataAdapter.Fill%2A> method of a <xref:System.Data.Common.DataAdapter> from a <xref:System.Data.DataSet>. For more information, see [Creating a DataSet](/dotnet/framework/data/adonet/dataset-datatable-dataview/creating-a-dataset) and [Populating a DataSet from a DataAdapter](/dotnet/framework/data/adonet/populating-a-dataset-from-a-dataadapter). To use the [!INCLUDE[wpfdesigner_current_long](~/includes/wpfdesigner-current-long-md.md)], see [Bind WPF controls to data in Visual Studio](/visualstudio/data-tools/bind-wpf-controls-to-data-in-visual-studio).  
+ The following example shows how to bind a <xref:System.Windows.Controls.DataGrid> to a <xref:System.Data.DataTable> and use column auto-generation. The <xref:System.Data.DataTable> is populated by using the <xref:System.Data.Common.DataAdapter.Fill%2A> method of a <xref:System.Data.Common.DataAdapter> from a <xref:System.Data.DataSet>. For more information, see [Creating a DataSet](/dotnet/framework/data/adonet/dataset-datatable-dataview/creating-a-dataset) and [Populating a DataSet from a DataAdapter](/dotnet/framework/data/adonet/populating-a-dataset-from-a-dataadapter). To use the WPF Designer for Visual Studio, see [Bind WPF controls to data in Visual Studio](/visualstudio/data-tools/bind-wpf-controls-to-data-in-visual-studio).  
   
  [!code-xaml[DataGrid1#1](~/samples/snippets/csharp/VS_Snippets_Wpf/datagrid1/csharp/window1.xaml#1)]  
   
diff --git a/xml/System.Windows/DependencyProperty.xml b/xml/System.Windows/DependencyProperty.xml
index d7ac1b68337..861365b0cf9 100644
--- a/xml/System.Windows/DependencyProperty.xml
+++ b/xml/System.Windows/DependencyProperty.xml
@@ -51,7 +51,7 @@
   
 -   The property reports information to WPF, such as whether changing a property value should require the layout system to recompose the visuals for an element.  
   
--   The property receives support in the [!INCLUDE[wpfdesigner_current_long](~/includes/wpfdesigner-current-long-md.md)].  For example, the property can be edited in the **Properties** window.  
+-   The property receives support in the WPF Designer for Visual Studio.  For example, the property can be edited in the **Properties** window.  
   
  To learn more about dependency properties, see [Dependency Properties Overview](/dotnet/framework/wpf/advanced/dependency-properties-overview). If you want properties on your custom types to support the capabilities in the preceding list, you should create a dependency property.  To learn how to create custom dependency properties, see [Custom Dependency Properties](/dotnet/framework/wpf/advanced/custom-dependency-properties).  
   

From d49706270f3a25084c66b6441e944454b0d06bbc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:52:28 -0800
Subject: [PATCH 225/236] wrt

---
 xml/System.IO.Compression/ZipArchive.xml      |  2 +-
 xml/System.IO.Compression/ZipArchiveEntry.xml |  2 +-
 .../IsolatedStorage.xml                       |  2 +-
 .../IsolatedStorageFile.xml                   |  2 +-
 .../IsolatedStorageFileStream.xml             |  2 +-
 xml/System.IO/Stream.xml                      |  2 +-
 xml/System.Reflection/AssemblyContentType.xml |  2 +-
 xml/System.Reflection/TypeAttributes.xml      |  2 +-
 .../NeutralResourcesLanguageAttribute.xml     |  2 +-
 .../WindowsRuntimeDesignerContext.xml         |  2 +-
 .../DefaultInterfaceAttribute.xml             |  4 +--
 .../EventRegistrationToken.xml                |  2 +-
 .../IActivationFactory.xml                    |  4 +--
 .../ReadOnlyArrayAttribute.xml                |  4 +--
 .../ReturnValueNameAttribute.xml              |  4 +--
 .../WindowsRuntimeMarshal.xml                 | 32 +++++++++----------
 .../WindowsRuntimeMetadata.xml                |  6 ++--
 .../WriteOnlyArrayAttribute.xml               |  4 +--
 .../ComInterfaceType.xml                      |  2 +-
 .../Marshal.xml                               | 16 +++++-----
 .../UnmanagedType.xml                         |  4 +--
 xml/System/Object.xml                         | 28 ++++++++--------
 xml/System/ValueType.xml                      | 10 +++---
 23 files changed, 70 insertions(+), 70 deletions(-)

diff --git a/xml/System.IO.Compression/ZipArchive.xml b/xml/System.IO.Compression/ZipArchive.xml
index 8eca8c73489..db35ee15069 100644
--- a/xml/System.IO.Compression/ZipArchive.xml
+++ b/xml/System.IO.Compression/ZipArchive.xml
@@ -51,7 +51,7 @@
   
  When you create a new entry, the file is compressed and added to the zip package. The <xref:System.IO.Compression.ZipArchive.CreateEntry%2A> method enables you to specify a directory hierarchy when adding the entry. You include the relative path of the new entry within the zip package. For example, creating a new entry with a relative path of `AddedFolder\NewFile.txt` creates a compressed text file in a directory named AddedFolder.  
   
- If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access four extension methods (from the <xref:System.IO.Compression.ZipFileExtensions> class) for the <xref:System.IO.Compression.ZipArchive> class: <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String)>, <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String,System.IO.Compression.CompressionLevel)>, <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String)>, and <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String,System.Boolean)> (available in .NET Core 2.0 and later versions). These extension methods enable you to compress and decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available for Windows 8.x Store apps. In Windows 8.x Store apps, you can compress and decompress files by using the <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream> class, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkID=246357) and [Decompressor](https://go.microsoft.com/fwlink/p/?LinkID=246358).  
+ If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access four extension methods (from the <xref:System.IO.Compression.ZipFileExtensions> class) for the <xref:System.IO.Compression.ZipArchive> class: <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String)>, <xref:System.IO.Compression.ZipFileExtensions.CreateEntryFromFile(System.IO.Compression.ZipArchive,System.String,System.String,System.IO.Compression.CompressionLevel)>, <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String)>, and <xref:System.IO.Compression.ZipFileExtensions.ExtractToDirectory(System.IO.Compression.ZipArchive,System.String,System.Boolean)> (available in .NET Core 2.0 and later versions). These extension methods enable you to compress and decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available for Windows 8.x Store apps. In Windows 8.x Store apps, you can compress and decompress files by using the <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream> class, or you can use the Windows Runtime types [Compressor](https://go.microsoft.com/fwlink/p/?LinkID=246357) and [Decompressor](https://go.microsoft.com/fwlink/p/?LinkID=246358).  
   
    
   
diff --git a/xml/System.IO.Compression/ZipArchiveEntry.xml b/xml/System.IO.Compression/ZipArchiveEntry.xml
index f80a2b6c88c..280ba9fce57 100644
--- a/xml/System.IO.Compression/ZipArchiveEntry.xml
+++ b/xml/System.IO.Compression/ZipArchiveEntry.xml
@@ -47,7 +47,7 @@
 |To open a stream to an individual file contained in a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Open%2A?displayProperty=nameWithType>|  
 |Delete a file from a zip archive|<xref:System.IO.Compression.ZipArchiveEntry.Delete%2A?displayProperty=nameWithType>|  
   
- If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in Windows 8. In Windows 8.x Store apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the [!INCLUDE[wrt](~/includes/wrt-md.md)] types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
+ If you reference the `System.IO.Compression.FileSystem` assembly in your project, you can access two extension methods for the <xref:System.IO.Compression.ZipArchiveEntry> class. Those methods are <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%29> and <xref:System.IO.Compression.ZipFileExtensions.ExtractToFile%28System.IO.Compression.ZipArchiveEntry%2CSystem.String%2CSystem.Boolean%29>, and they enable you to decompress the contents of the entry to a file. The `System.IO.Compression.FileSystem` assembly is not available in Windows 8. In Windows 8.x Store apps, you can decompress the contents of an archive by using <xref:System.IO.Compression.DeflateStream> or <xref:System.IO.Compression.GZipStream>, or you can use the Windows Runtime types [Compressor](https://go.microsoft.com/fwlink/p/?LinkId=246357) and [Decompressor](https://go.microsoft.com/fwlink/?LinkId=246358) to compress and decompress files.  
   
    
   
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorage.xml b/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
index beb7a302b85..ae4a3f41a98 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorage.xml
@@ -50,7 +50,7 @@
  For information about file-based isolated storage, see the <xref:System.IO.IsolatedStorage.IsolatedStorageFile> class.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the Windows Runtime API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml b/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
index 39cae434ab6..ec837e5adab 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorageFile.xml
@@ -62,7 +62,7 @@
  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the Windows Runtime API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
    
   
diff --git a/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml b/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
index 8fd967a2d60..90280c010e3 100644
--- a/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
+++ b/xml/System.IO.IsolatedStorage/IsolatedStorageFileStream.xml
@@ -58,7 +58,7 @@
  This type implements the <xref:System.IDisposable> interface. When you have finished using the type, you should dispose of it either directly or indirectly. To dispose of the type directly, call its <xref:System.IDisposable.Dispose%2A> method in a `try`/`catch` block. To dispose of it indirectly, use a language construct such as `using` (in C#) or `Using` (in Visual Basic). For more information, see the "Using an Object that Implements IDisposable" section in the <xref:System.IDisposable> interface topic.  
   
 > [!IMPORTANT]
->  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the [!INCLUDE[wrt](~/includes/wrt-md.md)] API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
+>  Isolated storage is not available for Windows 8.x Store apps. Instead, use the application data classes in the `Windows.Storage` namespaces included in the Windows Runtime API to store local data and files. For more information, see [Application data](https://go.microsoft.com/fwlink/?LinkId=229175) in the Windows Dev Center.  
   
    
   
diff --git a/xml/System.IO/Stream.xml b/xml/System.IO/Stream.xml
index a17fbaca178..aa3cf316c1f 100644
--- a/xml/System.IO/Stream.xml
+++ b/xml/System.IO/Stream.xml
@@ -100,7 +100,7 @@
   
  Starting with the .NET Framework 4.5, the <xref:System.IO.Stream> class includes async methods to simplify asynchronous operations. An async method contains `Async` in its name, such as <xref:System.IO.Stream.ReadAsync%2A>, <xref:System.IO.Stream.WriteAsync%2A>, <xref:System.IO.Stream.CopyToAsync%2A>, and <xref:System.IO.Stream.FlushAsync%2A>. These methods enable you to perform resource-intensive I/O operations without blocking the main thread. This performance consideration is particularly important in a Windows 8.x Store app or desktop app where a time-consuming stream operation can block the UI thread and make your app appear as if it is not working. The async methods are used in conjunction with the `async` and `await` keywords in Visual Basic and C#.  
   
- When used in a Windows 8.x Store app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)]. You can also convert a stream in the [!INCLUDE[wrt](~/includes/wrt-md.md)] to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
+ When used in a Windows 8.x Store app, <xref:System.IO.Stream> includes two extension methods: <xref:System.IO.WindowsRuntimeStreamExtensions.AsInputStream%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsOutputStream%2A>. These methods convert a <xref:System.IO.Stream> object to a stream in the Windows Runtime. You can also convert a stream in the Windows Runtime to a <xref:System.IO.Stream> object by using the <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForRead%2A> and <xref:System.IO.WindowsRuntimeStreamExtensions.AsStreamForWrite%2A> methods. For more information, see [How to: Convert Between .NET Framework Streams and Windows Runtime Streams](/dotnet/standard/io/how-to-convert-between-dotnet-streams-and-winrt-streams)  
   
  Some stream implementations perform local buffering of the underlying data to improve performance. For such streams, you can use the <xref:System.IO.Stream.Flush%2A> or <xref:System.IO.Stream.FlushAsync%2A> method to clear any internal buffers and ensure that all data has been written to the underlying data source or repository.  
   
diff --git a/xml/System.Reflection/AssemblyContentType.xml b/xml/System.Reflection/AssemblyContentType.xml
index 48a0ead3cb6..7c0fcf48bd3 100644
--- a/xml/System.Reflection/AssemblyContentType.xml
+++ b/xml/System.Reflection/AssemblyContentType.xml
@@ -131,7 +131,7 @@
       </ReturnValue>
       <MemberValue>1</MemberValue>
       <Docs>
-        <summary>The assembly contains [!INCLUDE[wrt](~/includes/wrt-md.md)] code.</summary>
+        <summary>The assembly contains Windows Runtime code.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Reflection/TypeAttributes.xml b/xml/System.Reflection/TypeAttributes.xml
index ca42fe637de..1f0d2f5881a 100644
--- a/xml/System.Reflection/TypeAttributes.xml
+++ b/xml/System.Reflection/TypeAttributes.xml
@@ -1331,7 +1331,7 @@
       </ReturnValue>
       <MemberValue>16384</MemberValue>
       <Docs>
-        <summary>Specifies a [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</summary>
+        <summary>Specifies a Windows Runtime type.</summary>
       </Docs>
     </Member>
   </Members>
diff --git a/xml/System.Resources/NeutralResourcesLanguageAttribute.xml b/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
index 35161dc7301..2d245210416 100644
--- a/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
+++ b/xml/System.Resources/NeutralResourcesLanguageAttribute.xml
@@ -82,7 +82,7 @@
 ## Windows 8.x Store Apps  
  In Windows 8.x Store apps whose resources are loaded and retrieved by using the <xref:System.Resources.ResourceManager> class, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute defines the neutral culture whose resources are used in the event of a failed probe. It does not specify the location of the resources. By default, <xref:System.Resources.ResourceManager> uses the app's package resource index (PRI) file to locate the resources of the default culture. The neutral culture that is defined by the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is added to the end of the UI language list to simulate this effect.  
   
- If you load and retrieve resources by using the [!INCLUDE[wrt](~/includes/wrt-md.md)][Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class or the types in the [Windows.ApplicationModel.Resources.Core](https://go.microsoft.com/fwlink/p/?LinkId=238194) namespace, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is ignored.  
+ If you load and retrieve resources by using the Windows Runtime[Windows.ApplicationModel.Resources.ResourceLoader](https://go.microsoft.com/fwlink/p/?LinkId=238182) class or the types in the [Windows.ApplicationModel.Resources.Core](https://go.microsoft.com/fwlink/p/?LinkId=238194) namespace, the <xref:System.Resources.NeutralResourcesLanguageAttribute> attribute is ignored.  
   
    
   
diff --git a/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml b/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
index cb3bef41078..981a6448ed5 100644
--- a/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
+++ b/xml/System.Runtime.DesignerServices/WindowsRuntimeDesignerContext.xml
@@ -51,7 +51,7 @@
       <Docs>
         <param name="paths">The paths to search.</param>
         <param name="name">The name of the context.</param>
-        <summary>Initializes a new instance of the <see cref="T:System.Runtime.DesignerServices.WindowsRuntimeDesignerContext" /> class, specifying the set of paths to search for third-party [!INCLUDE[wrt](~/includes/wrt-md.md)] types and for managed assemblies, and specifying the name of the context.</summary>
+        <summary>Initializes a new instance of the <see cref="T:System.Runtime.DesignerServices.WindowsRuntimeDesignerContext" /> class, specifying the set of paths to search for third-party Windows Runtime types and for managed assemblies, and specifying the name of the context.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.NotSupportedException">The current application domain is not the default application domain.  
   
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/DefaultInterfaceAttribute.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/DefaultInterfaceAttribute.xml
index 571741c9916..9a0a50554c6 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/DefaultInterfaceAttribute.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/DefaultInterfaceAttribute.xml
@@ -36,9 +36,9 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- When you develop [!INCLUDE[wrt](~/includes/wrt-md.md)] Components, use this attribute when you want to specify the default interface that is used to marshal the class the attribute is applied to. This is not necessary if you allow the class interfaces to be generated automatically.  
+ When you develop Windows Runtime Components, use this attribute when you want to specify the default interface that is used to marshal the class the attribute is applied to. This is not necessary if you allow the class interfaces to be generated automatically.  
   
- A [!INCLUDE[wrt](~/includes/wrt-md.md)] class must have a default interface. If the WinMdExp.exe utility does not detect a default interface for a class when it builds your [!INCLUDE[wrt](~/includes/wrt-md.md)]component, it chooses an interface as follows:  
+ A Windows Runtime class must have a default interface. If the WinMdExp.exe utility does not detect a default interface for a class when it builds your Windows Runtimecomponent, it chooses an interface as follows:  
   
 -   If the class has automatically generated interfaces, it uses the first one as the default.  
   
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/EventRegistrationToken.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/EventRegistrationToken.xml
index 7c5ae86c665..8372ea13f81 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/EventRegistrationToken.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/EventRegistrationToken.xml
@@ -30,7 +30,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Use the <xref:System.Runtime.InteropServices.WindowsRuntime.EventRegistrationToken> structure only if you use native [!INCLUDE[wrt](~/includes/wrt-md.md)] techniques to add and remove event handlers for [!INCLUDE[wrt](~/includes/wrt-md.md)] events. If you use the syntax that is provided by the C# or Visual Basic languages to add and remove event handlers, <xref:System.Runtime.InteropServices.WindowsRuntime.EventRegistrationToken> is an implementation detail handled by the compilers.  
+ Use the <xref:System.Runtime.InteropServices.WindowsRuntime.EventRegistrationToken> structure only if you use native Windows Runtime techniques to add and remove event handlers for Windows Runtime events. If you use the syntax that is provided by the C# or Visual Basic languages to add and remove event handlers, <xref:System.Runtime.InteropServices.WindowsRuntime.EventRegistrationToken> is an implementation detail handled by the compilers.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/IActivationFactory.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/IActivationFactory.xml
index a9daf9394a3..8df26a4c89f 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/IActivationFactory.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/IActivationFactory.xml
@@ -57,8 +57,8 @@
       </ReturnValue>
       <Parameters />
       <Docs>
-        <summary>Returns a new instance of the [!INCLUDE[wrt](~/includes/wrt-md.md)] class that is created by the <see cref="T:System.Runtime.InteropServices.WindowsRuntime.IActivationFactory" /> interface.</summary>
-        <returns>The new instance of the [!INCLUDE[wrt](~/includes/wrt-md.md)] class.</returns>
+        <summary>Returns a new instance of the Windows Runtime class that is created by the <see cref="T:System.Runtime.InteropServices.WindowsRuntime.IActivationFactory" /> interface.</summary>
+        <returns>The new instance of the Windows Runtime class.</returns>
         <remarks>To be added.</remarks>
       </Docs>
     </Member>
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/ReadOnlyArrayAttribute.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/ReadOnlyArrayAttribute.xml
index dd37f13cf6c..8648efa3561 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/ReadOnlyArrayAttribute.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/ReadOnlyArrayAttribute.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If an array parameter in your [!INCLUDE[wrt](~/includes/wrt-md.md)] component is passed by value (`ByVal` in Visual Basic), you must apply one of the following attributes to it:  
+ If an array parameter in your Windows Runtime component is passed by value (`ByVal` in Visual Basic), you must apply one of the following attributes to it:  
   
 -   Apply the <xref:System.Runtime.InteropServices.WindowsRuntime.ReadOnlyArrayAttribute> attribute if you intend the contents of the array to be used for input only.  
   
@@ -47,7 +47,7 @@
 > [!IMPORTANT]
 >  Parameters that have the <xref:System.Runtime.InteropServices.WindowsRuntime.ReadOnlyArrayAttribute> attribute behave differently depending on whether the caller is written in native code or managed code. If the caller is native code (JavaScript or Visual C++ component extensions), the array is copied when the call crosses the application binary interface (ABI) boundary. Elements are converted if necessary. Therefore, any accidental changes the method makes to an input-only array are not visible to the caller.  
 >   
->  If the caller is managed code, the array is not copied. The original array is available to the called method, as it would be in any method call in the .NET Framework. Array contents are mutable in .NET Framework code, so any changes the method makes to the array are visible to the caller. This is important to remember because it affects unit tests written for a [!INCLUDE[wrt](~/includes/wrt-md.md)] component. If the tests are written in managed code, the contents of an array will appear to be mutable during testing.  
+>  If the caller is managed code, the array is not copied. The original array is available to the called method, as it would be in any method call in the .NET Framework. Array contents are mutable in .NET Framework code, so any changes the method makes to the array are visible to the caller. This is important to remember because it affects unit tests written for a Windows Runtime component. If the tests are written in managed code, the contents of an array will appear to be mutable during testing.  
   
  Applying this attribute to a parameter that has the <xref:System.Runtime.InteropServices.InAttribute> or <xref:System.Runtime.InteropServices.OutAttribute> attribute causes an error when the module is exported. Applying the attribute to an `out` parameter also causes an error.  
   
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
index 9365cc09e9e..680665df066 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/ReturnValueNameAttribute.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- In a [!INCLUDE[wrt](~/includes/wrt-md.md)] component, all the parameters of a method and the return value must have names. By default, [Winmdexp.exe (Windows Runtime Metadata Export Tool)](/dotnet/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool) gives the return value the name "value". When you use a component in a Windows 8.x Store app written in JavaScript, you can use this name to retrieve the return value. For example, suppose a component defines a method that has a return value and two `out` parameters (`ByRef` parameters with the <xref:System.Runtime.InteropServices.OutAttribute> attribute in Visual Basic):  
+ In a Windows Runtime component, all the parameters of a method and the return value must have names. By default, [Winmdexp.exe (Windows Runtime Metadata Export Tool)](/dotnet/framework/tools/winmdexp-exe-windows-runtime-metadata-export-tool) gives the return value the name "value". When you use a component in a Windows 8.x Store app written in JavaScript, you can use this name to retrieve the return value. For example, suppose a component defines a method that has a return value and two `out` parameters (`ByRef` parameters with the <xref:System.Runtime.InteropServices.OutAttribute> attribute in Visual Basic):  
   
 ```csharp  
 public static int ComputeAverage([ReadOnlyArray()] int[] input,  
@@ -147,7 +147,7 @@ End Function
         <ReturnType>System.String</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets the name that was specified for the return value of a method in a [!INCLUDE[wrt](~/includes/wrt-md.md)] component.</summary>
+        <summary>Gets the name that was specified for the return value of a method in a Windows Runtime component.</summary>
         <value>The name of the method's return value.</value>
         <remarks>To be added.</remarks>
       </Docs>
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMarshal.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMarshal.xml
index 4713b39ff98..63734873503 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMarshal.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMarshal.xml
@@ -69,10 +69,10 @@
       </Parameters>
       <Docs>
         <typeparam name="T">The type of the delegate that represents the event handler.</typeparam>
-        <param name="addMethod">A delegate that represents the method that adds event handlers to the [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</param>
-        <param name="removeMethod">A delegate that represents the method that removes event handlers from the [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</param>
+        <param name="addMethod">A delegate that represents the method that adds event handlers to the Windows Runtime event.</param>
+        <param name="removeMethod">A delegate that represents the method that removes event handlers from the Windows Runtime event.</param>
         <param name="handler">A delegate the represents the event handler that is added.</param>
-        <summary>Adds the specified event handler to a [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</summary>
+        <summary>Adds the specified event handler to a Windows Runtime event.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="addMethod" /> is <see langword="null" />.  
@@ -117,9 +117,9 @@
       </Parameters>
       <Docs>
         <param name="ptr">The address of the [HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451) to free.</param>
-        <summary>Frees the specified [!INCLUDE[wrt](~/includes/wrt-md.md)][HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451).</summary>
+        <summary>Frees the specified Windows Runtime[HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451).</summary>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The [!INCLUDE[wrt](~/includes/wrt-md.md)] is not supported on the current version of the operating system.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The Windows Runtime is not supported on the current version of the operating system.</exception>
         <forInternalUseOnly />
         <altmember cref="M:System.Runtime.InteropServices.WindowsRuntime.WindowsRuntimeMarshal.StringToHString(System.String)" />
       </Docs>
@@ -157,8 +157,8 @@
         <Parameter Name="type" Type="System.Type" />
       </Parameters>
       <Docs>
-        <param name="type">The [!INCLUDE[wrt](~/includes/wrt-md.md)] type to get the activation factory interface for.</param>
-        <summary>Returns an object that implements the activation factory interface for the specified [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</summary>
+        <param name="type">The Windows Runtime type to get the activation factory interface for.</param>
+        <summary>Returns an object that implements the activation factory interface for the specified Windows Runtime type.</summary>
         <returns>An object that implements the activation factory interface.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -169,14 +169,14 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">
-          <paramref name="type" /> does not represent a [!INCLUDE[wrt](~/includes/wrt-md.md)] type (that is, belonging to the [!INCLUDE[wrt](~/includes/wrt-md.md)] itself or defined in a [!INCLUDE[wrt](~/includes/wrt-md.md)] component).  
+          <paramref name="type" /> does not represent a Windows Runtime type (that is, belonging to the Windows Runtime itself or defined in a Windows Runtime component).  
   
  -or-  
   
  The object specified for <paramref name="type" /> was not provided by the common language runtime type system.</exception>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="type" /> is <see langword="null" />.</exception>
-        <exception cref="T:System.TypeLoadException">The specified [!INCLUDE[wrt](~/includes/wrt-md.md)] class is not properly registered. For example, the .winmd file was located, but the [!INCLUDE[wrt](~/includes/wrt-md.md)] failed to locate the implementation.</exception>
+        <exception cref="T:System.TypeLoadException">The specified Windows Runtime class is not properly registered. For example, the .winmd file was located, but the Windows Runtime failed to locate the implementation.</exception>
         <forInternalUseOnly />
       </Docs>
     </Member>
@@ -214,10 +214,10 @@
       </Parameters>
       <Docs>
         <param name="ptr">An unmanaged pointer to the [HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451) to copy.</param>
-        <summary>Returns a managed string that contains a copy of the specified [!INCLUDE[wrt](~/includes/wrt-md.md)][HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451).</summary>
+        <summary>Returns a managed string that contains a copy of the specified Windows Runtime[HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451).</summary>
         <returns>A managed string that contains a copy of the <see href="https://docs.microsoft.com/windows/desktop/WinRT/hstring">HSTRING</see> if <paramref name="ptr" /> is not <see cref="F:System.IntPtr.Zero" />; otherwise, <see cref="F:System.String.Empty" />.</returns>
         <remarks>To be added.</remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The [!INCLUDE[wrt](~/includes/wrt-md.md)] is not supported on the current version of the operating system.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The Windows Runtime is not supported on the current version of the operating system.</exception>
         <forInternalUseOnly />
       </Docs>
     </Member>
@@ -254,7 +254,7 @@
         <Parameter Name="removeMethod" Type="System.Action&lt;System.Runtime.InteropServices.WindowsRuntime.EventRegistrationToken&gt;" />
       </Parameters>
       <Docs>
-        <param name="removeMethod">A delegate that represents the method that removes event handlers from the [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</param>
+        <param name="removeMethod">A delegate that represents the method that removes event handlers from the Windows Runtime event.</param>
         <summary>Removes all the event handlers that can be removed by using the specified method.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
@@ -300,9 +300,9 @@
       </Parameters>
       <Docs>
         <typeparam name="T">The type of the delegate that represents the event handler.</typeparam>
-        <param name="removeMethod">A delegate that represents the method that removes event handlers from the [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</param>
+        <param name="removeMethod">A delegate that represents the method that removes event handlers from the Windows Runtime event.</param>
         <param name="handler">The event handler that is removed.</param>
-        <summary>Removes the specified event handler from a [!INCLUDE[wrt](~/includes/wrt-md.md)] event.</summary>
+        <summary>Removes the specified event handler from a Windows Runtime event.</summary>
         <remarks>To be added.</remarks>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="removeMethod" /> is <see langword="null" />.</exception>
@@ -343,7 +343,7 @@
       </Parameters>
       <Docs>
         <param name="s">The managed string to copy.</param>
-        <summary>Allocates a [!INCLUDE[wrt](~/includes/wrt-md.md)][HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451) and copies the specified managed string to it.</summary>
+        <summary>Allocates a Windows Runtime[HSTRING](https://go.microsoft.com/fwlink/p/?LinkId=246451) and copies the specified managed string to it.</summary>
         <returns>An unmanaged pointer to the new <see href="https://docs.microsoft.com/windows/desktop/WinRT/hstring">HSTRING</see>, or <see cref="F:System.IntPtr.Zero" /> if <paramref name="s" /> is <see cref="F:System.String.Empty" />.</returns>
         <remarks>
           <format type="text/markdown"><![CDATA[  
@@ -353,7 +353,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The [!INCLUDE[wrt](~/includes/wrt-md.md)] is not supported on the current version of the operating system.</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The Windows Runtime is not supported on the current version of the operating system.</exception>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="s" /> is <see langword="null" />.</exception>
         <forInternalUseOnly />
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMetadata.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMetadata.xml
index 33ef342da02..2f1e07cab5f 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMetadata.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/WindowsRuntimeMetadata.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Unlike the .NET Framework, assembly identity isn't important for [!INCLUDE[wrt](~/includes/wrt-md.md)] types. In the [!INCLUDE[wrt](~/includes/wrt-md.md)], Windows Metadata files (.WinMD files) contain only metadata, not code. Types can move from one Windows Metadata file to another in a service pack release, so it's important to be able to locate the Windows Metadata files that are associated with a namespace.  
+ Unlike the .NET Framework, assembly identity isn't important for Windows Runtime types. In the Windows Runtime, Windows Metadata files (.WinMD files) contain only metadata, not code. Types can move from one Windows Metadata file to another in a service pack release, so it's important to be able to locate the Windows Metadata files that are associated with a namespace.  
   
 > [!NOTE]
 >  Sub-namespaces don't imply containment. That is, namespace A.B isn't contained in namespace A.  
@@ -155,7 +155,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operating system version does not support the [!INCLUDE[wrt](~/includes/wrt-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operating system version does not support the Windows Runtime.</exception>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="namespaceName" /> is <see langword="null" />.</exception>
       </Docs>
@@ -201,7 +201,7 @@
   
  ]]></format>
         </remarks>
-        <exception cref="T:System.PlatformNotSupportedException">The operating system version does not support the [!INCLUDE[wrt](~/includes/wrt-md.md)].</exception>
+        <exception cref="T:System.PlatformNotSupportedException">The operating system version does not support the Windows Runtime.</exception>
         <exception cref="T:System.ArgumentNullException">
           <paramref name="namespaceName" /> is <see langword="null" />.</exception>
       </Docs>
diff --git a/xml/System.Runtime.InteropServices.WindowsRuntime/WriteOnlyArrayAttribute.xml b/xml/System.Runtime.InteropServices.WindowsRuntime/WriteOnlyArrayAttribute.xml
index b845bc64c18..abb8ec0ad14 100644
--- a/xml/System.Runtime.InteropServices.WindowsRuntime/WriteOnlyArrayAttribute.xml
+++ b/xml/System.Runtime.InteropServices.WindowsRuntime/WriteOnlyArrayAttribute.xml
@@ -36,7 +36,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- If an array parameter in your [!INCLUDE[wrt](~/includes/wrt-md.md)] component is passed by value (`ByVal` in Visual Basic), you must apply one of the following attributes to it:  
+ If an array parameter in your Windows Runtime component is passed by value (`ByVal` in Visual Basic), you must apply one of the following attributes to it:  
   
 -   Apply the <xref:System.Runtime.InteropServices.WindowsRuntime.ReadOnlyArrayAttribute> attribute if you intend the contents of the array to be used for input only.  
   
@@ -47,7 +47,7 @@
 > [!IMPORTANT]
 >  Parameters that have the <xref:System.Runtime.InteropServices.WindowsRuntime.WriteOnlyArrayAttribute> attribute behave differently depending on whether the caller is written in native code or managed code. If the caller is native code (JavaScript or Visual C++ component extensions), the called method can't make any assumptions about the contents of the original array. For example, the array the method receives might not be initialized, or might contain default values. The method is expected to set the values of all the elements in the array.  
 >   
->  If the caller is managed code, the caller's original array is passed to the called method, as it would be in any method call in the .NET Framework. Array contents are mutable in managed code, so the method can selectively read and change those values. This is important to remember because it affects unit tests written for a [!INCLUDE[wrt](~/includes/wrt-md.md)] component. If the tests are written in managed code, the contents of an array will appear to be mutable during testing, and the results are likely to be different if the method is called from native code later.  
+>  If the caller is managed code, the caller's original array is passed to the called method, as it would be in any method call in the .NET Framework. Array contents are mutable in managed code, so the method can selectively read and change those values. This is important to remember because it affects unit tests written for a Windows Runtime component. If the tests are written in managed code, the contents of an array will appear to be mutable during testing, and the results are likely to be different if the method is called from native code later.  
   
  Applying this attribute to an `out` parameter or to a parameter that has the <xref:System.Runtime.InteropServices.InAttribute> attribute causes an error when the module is exported. Applying the attribute to a parameter that has the <xref:System.Runtime.InteropServices.OutAttribute> attribute causes an error unless the parameter also has the Visual Basic `ByRef` modifier. In that case, the attribute is redundant but allowed.  
   
diff --git a/xml/System.Runtime.InteropServices/ComInterfaceType.xml b/xml/System.Runtime.InteropServices/ComInterfaceType.xml
index 4f27f29ad2f..5edb2081349 100644
--- a/xml/System.Runtime.InteropServices/ComInterfaceType.xml
+++ b/xml/System.Runtime.InteropServices/ComInterfaceType.xml
@@ -200,7 +200,7 @@
       </ReturnValue>
       <MemberValue>3</MemberValue>
       <Docs>
-        <summary>Indicates that an interface is exposed to COM as a [!INCLUDE[wrt](~/includes/wrt-md.md)] interface.</summary>
+        <summary>Indicates that an interface is exposed to COM as a Windows Runtime interface.</summary>
       </Docs>
     </Member>
     <Member MemberName="InterfaceIsIUnknown">
diff --git a/xml/System.Runtime.InteropServices/Marshal.xml b/xml/System.Runtime.InteropServices/Marshal.xml
index 5305ed761b8..fd8a125c8cd 100644
--- a/xml/System.Runtime.InteropServices/Marshal.xml
+++ b/xml/System.Runtime.InteropServices/Marshal.xml
@@ -1864,7 +1864,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">
-          <paramref name="o" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] object.</exception>
+          <paramref name="o" /> is a Windows Runtime object.</exception>
       </Docs>
     </Member>
     <Member MemberName="CreateAggregatedObject&lt;T&gt;">
@@ -1933,7 +1933,7 @@
  ]]></format>
         </remarks>
         <exception cref="T:System.ArgumentException">
-          <paramref name="o" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] object.</exception>
+          <paramref name="o" /> is a Windows Runtime object.</exception>
       </Docs>
     </Member>
     <Member MemberName="CreateWrapperOfType">
@@ -2019,7 +2019,7 @@
   
  -or-  
   
- <paramref name="t" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</exception>
+ <paramref name="t" /> is a Windows Runtime type.</exception>
         <exception cref="T:System.ArgumentNullException">The <paramref name="t" /> parameter is <see langword="null" />.</exception>
         <exception cref="T:System.InvalidCastException">
           <paramref name="o" /> cannot be converted to the destination type because it does not support all required interfaces.</exception>
@@ -2104,7 +2104,7 @@
   
  -or-  
   
- <typeparamref name="T" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</exception>
+ <typeparamref name="T" /> is a Windows Runtime type.</exception>
         <exception cref="T:System.InvalidCastException">
           <paramref name="o" /> cannot be converted to the <paramref name="TWrapper" /> because it does not support all required interfaces.</exception>
       </Docs>
@@ -3120,7 +3120,7 @@
   
  -or-  
   
- <paramref name="obj" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] object.</exception>
+ <paramref name="obj" /> is a Windows Runtime object.</exception>
         <altmember cref="M:System.Runtime.InteropServices.Marshal.SetComObjectData(System.Object,System.Object,System.Object)" />
       </Docs>
     </Member>
@@ -4142,7 +4142,7 @@
   
  -or-  
   
- <paramref name="t" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</exception>
+ <paramref name="t" /> is a Windows Runtime type.</exception>
         <exception cref="T:System.Runtime.InteropServices.COMException">A type library is registered for the assembly that contains the type, but the type definition cannot be found.</exception>
         <altmember cref="M:System.Runtime.InteropServices.Marshal.GetTypeForITypeInfo(System.IntPtr)" />
         <altmember cref="T:System.Runtime.InteropServices.MarshalAsAttribute" />
@@ -5197,7 +5197,7 @@ There is a difference in the behavior of the `GetLastWin32Error` method on .NET
   
  -or-  
   
- <paramref name="t" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] type.</exception>
+ <paramref name="t" /> is a Windows Runtime type.</exception>
         <altmember cref="T:System.Runtime.InteropServices.ComImportAttribute" />
       </Docs>
     </Member>
@@ -9432,7 +9432,7 @@ There is a difference in the behavior of the `GetLastWin32Error` method on .NET
   
  -or-  
   
- <paramref name="obj" /> is a [!INCLUDE[wrt](~/includes/wrt-md.md)] object.</exception>
+ <paramref name="obj" /> is a Windows Runtime object.</exception>
         <altmember cref="M:System.Runtime.InteropServices.Marshal.GetComObjectData(System.Object,System.Object)" />
       </Docs>
     </Member>
diff --git a/xml/System.Runtime.InteropServices/UnmanagedType.xml b/xml/System.Runtime.InteropServices/UnmanagedType.xml
index 5d0ade85d80..ff96042dac2 100644
--- a/xml/System.Runtime.InteropServices/UnmanagedType.xml
+++ b/xml/System.Runtime.InteropServices/UnmanagedType.xml
@@ -538,7 +538,7 @@
       </ReturnValue>
       <MemberValue>47</MemberValue>
       <Docs>
-        <summary>A [!INCLUDE[wrt](~/includes/wrt-md.md)] string. You can use this member on the <see cref="T:System.String" /> data type.</summary>
+        <summary>A Windows Runtime string. You can use this member on the <see cref="T:System.String" /> data type.</summary>
       </Docs>
     </Member>
     <Member MemberName="I1">
@@ -792,7 +792,7 @@
       </ReturnValue>
       <MemberValue>46</MemberValue>
       <Docs>
-        <summary>A [!INCLUDE[wrt](~/includes/wrt-md.md)] interface pointer. You can use this member on the <see cref="T:System.Object" /> data type.</summary>
+        <summary>A Windows Runtime interface pointer. You can use this member on the <see cref="T:System.Object" /> data type.</summary>
       </Docs>
     </Member>
     <Member MemberName="Interface">
diff --git a/xml/System/Object.xml b/xml/System/Object.xml
index 63ed66ffae4..3f009f186f5 100644
--- a/xml/System/Object.xml
+++ b/xml/System/Object.xml
@@ -226,11 +226,11 @@
   
  Because the <xref:System.Object> class is the base class for all types in the .NET Framework, the <xref:System.Object.Equals%28System.Object%29?displayProperty=nameWithType> method provides the default equality comparison for all other types. However, types often override the <xref:System.Object.Equals%2A> method to implement value equality. For more information, see the Notes for Callers and Notes for Inheritors sections.  
   
-## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
- When you call the <xref:System.Object.Equals%28System.Object%29> method overload on a class in the [!INCLUDE[wrt](~/includes/wrt-md.md)], it provides the default behavior for classes that don't override <xref:System.Object.Equals%28System.Object%29>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the [!INCLUDE[wrt](~/includes/wrt-md.md)] don't inherit <xref:System.Object>, and currently don't implement an <xref:System.Object.Equals%28System.Object%29> method. However, they appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
+## Notes for the Windows Runtime  
+ When you call the <xref:System.Object.Equals%28System.Object%29> method overload on a class in the Windows Runtime, it provides the default behavior for classes that don't override <xref:System.Object.Equals%28System.Object%29>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the Windows Runtime don't inherit <xref:System.Object>, and currently don't implement an <xref:System.Object.Equals%28System.Object%29> method. However, they appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
   
 > [!NOTE]
->  [!INCLUDE[wrt](~/includes/wrt-md.md)] classes that are written in C# or Visual Basic can override the <xref:System.Object.Equals%28System.Object%29> method overload.  
+>  Windows Runtime classes that are written in C# or Visual Basic can override the <xref:System.Object.Equals%28System.Object%29> method overload.  
   
 ## Notes for Callers  
  Derived classes frequently override the <xref:System.Object.Equals%28System.Object%29?displayProperty=nameWithType> method to implement value equality. In addition, types also frequently provide an additional strongly typed overload to the `Equals` method, typically by implementing the <xref:System.IEquatable%601> interface. When you call the `Equals` method to test for equality, you should know whether the current instance overrides <xref:System.Object.Equals%2A?displayProperty=nameWithType> and understand how a particular call to an `Equals` method is resolved. Otherwise, you may be performing a test for equality that is different from what you intended, and the method may return an unexpected value.  
@@ -648,11 +648,11 @@ and the <xref:System.IDisposable> interface. The <xref:System.IDisposable.Dispos
   
  If an object that is used as a key in a hash table does not provide a useful implementation of <xref:System.Object.GetHashCode%2A>, you can specify a hash code provider by supplying an <xref:System.Collections.IEqualityComparer> implementation to one of the overloads of the <xref:System.Collections.Hashtable> class constructor.  
   
-## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
- When you call the <xref:System.Object.GetHashCode%2A> method on a class in the [!INCLUDE[wrt](~/includes/wrt-md.md)], it provides the default behavior for classes that don't override <xref:System.Object.GetHashCode%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the [!INCLUDE[wrt](~/includes/wrt-md.md)] don't inherit <xref:System.Object>, and currently don't implement a <xref:System.Object.GetHashCode%2A>. However, they appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
+## Notes for the Windows Runtime  
+ When you call the <xref:System.Object.GetHashCode%2A> method on a class in the Windows Runtime, it provides the default behavior for classes that don't override <xref:System.Object.GetHashCode%2A>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the Windows Runtime don't inherit <xref:System.Object>, and currently don't implement a <xref:System.Object.GetHashCode%2A>. However, they appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
   
 > [!NOTE]
->  [!INCLUDE[wrt](~/includes/wrt-md.md)] classes that are written in C# or Visual Basic can override the <xref:System.Object.GetHashCode%2A> method.  
+>  Windows Runtime classes that are written in C# or Visual Basic can override the <xref:System.Object.GetHashCode%2A> method.  
   
    
   
@@ -1127,23 +1127,23 @@ and the <xref:System.IDisposable> interface. The <xref:System.IDisposable.Dispos
      :::code language="vb" source="~/samples/snippets/visualbasic/VS_Snippets_CLR_System/system.object.tostring/vb/customize2.vb" id="Snippet8"::: 
   
 <a name="WinRT"></a>   
-## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
- When you call the <xref:System.Object.ToString%2A> method on a class in the [!INCLUDE[wrt](~/includes/wrt-md.md)], it provides the default behavior for classes that don't override <xref:System.Object.ToString%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the [!INCLUDE[wrt](~/includes/wrt-md.md)] don't inherit <xref:System.Object>, and don't always implement a <xref:System.Object.ToString%2A>. However, they always appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides a default behavior for these methods.  
+## Notes for the Windows Runtime  
+ When you call the <xref:System.Object.ToString%2A> method on a class in the Windows Runtime, it provides the default behavior for classes that don't override <xref:System.Object.ToString%2A>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Classes in the Windows Runtime don't inherit <xref:System.Object>, and don't always implement a <xref:System.Object.ToString%2A>. However, they always appear to have <xref:System.Object.ToString%2A>, <xref:System.Object.Equals%28System.Object%29>, and <xref:System.Object.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides a default behavior for these methods.  
   
- Starting with .NET Framework 4.5.1, the common language runtime uses [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) on a [!INCLUDE[wrt](~/includes/wrt-md.md)] object before falling back to the default implementation of <xref:System.Object.ToString%2A?displayProperty=nameWithType>.  
+ Starting with .NET Framework 4.5.1, the common language runtime uses [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) on a Windows Runtime object before falling back to the default implementation of <xref:System.Object.ToString%2A?displayProperty=nameWithType>.  
   
 > [!NOTE]
-> [!INCLUDE[wrt](~/includes/wrt-md.md)] classes that are written in C# or Visual Basic can override the <xref:System.Object.ToString%2A> method.  
+> Windows Runtime classes that are written in C# or Visual Basic can override the <xref:System.Object.ToString%2A> method.  
   
-### The [!INCLUDE[wrt](~/includes/wrt-md.md)] and the IStringable Interface  
- Starting with Windows 8.1, the [!INCLUDE[wrt](~/includes/wrt-md.md)] includes an [IStringable](xref:Windows.Foundation.IStringable) interface whose single method, [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString), provides basic formatting support comparable to that provided by <xref:System.Object.ToString%2A?displayProperty=nameWithType>. To prevent ambiguity, you should not implement [IStringable](xref:Windows.Foundation.IStringable) on managed types.  
+### The Windows Runtime and the IStringable Interface  
+ Starting with Windows 8.1, the Windows Runtime includes an [IStringable](xref:Windows.Foundation.IStringable) interface whose single method, [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString), provides basic formatting support comparable to that provided by <xref:System.Object.ToString%2A?displayProperty=nameWithType>. To prevent ambiguity, you should not implement [IStringable](xref:Windows.Foundation.IStringable) on managed types.  
   
  When managed objects are called by native code or by code written in languages such as JavaScript or C++/CX, they appear to implement [IStringable](xref:Windows.Foundation.IStringable). The common language runtime automatically routes calls from [IStringable.ToString](xref:Windows.Foundation.IStringable.ToString) to <xref:System.Object.ToString%2A?displayProperty=nameWithType> if [IStringable](xref:Windows.Foundation.IStringable) is not implemented on the managed object.  
   
 > [!WARNING]
->  Because the common language runtime auto-implements [IStringable](xref:Windows.Foundation.IStringable) for all managed types in Windows Store apps, we recommend that you do not provide your own `IStringable` implementation. Implementing `IStringable` may result in unintended behavior when calling `ToString` from the [!INCLUDE[wrt](~/includes/wrt-md.md)], C++/CX, or JavaScript.  
+>  Because the common language runtime auto-implements [IStringable](xref:Windows.Foundation.IStringable) for all managed types in Windows Store apps, we recommend that you do not provide your own `IStringable` implementation. Implementing `IStringable` may result in unintended behavior when calling `ToString` from the Windows Runtime, C++/CX, or JavaScript.  
   
- If you do choose to implement [IStringable](xref:Windows.Foundation.IStringable) in a public managed type that's exported in a [!INCLUDE[wrt](~/includes/wrt-md.md)] component, the following restrictions apply:  
+ If you do choose to implement [IStringable](xref:Windows.Foundation.IStringable) in a public managed type that's exported in a Windows Runtime component, the following restrictions apply:  
   
 - You can define the [IStringable](xref:Windows.Foundation.IStringable) interface only in a "class implements" relationship, as follows:
 
diff --git a/xml/System/ValueType.xml b/xml/System/ValueType.xml
index 6a9889d69f6..6b4237e0430 100644
--- a/xml/System/ValueType.xml
+++ b/xml/System/ValueType.xml
@@ -171,8 +171,8 @@
 > [!TIP]
 >  Particularly if your value type contains fields that are reference types, you should override the <xref:System.ValueType.Equals%28System.Object%29> method. This can improve performance and enable you to more closely represent the meaning of equality for the type.  
   
-## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
- When you call the <xref:System.ValueType.Equals%2A> method on a [!INCLUDE[wrt](~/includes/wrt-md.md)] structure, it provides the default behavior for value types that don't override <xref:System.ValueType.Equals%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). [!INCLUDE[wrt](~/includes/wrt-md.md)] structures can't override <xref:System.ValueType.Equals%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the [!INCLUDE[wrt](~/includes/wrt-md.md)] itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
+## Notes for the Windows Runtime  
+ When you call the <xref:System.ValueType.Equals%2A> method on a Windows Runtime structure, it provides the default behavior for value types that don't override <xref:System.ValueType.Equals%2A>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Windows Runtime structures can't override <xref:System.ValueType.Equals%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the Windows Runtime itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
   
    
   
@@ -239,8 +239,8 @@
   
  For more information, see <xref:System.Object.GetHashCode%2A?displayProperty=nameWithType>, and <xref:System.Collections.Hashtable?displayProperty=nameWithType>.  
   
-## Notes for the [!INCLUDE[wrt](~/includes/wrt-md.md)]  
- When you call the <xref:System.ValueType.GetHashCode%2A> method on a [!INCLUDE[wrt](~/includes/wrt-md.md)] structure, it provides the default behavior for value types that don't override <xref:System.ValueType.GetHashCode%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). [!INCLUDE[wrt](~/includes/wrt-md.md)] structures can't override <xref:System.ValueType.GetHashCode%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the [!INCLUDE[wrt](~/includes/wrt-md.md)] itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
+## Notes for the Windows Runtime  
+ When you call the <xref:System.ValueType.GetHashCode%2A> method on a Windows Runtime structure, it provides the default behavior for value types that don't override <xref:System.ValueType.GetHashCode%2A>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Windows Runtime structures can't override <xref:System.ValueType.GetHashCode%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the Windows Runtime itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
   
    
   
@@ -308,7 +308,7 @@
  Note that, although enumeration types are also value types, they derive from the <xref:System.Enum> class, which overrides  <xref:System.ValueType.ToString%2A?displayProperty=nameWithType>.  
   
 ## Notes for the Windows Runtime  
- When you call the <xref:System.ValueType.ToString%2A> method on a [!INCLUDE[wrt](~/includes/wrt-md.md)] structure, it provides the default behavior for value types that don't override <xref:System.ValueType.ToString%2A>. This is part of the support that the .NET Framework provides for the [!INCLUDE[wrt](~/includes/wrt-md.md)] (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). [!INCLUDE[wrt](~/includes/wrt-md.md)] structures can't override <xref:System.ValueType.ToString%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the [!INCLUDE[wrt](~/includes/wrt-md.md)] itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
+ When you call the <xref:System.ValueType.ToString%2A> method on a Windows Runtime structure, it provides the default behavior for value types that don't override <xref:System.ValueType.ToString%2A>. This is part of the support that the .NET Framework provides for the Windows Runtime (see [.NET Framework Support for Windows Store Apps and Windows Runtime](/dotnet/standard/cross-platform/support-for-windows-store-apps-and-windows-runtime)). Windows Runtime structures can't override <xref:System.ValueType.ToString%2A>, even if they're written with C# or Visual Basic, because they can't have methods. (In addition, structures in the Windows Runtime itself don't inherit <xref:System.ValueType>.) However, they appear to have <xref:System.ValueType.ToString%2A>, <xref:System.ValueType.Equals%2A>, and <xref:System.ValueType.GetHashCode%2A> methods when you use them in your C# or Visual Basic code, and the .NET Framework provides the default behavior for these methods.  
   
  ]]></format>
         </remarks>

From 3d42abb330c2146354239de8ceeb142cb7caaaa6 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:53:00 -0800
Subject: [PATCH 226/236] ws2003

---
 xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml | 2 +-
 xml/System.ServiceModel.Configuration/TcpTransportElement.xml   | 2 +-
 xml/System.ServiceModel/AuditLogLocation.xml                    | 2 +-
 xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml             | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
index 783625f5729..8ab677babe8 100644
--- a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
@@ -736,7 +736,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).  
   
- This property is applicable only on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and [!INCLUDE[ws2003](~/includes/ws2003-md.md)]. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
+ This property is applicable only on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
   
    
   
diff --git a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
index 76481a18585..a2d90eb028b 100644
--- a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
+++ b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
@@ -364,7 +364,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).  
   
- This property is only applicable on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and [!INCLUDE[ws2003](~/includes/ws2003-md.md)]. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
+ This property is only applicable on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel/AuditLogLocation.xml b/xml/System.ServiceModel/AuditLogLocation.xml
index 3c3ab43091e..307d5c074c1 100644
--- a/xml/System.ServiceModel/AuditLogLocation.xml
+++ b/xml/System.ServiceModel/AuditLogLocation.xml
@@ -91,7 +91,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on [!INCLUDE[wv](~/includes/wv-md.md)] and [!INCLUDE[ws2003](~/includes/ws2003-md.md)] and later platforms), the default log location is the Security log. Otherwise (such as in [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)]), the default log location is the Application log.</summary>
+        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on [!INCLUDE[wv](~/includes/wv-md.md)] and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)]), the default log location is the Application log.</summary>
       </Docs>
     </Member>
     <Member MemberName="Security">
diff --git a/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml b/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
index 6a409244055..7123dc5bc5d 100644
--- a/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
+++ b/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
@@ -24,7 +24,7 @@
   
  For encryption to work, the <xref:System.ServiceModel.MsmqTransportSecurity.MsmqProtectionLevel%2A> property must be set to <xref:System.Net.Security.ProtectionLevel.EncryptAndSign>.  
   
- Only RC4Stream is supported on [!INCLUDE[ws2003](~/includes/ws2003-md.md)] and [!INCLUDE[wxp](~/includes/wxp-md.md)].  
+ Only RC4Stream is supported on Windows Server 2003 and [!INCLUDE[wxp](~/includes/wxp-md.md)].  
   
  ]]></format>
     </remarks>

From ae8d8d9c51c3c43f34b5a04d0acd9b41e8a2e0f1 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:53:37 -0800
Subject: [PATCH 227/236] wv

---
 xml/System.ServiceModel.Channels/MsmqBindingElementBase.xml | 6 +++---
 .../TcpTransportBindingElement.xml                          | 2 +-
 .../MsmqBindingElementBase.xml                              | 4 ++--
 .../TcpTransportElement.xml                                 | 2 +-
 xml/System.ServiceModel/AuditLogLocation.xml                | 2 +-
 xml/System.ServiceModel/MsmqBindingBase.xml                 | 4 ++--
 xml/System.ServiceModel/MsmqSecureHashAlgorithm.xml         | 2 +-
 xml/System.ServiceModel/ReceiveErrorHandling.xml            | 2 +-
 8 files changed, 12 insertions(+), 12 deletions(-)

diff --git a/xml/System.ServiceModel.Channels/MsmqBindingElementBase.xml b/xml/System.ServiceModel.Channels/MsmqBindingElementBase.xml
index ccc9cd2056f..8ec87f63315 100644
--- a/xml/System.ServiceModel.Channels/MsmqBindingElementBase.xml
+++ b/xml/System.ServiceModel.Channels/MsmqBindingElementBase.xml
@@ -68,7 +68,7 @@
   
  If <xref:System.ServiceModel.Channels.MsmqBindingElementBase.DeadLetterQueue%2A> is set to <xref:System.ServiceModel.DeadLetterQueue.None> or <xref:System.ServiceModel.DeadLetterQueue.System>, then <xref:System.ServiceModel.Channels.MsmqBindingElementBase.CustomDeadLetterQueue%2A> must be set to `null`. If <xref:System.ServiceModel.Channels.MsmqBindingElementBase.CustomDeadLetterQueue%2A> is not `null`, then <xref:System.ServiceModel.Channels.MsmqBindingElementBase.DeadLetterQueue%2A> must be set to <xref:System.ServiceModel.DeadLetterQueue.Custom>.  
   
- The <xref:System.ServiceModel.Channels.MsmqBindingElementBase.CustomDeadLetterQueue%2A> property can be set only on operating systems starting with [!INCLUDE[wv](~/includes/wv-md.md)].  
+ The <xref:System.ServiceModel.Channels.MsmqBindingElementBase.CustomDeadLetterQueue%2A> property can be set only on operating systems starting with Windows Vista.  
   
  ]]></format>
         </remarks>
@@ -281,7 +281,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A retry cycle is when a message is transferred from the retry queue to the application queue to attempt delivery to the application. Messages are placed in the retry queue after failing a number of immediate retries as specified by <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.ReceiveRetryCount%2A>. `MaxRetryCycles` specifies the number of retry cycles and does not include the initial attempt to send the message. An attempt to deliver a message is made a maximum of (1 + MaxRetryCycles) * (ReceiveRetryCount + 1) times. For example, if ReceiveRetryCount = 0 and MaxRetryCycles is 1, there is a maximum of two attempts to deliver the message. This property is used only on operating systems starting with [!INCLUDE[wv](~/includes/wv-md.md)].  
+ A retry cycle is when a message is transferred from the retry queue to the application queue to attempt delivery to the application. Messages are placed in the retry queue after failing a number of immediate retries as specified by <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.ReceiveRetryCount%2A>. `MaxRetryCycles` specifies the number of retry cycles and does not include the initial attempt to send the message. An attempt to deliver a message is made a maximum of (1 + MaxRetryCycles) * (ReceiveRetryCount + 1) times. For example, if ReceiveRetryCount = 0 and MaxRetryCycles is 1, there is a maximum of two attempts to deliver the message. This property is used only on operating systems starting with Windows Vista.  
   
  ]]></format>
         </remarks>
@@ -468,7 +468,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A single retry cycle makes repeated attempts to deliver a message to the receiving application (specified by the <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> property). If all attempts fail, the message is placed back in the retry queue. This property specifies how long the message remains in the retry queue before it is transferred to the application queue for another retry cycle. This property can only be used on operating systems starting with [!INCLUDE[wv](~/includes/wv-md.md)].  
+ A single retry cycle makes repeated attempts to deliver a message to the receiving application (specified by the <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> property). If all attempts fail, the message is placed back in the retry queue. This property specifies how long the message remains in the retry queue before it is transferred to the application queue for another retry cycle. This property can only be used on operating systems starting with Windows Vista.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
index 8ab677babe8..1ca7a0c6a9a 100644
--- a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
@@ -736,7 +736,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).  
   
- This property is applicable only on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
+ This property is applicable only on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
   
    
   
diff --git a/xml/System.ServiceModel.Configuration/MsmqBindingElementBase.xml b/xml/System.ServiceModel.Configuration/MsmqBindingElementBase.xml
index 27a5893cfab..6839a7a9f4a 100644
--- a/xml/System.ServiceModel.Configuration/MsmqBindingElementBase.xml
+++ b/xml/System.ServiceModel.Configuration/MsmqBindingElementBase.xml
@@ -350,7 +350,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A *retry cycle* is when a message is transferred from the retry queue to the application queue to attempt delivery to the application. Messages are placed in the retry queue after failing a number of immediate retries as specified by <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.ReceiveRetryCount%2A>. <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> specifies the number of retry cycles and does not include the initial attempt to send the message. An attempt to deliver a message is made a maximum of (1 + MaxRetryCycles) * (ReceiveRetryCount + 1) times. For example, if ReceiveRetryCount = 0 and MaxRetryCycles is 1, there is a maximum of two attempts to deliver the message. This property is available starting with the [!INCLUDE[wv](~/includes/wv-md.md)] operating system.  
+ A *retry cycle* is when a message is transferred from the retry queue to the application queue to attempt delivery to the application. Messages are placed in the retry queue after failing a number of immediate retries as specified by <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.ReceiveRetryCount%2A>. <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> specifies the number of retry cycles and does not include the initial attempt to send the message. An attempt to deliver a message is made a maximum of (1 + MaxRetryCycles) * (ReceiveRetryCount + 1) times. For example, if ReceiveRetryCount = 0 and MaxRetryCycles is 1, there is a maximum of two attempts to deliver the message. This property is available starting with the Windows Vista operating system.  
   
  ]]></format>
         </remarks>
@@ -561,7 +561,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A single retry cycle makes repeated attempts to deliver a message to the receiving application (specified by the <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> property). If all attempts fail, the message is placed back in the retry queue. This property specifies how long the message remains in the retry queue before it is transferred to the application queue for another retry cycle. This property is available starting with the [!INCLUDE[wv](~/includes/wv-md.md)] or later operating systems.  
+ A single retry cycle makes repeated attempts to deliver a message to the receiving application (specified by the <xref:System.ServiceModel.Configuration.MsmqBindingElementBase.MaxRetryCycles%2A> property). If all attempts fail, the message is placed back in the retry queue. This property specifies how long the message remains in the retry queue before it is transferred to the application queue for another retry cycle. This property is available starting with the Windows Vista or later operating systems.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
index a2d90eb028b..0b2d62ff856 100644
--- a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
+++ b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
@@ -364,7 +364,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).  
   
- This property is only applicable on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. [!INCLUDE[wv](~/includes/wv-md.md)] has a machine-wide configuration option for Teredo, so when running [!INCLUDE[wv](~/includes/wv-md.md)], this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
+ This property is only applicable on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel/AuditLogLocation.xml b/xml/System.ServiceModel/AuditLogLocation.xml
index 307d5c074c1..b2861a2ba27 100644
--- a/xml/System.ServiceModel/AuditLogLocation.xml
+++ b/xml/System.ServiceModel/AuditLogLocation.xml
@@ -91,7 +91,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on [!INCLUDE[wv](~/includes/wv-md.md)] and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)]), the default log location is the Application log.</summary>
+        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on Windows Vista and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)]), the default log location is the Application log.</summary>
       </Docs>
     </Member>
     <Member MemberName="Security">
diff --git a/xml/System.ServiceModel/MsmqBindingBase.xml b/xml/System.ServiceModel/MsmqBindingBase.xml
index 951af017ea1..883950d7c93 100644
--- a/xml/System.ServiceModel/MsmqBindingBase.xml
+++ b/xml/System.ServiceModel/MsmqBindingBase.xml
@@ -369,9 +369,9 @@
   
  When this property is set to <xref:System.ServiceModel.ReceiveErrorHandling.Drop>, the poison message is dropped.  
   
- When this property is set to <xref:System.ServiceModel.ReceiveErrorHandling.Reject>, a negative acknowledgement is sent to the client and the poison message is removed from the queue. This option is available only on Message Queuing 4.0 and requires [!INCLUDE[wv](~/includes/wv-md.md)].  
+ When this property is set to <xref:System.ServiceModel.ReceiveErrorHandling.Reject>, a negative acknowledgement is sent to the client and the poison message is removed from the queue. This option is available only on Message Queuing 4.0 and requires Windows Vista.  
   
- When set to <xref:System.ServiceModel.ReceiveErrorHandling.Move>, the poison message is moved to the final poison subqueue. This option is only available on Message Queuing 4.0 and requires [!INCLUDE[wv](~/includes/wv-md.md)].  
+ When set to <xref:System.ServiceModel.ReceiveErrorHandling.Move>, the poison message is moved to the final poison subqueue. This option is only available on Message Queuing 4.0 and requires Windows Vista.  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel/MsmqSecureHashAlgorithm.xml b/xml/System.ServiceModel/MsmqSecureHashAlgorithm.xml
index 377059cd29e..4a05bcaa3ca 100644
--- a/xml/System.ServiceModel/MsmqSecureHashAlgorithm.xml
+++ b/xml/System.ServiceModel/MsmqSecureHashAlgorithm.xml
@@ -22,7 +22,7 @@
 ## Remarks  
  Message Queuing can secure messages by signing them. The <xref:System.ServiceModel.MsmqSecureHashAlgorithm> class is an enumeration that contains the hashing algorithms that Message Queuing can use to sign messages.  
   
- Sha256 and Sha512 are supported only on [!INCLUDE[wv](~/includes/wv-md.md)].  
+ Sha256 and Sha512 are supported only on Windows Vista.  
   
  ]]></format>
     </remarks>
diff --git a/xml/System.ServiceModel/ReceiveErrorHandling.xml b/xml/System.ServiceModel/ReceiveErrorHandling.xml
index 4b4ed7ab449..90fa0a7c0cf 100644
--- a/xml/System.ServiceModel/ReceiveErrorHandling.xml
+++ b/xml/System.ServiceModel/ReceiveErrorHandling.xml
@@ -20,7 +20,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A *poison message* is a message that fails repeated attempts to deliver to the application. This is applicable only when using a Message Queuing (MSMQ)-based binding. The default value is `Fault`, which faults the listener and therefore the ServiceHost. In the case where the service was to fault because of a poison message, a <xref:System.ServiceModel.MsmqPoisonMessageException> is thrown. The exception contains the `LookupId` of the MSMQ message that can be used to move the message out of the way using System.Messaging API. Certain values of the <xref:System.ServiceModel.ReceiveErrorHandling> enumeration such as `Reject` and `Move` are only available on [!INCLUDE[wv](~/includes/wv-md.md)]. You control poison message handling by setting the <xref:System.ServiceModel.Channels.MsmqBindingElementBase.ReceiveErrorHandling%2A> property to one of the values of this enumeration.  
+ A *poison message* is a message that fails repeated attempts to deliver to the application. This is applicable only when using a Message Queuing (MSMQ)-based binding. The default value is `Fault`, which faults the listener and therefore the ServiceHost. In the case where the service was to fault because of a poison message, a <xref:System.ServiceModel.MsmqPoisonMessageException> is thrown. The exception contains the `LookupId` of the MSMQ message that can be used to move the message out of the way using System.Messaging API. Certain values of the <xref:System.ServiceModel.ReceiveErrorHandling> enumeration such as `Reject` and `Move` are only available on Windows Vista. You control poison message handling by setting the <xref:System.ServiceModel.Channels.MsmqBindingElementBase.ReceiveErrorHandling%2A> property to one of the values of this enumeration.  
   
    
   

From 32db3f6ee1bd5d2add4f0e44c1a548bf8a319157 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:56:57 -0800
Subject: [PATCH 228/236] wxp

---
 xml/System.ServiceModel.Channels/SecurityBindingElement.xml | 4 ++--
 xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml         | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.ServiceModel.Channels/SecurityBindingElement.xml b/xml/System.ServiceModel.Channels/SecurityBindingElement.xml
index a8a74a170ef..317051fece5 100644
--- a/xml/System.ServiceModel.Channels/SecurityBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/SecurityBindingElement.xml
@@ -1248,7 +1248,7 @@
  Otherwise, a <xref:System.ServiceModel.Channels.SymmetricSecurityBindingElement> is returned, with <xref:System.ServiceModel.Channels.SymmetricSecurityBindingElement.RequireSignatureConfirmation%2A> set to `false`.  
   
 > [!NOTE]
->  When impersonation is required on [!INCLUDE[wxp](~/includes/wxp-md.md)], use a secure session without a security context token. When security context tokens are used with impersonation an <xref:System.InvalidOperationException> is thrown. For more information, see [Unsupported Scenarios](/dotnet/framework/wcf/feature-details/unsupported-scenarios). For more information about secure sessions, see [Secure Sessions](/dotnet/framework/wcf/feature-details/secure-sessions).  
+>  When impersonation is required on Windows XP, use a secure session without a security context token. When security context tokens are used with impersonation an <xref:System.InvalidOperationException> is thrown. For more information, see [Unsupported Scenarios](/dotnet/framework/wcf/feature-details/unsupported-scenarios). For more information about secure sessions, see [Secure Sessions](/dotnet/framework/wcf/feature-details/secure-sessions).  
   
    
   
@@ -1308,7 +1308,7 @@
  Otherwise, a <xref:System.ServiceModel.Channels.SymmetricSecurityBindingElement> is returned, with <xref:System.ServiceModel.Channels.SymmetricSecurityBindingElement.RequireSignatureConfirmation%2A> set to `false`.  
   
 > [!NOTE]
->  When impersonation is required on [!INCLUDE[wxp](~/includes/wxp-md.md)], use a secure session without a security context token. When security context tokens are used with impersonation an <xref:System.InvalidOperationException> is thrown. For more information, see [Unsupported Scenarios](/dotnet/framework/wcf/feature-details/unsupported-scenarios). For more information about secure sessions, see [Secure Sessions](/dotnet/framework/wcf/feature-details/secure-sessions).  
+>  When impersonation is required on Windows XP, use a secure session without a security context token. When security context tokens are used with impersonation an <xref:System.InvalidOperationException> is thrown. For more information, see [Unsupported Scenarios](/dotnet/framework/wcf/feature-details/unsupported-scenarios). For more information about secure sessions, see [Secure Sessions](/dotnet/framework/wcf/feature-details/secure-sessions).  
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml b/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
index 7123dc5bc5d..be2baf5e433 100644
--- a/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
+++ b/xml/System.ServiceModel/MsmqEncryptionAlgorithm.xml
@@ -24,7 +24,7 @@
   
  For encryption to work, the <xref:System.ServiceModel.MsmqTransportSecurity.MsmqProtectionLevel%2A> property must be set to <xref:System.Net.Security.ProtectionLevel.EncryptAndSign>.  
   
- Only RC4Stream is supported on Windows Server 2003 and [!INCLUDE[wxp](~/includes/wxp-md.md)].  
+ Only RC4Stream is supported on Windows Server 2003 and Windows XP.  
   
  ]]></format>
     </remarks>

From 11572e2b7d7a397758a7a812ffc99cd232c34739 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:57:19 -0800
Subject: [PATCH 229/236] wxpsp2

---
 xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml | 2 +-
 xml/System.ServiceModel.Configuration/TcpTransportElement.xml   | 2 +-
 xml/System.ServiceModel/AuditLogLocation.xml                    | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
index 1ca7a0c6a9a..f1a57ff4595 100644
--- a/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
+++ b/xml/System.ServiceModel.Channels/TcpTransportBindingElement.xml
@@ -736,7 +736,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).  
   
- This property is applicable only on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
+ This property is applicable only on Windows XP SP2 and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96649).
   
    
   
diff --git a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
index 0b2d62ff856..dc053f7562d 100644
--- a/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
+++ b/xml/System.ServiceModel.Configuration/TcpTransportElement.xml
@@ -364,7 +364,7 @@
 ## Remarks  
  This property enables Teredo for the underlying TCP socket. For more information, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).  
   
- This property is only applicable on [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)] and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
+ This property is only applicable on Windows XP SP2 and Windows Server 2003. Windows Vista has a machine-wide configuration option for Teredo, so when running Windows Vista, this property is ignored. Teredo requires that the client and service machines both have the Microsoft IPv6 stack installed and correctly configured for Teredo usage. For more information about configuring Teredo, see [Teredo Overview](https://go.microsoft.com/fwlink/?LinkId=96651).
   
  ]]></format>
         </remarks>
diff --git a/xml/System.ServiceModel/AuditLogLocation.xml b/xml/System.ServiceModel/AuditLogLocation.xml
index b2861a2ba27..3eeae053afd 100644
--- a/xml/System.ServiceModel/AuditLogLocation.xml
+++ b/xml/System.ServiceModel/AuditLogLocation.xml
@@ -91,7 +91,7 @@
       </ReturnValue>
       <MemberValue>0</MemberValue>
       <Docs>
-        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on Windows Vista and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in [!INCLUDE[wxpsp2](~/includes/wxpsp2-md.md)]), the default log location is the Application log.</summary>
+        <summary>Specifies the default location, which is determined by the operating system. If writing to the Security log is supported (such as on Windows Vista and Windows Server 2003 and later platforms), the default log location is the Security log. Otherwise (such as in Windows XP SP2), the default log location is the Application log.</summary>
       </Docs>
     </Member>
     <Member MemberName="Security">

From c92d26fc3c4d2a54b23b0b88acffb963cc373d2b Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 14:57:42 -0800
Subject: [PATCH 230/236] xaml2009

---
 xml/System.Xaml/XamlLanguage.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Xaml/XamlLanguage.xml b/xml/System.Xaml/XamlLanguage.xml
index b8d1e4813e3..82d7aed84f6 100644
--- a/xml/System.Xaml/XamlLanguage.xml
+++ b/xml/System.Xaml/XamlLanguage.xml
@@ -100,7 +100,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A factory method is a [!INCLUDE[xaml2009](~/includes/xaml2009-md.md)] feature for identifying an alternative technique that constructs the underlying type for a XAML type. The `Arguments` specify the input of a factory method and enable specifying that information in markup. The default techniques, in absence of a factory method, are to attempt to find a parameterless constructor and then attempt to find an identified type converter for type, member, or destination type.  
+ A factory method is a XAML2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The `Arguments` specify the input of a factory method and enable specifying that information in markup. The default techniques, in absence of a factory method, are to attempt to find a parameterless constructor and then attempt to find an identified type converter for type, member, or destination type.  
   
  For the generic usage, the `Arguments` wrap the objects or initialization text of all construction inputs that are specified as necessary for the `TypeArguments`.  
   
@@ -160,7 +160,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `AsyncRecords` concept is part of [!INCLUDE[xaml2009](~/includes/xaml2009-md.md)]. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
+ The `AsyncRecords` concept is part of XAML2009. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This directive is part of [!INCLUDE[xaml2009](~/includes/xaml2009-md.md)]. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
+ This directive is part of XAML2009. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
   
  ]]></format>
         </remarks>
@@ -501,7 +501,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A factory method is a [!INCLUDE[xaml2009](~/includes/xaml2009-md.md)] feature for identifying an alternative technique that constructs the underlying type for a XAML type. The default technique, if a factory method is unavailable, is to try to find a parameterless constructor, and then try to find an identified type converter on type, member, or destination type.  
+ A factory method is a XAML2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The default technique, if a factory method is unavailable, is to try to find a parameterless constructor, and then try to find an identified type converter on type, member, or destination type.  
   
  ]]></format>
         </remarks>
@@ -973,7 +973,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `Reference` is a [!INCLUDE[xaml2009](~/includes/xaml2009-md.md)] feature for referencing another object node in the markup. The implementation for .NET Framework XAML Services is found in <xref:System.Windows.Markup.Reference?displayProperty=nameWithType>.  
+ `Reference` is a XAML2009 feature for referencing another object node in the markup. The implementation for .NET Framework XAML Services is found in <xref:System.Windows.Markup.Reference?displayProperty=nameWithType>.  
   
  ]]></format>
         </remarks>

From a1ee9be35fc7bb07060c39a511dee2bdee2926dc Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 15:11:39 -0800
Subject: [PATCH 231/236] tlasharptla-iptc

---
 xml/System.Windows.Media.Imaging/BitmapMetadata.xml    | 10 +++++-----
 .../BitmapMetadataBlob.xml                             |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
index af9a753fda6..c15ca7e8754 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadata.xml
@@ -31,7 +31,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but is not necessary to display the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
  If a <xref:System.Windows.Media.Imaging.BitmapMetadata> is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that is obtained by using a <xref:System.Windows.Media.Imaging.BitmapDecoder>, it is read-only by default and mutable operations will throw an exception. If it is exposed by a <xref:System.Windows.Media.Imaging.BitmapFrame> that wraps another <xref:System.Windows.Media.Imaging.BitmapSource>, it is mutable on construction.  
   
@@ -433,7 +433,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
  ]]></format>
         </remarks>
@@ -691,7 +691,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
    
   
@@ -910,7 +910,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
  ]]></format>
         </remarks>
@@ -960,7 +960,7 @@
 ## Remarks  
  Metadata that is associated with an image is data that describes the image but that is not necessary for display of the image. Each supported bitmap image format handles metadata differently, but the facility for reading and writing metadata is the same.  
   
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
    
   
diff --git a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
index 7b399c15945..8cd4d29eb9d 100644
--- a/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
+++ b/xml/System.Windows.Media.Imaging/BitmapMetadataBlob.xml
@@ -21,7 +21,7 @@
       <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), [!INCLUDE[TLA#tla_iptc](~/includes/tlasharptla-iptc-md.md)], and Extensible Metadata Platform (XMP).  
+ Windows Presentation Foundation (WPF) supports the following image metadata schemas: Exchangeable image file (Exif), tEXt (PNG Textual Data), image file directory (IFD), International Press Telecommunications Council (IPTC), and Extensible Metadata Platform (XMP).  
   
  ]]></format>
     </remarks>

From 8aacec6aca5ba010f3b5f02be51d9cb6c7ba4a4c Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 15:12:12 -0800
Subject: [PATCH 232/236] winxpfamily

---
 xml/System.Windows.Forms/Clipboard.xml    |  6 +++---
 xml/System.Windows.Forms/ListViewItem.xml | 24 +++++++++++------------
 xml/System.Windows.Forms/PrintDialog.xml  |  2 +-
 xml/System.Windows.Forms/ProgressBar.xml  |  2 +-
 4 files changed, 17 insertions(+), 17 deletions(-)

diff --git a/xml/System.Windows.Forms/Clipboard.xml b/xml/System.Windows.Forms/Clipboard.xml
index 418d4f27853..0f8e535ae4f 100644
--- a/xml/System.Windows.Forms/Clipboard.xml
+++ b/xml/System.Windows.Forms/Clipboard.xml
@@ -349,7 +349,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on Windows XP Home Edition, Windows XP Professional, Windows Server 2003 and Windows 2000. Otherwise, this method checks for the presence of data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  Use this method to determine whether the Clipboard contains text data before retrieving it with the <xref:System.Windows.Forms.Clipboard.GetText%2A> method.  
   
@@ -732,7 +732,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method returns text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method returns text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method returns text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on Windows XP Home Edition, Windows XP Professional, Windows Server 2003 and Windows 2000. Otherwise, this method returns text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  Use the <xref:System.Windows.Forms.Clipboard.ContainsText%2A> method to determine whether the Clipboard contains text data before retrieving it with this method.  
   
@@ -1345,7 +1345,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This method adds text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and Windows 2000. Otherwise, this method adds text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
+ This method adds text data in the <xref:System.Windows.Forms.TextDataFormat.UnicodeText> format on Windows XP Home Edition, Windows XP Professional, Windows Server 2003 and Windows 2000. Otherwise, this method adds text data in the <xref:System.Windows.Forms.TextDataFormat.Text> format.  
   
  To retrieve text data from the Clipboard, first use the <xref:System.Windows.Forms.Clipboard.ContainsText%2A> method to determine whether the Clipboard contains text data before retrieving it with the <xref:System.Windows.Forms.Clipboard.GetText%2A> method.  
   
diff --git a/xml/System.Windows.Forms/ListViewItem.xml b/xml/System.Windows.Forms/ListViewItem.xml
index bce79bec13e..eeeea0852ec 100644
--- a/xml/System.Windows.Forms/ListViewItem.xml
+++ b/xml/System.Windows.Forms/ListViewItem.xml
@@ -241,7 +241,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -372,7 +372,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  The text of the <xref:System.Windows.Forms.ListViewItem> should not exceed 259 characters or unexpected behavior could occur.  
   
@@ -471,7 +471,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -578,7 +578,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  The text of the <xref:System.Windows.Forms.ListViewItem> should not exceed 259 characters or unexpected behavior could occur.  
   
@@ -622,7 +622,7 @@
  The `imageKey` parameter specifies an image in the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> associated with the owning <xref:System.Windows.Forms.ListView> control, which can be accessed with the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> property.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  The text of the <xref:System.Windows.Forms.ListViewItem> should not exceed 259 characters or unexpected behavior could occur.  
   
@@ -661,7 +661,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -703,7 +703,7 @@
  The `imageKey` parameter specifies an image in the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> associated with the owning <xref:System.Windows.Forms.ListView> control, which can be accessed with the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> property.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -740,7 +740,7 @@
  This version of the constructor is useful when you create <xref:System.Windows.Forms.ListViewItem.ListViewSubItem> objects before adding them to a <xref:System.Windows.Forms.ListViewItem> object (for example, to indicate special formatting or to use the subitems in multiple items). It also allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -783,7 +783,7 @@
  The `imageKey` parameter specifies an image in the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> associated with the owning <xref:System.Windows.Forms.ListView> control, which can be accessed with the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> property.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -911,7 +911,7 @@
  This version of the constructor allows you to specify the group to which an item belongs.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -961,7 +961,7 @@
  The `imageKey` parameter specifies an image in the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> associated with the owning <xref:System.Windows.Forms.ListView> control, which can be accessed with the <xref:System.Windows.Forms.ListViewItem.ImageList%2A> property.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
  ]]></format>
         </remarks>
@@ -1565,7 +1565,7 @@ ListViewItem1.Font = New Font(ListViewItem1.Font, _
  Use this property to set the group to which an item belongs. You can also set the group in the <xref:System.Windows.Forms.ListViewItem.%23ctor%2A> constructor, or you can use this property to modify the group membership at run time. If you set this property to `null` and there are groups in the <xref:System.Windows.Forms.ListView.Groups%2A?displayProperty=nameWithType> collection, the item will appear in the default group, which has the header label "DefaultGroupSystem.Windows.Forms". The default group is not contained in the <xref:System.Windows.Forms.ListView.Groups%2A?displayProperty=nameWithType> collection, and cannot be altered. It is primarily useful in debugging to ensure that all items have been properly added to groups.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family ([!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)]). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
+>  <xref:System.Windows.Forms.ListView> groups are only available on Windows XP and the Windows Server 2003 family (Windows XP Home Edition, Windows XP Professional, Windows Server 2003). For more information, see the <xref:System.Windows.Forms.ListViewGroup> overview topic.  
   
    
   
diff --git a/xml/System.Windows.Forms/PrintDialog.xml b/xml/System.Windows.Forms/PrintDialog.xml
index 0820d40ddc3..8eeec64515e 100644
--- a/xml/System.Windows.Forms/PrintDialog.xml
+++ b/xml/System.Windows.Forms/PrintDialog.xml
@@ -597,7 +597,7 @@
         <ReturnType>System.Boolean</ReturnType>
       </ReturnValue>
       <Docs>
-        <summary>Gets or sets a value indicating whether the dialog should be shown in the Windows XP style for systems running [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] or later.</summary>
+        <summary>Gets or sets a value indicating whether the dialog should be shown in the Windows XP style for systems running Windows XP Home Edition, Windows XP Professional, Windows Server 2003 or later.</summary>
         <value>
           <see langword="true" /> to indicate the dialog should be shown with the Windows XP style, otherwise <see langword="false" />. The default is <see langword="false" />.</value>
         <remarks>
diff --git a/xml/System.Windows.Forms/ProgressBar.xml b/xml/System.Windows.Forms/ProgressBar.xml
index fa4874bf230..32e2e04eb8a 100644
--- a/xml/System.Windows.Forms/ProgressBar.xml
+++ b/xml/System.Windows.Forms/ProgressBar.xml
@@ -61,7 +61,7 @@
  There are a number of ways to modify the value displayed by the <xref:System.Windows.Forms.ProgressBar> other than changing the <xref:System.Windows.Forms.ProgressBar.Value%2A> property directly. You can use the <xref:System.Windows.Forms.ProgressBar.Step%2A> property to specify a specific value to increment the <xref:System.Windows.Forms.ProgressBar.Value%2A> property by, and then call the <xref:System.Windows.Forms.ProgressBar.PerformStep%2A> method to increment the value. To vary the increment value, you can use the <xref:System.Windows.Forms.ProgressBar.Increment%2A> method and specify a value with which to increment the <xref:System.Windows.Forms.ProgressBar.Value%2A> property.  
   
 > [!NOTE]
->  <xref:System.Windows.Forms.Control.ForeColor%2A> and <xref:System.Windows.Forms.Control.BackColor%2A> changes for the <xref:System.Windows.Forms.ProgressBar> will not be honored when visual styles are enabled on [!INCLUDE[WinXpFamily](~/includes/winxpfamily-md.md)] and above.  
+>  <xref:System.Windows.Forms.Control.ForeColor%2A> and <xref:System.Windows.Forms.Control.BackColor%2A> changes for the <xref:System.Windows.Forms.ProgressBar> will not be honored when visual styles are enabled on Windows XP Home Edition, Windows XP Professional, Windows Server 2003 and above.  
   
    
   

From a23ac9d822177ba0eb4ff71fda6950c29f5703a9 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 15:17:55 -0800
Subject: [PATCH 233/236] Deleting md files with contents with length 50-80
 chars

---
 includes/tlasharptla-iptc-md.md | 1 -
 includes/winxpfamily-md.md      | 1 -
 2 files changed, 2 deletions(-)
 delete mode 100644 includes/tlasharptla-iptc-md.md
 delete mode 100644 includes/winxpfamily-md.md

diff --git a/includes/tlasharptla-iptc-md.md b/includes/tlasharptla-iptc-md.md
deleted file mode 100644
index ee25250a1cf..00000000000
--- a/includes/tlasharptla-iptc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-International Press Telecommunications Council (IPTC)
\ No newline at end of file
diff --git a/includes/winxpfamily-md.md b/includes/winxpfamily-md.md
deleted file mode 100644
index 6cb77eb13b5..00000000000
--- a/includes/winxpfamily-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows XP Home Edition, Windows XP Professional, Windows Server 2003
\ No newline at end of file

From dc2de0fc3e7af10179167c13867b5a7d98e5da35 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 15:35:41 -0800
Subject: [PATCH 234/236] Deleting md files with contents with length up to 50
 chars

---
 includes/ado-whidbey-long-md.md                     | 1 -
 includes/adonet-edm-md.md                           | 1 -
 includes/adonet-ef-md.md                            | 1 -
 includes/ajax-current-short-md.md                   | 1 -
 includes/compact-md.md                              | 1 -
 includes/cpp-iter-arg-md.md                         | 1 -
 includes/csprcslong-md.md                           | 1 -
 includes/desktop-appname-md.md                      | 1 -
 includes/dnprdnext-md.md                            | 1 -
 includes/dnprdnlong-md.md                           | 1 -
 includes/dnprdnshort-md.md                          | 1 -
 includes/dp-id-field-label-md.md                    | 1 -
 includes/esql-md.md                                 | 1 -
 includes/iisver-md.md                               | 1 -
 includes/infocard-md.md                             | 1 -
 includes/linq-dataset-md.md                         | 1 -
 includes/ndptecclick-md.md                          | 1 -
 includes/ndptecgdi-md.md                            | 1 -
 includes/ndptecgdiplus-md.md                        | 1 -
 includes/net-client-v40-long-md.md                  | 1 -
 includes/net-core-md.md                             | 1 -
 includes/net-native-md.md                           | 1 -
 includes/net-portable-md.md                         | 1 -
 includes/net-v10-short-md.md                        | 1 -
 includes/net-v11-long-md.md                         | 1 -
 includes/net-v11-short-md.md                        | 1 -
 includes/net-v20sp1-long-md.md                      | 1 -
 includes/net-v20sp1-short-md.md                     | 1 -
 includes/net-v30-long-md.md                         | 1 -
 includes/net-v30-short-md.md                        | 1 -
 includes/net-v35-long-md.md                         | 1 -
 includes/net-v35-short-md.md                        | 1 -
 includes/net-v35sp1-long-md.md                      | 1 -
 includes/net-v35sp1-short-md.md                     | 1 -
 includes/net-v40-long-md.md                         | 1 -
 includes/net-v40-short-md.md                        | 1 -
 includes/net-v45-md.md                              | 1 -
 includes/net-v451-md.md                             | 1 -
 includes/net-v452-md.md                             | 1 -
 includes/net-v46-md.md                              | 1 -
 includes/net-v461-md.md                             | 1 -
 includes/net-v462-md.md                             | 1 -
 includes/net-v463-md.md                             | 1 -
 includes/net-win8-profile-md.md                     | 1 -
 includes/netfx35-long-md.md                         | 1 -
 includes/netfx35-short-md.md                        | 1 -
 includes/netfx40-long-md.md                         | 1 -
 includes/netfx40-short-md.md                        | 1 -
 includes/ofprword-md.md                             | 1 -
 includes/sil3-first-md.md                           | 1 -
 includes/silverlight-md.md                          | 1 -
 includes/sqltecxlinq-md.md                          | 1 -
 includes/sqprsqlong-md.md                           | 1 -
 includes/ss2k-md.md                                 | 1 -
 includes/ssastoria-md.md                            | 1 -
 includes/ssew-md.md                                 | 1 -
 includes/sskatmai-r2-md.md                          | 1 -
 includes/ssodatashort-md.md                         | 1 -
 includes/tla2sharptla-2d-md.md                      | 1 -
 includes/tla2sharptla-3d-md.md                      | 1 -
 includes/tla2sharptla-baml-md.md                    | 1 -
 includes/tla2sharptla-bpp-md.md                     | 1 -
 includes/tla2sharptla-caf-md.md                     | 1 -
 includes/tla2sharptla-clr-md.md                     | 1 -
 includes/tla2sharptla-com-md.md                     | 1 -
 includes/tla2sharptla-dpi-md.md                     | 1 -
 includes/tla2sharptla-dx-md.md                      | 1 -
 includes/tla2sharptla-exif-md.md                    | 1 -
 includes/tla2sharptla-gui-md.md                     | 1 -
 includes/tla2sharptla-html-md.md                    | 1 -
 includes/tla2sharptla-idsharpplural-md.md           | 1 -
 includes/tla2sharptla-ie6-md.md                     | 1 -
 includes/tla2sharptla-ie7-md.md                     | 1 -
 includes/tla2sharptla-iegeneric-md.md               | 1 -
 includes/tla2sharptla-mime-md.md                    | 1 -
 includes/tla2sharptla-net-md.md                     | 1 -
 includes/tla2sharptla-netframewkattr-md.md          | 1 -
 includes/tla2sharptla-opentype-md.md                | 1 -
 includes/tla2sharptla-passport-md.md                | 1 -
 includes/tla2sharptla-png-md.md                     | 1 -
 includes/tla2sharptla-riff-md.md                    | 1 -
 includes/tla2sharptla-sdk-md.md                     | 1 -
 includes/tla2sharptla-tiff-md.md                    | 1 -
 includes/tla2sharptla-titlexaml-md.md               | 1 -
 includes/tla2sharptla-tpc-md.md                     | 1 -
 includes/tla2sharptla-ui-md.md                      | 1 -
 includes/tla2sharptla-uiautomation-md.md            | 1 -
 includes/tla2sharptla-url-md.md                     | 1 -
 includes/tla2sharptla-wdp-md.md                     | 1 -
 includes/tla2sharptla-win32-md.md                   | 1 -
 includes/tla2sharptla-winclient-md.md               | 1 -
 includes/tla2sharptla-winvista-md.md                | 1 -
 includes/tla2sharptla-wpf-md.md                     | 1 -
 includes/tla2sharptla-xaml-md.md                    | 1 -
 includes/tla2sharptla-xbap-md.md                    | 1 -
 includes/tla2sharptla-xbapsharpplural-md.md         | 1 -
 includes/tla2sharptla-xml-md.md                     | 1 -
 includes/tla2sharptla-xps-md.md                     | 1 -
 includes/tla2sharptla-xrml-md.md                    | 1 -
 includes/tlasharptla-2d-md.md                       | 1 -
 includes/tlasharptla-3d-md.md                       | 1 -
 includes/tlasharptla-aa-md.md                       | 1 -
 includes/tlasharptla-adonet-md.md                   | 1 -
 includes/tlasharptla-aero-md.md                     | 1 -
 includes/tlasharptla-argb-md.md                     | 1 -
 includes/tlasharptla-ascii-md.md                    | 1 -
 includes/tlasharptla-baml-md.md                     | 1 -
 includes/tlasharptla-bmp-md.md                      | 1 -
 includes/tlasharptla-bpp-md.md                      | 1 -
 includes/tlasharptla-caf-md.md                      | 1 -
 includes/tlasharptla-cas-md.md                      | 1 -
 includes/tlasharptla-clickonce-md.md                | 1 -
 includes/tlasharptla-clr-md.md                      | 1 -
 includes/tlasharptla-com-md.md                      | 1 -
 includes/tlasharptla-dhtml-md.md                    | 1 -
 includes/tlasharptla-dipixel-md.md                  | 1 -
 includes/tlasharptla-dipixelsharpplural-md.md       | 1 -
 includes/tlasharptla-dll-md.md                      | 1 -
 includes/tlasharptla-dpi-md.md                      | 1 -
 includes/tlasharptla-emf-md.md                      | 1 -
 includes/tlasharptla-exif-md.md                     | 1 -
 includes/tlasharptla-gdi-md.md                      | 1 -
 includes/tlasharptla-gif-md.md                      | 1 -
 includes/tlasharptla-gui-md.md                      | 1 -
 includes/tlasharptla-html-md.md                     | 1 -
 includes/tlasharptla-icc-md.md                      | 1 -
 includes/tlasharptla-icm-md.md                      | 1 -
 includes/tlasharptla-id-md.md                       | 1 -
 includes/tlasharptla-idsharpplural-md.md            | 1 -
 includes/tlasharptla-ie-md.md                       | 1 -
 includes/tlasharptla-ie6-md.md                      | 1 -
 includes/tlasharptla-ie7-md.md                      | 1 -
 includes/tlasharptla-iegeneric-md.md                | 1 -
 includes/tlasharptla-ifd-md.md                      | 1 -
 includes/tlasharptla-ime-md.md                      | 1 -
 includes/tlasharptla-isf-md.md                      | 1 -
 includes/tlasharptla-isv-md.md                      | 1 -
 includes/tlasharptla-jpeg-md.md                     | 1 -
 includes/tlasharptla-jpegorg-md.md                  | 1 -
 includes/tlasharptla-longhorn-md.md                 | 1 -
 includes/tlasharptla-mdi-md.md                      | 1 -
 includes/tlasharptla-mime-md.md                     | 1 -
 includes/tlasharptla-msbuild-md.md                  | 1 -
 includes/tlasharptla-mswin-md.md                    | 1 -
 includes/tlasharptla-net-md.md                      | 1 -
 includes/tlasharptla-netframewkattr-md.md           | 1 -
 includes/tlasharptla-opentype-md.md                 | 1 -
 includes/tlasharptla-outlook-md.md                  | 1 -
 includes/tlasharptla-passport-md.md                 | 1 -
 includes/tlasharptla-png-md.md                      | 1 -
 includes/tlasharptla-riff-md.md                     | 1 -
 includes/tlasharptla-rtf-md.md                      | 1 -
 includes/tlasharptla-sha1-md.md                     | 1 -
 includes/tlasharptla-tiff-md.md                     | 1 -
 includes/tlasharptla-titlewinclient-md.md           | 1 -
 includes/tlasharptla-titlexaml-md.md                | 1 -
 includes/tlasharptla-tpc-md.md                      | 1 -
 includes/tlasharptla-ui-md.md                       | 1 -
 includes/tlasharptla-uiautomation-md.md             | 1 -
 includes/tlasharptla-uiautomationsharpinitcap-md.md | 1 -
 includes/tlasharptla-unc-md.md                      | 1 -
 includes/tlasharptla-unicode-md.md                  | 1 -
 includes/tlasharptla-url-md.md                      | 1 -
 includes/tlasharptla-visualstu-md.md                | 1 -
 includes/tlasharptla-wdp-md.md                      | 1 -
 includes/tlasharptla-win-md.md                      | 1 -
 includes/tlasharptla-win32-md.md                    | 1 -
 includes/tlasharptla-winclient-md.md                | 1 -
 includes/tlasharptla-winexpl-md.md                  | 1 -
 includes/tlasharptla-winforms-md.md                 | 1 -
 includes/tlasharptla-winfxwebapp-md.md              | 1 -
 includes/tlasharptla-winvista-md.md                 | 1 -
 includes/tlasharptla-wmp-md.md                      | 1 -
 includes/tlasharptla-word-md.md                     | 1 -
 includes/tlasharptla-wys-md.md                      | 1 -
 includes/tlasharptla-xaml-md.md                     | 1 -
 includes/tlasharptla-xbap-md.md                     | 1 -
 includes/tlasharptla-xbapsharpplural-md.md          | 1 -
 includes/tlasharptla-xl-md.md                       | 1 -
 includes/tlasharptla-xml-md.md                      | 1 -
 includes/tlasharptla-xmldom-md.md                   | 1 -
 includes/tlasharptla-xmp-md.md                      | 1 -
 includes/tlasharptla-xps-md.md                      | 1 -
 includes/tlasharptla-xrml-md.md                     | 1 -
 includes/tlasharptla-xsd-md.md                      | 1 -
 includes/tsql-md.md                                 | 1 -
 includes/vb-orcas-long-md.md                        | 1 -
 includes/vbprvbext-md.md                            | 1 -
 includes/vbprvblong-md.md                           | 1 -
 includes/vbtecdlinq-md.md                           | 1 -
 includes/vbteclinq-md.md                            | 1 -
 includes/vbteclinqext-md.md                         | 1 -
 includes/vcprvc-md.md                               | 1 -
 includes/vcprvclong-md.md                           | 1 -
 includes/vs-dev10-long-md.md                        | 1 -
 includes/vs-orcas-ext-md.md                         | 1 -
 includes/vs-orcas-long-md.md                        | 1 -
 includes/vs-ordesigner-long-md.md                   | 1 -
 includes/vs-ordesigner-short-md.md                  | 1 -
 includes/vs2010-md.md                               | 1 -
 includes/vsprvsext-md.md                            | 1 -
 includes/vsprvslong-md.md                           | 1 -
 includes/vstecado-md.md                             | 1 -
 includes/vstecasp-md.md                             | 1 -
 includes/vstecasplong-md.md                         | 1 -
 includes/vstecmsbuild-md.md                         | 1 -
 includes/vwd-exp-dev10-long-md.md                   | 1 -
 includes/vwd-exp-orcas-long-md.md                   | 1 -
 includes/vwprvw-md.md                               | 1 -
 includes/wf1-md.md                                  | 1 -
 includes/wfd1-md.md                                 | 1 -
 includes/wfd2-md.md                                 | 1 -
 includes/win2kfamily-md.md                          | 1 -
 includes/win7-md.md                                 | 1 -
 includes/win8-appname-long-md.md                    | 1 -
 includes/win8-appstore-long-md.md                   | 1 -
 includes/win8-md.md                                 | 1 -
 includes/win81-md.md                                | 1 -
 includes/wince-md.md                                | 1 -
 includes/windowsver-md.md                           | 1 -
 includes/winnt4family-md.md                         | 1 -
 includes/winxp-md.md                                | 1 -
 includes/winxpsvr-md.md                             | 1 -
 includes/wiprlhext-md.md                            | 1 -
 includes/wpfdesigner-current-long-md.md             | 1 -
 includes/wrt-md.md                                  | 1 -
 includes/ws2003-md.md                               | 1 -
 includes/wv-md.md                                   | 1 -
 includes/wxp-md.md                                  | 1 -
 includes/wxpsp2-md.md                               | 1 -
 includes/xaml2009-md.md                             | 1 -
 231 files changed, 231 deletions(-)
 delete mode 100644 includes/ado-whidbey-long-md.md
 delete mode 100644 includes/adonet-edm-md.md
 delete mode 100644 includes/adonet-ef-md.md
 delete mode 100644 includes/ajax-current-short-md.md
 delete mode 100644 includes/compact-md.md
 delete mode 100644 includes/cpp-iter-arg-md.md
 delete mode 100644 includes/csprcslong-md.md
 delete mode 100644 includes/desktop-appname-md.md
 delete mode 100644 includes/dnprdnext-md.md
 delete mode 100644 includes/dnprdnlong-md.md
 delete mode 100644 includes/dnprdnshort-md.md
 delete mode 100644 includes/dp-id-field-label-md.md
 delete mode 100644 includes/esql-md.md
 delete mode 100644 includes/iisver-md.md
 delete mode 100644 includes/infocard-md.md
 delete mode 100644 includes/linq-dataset-md.md
 delete mode 100644 includes/ndptecclick-md.md
 delete mode 100644 includes/ndptecgdi-md.md
 delete mode 100644 includes/ndptecgdiplus-md.md
 delete mode 100644 includes/net-client-v40-long-md.md
 delete mode 100644 includes/net-core-md.md
 delete mode 100644 includes/net-native-md.md
 delete mode 100644 includes/net-portable-md.md
 delete mode 100644 includes/net-v10-short-md.md
 delete mode 100644 includes/net-v11-long-md.md
 delete mode 100644 includes/net-v11-short-md.md
 delete mode 100644 includes/net-v20sp1-long-md.md
 delete mode 100644 includes/net-v20sp1-short-md.md
 delete mode 100644 includes/net-v30-long-md.md
 delete mode 100644 includes/net-v30-short-md.md
 delete mode 100644 includes/net-v35-long-md.md
 delete mode 100644 includes/net-v35-short-md.md
 delete mode 100644 includes/net-v35sp1-long-md.md
 delete mode 100644 includes/net-v35sp1-short-md.md
 delete mode 100644 includes/net-v40-long-md.md
 delete mode 100644 includes/net-v40-short-md.md
 delete mode 100644 includes/net-v45-md.md
 delete mode 100644 includes/net-v451-md.md
 delete mode 100644 includes/net-v452-md.md
 delete mode 100644 includes/net-v46-md.md
 delete mode 100644 includes/net-v461-md.md
 delete mode 100644 includes/net-v462-md.md
 delete mode 100644 includes/net-v463-md.md
 delete mode 100644 includes/net-win8-profile-md.md
 delete mode 100644 includes/netfx35-long-md.md
 delete mode 100644 includes/netfx35-short-md.md
 delete mode 100644 includes/netfx40-long-md.md
 delete mode 100644 includes/netfx40-short-md.md
 delete mode 100644 includes/ofprword-md.md
 delete mode 100644 includes/sil3-first-md.md
 delete mode 100644 includes/silverlight-md.md
 delete mode 100644 includes/sqltecxlinq-md.md
 delete mode 100644 includes/sqprsqlong-md.md
 delete mode 100644 includes/ss2k-md.md
 delete mode 100644 includes/ssastoria-md.md
 delete mode 100644 includes/ssew-md.md
 delete mode 100644 includes/sskatmai-r2-md.md
 delete mode 100644 includes/ssodatashort-md.md
 delete mode 100644 includes/tla2sharptla-2d-md.md
 delete mode 100644 includes/tla2sharptla-3d-md.md
 delete mode 100644 includes/tla2sharptla-baml-md.md
 delete mode 100644 includes/tla2sharptla-bpp-md.md
 delete mode 100644 includes/tla2sharptla-caf-md.md
 delete mode 100644 includes/tla2sharptla-clr-md.md
 delete mode 100644 includes/tla2sharptla-com-md.md
 delete mode 100644 includes/tla2sharptla-dpi-md.md
 delete mode 100644 includes/tla2sharptla-dx-md.md
 delete mode 100644 includes/tla2sharptla-exif-md.md
 delete mode 100644 includes/tla2sharptla-gui-md.md
 delete mode 100644 includes/tla2sharptla-html-md.md
 delete mode 100644 includes/tla2sharptla-idsharpplural-md.md
 delete mode 100644 includes/tla2sharptla-ie6-md.md
 delete mode 100644 includes/tla2sharptla-ie7-md.md
 delete mode 100644 includes/tla2sharptla-iegeneric-md.md
 delete mode 100644 includes/tla2sharptla-mime-md.md
 delete mode 100644 includes/tla2sharptla-net-md.md
 delete mode 100644 includes/tla2sharptla-netframewkattr-md.md
 delete mode 100644 includes/tla2sharptla-opentype-md.md
 delete mode 100644 includes/tla2sharptla-passport-md.md
 delete mode 100644 includes/tla2sharptla-png-md.md
 delete mode 100644 includes/tla2sharptla-riff-md.md
 delete mode 100644 includes/tla2sharptla-sdk-md.md
 delete mode 100644 includes/tla2sharptla-tiff-md.md
 delete mode 100644 includes/tla2sharptla-titlexaml-md.md
 delete mode 100644 includes/tla2sharptla-tpc-md.md
 delete mode 100644 includes/tla2sharptla-ui-md.md
 delete mode 100644 includes/tla2sharptla-uiautomation-md.md
 delete mode 100644 includes/tla2sharptla-url-md.md
 delete mode 100644 includes/tla2sharptla-wdp-md.md
 delete mode 100644 includes/tla2sharptla-win32-md.md
 delete mode 100644 includes/tla2sharptla-winclient-md.md
 delete mode 100644 includes/tla2sharptla-winvista-md.md
 delete mode 100644 includes/tla2sharptla-wpf-md.md
 delete mode 100644 includes/tla2sharptla-xaml-md.md
 delete mode 100644 includes/tla2sharptla-xbap-md.md
 delete mode 100644 includes/tla2sharptla-xbapsharpplural-md.md
 delete mode 100644 includes/tla2sharptla-xml-md.md
 delete mode 100644 includes/tla2sharptla-xps-md.md
 delete mode 100644 includes/tla2sharptla-xrml-md.md
 delete mode 100644 includes/tlasharptla-2d-md.md
 delete mode 100644 includes/tlasharptla-3d-md.md
 delete mode 100644 includes/tlasharptla-aa-md.md
 delete mode 100644 includes/tlasharptla-adonet-md.md
 delete mode 100644 includes/tlasharptla-aero-md.md
 delete mode 100644 includes/tlasharptla-argb-md.md
 delete mode 100644 includes/tlasharptla-ascii-md.md
 delete mode 100644 includes/tlasharptla-baml-md.md
 delete mode 100644 includes/tlasharptla-bmp-md.md
 delete mode 100644 includes/tlasharptla-bpp-md.md
 delete mode 100644 includes/tlasharptla-caf-md.md
 delete mode 100644 includes/tlasharptla-cas-md.md
 delete mode 100644 includes/tlasharptla-clickonce-md.md
 delete mode 100644 includes/tlasharptla-clr-md.md
 delete mode 100644 includes/tlasharptla-com-md.md
 delete mode 100644 includes/tlasharptla-dhtml-md.md
 delete mode 100644 includes/tlasharptla-dipixel-md.md
 delete mode 100644 includes/tlasharptla-dipixelsharpplural-md.md
 delete mode 100644 includes/tlasharptla-dll-md.md
 delete mode 100644 includes/tlasharptla-dpi-md.md
 delete mode 100644 includes/tlasharptla-emf-md.md
 delete mode 100644 includes/tlasharptla-exif-md.md
 delete mode 100644 includes/tlasharptla-gdi-md.md
 delete mode 100644 includes/tlasharptla-gif-md.md
 delete mode 100644 includes/tlasharptla-gui-md.md
 delete mode 100644 includes/tlasharptla-html-md.md
 delete mode 100644 includes/tlasharptla-icc-md.md
 delete mode 100644 includes/tlasharptla-icm-md.md
 delete mode 100644 includes/tlasharptla-id-md.md
 delete mode 100644 includes/tlasharptla-idsharpplural-md.md
 delete mode 100644 includes/tlasharptla-ie-md.md
 delete mode 100644 includes/tlasharptla-ie6-md.md
 delete mode 100644 includes/tlasharptla-ie7-md.md
 delete mode 100644 includes/tlasharptla-iegeneric-md.md
 delete mode 100644 includes/tlasharptla-ifd-md.md
 delete mode 100644 includes/tlasharptla-ime-md.md
 delete mode 100644 includes/tlasharptla-isf-md.md
 delete mode 100644 includes/tlasharptla-isv-md.md
 delete mode 100644 includes/tlasharptla-jpeg-md.md
 delete mode 100644 includes/tlasharptla-jpegorg-md.md
 delete mode 100644 includes/tlasharptla-longhorn-md.md
 delete mode 100644 includes/tlasharptla-mdi-md.md
 delete mode 100644 includes/tlasharptla-mime-md.md
 delete mode 100644 includes/tlasharptla-msbuild-md.md
 delete mode 100644 includes/tlasharptla-mswin-md.md
 delete mode 100644 includes/tlasharptla-net-md.md
 delete mode 100644 includes/tlasharptla-netframewkattr-md.md
 delete mode 100644 includes/tlasharptla-opentype-md.md
 delete mode 100644 includes/tlasharptla-outlook-md.md
 delete mode 100644 includes/tlasharptla-passport-md.md
 delete mode 100644 includes/tlasharptla-png-md.md
 delete mode 100644 includes/tlasharptla-riff-md.md
 delete mode 100644 includes/tlasharptla-rtf-md.md
 delete mode 100644 includes/tlasharptla-sha1-md.md
 delete mode 100644 includes/tlasharptla-tiff-md.md
 delete mode 100644 includes/tlasharptla-titlewinclient-md.md
 delete mode 100644 includes/tlasharptla-titlexaml-md.md
 delete mode 100644 includes/tlasharptla-tpc-md.md
 delete mode 100644 includes/tlasharptla-ui-md.md
 delete mode 100644 includes/tlasharptla-uiautomation-md.md
 delete mode 100644 includes/tlasharptla-uiautomationsharpinitcap-md.md
 delete mode 100644 includes/tlasharptla-unc-md.md
 delete mode 100644 includes/tlasharptla-unicode-md.md
 delete mode 100644 includes/tlasharptla-url-md.md
 delete mode 100644 includes/tlasharptla-visualstu-md.md
 delete mode 100644 includes/tlasharptla-wdp-md.md
 delete mode 100644 includes/tlasharptla-win-md.md
 delete mode 100644 includes/tlasharptla-win32-md.md
 delete mode 100644 includes/tlasharptla-winclient-md.md
 delete mode 100644 includes/tlasharptla-winexpl-md.md
 delete mode 100644 includes/tlasharptla-winforms-md.md
 delete mode 100644 includes/tlasharptla-winfxwebapp-md.md
 delete mode 100644 includes/tlasharptla-winvista-md.md
 delete mode 100644 includes/tlasharptla-wmp-md.md
 delete mode 100644 includes/tlasharptla-word-md.md
 delete mode 100644 includes/tlasharptla-wys-md.md
 delete mode 100644 includes/tlasharptla-xaml-md.md
 delete mode 100644 includes/tlasharptla-xbap-md.md
 delete mode 100644 includes/tlasharptla-xbapsharpplural-md.md
 delete mode 100644 includes/tlasharptla-xl-md.md
 delete mode 100644 includes/tlasharptla-xml-md.md
 delete mode 100644 includes/tlasharptla-xmldom-md.md
 delete mode 100644 includes/tlasharptla-xmp-md.md
 delete mode 100644 includes/tlasharptla-xps-md.md
 delete mode 100644 includes/tlasharptla-xrml-md.md
 delete mode 100644 includes/tlasharptla-xsd-md.md
 delete mode 100644 includes/tsql-md.md
 delete mode 100644 includes/vb-orcas-long-md.md
 delete mode 100644 includes/vbprvbext-md.md
 delete mode 100644 includes/vbprvblong-md.md
 delete mode 100644 includes/vbtecdlinq-md.md
 delete mode 100644 includes/vbteclinq-md.md
 delete mode 100644 includes/vbteclinqext-md.md
 delete mode 100644 includes/vcprvc-md.md
 delete mode 100644 includes/vcprvclong-md.md
 delete mode 100644 includes/vs-dev10-long-md.md
 delete mode 100644 includes/vs-orcas-ext-md.md
 delete mode 100644 includes/vs-orcas-long-md.md
 delete mode 100644 includes/vs-ordesigner-long-md.md
 delete mode 100644 includes/vs-ordesigner-short-md.md
 delete mode 100644 includes/vs2010-md.md
 delete mode 100644 includes/vsprvsext-md.md
 delete mode 100644 includes/vsprvslong-md.md
 delete mode 100644 includes/vstecado-md.md
 delete mode 100644 includes/vstecasp-md.md
 delete mode 100644 includes/vstecasplong-md.md
 delete mode 100644 includes/vstecmsbuild-md.md
 delete mode 100644 includes/vwd-exp-dev10-long-md.md
 delete mode 100644 includes/vwd-exp-orcas-long-md.md
 delete mode 100644 includes/vwprvw-md.md
 delete mode 100644 includes/wf1-md.md
 delete mode 100644 includes/wfd1-md.md
 delete mode 100644 includes/wfd2-md.md
 delete mode 100644 includes/win2kfamily-md.md
 delete mode 100644 includes/win7-md.md
 delete mode 100644 includes/win8-appname-long-md.md
 delete mode 100644 includes/win8-appstore-long-md.md
 delete mode 100644 includes/win8-md.md
 delete mode 100644 includes/win81-md.md
 delete mode 100644 includes/wince-md.md
 delete mode 100644 includes/windowsver-md.md
 delete mode 100644 includes/winnt4family-md.md
 delete mode 100644 includes/winxp-md.md
 delete mode 100644 includes/winxpsvr-md.md
 delete mode 100644 includes/wiprlhext-md.md
 delete mode 100644 includes/wpfdesigner-current-long-md.md
 delete mode 100644 includes/wrt-md.md
 delete mode 100644 includes/ws2003-md.md
 delete mode 100644 includes/wv-md.md
 delete mode 100644 includes/wxp-md.md
 delete mode 100644 includes/wxpsp2-md.md
 delete mode 100644 includes/xaml2009-md.md

diff --git a/includes/ado-whidbey-long-md.md b/includes/ado-whidbey-long-md.md
deleted file mode 100644
index 84e4a3f81cb..00000000000
--- a/includes/ado-whidbey-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ADO.NET 2.0
\ No newline at end of file
diff --git a/includes/adonet-edm-md.md b/includes/adonet-edm-md.md
deleted file mode 100644
index 9671f3d5827..00000000000
--- a/includes/adonet-edm-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Entity Data Model
\ No newline at end of file
diff --git a/includes/adonet-ef-md.md b/includes/adonet-ef-md.md
deleted file mode 100644
index 5153cabe4fa..00000000000
--- a/includes/adonet-ef-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Entity Framework
\ No newline at end of file
diff --git a/includes/ajax-current-short-md.md b/includes/ajax-current-short-md.md
deleted file mode 100644
index 1f2bba75f75..00000000000
--- a/includes/ajax-current-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Ajax
\ No newline at end of file
diff --git a/includes/compact-md.md b/includes/compact-md.md
deleted file mode 100644
index f09d3f50950..00000000000
--- a/includes/compact-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Compact Framework
\ No newline at end of file
diff --git a/includes/cpp-iter-arg-md.md b/includes/cpp-iter-arg-md.md
deleted file mode 100644
index e6f7748d475..00000000000
--- a/includes/cpp-iter-arg-md.md
+++ /dev/null
@@ -1 +0,0 @@
-The type of an element in the controlled sequence.
\ No newline at end of file
diff --git a/includes/csprcslong-md.md b/includes/csprcslong-md.md
deleted file mode 100644
index 0190f9c8971..00000000000
--- a/includes/csprcslong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual C# 2005
\ No newline at end of file
diff --git a/includes/desktop-appname-md.md b/includes/desktop-appname-md.md
deleted file mode 100644
index 8714ca25df6..00000000000
--- a/includes/desktop-appname-md.md
+++ /dev/null
@@ -1 +0,0 @@
-desktop
\ No newline at end of file
diff --git a/includes/dnprdnext-md.md b/includes/dnprdnext-md.md
deleted file mode 100644
index a85e933d2f6..00000000000
--- a/includes/dnprdnext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 2.0
\ No newline at end of file
diff --git a/includes/dnprdnlong-md.md b/includes/dnprdnlong-md.md
deleted file mode 100644
index a85e933d2f6..00000000000
--- a/includes/dnprdnlong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 2.0
\ No newline at end of file
diff --git a/includes/dnprdnshort-md.md b/includes/dnprdnshort-md.md
deleted file mode 100644
index 578b265eda1..00000000000
--- a/includes/dnprdnshort-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework
\ No newline at end of file
diff --git a/includes/dp-id-field-label-md.md b/includes/dp-id-field-label-md.md
deleted file mode 100644
index 543d051fb3a..00000000000
--- a/includes/dp-id-field-label-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Dependency property identifier field:
\ No newline at end of file
diff --git a/includes/esql-md.md b/includes/esql-md.md
deleted file mode 100644
index 454e7fd1848..00000000000
--- a/includes/esql-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Entity SQL
\ No newline at end of file
diff --git a/includes/iisver-md.md b/includes/iisver-md.md
deleted file mode 100644
index 67f5b1fa851..00000000000
--- a/includes/iisver-md.md
+++ /dev/null
@@ -1 +0,0 @@
-IIS 7.0
\ No newline at end of file
diff --git a/includes/infocard-md.md b/includes/infocard-md.md
deleted file mode 100644
index 4c1f24ace17..00000000000
--- a/includes/infocard-md.md
+++ /dev/null
@@ -1 +0,0 @@
-CardSpace
\ No newline at end of file
diff --git a/includes/linq-dataset-md.md b/includes/linq-dataset-md.md
deleted file mode 100644
index 7cb495733db..00000000000
--- a/includes/linq-dataset-md.md
+++ /dev/null
@@ -1 +0,0 @@
-LINQ to DataSet
\ No newline at end of file
diff --git a/includes/ndptecclick-md.md b/includes/ndptecclick-md.md
deleted file mode 100644
index 9354b8371a8..00000000000
--- a/includes/ndptecclick-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ClickOnce
\ No newline at end of file
diff --git a/includes/ndptecgdi-md.md b/includes/ndptecgdi-md.md
deleted file mode 100644
index dca1dfd7aac..00000000000
--- a/includes/ndptecgdi-md.md
+++ /dev/null
@@ -1 +0,0 @@
-GDI
\ No newline at end of file
diff --git a/includes/ndptecgdiplus-md.md b/includes/ndptecgdiplus-md.md
deleted file mode 100644
index 5b0edbf8453..00000000000
--- a/includes/ndptecgdiplus-md.md
+++ /dev/null
@@ -1 +0,0 @@
-GDI+
\ No newline at end of file
diff --git a/includes/net-client-v40-long-md.md b/includes/net-client-v40-long-md.md
deleted file mode 100644
index 6eb2fced46b..00000000000
--- a/includes/net-client-v40-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4 Client Profile
\ No newline at end of file
diff --git a/includes/net-core-md.md b/includes/net-core-md.md
deleted file mode 100644
index f53daf1278b..00000000000
--- a/includes/net-core-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Core
\ No newline at end of file
diff --git a/includes/net-native-md.md b/includes/net-native-md.md
deleted file mode 100644
index e4b04f97331..00000000000
--- a/includes/net-native-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Native
\ No newline at end of file
diff --git a/includes/net-portable-md.md b/includes/net-portable-md.md
deleted file mode 100644
index 27b84cba069..00000000000
--- a/includes/net-portable-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Portable Class Library
\ No newline at end of file
diff --git a/includes/net-v10-short-md.md b/includes/net-v10-short-md.md
deleted file mode 100644
index 2fa845562a3..00000000000
--- a/includes/net-v10-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 1.0
\ No newline at end of file
diff --git a/includes/net-v11-long-md.md b/includes/net-v11-long-md.md
deleted file mode 100644
index cee1774a1ff..00000000000
--- a/includes/net-v11-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 1.1
\ No newline at end of file
diff --git a/includes/net-v11-short-md.md b/includes/net-v11-short-md.md
deleted file mode 100644
index cee1774a1ff..00000000000
--- a/includes/net-v11-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 1.1
\ No newline at end of file
diff --git a/includes/net-v20sp1-long-md.md b/includes/net-v20sp1-long-md.md
deleted file mode 100644
index 8c0ce41f6b4..00000000000
--- a/includes/net-v20sp1-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 2.0 Service Pack 1
\ No newline at end of file
diff --git a/includes/net-v20sp1-short-md.md b/includes/net-v20sp1-short-md.md
deleted file mode 100644
index 9cf1b8e62db..00000000000
--- a/includes/net-v20sp1-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 2.0 SP1
\ No newline at end of file
diff --git a/includes/net-v30-long-md.md b/includes/net-v30-long-md.md
deleted file mode 100644
index 8ed710fd7bf..00000000000
--- a/includes/net-v30-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.0
\ No newline at end of file
diff --git a/includes/net-v30-short-md.md b/includes/net-v30-short-md.md
deleted file mode 100644
index 8ed710fd7bf..00000000000
--- a/includes/net-v30-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.0
\ No newline at end of file
diff --git a/includes/net-v35-long-md.md b/includes/net-v35-long-md.md
deleted file mode 100644
index 8c423191688..00000000000
--- a/includes/net-v35-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
- .NET Framework 3.5 
diff --git a/includes/net-v35-short-md.md b/includes/net-v35-short-md.md
deleted file mode 100644
index 3b3e17628c7..00000000000
--- a/includes/net-v35-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.5
\ No newline at end of file
diff --git a/includes/net-v35sp1-long-md.md b/includes/net-v35sp1-long-md.md
deleted file mode 100644
index a4bbf5adf40..00000000000
--- a/includes/net-v35sp1-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.5 Service Pack 1
\ No newline at end of file
diff --git a/includes/net-v35sp1-short-md.md b/includes/net-v35sp1-short-md.md
deleted file mode 100644
index 0f46ca34db3..00000000000
--- a/includes/net-v35sp1-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.5 SP1
\ No newline at end of file
diff --git a/includes/net-v40-long-md.md b/includes/net-v40-long-md.md
deleted file mode 100644
index a6ccdbf9fb7..00000000000
--- a/includes/net-v40-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4
\ No newline at end of file
diff --git a/includes/net-v40-short-md.md b/includes/net-v40-short-md.md
deleted file mode 100644
index a6ccdbf9fb7..00000000000
--- a/includes/net-v40-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4
\ No newline at end of file
diff --git a/includes/net-v45-md.md b/includes/net-v45-md.md
deleted file mode 100644
index 7b4bf0fb0dc..00000000000
--- a/includes/net-v45-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.5
\ No newline at end of file
diff --git a/includes/net-v451-md.md b/includes/net-v451-md.md
deleted file mode 100644
index 81ec8b4536e..00000000000
--- a/includes/net-v451-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.5.1
\ No newline at end of file
diff --git a/includes/net-v452-md.md b/includes/net-v452-md.md
deleted file mode 100644
index 5db8902ca2f..00000000000
--- a/includes/net-v452-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.5.2
\ No newline at end of file
diff --git a/includes/net-v46-md.md b/includes/net-v46-md.md
deleted file mode 100644
index f091db4a79c..00000000000
--- a/includes/net-v46-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.6
\ No newline at end of file
diff --git a/includes/net-v461-md.md b/includes/net-v461-md.md
deleted file mode 100644
index f12ccd97aa6..00000000000
--- a/includes/net-v461-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.6.1
\ No newline at end of file
diff --git a/includes/net-v462-md.md b/includes/net-v462-md.md
deleted file mode 100644
index 5386eb0cfae..00000000000
--- a/includes/net-v462-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.6.2
\ No newline at end of file
diff --git a/includes/net-v463-md.md b/includes/net-v463-md.md
deleted file mode 100644
index 1d73e3cdcca..00000000000
--- a/includes/net-v463-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4.7
\ No newline at end of file
diff --git a/includes/net-win8-profile-md.md b/includes/net-win8-profile-md.md
deleted file mode 100644
index 4a9dc2f8dcf..00000000000
--- a/includes/net-win8-profile-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET for Windows 8.x Store apps
\ No newline at end of file
diff --git a/includes/netfx35-long-md.md b/includes/netfx35-long-md.md
deleted file mode 100644
index 137eaf9672c..00000000000
--- a/includes/netfx35-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework version 3.5
\ No newline at end of file
diff --git a/includes/netfx35-short-md.md b/includes/netfx35-short-md.md
deleted file mode 100644
index 3b3e17628c7..00000000000
--- a/includes/netfx35-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 3.5
\ No newline at end of file
diff --git a/includes/netfx40-long-md.md b/includes/netfx40-long-md.md
deleted file mode 100644
index 159059ada1c..00000000000
--- a/includes/netfx40-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework version 4
\ No newline at end of file
diff --git a/includes/netfx40-short-md.md b/includes/netfx40-short-md.md
deleted file mode 100644
index a6ccdbf9fb7..00000000000
--- a/includes/netfx40-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework 4
\ No newline at end of file
diff --git a/includes/ofprword-md.md b/includes/ofprword-md.md
deleted file mode 100644
index 4c0765a254f..00000000000
--- a/includes/ofprword-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Word
\ No newline at end of file
diff --git a/includes/sil3-first-md.md b/includes/sil3-first-md.md
deleted file mode 100644
index 5734e289b38..00000000000
--- a/includes/sil3-first-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Silverlight 3
\ No newline at end of file
diff --git a/includes/silverlight-md.md b/includes/silverlight-md.md
deleted file mode 100644
index df62f960fed..00000000000
--- a/includes/silverlight-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Silverlight
\ No newline at end of file
diff --git a/includes/sqltecxlinq-md.md b/includes/sqltecxlinq-md.md
deleted file mode 100644
index 2034e69937a..00000000000
--- a/includes/sqltecxlinq-md.md
+++ /dev/null
@@ -1 +0,0 @@
-LINQ to XML
\ No newline at end of file
diff --git a/includes/sqprsqlong-md.md b/includes/sqprsqlong-md.md
deleted file mode 100644
index f2d5b72816d..00000000000
--- a/includes/sqprsqlong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-SQL Server 2005
\ No newline at end of file
diff --git a/includes/ss2k-md.md b/includes/ss2k-md.md
deleted file mode 100644
index 3fe9a5c1949..00000000000
--- a/includes/ss2k-md.md
+++ /dev/null
@@ -1 +0,0 @@
-SQL Server 2000
\ No newline at end of file
diff --git a/includes/ssastoria-md.md b/includes/ssastoria-md.md
deleted file mode 100644
index 7ccf532a05d..00000000000
--- a/includes/ssastoria-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WCF Data Services
\ No newline at end of file
diff --git a/includes/ssew-md.md b/includes/ssew-md.md
deleted file mode 100644
index d3ab3d9099e..00000000000
--- a/includes/ssew-md.md
+++ /dev/null
@@ -1 +0,0 @@
-SQL Server Compact 3.5
\ No newline at end of file
diff --git a/includes/sskatmai-r2-md.md b/includes/sskatmai-r2-md.md
deleted file mode 100644
index 16f111e6b9c..00000000000
--- a/includes/sskatmai-r2-md.md
+++ /dev/null
@@ -1 +0,0 @@
-SQL Server 2008 R2
\ No newline at end of file
diff --git a/includes/ssodatashort-md.md b/includes/ssodatashort-md.md
deleted file mode 100644
index 52fc7f5729f..00000000000
--- a/includes/ssodatashort-md.md
+++ /dev/null
@@ -1 +0,0 @@
-OData
\ No newline at end of file
diff --git a/includes/tla2sharptla-2d-md.md b/includes/tla2sharptla-2d-md.md
deleted file mode 100644
index 23190149962..00000000000
--- a/includes/tla2sharptla-2d-md.md
+++ /dev/null
@@ -1 +0,0 @@
-2-D
\ No newline at end of file
diff --git a/includes/tla2sharptla-3d-md.md b/includes/tla2sharptla-3d-md.md
deleted file mode 100644
index a8b112e9f71..00000000000
--- a/includes/tla2sharptla-3d-md.md
+++ /dev/null
@@ -1 +0,0 @@
-3-D
\ No newline at end of file
diff --git a/includes/tla2sharptla-baml-md.md b/includes/tla2sharptla-baml-md.md
deleted file mode 100644
index e45e928c49a..00000000000
--- a/includes/tla2sharptla-baml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-BAML
\ No newline at end of file
diff --git a/includes/tla2sharptla-bpp-md.md b/includes/tla2sharptla-bpp-md.md
deleted file mode 100644
index 315a6682a8a..00000000000
--- a/includes/tla2sharptla-bpp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-BPP
\ No newline at end of file
diff --git a/includes/tla2sharptla-caf-md.md b/includes/tla2sharptla-caf-md.md
deleted file mode 100644
index cbbf1fee287..00000000000
--- a/includes/tla2sharptla-caf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Annotations Framework
\ No newline at end of file
diff --git a/includes/tla2sharptla-clr-md.md b/includes/tla2sharptla-clr-md.md
deleted file mode 100644
index 24584f2c1f2..00000000000
--- a/includes/tla2sharptla-clr-md.md
+++ /dev/null
@@ -1 +0,0 @@
-CLR
\ No newline at end of file
diff --git a/includes/tla2sharptla-com-md.md b/includes/tla2sharptla-com-md.md
deleted file mode 100644
index 2ce1fe653b3..00000000000
--- a/includes/tla2sharptla-com-md.md
+++ /dev/null
@@ -1 +0,0 @@
-COM
\ No newline at end of file
diff --git a/includes/tla2sharptla-dpi-md.md b/includes/tla2sharptla-dpi-md.md
deleted file mode 100644
index 98a0f7fb82e..00000000000
--- a/includes/tla2sharptla-dpi-md.md
+++ /dev/null
@@ -1 +0,0 @@
-dpi
\ No newline at end of file
diff --git a/includes/tla2sharptla-dx-md.md b/includes/tla2sharptla-dx-md.md
deleted file mode 100644
index 71d221e075a..00000000000
--- a/includes/tla2sharptla-dx-md.md
+++ /dev/null
@@ -1 +0,0 @@
-DirectX
\ No newline at end of file
diff --git a/includes/tla2sharptla-exif-md.md b/includes/tla2sharptla-exif-md.md
deleted file mode 100644
index 3e484bc7a73..00000000000
--- a/includes/tla2sharptla-exif-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Exif
\ No newline at end of file
diff --git a/includes/tla2sharptla-gui-md.md b/includes/tla2sharptla-gui-md.md
deleted file mode 100644
index 70fac1bcb13..00000000000
--- a/includes/tla2sharptla-gui-md.md
+++ /dev/null
@@ -1 +0,0 @@
-GUI
\ No newline at end of file
diff --git a/includes/tla2sharptla-html-md.md b/includes/tla2sharptla-html-md.md
deleted file mode 100644
index 3225efc49a9..00000000000
--- a/includes/tla2sharptla-html-md.md
+++ /dev/null
@@ -1 +0,0 @@
-HTML
\ No newline at end of file
diff --git a/includes/tla2sharptla-idsharpplural-md.md b/includes/tla2sharptla-idsharpplural-md.md
deleted file mode 100644
index 609a8712ba6..00000000000
--- a/includes/tla2sharptla-idsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-IDs
\ No newline at end of file
diff --git a/includes/tla2sharptla-ie6-md.md b/includes/tla2sharptla-ie6-md.md
deleted file mode 100644
index e880d15a013..00000000000
--- a/includes/tla2sharptla-ie6-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Internet Explorer 6
\ No newline at end of file
diff --git a/includes/tla2sharptla-ie7-md.md b/includes/tla2sharptla-ie7-md.md
deleted file mode 100644
index 95495b465f0..00000000000
--- a/includes/tla2sharptla-ie7-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Internet Explorer 7
\ No newline at end of file
diff --git a/includes/tla2sharptla-iegeneric-md.md b/includes/tla2sharptla-iegeneric-md.md
deleted file mode 100644
index 44bb34c8f97..00000000000
--- a/includes/tla2sharptla-iegeneric-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Internet Explorer
\ No newline at end of file
diff --git a/includes/tla2sharptla-mime-md.md b/includes/tla2sharptla-mime-md.md
deleted file mode 100644
index 59664a72a19..00000000000
--- a/includes/tla2sharptla-mime-md.md
+++ /dev/null
@@ -1 +0,0 @@
-MIME
\ No newline at end of file
diff --git a/includes/tla2sharptla-net-md.md b/includes/tla2sharptla-net-md.md
deleted file mode 100644
index d49ef201e75..00000000000
--- a/includes/tla2sharptla-net-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET
\ No newline at end of file
diff --git a/includes/tla2sharptla-netframewkattr-md.md b/includes/tla2sharptla-netframewkattr-md.md
deleted file mode 100644
index ee303926c37..00000000000
--- a/includes/tla2sharptla-netframewkattr-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework attribute
\ No newline at end of file
diff --git a/includes/tla2sharptla-opentype-md.md b/includes/tla2sharptla-opentype-md.md
deleted file mode 100644
index fad0b0bfa09..00000000000
--- a/includes/tla2sharptla-opentype-md.md
+++ /dev/null
@@ -1 +0,0 @@
-OpenType
\ No newline at end of file
diff --git a/includes/tla2sharptla-passport-md.md b/includes/tla2sharptla-passport-md.md
deleted file mode 100644
index 46ca96f199f..00000000000
--- a/includes/tla2sharptla-passport-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Live ID
\ No newline at end of file
diff --git a/includes/tla2sharptla-png-md.md b/includes/tla2sharptla-png-md.md
deleted file mode 100644
index 67461379f1f..00000000000
--- a/includes/tla2sharptla-png-md.md
+++ /dev/null
@@ -1 +0,0 @@
-PNG
\ No newline at end of file
diff --git a/includes/tla2sharptla-riff-md.md b/includes/tla2sharptla-riff-md.md
deleted file mode 100644
index a71100636e8..00000000000
--- a/includes/tla2sharptla-riff-md.md
+++ /dev/null
@@ -1 +0,0 @@
-RIFF
\ No newline at end of file
diff --git a/includes/tla2sharptla-sdk-md.md b/includes/tla2sharptla-sdk-md.md
deleted file mode 100644
index bb3427d9181..00000000000
--- a/includes/tla2sharptla-sdk-md.md
+++ /dev/null
@@ -1 +0,0 @@
-SDK
\ No newline at end of file
diff --git a/includes/tla2sharptla-tiff-md.md b/includes/tla2sharptla-tiff-md.md
deleted file mode 100644
index 915ecc800dd..00000000000
--- a/includes/tla2sharptla-tiff-md.md
+++ /dev/null
@@ -1 +0,0 @@
-TIFF
\ No newline at end of file
diff --git a/includes/tla2sharptla-titlexaml-md.md b/includes/tla2sharptla-titlexaml-md.md
deleted file mode 100644
index 7d3d6afaedc..00000000000
--- a/includes/tla2sharptla-titlexaml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML
\ No newline at end of file
diff --git a/includes/tla2sharptla-tpc-md.md b/includes/tla2sharptla-tpc-md.md
deleted file mode 100644
index 834bcfc55be..00000000000
--- a/includes/tla2sharptla-tpc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Tablet PC
\ No newline at end of file
diff --git a/includes/tla2sharptla-ui-md.md b/includes/tla2sharptla-ui-md.md
deleted file mode 100644
index f599d5c5cad..00000000000
--- a/includes/tla2sharptla-ui-md.md
+++ /dev/null
@@ -1 +0,0 @@
-UI
\ No newline at end of file
diff --git a/includes/tla2sharptla-uiautomation-md.md b/includes/tla2sharptla-uiautomation-md.md
deleted file mode 100644
index c8f4954a9c8..00000000000
--- a/includes/tla2sharptla-uiautomation-md.md
+++ /dev/null
@@ -1 +0,0 @@
-UI Automation
\ No newline at end of file
diff --git a/includes/tla2sharptla-url-md.md b/includes/tla2sharptla-url-md.md
deleted file mode 100644
index e6a755c451b..00000000000
--- a/includes/tla2sharptla-url-md.md
+++ /dev/null
@@ -1 +0,0 @@
-URL
\ No newline at end of file
diff --git a/includes/tla2sharptla-wdp-md.md b/includes/tla2sharptla-wdp-md.md
deleted file mode 100644
index 42498a289c9..00000000000
--- a/includes/tla2sharptla-wdp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Media Photo
\ No newline at end of file
diff --git a/includes/tla2sharptla-win32-md.md b/includes/tla2sharptla-win32-md.md
deleted file mode 100644
index df14f554429..00000000000
--- a/includes/tla2sharptla-win32-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Win32
\ No newline at end of file
diff --git a/includes/tla2sharptla-winclient-md.md b/includes/tla2sharptla-winclient-md.md
deleted file mode 100644
index 92826b01ec3..00000000000
--- a/includes/tla2sharptla-winclient-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WPF
\ No newline at end of file
diff --git a/includes/tla2sharptla-winvista-md.md b/includes/tla2sharptla-winvista-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/tla2sharptla-winvista-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/tla2sharptla-wpf-md.md b/includes/tla2sharptla-wpf-md.md
deleted file mode 100644
index 92826b01ec3..00000000000
--- a/includes/tla2sharptla-wpf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WPF
\ No newline at end of file
diff --git a/includes/tla2sharptla-xaml-md.md b/includes/tla2sharptla-xaml-md.md
deleted file mode 100644
index 7d3d6afaedc..00000000000
--- a/includes/tla2sharptla-xaml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML
\ No newline at end of file
diff --git a/includes/tla2sharptla-xbap-md.md b/includes/tla2sharptla-xbap-md.md
deleted file mode 100644
index 6d0f65efa85..00000000000
--- a/includes/tla2sharptla-xbap-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XBAP
\ No newline at end of file
diff --git a/includes/tla2sharptla-xbapsharpplural-md.md b/includes/tla2sharptla-xbapsharpplural-md.md
deleted file mode 100644
index 63dc7de84d0..00000000000
--- a/includes/tla2sharptla-xbapsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XBAPs
\ No newline at end of file
diff --git a/includes/tla2sharptla-xml-md.md b/includes/tla2sharptla-xml-md.md
deleted file mode 100644
index f86a2f5fe92..00000000000
--- a/includes/tla2sharptla-xml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XML
\ No newline at end of file
diff --git a/includes/tla2sharptla-xps-md.md b/includes/tla2sharptla-xps-md.md
deleted file mode 100644
index bc32e60a990..00000000000
--- a/includes/tla2sharptla-xps-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XPS
\ No newline at end of file
diff --git a/includes/tla2sharptla-xrml-md.md b/includes/tla2sharptla-xrml-md.md
deleted file mode 100644
index cceedef6a85..00000000000
--- a/includes/tla2sharptla-xrml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XrML
\ No newline at end of file
diff --git a/includes/tlasharptla-2d-md.md b/includes/tlasharptla-2d-md.md
deleted file mode 100644
index 23190149962..00000000000
--- a/includes/tlasharptla-2d-md.md
+++ /dev/null
@@ -1 +0,0 @@
-2-D
\ No newline at end of file
diff --git a/includes/tlasharptla-3d-md.md b/includes/tlasharptla-3d-md.md
deleted file mode 100644
index a8b112e9f71..00000000000
--- a/includes/tlasharptla-3d-md.md
+++ /dev/null
@@ -1 +0,0 @@
-3-D
\ No newline at end of file
diff --git a/includes/tlasharptla-aa-md.md b/includes/tlasharptla-aa-md.md
deleted file mode 100644
index 53bf1bc086c..00000000000
--- a/includes/tlasharptla-aa-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Active Accessibility
\ No newline at end of file
diff --git a/includes/tlasharptla-adonet-md.md b/includes/tlasharptla-adonet-md.md
deleted file mode 100644
index 7b6552e6405..00000000000
--- a/includes/tlasharptla-adonet-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ADO.NET
\ No newline at end of file
diff --git a/includes/tlasharptla-aero-md.md b/includes/tlasharptla-aero-md.md
deleted file mode 100644
index 596f97cb2ad..00000000000
--- a/includes/tlasharptla-aero-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Aero
\ No newline at end of file
diff --git a/includes/tlasharptla-argb-md.md b/includes/tlasharptla-argb-md.md
deleted file mode 100644
index 061590f4b45..00000000000
--- a/includes/tlasharptla-argb-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ARGB
\ No newline at end of file
diff --git a/includes/tlasharptla-ascii-md.md b/includes/tlasharptla-ascii-md.md
deleted file mode 100644
index 290822646f5..00000000000
--- a/includes/tlasharptla-ascii-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ASCII
\ No newline at end of file
diff --git a/includes/tlasharptla-baml-md.md b/includes/tlasharptla-baml-md.md
deleted file mode 100644
index d43a4bfd804..00000000000
--- a/includes/tlasharptla-baml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-binary XAML (BAML)
\ No newline at end of file
diff --git a/includes/tlasharptla-bmp-md.md b/includes/tlasharptla-bmp-md.md
deleted file mode 100644
index 1dda1bbd7ae..00000000000
--- a/includes/tlasharptla-bmp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-bitmap (BMP)
\ No newline at end of file
diff --git a/includes/tlasharptla-bpp-md.md b/includes/tlasharptla-bpp-md.md
deleted file mode 100644
index 949f6c8904d..00000000000
--- a/includes/tlasharptla-bpp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-bits per pixel (BPP)
\ No newline at end of file
diff --git a/includes/tlasharptla-caf-md.md b/includes/tlasharptla-caf-md.md
deleted file mode 100644
index 0b4f564eed7..00000000000
--- a/includes/tlasharptla-caf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Annotations Framework
\ No newline at end of file
diff --git a/includes/tlasharptla-cas-md.md b/includes/tlasharptla-cas-md.md
deleted file mode 100644
index 1b55ee4f4bf..00000000000
--- a/includes/tlasharptla-cas-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Code Access Security (CAS)
\ No newline at end of file
diff --git a/includes/tlasharptla-clickonce-md.md b/includes/tlasharptla-clickonce-md.md
deleted file mode 100644
index 9354b8371a8..00000000000
--- a/includes/tlasharptla-clickonce-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ClickOnce
\ No newline at end of file
diff --git a/includes/tlasharptla-clr-md.md b/includes/tlasharptla-clr-md.md
deleted file mode 100644
index aae1d297846..00000000000
--- a/includes/tlasharptla-clr-md.md
+++ /dev/null
@@ -1 +0,0 @@
-common language runtime (CLR)
\ No newline at end of file
diff --git a/includes/tlasharptla-com-md.md b/includes/tlasharptla-com-md.md
deleted file mode 100644
index bcd1d039d93..00000000000
--- a/includes/tlasharptla-com-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Component Object Model (COM)
\ No newline at end of file
diff --git a/includes/tlasharptla-dhtml-md.md b/includes/tlasharptla-dhtml-md.md
deleted file mode 100644
index c049622549b..00000000000
--- a/includes/tlasharptla-dhtml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Dynamic HTML (DHTML)
\ No newline at end of file
diff --git a/includes/tlasharptla-dipixel-md.md b/includes/tlasharptla-dipixel-md.md
deleted file mode 100644
index 853f091f5a9..00000000000
--- a/includes/tlasharptla-dipixel-md.md
+++ /dev/null
@@ -1 +0,0 @@
-device-independent unit (1/96th inch)
\ No newline at end of file
diff --git a/includes/tlasharptla-dipixelsharpplural-md.md b/includes/tlasharptla-dipixelsharpplural-md.md
deleted file mode 100644
index 376eb02a701..00000000000
--- a/includes/tlasharptla-dipixelsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-device-independent units (1/96th inch per unit)
\ No newline at end of file
diff --git a/includes/tlasharptla-dll-md.md b/includes/tlasharptla-dll-md.md
deleted file mode 100644
index 34bf682a547..00000000000
--- a/includes/tlasharptla-dll-md.md
+++ /dev/null
@@ -1 +0,0 @@
-dynamic-link library (DLL)
\ No newline at end of file
diff --git a/includes/tlasharptla-dpi-md.md b/includes/tlasharptla-dpi-md.md
deleted file mode 100644
index b3e2a26117b..00000000000
--- a/includes/tlasharptla-dpi-md.md
+++ /dev/null
@@ -1 +0,0 @@
-dots per inch (dpi)
\ No newline at end of file
diff --git a/includes/tlasharptla-emf-md.md b/includes/tlasharptla-emf-md.md
deleted file mode 100644
index 0a806a65d09..00000000000
--- a/includes/tlasharptla-emf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Enhanced Metafile (EMF)
\ No newline at end of file
diff --git a/includes/tlasharptla-exif-md.md b/includes/tlasharptla-exif-md.md
deleted file mode 100644
index e83b97fa051..00000000000
--- a/includes/tlasharptla-exif-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Exchangeable image file (Exif)
\ No newline at end of file
diff --git a/includes/tlasharptla-gdi-md.md b/includes/tlasharptla-gdi-md.md
deleted file mode 100644
index 76a6f0989db..00000000000
--- a/includes/tlasharptla-gdi-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows Graphics Device Interface (GDI)
\ No newline at end of file
diff --git a/includes/tlasharptla-gif-md.md b/includes/tlasharptla-gif-md.md
deleted file mode 100644
index 37b0d8db92e..00000000000
--- a/includes/tlasharptla-gif-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Graphics Interchange Format (GIF)
\ No newline at end of file
diff --git a/includes/tlasharptla-gui-md.md b/includes/tlasharptla-gui-md.md
deleted file mode 100644
index 1413fa23350..00000000000
--- a/includes/tlasharptla-gui-md.md
+++ /dev/null
@@ -1 +0,0 @@
-graphical user interface (GUI)
\ No newline at end of file
diff --git a/includes/tlasharptla-html-md.md b/includes/tlasharptla-html-md.md
deleted file mode 100644
index 3225efc49a9..00000000000
--- a/includes/tlasharptla-html-md.md
+++ /dev/null
@@ -1 +0,0 @@
-HTML
\ No newline at end of file
diff --git a/includes/tlasharptla-icc-md.md b/includes/tlasharptla-icc-md.md
deleted file mode 100644
index 1b50117c2d8..00000000000
--- a/includes/tlasharptla-icc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-International Color Consortium (ICC)
\ No newline at end of file
diff --git a/includes/tlasharptla-icm-md.md b/includes/tlasharptla-icm-md.md
deleted file mode 100644
index de667e4fcd3..00000000000
--- a/includes/tlasharptla-icm-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Image Color Management (ICM)
\ No newline at end of file
diff --git a/includes/tlasharptla-id-md.md b/includes/tlasharptla-id-md.md
deleted file mode 100644
index e9576e4e1de..00000000000
--- a/includes/tlasharptla-id-md.md
+++ /dev/null
@@ -1 +0,0 @@
-identifier (ID)
\ No newline at end of file
diff --git a/includes/tlasharptla-idsharpplural-md.md b/includes/tlasharptla-idsharpplural-md.md
deleted file mode 100644
index 3fe608f9635..00000000000
--- a/includes/tlasharptla-idsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-identifiers (IDs)
\ No newline at end of file
diff --git a/includes/tlasharptla-ie-md.md b/includes/tlasharptla-ie-md.md
deleted file mode 100644
index a0e6d7ff79e..00000000000
--- a/includes/tlasharptla-ie-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Internet Explorer
\ No newline at end of file
diff --git a/includes/tlasharptla-ie6-md.md b/includes/tlasharptla-ie6-md.md
deleted file mode 100644
index e880d15a013..00000000000
--- a/includes/tlasharptla-ie6-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Internet Explorer 6
\ No newline at end of file
diff --git a/includes/tlasharptla-ie7-md.md b/includes/tlasharptla-ie7-md.md
deleted file mode 100644
index 7e19a10469c..00000000000
--- a/includes/tlasharptla-ie7-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Internet Explorer 7
\ No newline at end of file
diff --git a/includes/tlasharptla-iegeneric-md.md b/includes/tlasharptla-iegeneric-md.md
deleted file mode 100644
index 2563bf1452e..00000000000
--- a/includes/tlasharptla-iegeneric-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Internet Explorer
\ No newline at end of file
diff --git a/includes/tlasharptla-ifd-md.md b/includes/tlasharptla-ifd-md.md
deleted file mode 100644
index 6247f5e998b..00000000000
--- a/includes/tlasharptla-ifd-md.md
+++ /dev/null
@@ -1 +0,0 @@
-image file directory (IFD)
\ No newline at end of file
diff --git a/includes/tlasharptla-ime-md.md b/includes/tlasharptla-ime-md.md
deleted file mode 100644
index 25a7853fe8d..00000000000
--- a/includes/tlasharptla-ime-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Input Method Editor (IME)
\ No newline at end of file
diff --git a/includes/tlasharptla-isf-md.md b/includes/tlasharptla-isf-md.md
deleted file mode 100644
index 51c6a562d55..00000000000
--- a/includes/tlasharptla-isf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Ink Serialized Format (ISF)
\ No newline at end of file
diff --git a/includes/tlasharptla-isv-md.md b/includes/tlasharptla-isv-md.md
deleted file mode 100644
index 7bc9c9b3dc2..00000000000
--- a/includes/tlasharptla-isv-md.md
+++ /dev/null
@@ -1 +0,0 @@
-independent software vendor (ISV)
\ No newline at end of file
diff --git a/includes/tlasharptla-jpeg-md.md b/includes/tlasharptla-jpeg-md.md
deleted file mode 100644
index d4d1537f685..00000000000
--- a/includes/tlasharptla-jpeg-md.md
+++ /dev/null
@@ -1 +0,0 @@
-JPEG
\ No newline at end of file
diff --git a/includes/tlasharptla-jpegorg-md.md b/includes/tlasharptla-jpegorg-md.md
deleted file mode 100644
index 5936d841425..00000000000
--- a/includes/tlasharptla-jpegorg-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Joint Photographics Experts Group (JPEG)
\ No newline at end of file
diff --git a/includes/tlasharptla-longhorn-md.md b/includes/tlasharptla-longhorn-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/tlasharptla-longhorn-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/tlasharptla-mdi-md.md b/includes/tlasharptla-mdi-md.md
deleted file mode 100644
index a1caa7f98b6..00000000000
--- a/includes/tlasharptla-mdi-md.md
+++ /dev/null
@@ -1 +0,0 @@
-multiple-document interface (MDI)
\ No newline at end of file
diff --git a/includes/tlasharptla-mime-md.md b/includes/tlasharptla-mime-md.md
deleted file mode 100644
index dfe9753fb7a..00000000000
--- a/includes/tlasharptla-mime-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Multipurpose Internet Mail Extensions (MIME)
\ No newline at end of file
diff --git a/includes/tlasharptla-msbuild-md.md b/includes/tlasharptla-msbuild-md.md
deleted file mode 100644
index 574f41e51c4..00000000000
--- a/includes/tlasharptla-msbuild-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft build engine (MSBuild)
\ No newline at end of file
diff --git a/includes/tlasharptla-mswin-md.md b/includes/tlasharptla-mswin-md.md
deleted file mode 100644
index 1058cb39495..00000000000
--- a/includes/tlasharptla-mswin-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows
\ No newline at end of file
diff --git a/includes/tlasharptla-net-md.md b/includes/tlasharptla-net-md.md
deleted file mode 100644
index ed5316af359..00000000000
--- a/includes/tlasharptla-net-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft .NET
\ No newline at end of file
diff --git a/includes/tlasharptla-netframewkattr-md.md b/includes/tlasharptla-netframewkattr-md.md
deleted file mode 100644
index ee303926c37..00000000000
--- a/includes/tlasharptla-netframewkattr-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework attribute
\ No newline at end of file
diff --git a/includes/tlasharptla-opentype-md.md b/includes/tlasharptla-opentype-md.md
deleted file mode 100644
index fad0b0bfa09..00000000000
--- a/includes/tlasharptla-opentype-md.md
+++ /dev/null
@@ -1 +0,0 @@
-OpenType
\ No newline at end of file
diff --git a/includes/tlasharptla-outlook-md.md b/includes/tlasharptla-outlook-md.md
deleted file mode 100644
index 624028563d0..00000000000
--- a/includes/tlasharptla-outlook-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Outlook
\ No newline at end of file
diff --git a/includes/tlasharptla-passport-md.md b/includes/tlasharptla-passport-md.md
deleted file mode 100644
index 46ca96f199f..00000000000
--- a/includes/tlasharptla-passport-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Live ID
\ No newline at end of file
diff --git a/includes/tlasharptla-png-md.md b/includes/tlasharptla-png-md.md
deleted file mode 100644
index 1f7bd6dabcc..00000000000
--- a/includes/tlasharptla-png-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Portable Network Graphics (PNG)
\ No newline at end of file
diff --git a/includes/tlasharptla-riff-md.md b/includes/tlasharptla-riff-md.md
deleted file mode 100644
index 53d4b8443d0..00000000000
--- a/includes/tlasharptla-riff-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Resource Interchange File Format (RIFF)
\ No newline at end of file
diff --git a/includes/tlasharptla-rtf-md.md b/includes/tlasharptla-rtf-md.md
deleted file mode 100644
index 9a376842ab5..00000000000
--- a/includes/tlasharptla-rtf-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Rich Text Format (RTF)
\ No newline at end of file
diff --git a/includes/tlasharptla-sha1-md.md b/includes/tlasharptla-sha1-md.md
deleted file mode 100644
index 2b48d240e1c..00000000000
--- a/includes/tlasharptla-sha1-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Secure Hash Algorithm version 1.0 (SHA1)
\ No newline at end of file
diff --git a/includes/tlasharptla-tiff-md.md b/includes/tlasharptla-tiff-md.md
deleted file mode 100644
index 68948a6cc5f..00000000000
--- a/includes/tlasharptla-tiff-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Tagged Image File Format (TIFF)
\ No newline at end of file
diff --git a/includes/tlasharptla-titlewinclient-md.md b/includes/tlasharptla-titlewinclient-md.md
deleted file mode 100644
index 92826b01ec3..00000000000
--- a/includes/tlasharptla-titlewinclient-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WPF
\ No newline at end of file
diff --git a/includes/tlasharptla-titlexaml-md.md b/includes/tlasharptla-titlexaml-md.md
deleted file mode 100644
index 7d3d6afaedc..00000000000
--- a/includes/tlasharptla-titlexaml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML
\ No newline at end of file
diff --git a/includes/tlasharptla-tpc-md.md b/includes/tlasharptla-tpc-md.md
deleted file mode 100644
index 834bcfc55be..00000000000
--- a/includes/tlasharptla-tpc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Tablet PC
\ No newline at end of file
diff --git a/includes/tlasharptla-ui-md.md b/includes/tlasharptla-ui-md.md
deleted file mode 100644
index c1dd193547c..00000000000
--- a/includes/tlasharptla-ui-md.md
+++ /dev/null
@@ -1 +0,0 @@
-user interface (UI)
\ No newline at end of file
diff --git a/includes/tlasharptla-uiautomation-md.md b/includes/tlasharptla-uiautomation-md.md
deleted file mode 100644
index 0ce40bf644c..00000000000
--- a/includes/tlasharptla-uiautomation-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft UI Automation
\ No newline at end of file
diff --git a/includes/tlasharptla-uiautomationsharpinitcap-md.md b/includes/tlasharptla-uiautomationsharpinitcap-md.md
deleted file mode 100644
index c8f4954a9c8..00000000000
--- a/includes/tlasharptla-uiautomationsharpinitcap-md.md
+++ /dev/null
@@ -1 +0,0 @@
-UI Automation
\ No newline at end of file
diff --git a/includes/tlasharptla-unc-md.md b/includes/tlasharptla-unc-md.md
deleted file mode 100644
index bc412a4c57b..00000000000
--- a/includes/tlasharptla-unc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Universal Naming Convention (UNC)
\ No newline at end of file
diff --git a/includes/tlasharptla-unicode-md.md b/includes/tlasharptla-unicode-md.md
deleted file mode 100644
index a0388044512..00000000000
--- a/includes/tlasharptla-unicode-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Unicode
\ No newline at end of file
diff --git a/includes/tlasharptla-url-md.md b/includes/tlasharptla-url-md.md
deleted file mode 100644
index e6a755c451b..00000000000
--- a/includes/tlasharptla-url-md.md
+++ /dev/null
@@ -1 +0,0 @@
-URL
\ No newline at end of file
diff --git a/includes/tlasharptla-visualstu-md.md b/includes/tlasharptla-visualstu-md.md
deleted file mode 100644
index 5f8ebc7ff9a..00000000000
--- a/includes/tlasharptla-visualstu-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Visual Studio
\ No newline at end of file
diff --git a/includes/tlasharptla-wdp-md.md b/includes/tlasharptla-wdp-md.md
deleted file mode 100644
index d184490a59f..00000000000
--- a/includes/tlasharptla-wdp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows Media Photo
\ No newline at end of file
diff --git a/includes/tlasharptla-win-md.md b/includes/tlasharptla-win-md.md
deleted file mode 100644
index 09919ea7bee..00000000000
--- a/includes/tlasharptla-win-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows
\ No newline at end of file
diff --git a/includes/tlasharptla-win32-md.md b/includes/tlasharptla-win32-md.md
deleted file mode 100644
index df14f554429..00000000000
--- a/includes/tlasharptla-win32-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Win32
\ No newline at end of file
diff --git a/includes/tlasharptla-winclient-md.md b/includes/tlasharptla-winclient-md.md
deleted file mode 100644
index ec2f2b4ecea..00000000000
--- a/includes/tlasharptla-winclient-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Presentation Foundation (WPF)
\ No newline at end of file
diff --git a/includes/tlasharptla-winexpl-md.md b/includes/tlasharptla-winexpl-md.md
deleted file mode 100644
index 050c02289e3..00000000000
--- a/includes/tlasharptla-winexpl-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows Explorer
\ No newline at end of file
diff --git a/includes/tlasharptla-winforms-md.md b/includes/tlasharptla-winforms-md.md
deleted file mode 100644
index cc70f580d7d..00000000000
--- a/includes/tlasharptla-winforms-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Forms
\ No newline at end of file
diff --git a/includes/tlasharptla-winfxwebapp-md.md b/includes/tlasharptla-winfxwebapp-md.md
deleted file mode 100644
index a538161e413..00000000000
--- a/includes/tlasharptla-winfxwebapp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML browser application (XBAP)
\ No newline at end of file
diff --git a/includes/tlasharptla-winvista-md.md b/includes/tlasharptla-winvista-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/tlasharptla-winvista-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/tlasharptla-wmp-md.md b/includes/tlasharptla-wmp-md.md
deleted file mode 100644
index 64ccfac2dc7..00000000000
--- a/includes/tlasharptla-wmp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows Media Player
\ No newline at end of file
diff --git a/includes/tlasharptla-word-md.md b/includes/tlasharptla-word-md.md
deleted file mode 100644
index 4c0765a254f..00000000000
--- a/includes/tlasharptla-word-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Word
\ No newline at end of file
diff --git a/includes/tlasharptla-wys-md.md b/includes/tlasharptla-wys-md.md
deleted file mode 100644
index 145a582eaa0..00000000000
--- a/includes/tlasharptla-wys-md.md
+++ /dev/null
@@ -1 +0,0 @@
-"what you see is what you get" (WYSIWYG)
\ No newline at end of file
diff --git a/includes/tlasharptla-xaml-md.md b/includes/tlasharptla-xaml-md.md
deleted file mode 100644
index 64155c7f9ba..00000000000
--- a/includes/tlasharptla-xaml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Extensible Application Markup Language (XAML)
\ No newline at end of file
diff --git a/includes/tlasharptla-xbap-md.md b/includes/tlasharptla-xbap-md.md
deleted file mode 100644
index a538161e413..00000000000
--- a/includes/tlasharptla-xbap-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML browser application (XBAP)
\ No newline at end of file
diff --git a/includes/tlasharptla-xbapsharpplural-md.md b/includes/tlasharptla-xbapsharpplural-md.md
deleted file mode 100644
index 9af96f3a115..00000000000
--- a/includes/tlasharptla-xbapsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML browser applications (XBAPs)
\ No newline at end of file
diff --git a/includes/tlasharptla-xl-md.md b/includes/tlasharptla-xl-md.md
deleted file mode 100644
index 45a379d7eac..00000000000
--- a/includes/tlasharptla-xl-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Excel
\ No newline at end of file
diff --git a/includes/tlasharptla-xml-md.md b/includes/tlasharptla-xml-md.md
deleted file mode 100644
index f86a2f5fe92..00000000000
--- a/includes/tlasharptla-xml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XML
\ No newline at end of file
diff --git a/includes/tlasharptla-xmldom-md.md b/includes/tlasharptla-xmldom-md.md
deleted file mode 100644
index 616fe700d83..00000000000
--- a/includes/tlasharptla-xmldom-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XML Document Object Model (DOM)
\ No newline at end of file
diff --git a/includes/tlasharptla-xmp-md.md b/includes/tlasharptla-xmp-md.md
deleted file mode 100644
index 25a4fdd4209..00000000000
--- a/includes/tlasharptla-xmp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Extensible Metadata Platform (XMP)
\ No newline at end of file
diff --git a/includes/tlasharptla-xps-md.md b/includes/tlasharptla-xps-md.md
deleted file mode 100644
index b0d87920a46..00000000000
--- a/includes/tlasharptla-xps-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XML Paper Specification (XPS)
\ No newline at end of file
diff --git a/includes/tlasharptla-xrml-md.md b/includes/tlasharptla-xrml-md.md
deleted file mode 100644
index ee16d7b501a..00000000000
--- a/includes/tlasharptla-xrml-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Extensible Rights Markup Language (XrML)
\ No newline at end of file
diff --git a/includes/tlasharptla-xsd-md.md b/includes/tlasharptla-xsd-md.md
deleted file mode 100644
index 32a590084be..00000000000
--- a/includes/tlasharptla-xsd-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XML Schema Definition (XSD)
\ No newline at end of file
diff --git a/includes/tsql-md.md b/includes/tsql-md.md
deleted file mode 100644
index 4b57ddad132..00000000000
--- a/includes/tsql-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Transact-SQL
\ No newline at end of file
diff --git a/includes/vb-orcas-long-md.md b/includes/vb-orcas-long-md.md
deleted file mode 100644
index 5ea91318d24..00000000000
--- a/includes/vb-orcas-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Basic 2008
\ No newline at end of file
diff --git a/includes/vbprvbext-md.md b/includes/vbprvbext-md.md
deleted file mode 100644
index d2677871c70..00000000000
--- a/includes/vbprvbext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Visual Basic 2005
\ No newline at end of file
diff --git a/includes/vbprvblong-md.md b/includes/vbprvblong-md.md
deleted file mode 100644
index 34139d90424..00000000000
--- a/includes/vbprvblong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Basic 2005
\ No newline at end of file
diff --git a/includes/vbtecdlinq-md.md b/includes/vbtecdlinq-md.md
deleted file mode 100644
index 52781fca7e9..00000000000
--- a/includes/vbtecdlinq-md.md
+++ /dev/null
@@ -1 +0,0 @@
-LINQ to SQL
\ No newline at end of file
diff --git a/includes/vbteclinq-md.md b/includes/vbteclinq-md.md
deleted file mode 100644
index 28c6d25f691..00000000000
--- a/includes/vbteclinq-md.md
+++ /dev/null
@@ -1 +0,0 @@
-LINQ
\ No newline at end of file
diff --git a/includes/vbteclinqext-md.md b/includes/vbteclinqext-md.md
deleted file mode 100644
index 37f0a0f69df..00000000000
--- a/includes/vbteclinqext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Language-Integrated Query (LINQ)
\ No newline at end of file
diff --git a/includes/vcprvc-md.md b/includes/vcprvc-md.md
deleted file mode 100644
index c6d2435e98d..00000000000
--- a/includes/vcprvc-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual C++
\ No newline at end of file
diff --git a/includes/vcprvclong-md.md b/includes/vcprvclong-md.md
deleted file mode 100644
index ed8b3171d49..00000000000
--- a/includes/vcprvclong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual C++ 2005
\ No newline at end of file
diff --git a/includes/vs-dev10-long-md.md b/includes/vs-dev10-long-md.md
deleted file mode 100644
index eaf2ee2b1c2..00000000000
--- a/includes/vs-dev10-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Studio 2010
\ No newline at end of file
diff --git a/includes/vs-orcas-ext-md.md b/includes/vs-orcas-ext-md.md
deleted file mode 100644
index 9e6c99a9c07..00000000000
--- a/includes/vs-orcas-ext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Visual Studio 2008
\ No newline at end of file
diff --git a/includes/vs-orcas-long-md.md b/includes/vs-orcas-long-md.md
deleted file mode 100644
index 80f0fb84087..00000000000
--- a/includes/vs-orcas-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Studio 2008
\ No newline at end of file
diff --git a/includes/vs-ordesigner-long-md.md b/includes/vs-ordesigner-long-md.md
deleted file mode 100644
index 00424e0c8fe..00000000000
--- a/includes/vs-ordesigner-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Object Relational Designer
\ No newline at end of file
diff --git a/includes/vs-ordesigner-short-md.md b/includes/vs-ordesigner-short-md.md
deleted file mode 100644
index 8595f697c07..00000000000
--- a/includes/vs-ordesigner-short-md.md
+++ /dev/null
@@ -1 +0,0 @@
-O/R Designer
\ No newline at end of file
diff --git a/includes/vs2010-md.md b/includes/vs2010-md.md
deleted file mode 100644
index eaf2ee2b1c2..00000000000
--- a/includes/vs2010-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Studio 2010
\ No newline at end of file
diff --git a/includes/vsprvsext-md.md b/includes/vsprvsext-md.md
deleted file mode 100644
index aedf061c2e3..00000000000
--- a/includes/vsprvsext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Visual Studio 2005
\ No newline at end of file
diff --git a/includes/vsprvslong-md.md b/includes/vsprvslong-md.md
deleted file mode 100644
index 33fb76fddc1..00000000000
--- a/includes/vsprvslong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Studio 2005
\ No newline at end of file
diff --git a/includes/vstecado-md.md b/includes/vstecado-md.md
deleted file mode 100644
index 7b6552e6405..00000000000
--- a/includes/vstecado-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ADO.NET
\ No newline at end of file
diff --git a/includes/vstecasp-md.md b/includes/vstecasp-md.md
deleted file mode 100644
index f41705de76e..00000000000
--- a/includes/vstecasp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ASP.NET
\ No newline at end of file
diff --git a/includes/vstecasplong-md.md b/includes/vstecasplong-md.md
deleted file mode 100644
index 04bf8881097..00000000000
--- a/includes/vstecasplong-md.md
+++ /dev/null
@@ -1 +0,0 @@
-ASP.NET 2.0
\ No newline at end of file
diff --git a/includes/vstecmsbuild-md.md b/includes/vstecmsbuild-md.md
deleted file mode 100644
index 3ff1ea73f85..00000000000
--- a/includes/vstecmsbuild-md.md
+++ /dev/null
@@ -1 +0,0 @@
-MSBuild
\ No newline at end of file
diff --git a/includes/vwd-exp-dev10-long-md.md b/includes/vwd-exp-dev10-long-md.md
deleted file mode 100644
index deb193b53a6..00000000000
--- a/includes/vwd-exp-dev10-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Web Developer 2010 Express
\ No newline at end of file
diff --git a/includes/vwd-exp-orcas-long-md.md b/includes/vwd-exp-orcas-long-md.md
deleted file mode 100644
index 07cb50fb027..00000000000
--- a/includes/vwd-exp-orcas-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Web Developer 2008 Express Edition
\ No newline at end of file
diff --git a/includes/vwprvw-md.md b/includes/vwprvw-md.md
deleted file mode 100644
index fda902d1c55..00000000000
--- a/includes/vwprvw-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Web Developer
\ No newline at end of file
diff --git a/includes/wf1-md.md b/includes/wf1-md.md
deleted file mode 100644
index c99b2aafaa7..00000000000
--- a/includes/wf1-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WF
\ No newline at end of file
diff --git a/includes/wfd1-md.md b/includes/wfd1-md.md
deleted file mode 100644
index 133d69850a6..00000000000
--- a/includes/wfd1-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Workflow Designer
\ No newline at end of file
diff --git a/includes/wfd2-md.md b/includes/wfd2-md.md
deleted file mode 100644
index 0de80648538..00000000000
--- a/includes/wfd2-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Workflow Designer
\ No newline at end of file
diff --git a/includes/win2kfamily-md.md b/includes/win2kfamily-md.md
deleted file mode 100644
index e93c2ee2f25..00000000000
--- a/includes/win2kfamily-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 2000
\ No newline at end of file
diff --git a/includes/win7-md.md b/includes/win7-md.md
deleted file mode 100644
index 0bef53745cf..00000000000
--- a/includes/win7-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 7
\ No newline at end of file
diff --git a/includes/win8-appname-long-md.md b/includes/win8-appname-long-md.md
deleted file mode 100644
index 8bb01190c87..00000000000
--- a/includes/win8-appname-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 8.x Store
\ No newline at end of file
diff --git a/includes/win8-appstore-long-md.md b/includes/win8-appstore-long-md.md
deleted file mode 100644
index 6b3948f8c25..00000000000
--- a/includes/win8-appstore-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Store
\ No newline at end of file
diff --git a/includes/win8-md.md b/includes/win8-md.md
deleted file mode 100644
index f851b514732..00000000000
--- a/includes/win8-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 8
\ No newline at end of file
diff --git a/includes/win81-md.md b/includes/win81-md.md
deleted file mode 100644
index bcc2351f5f1..00000000000
--- a/includes/win81-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 8.1
\ No newline at end of file
diff --git a/includes/wince-md.md b/includes/wince-md.md
deleted file mode 100644
index a691fb6712b..00000000000
--- a/includes/wince-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Embedded CE
\ No newline at end of file
diff --git a/includes/windowsver-md.md b/includes/windowsver-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/windowsver-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/winnt4family-md.md b/includes/winnt4family-md.md
deleted file mode 100644
index 1c3e369f6d9..00000000000
--- a/includes/winnt4family-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows NT 4.0
\ No newline at end of file
diff --git a/includes/winxp-md.md b/includes/winxp-md.md
deleted file mode 100644
index 936c76a97d4..00000000000
--- a/includes/winxp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows XP
\ No newline at end of file
diff --git a/includes/winxpsvr-md.md b/includes/winxpsvr-md.md
deleted file mode 100644
index 5e9d928e681..00000000000
--- a/includes/winxpsvr-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Server 2003
\ No newline at end of file
diff --git a/includes/wiprlhext-md.md b/includes/wiprlhext-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/wiprlhext-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/wpfdesigner-current-long-md.md b/includes/wpfdesigner-current-long-md.md
deleted file mode 100644
index 82e1233fccc..00000000000
--- a/includes/wpfdesigner-current-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-WPF Designer for Visual Studio
\ No newline at end of file
diff --git a/includes/wrt-md.md b/includes/wrt-md.md
deleted file mode 100644
index 4e62e3076ab..00000000000
--- a/includes/wrt-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Runtime
\ No newline at end of file
diff --git a/includes/ws2003-md.md b/includes/ws2003-md.md
deleted file mode 100644
index 5e9d928e681..00000000000
--- a/includes/ws2003-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Server 2003
\ No newline at end of file
diff --git a/includes/wv-md.md b/includes/wv-md.md
deleted file mode 100644
index 394a749f72d..00000000000
--- a/includes/wv-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows Vista
\ No newline at end of file
diff --git a/includes/wxp-md.md b/includes/wxp-md.md
deleted file mode 100644
index 936c76a97d4..00000000000
--- a/includes/wxp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows XP
\ No newline at end of file
diff --git a/includes/wxpsp2-md.md b/includes/wxpsp2-md.md
deleted file mode 100644
index 04a512a7f73..00000000000
--- a/includes/wxpsp2-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows XP SP2
\ No newline at end of file
diff --git a/includes/xaml2009-md.md b/includes/xaml2009-md.md
deleted file mode 100644
index bfa2288600a..00000000000
--- a/includes/xaml2009-md.md
+++ /dev/null
@@ -1 +0,0 @@
-XAML2009
\ No newline at end of file

From 4f8af83cff580aa9169c69692bb5162de3766745 Mon Sep 17 00:00:00 2001
From: carlossanlop <carlossanlop@users.noreply.github.com>
Date: Wed, 24 Feb 2021 15:38:42 -0800
Subject: [PATCH 235/236] Deleting md files with no references

---
 includes/tla2sharptla-uisharpplural-md.md            | 1 -
 includes/tlasharptla-ms-md.md                        | 1 -
 includes/tlasharptla-netframewkattrsharpplural-md.md | 1 -
 includes/tlasharptla-winnetsvrfam-md.md              | 1 -
 includes/tlasharptla-winxp-md.md                     | 1 -
 includes/vs-dev11-long-md.md                         | 1 -
 includes/win2kserver-md.md                           | 1 -
 includes/winxppro-md.md                              | 1 -
 8 files changed, 8 deletions(-)
 delete mode 100644 includes/tla2sharptla-uisharpplural-md.md
 delete mode 100644 includes/tlasharptla-ms-md.md
 delete mode 100644 includes/tlasharptla-netframewkattrsharpplural-md.md
 delete mode 100644 includes/tlasharptla-winnetsvrfam-md.md
 delete mode 100644 includes/tlasharptla-winxp-md.md
 delete mode 100644 includes/vs-dev11-long-md.md
 delete mode 100644 includes/win2kserver-md.md
 delete mode 100644 includes/winxppro-md.md

diff --git a/includes/tla2sharptla-uisharpplural-md.md b/includes/tla2sharptla-uisharpplural-md.md
deleted file mode 100644
index e1a4e2447ab..00000000000
--- a/includes/tla2sharptla-uisharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-UIs
\ No newline at end of file
diff --git a/includes/tlasharptla-ms-md.md b/includes/tlasharptla-ms-md.md
deleted file mode 100644
index a04fcf98800..00000000000
--- a/includes/tlasharptla-ms-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft
\ No newline at end of file
diff --git a/includes/tlasharptla-netframewkattrsharpplural-md.md b/includes/tlasharptla-netframewkattrsharpplural-md.md
deleted file mode 100644
index 453dbfb6f67..00000000000
--- a/includes/tlasharptla-netframewkattrsharpplural-md.md
+++ /dev/null
@@ -1 +0,0 @@
-.NET Framework attributes
\ No newline at end of file
diff --git a/includes/tlasharptla-winnetsvrfam-md.md b/includes/tlasharptla-winnetsvrfam-md.md
deleted file mode 100644
index e20849463a2..00000000000
--- a/includes/tlasharptla-winnetsvrfam-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows Server 2003
\ No newline at end of file
diff --git a/includes/tlasharptla-winxp-md.md b/includes/tlasharptla-winxp-md.md
deleted file mode 100644
index e0723a78af5..00000000000
--- a/includes/tlasharptla-winxp-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Microsoft Windows XP
\ No newline at end of file
diff --git a/includes/vs-dev11-long-md.md b/includes/vs-dev11-long-md.md
deleted file mode 100644
index e42d5412a81..00000000000
--- a/includes/vs-dev11-long-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Visual Studio 2012
\ No newline at end of file
diff --git a/includes/win2kserver-md.md b/includes/win2kserver-md.md
deleted file mode 100644
index ce3432feecb..00000000000
--- a/includes/win2kserver-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows 2000 Server
\ No newline at end of file
diff --git a/includes/winxppro-md.md b/includes/winxppro-md.md
deleted file mode 100644
index 15f02f47fdc..00000000000
--- a/includes/winxppro-md.md
+++ /dev/null
@@ -1 +0,0 @@
-Windows XP Professional
\ No newline at end of file

From 22dd25d7a1bbeb4399757279a18bb9fc13577f81 Mon Sep 17 00:00:00 2001
From: Carlos Sanchez <1175054+carlossanlop@users.noreply.github.com>
Date: Thu, 25 Feb 2021 09:59:20 -0800
Subject: [PATCH 236/236] Apply suggestions from code review

Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
---
 xml/System.Xaml/XamlLanguage.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/xml/System.Xaml/XamlLanguage.xml b/xml/System.Xaml/XamlLanguage.xml
index 82d7aed84f6..520536d5b33 100644
--- a/xml/System.Xaml/XamlLanguage.xml
+++ b/xml/System.Xaml/XamlLanguage.xml
@@ -100,7 +100,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A factory method is a XAML2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The `Arguments` specify the input of a factory method and enable specifying that information in markup. The default techniques, in absence of a factory method, are to attempt to find a parameterless constructor and then attempt to find an identified type converter for type, member, or destination type.  
+ A factory method is a XAML 2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The `Arguments` specify the input of a factory method and enable specifying that information in markup. The default techniques, in absence of a factory method, are to attempt to find a parameterless constructor and then attempt to find an identified type converter for type, member, or destination type.  
   
  For the generic usage, the `Arguments` wrap the objects or initialization text of all construction inputs that are specified as necessary for the `TypeArguments`.  
   
@@ -160,7 +160,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- The `AsyncRecords` concept is part of XAML2009. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
+ The `AsyncRecords` concept is part of XAML 2009. For more information, see [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
   
  ]]></format>
         </remarks>
@@ -334,7 +334,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- This directive is part of XAML2009. See [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
+ This directive is part of XAML 2009. For more information, see [XAML 2009 Language Features](/dotnet/framework/xaml-services/xaml-2009-language-features).  
   
  ]]></format>
         </remarks>
@@ -501,7 +501,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- A factory method is a XAML2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The default technique, if a factory method is unavailable, is to try to find a parameterless constructor, and then try to find an identified type converter on type, member, or destination type.  
+ A factory method is a XAML 2009 feature for identifying an alternative technique that constructs the underlying type for a XAML type. The default technique, if a factory method is unavailable, is to try to find a parameterless constructor, and then try to find an identified type converter on type, member, or destination type.  
   
  ]]></format>
         </remarks>
@@ -973,7 +973,7 @@
           <format type="text/markdown"><![CDATA[  
   
 ## Remarks  
- `Reference` is a XAML2009 feature for referencing another object node in the markup. The implementation for .NET Framework XAML Services is found in <xref:System.Windows.Markup.Reference?displayProperty=nameWithType>.  
+ `Reference` is a XAML 2009 feature for referencing another object node in the markup. The implementation for .NET Framework XAML Services is found in <xref:System.Windows.Markup.Reference?displayProperty=nameWithType>.  
   
  ]]></format>
         </remarks>
